电脑蓝屏，求分析，已传DUMP文件

juechao2000

今天蓝屏两回了，求大神分析

woxihuan2011

UsbHub3.sys引发的0x44驱动程序错误蓝屏，你最近改动过驱动程序吗？

juechao2000

woxihuan2011 发表于 2015-1-28 20:12
UsbHub3.sys引发的0x44驱动程序错误蓝屏，你最近改动过驱动程序吗？

前几天新买了个鼠标，装了驱动程序，难道是这个原因

woxihuan2011

juechao2000 发表于 2015-1-28 20:20
前几天新买了个鼠标，装了驱动程序，难道是这个原因

把这个驱动程序卸载，用系统自带的试一试。

812534593

2L应该是用的bluescreenview查看的，显示是notskrnl.exe、Null.SYS和UsbHub2.sys造成的！
我用windbg看，认为也是驱动造成的！
相关信息如下：

1. 
   
2. *******************************************************************************
   
3. *                                                                             *
   
4. *                        Bugcheck Analysis                                    *
   
5. *                                                                             *
   
6. *******************************************************************************
   
7. 
   
8. Use !analyze -v to get detailed debugging information.
   
9. 
   
10. BugCheck 44, {ffffe000c0430b80, 1e8c, 0, 0}
    
11. 
    
12. Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+a03a )
    
13. 
    
14. Followup: MachineOwner
    
15. ---------
    
16. 
    
17. 2: kd> !analyze -v
    
18. *******************************************************************************
    
19. *                                                                             *
    
20. *                        Bugcheck Analysis                                    *
    
21. *                                                                             *
    
22. *******************************************************************************
    
23. 
    
24. MULTIPLE_IRP_COMPLETE_REQUESTS (44)
    
25. A driver has requested that an IRP be completed (IoCompleteRequest()), but
    
26. the packet has already been completed.  This is a tough bug to find because
    
27. the easiest case, a driver actually attempted to complete its own packet
    
28. twice, is generally not what happened.  Rather, two separate drivers each
    
29. believe that they own the packet, and each attempts to complete it.  The
    
30. first actually works, and the second fails.  Tracking down which drivers
    
31. in the system actually did this is difficult, generally because the trails
    
32. of the first driver have been covered by the second.  However, the driver
    
33. stack for the current request can be found by examining the DeviceObject
    
34. fields in each of the stack locations.
    
35. Arguments:
    
36. Arg1: ffffe000c0430b80, Address of the IRP
    
37. Arg2: 0000000000001e8c
    
38. Arg3: 0000000000000000
    
39. Arg4: 0000000000000000
    
40. 
    
41. Debugging Details:
    
42. ------------------
    
43. 
    
44. 
    
45. IRP_ADDRESS:  ffffe000c0430b80
    
46. 
    
47. FOLLOWUP_IP:
    
48. nt! ?? ::FNODOBFM::`string'+a03a
    
49. fffff801`4c1e4fea cc              int     3
    
50. 
    
51. CUSTOMER_CRASH_COUNT:  1
    
52. 
    
53. DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
54. 
    
55. BUGCHECK_STR:  0x44
    
56. 
    
57. PROCESS_NAME:  csrss.exe
    
58. 
    
59. CURRENT_IRQL:  1
    
60. 
    
61. LAST_CONTROL_TRANSFER:  from fffff8014c1e4fea to fffff8014c1caaa0
    
62. 
    
63. STACK_TEXT:  
    
64. ffffd000`2280e578 fffff801`4c1e4fea : 00000000`00000044 ffffe000`c0430b80 00000000`00001e8c 00000000`00000000 : nt!KeBugCheckEx
    
65. ffffd000`2280e580 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xa03a
    
66. 
    
67. 
    
68. STACK_COMMAND:  kb
    
69. 
    
70. SYMBOL_STACK_INDEX:  1
    
71. 
    
72. SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+a03a
    
73. 
    
74. FOLLOWUP_NAME:  MachineOwner
    
75. 
    
76. MODULE_NAME: nt
    
77. 
    
78. IMAGE_NAME:  ntkrnlmp.exe
    
79. 
    
80. DEBUG_FLR_IMAGE_TIMESTAMP:  545167e0
    
81. 
    
82. FAILURE_BUCKET_ID:  X64_0x44_nt!_??_::FNODOBFM::_string_+a03a
    
83. 
    
84. BUCKET_ID:  X64_0x44_nt!_??_::FNODOBFM::_string_+a03a
    
85. 
    
86. Followup: MachineOwner
    
87. ---------
    

复制代码