Advertisement
chenshaoju

BODS when sleep Wdf01000.sys

Jan 18th, 2013
304
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.12 KB | None | 0 0
  1.  
  2. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [D:\My Documents\Desktop\011813-28548-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  9. Symbol search path is: srv*D:\symbols\*http://msdl.microsoft.com/download/symbols
  10. Executable search path is:
  11. Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
  12. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  13. Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
  14. Machine Name:
  15. Kernel base = 0xfffff800`0465e000 PsLoadedModuleList = 0xfffff800`048a2670
  16. Debug session time: Fri Jan 18 17:23:59.661 2013 (UTC + 8:00)
  17. System Uptime: 5 days 0:39:29.933
  18. Loading Kernel Symbols
  19. ...............................................................
  20. ................................................................
  21. ..........................................................
  22. Loading User Symbols
  23. Loading unloaded module list
  24. ..................................................
  25. 3: kd> !analyze -v
  26. *******************************************************************************
  27. * *
  28. * Bugcheck Analysis *
  29. * *
  30. *******************************************************************************
  31.  
  32. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
  33. This is a very common bugcheck. Usually the exception address pinpoints
  34. the driver/function that caused the problem. Always note this address
  35. as well as the link date of the driver/image that contains this address.
  36. Some common problems are exception code 0x80000003. This means a hard
  37. coded breakpoint or assertion was hit, but this system was booted
  38. /NODEBUG. This is not supposed to happen as developers should never have
  39. hardcoded breakpoints in retail code, but ...
  40. If this happens, make sure a debugger gets connected, and the
  41. system is booted /DEBUG. This will let us see why this breakpoint is
  42. happening.
  43. Arguments:
  44. Arg1: ffffffff80000003, The exception code that was not handled
  45. Arg2: fffff800046d4dd0, The address that the exception occurred at
  46. Arg3: fffff88004fdfbe8, Exception Record Address
  47. Arg4: fffff88004fdf440, Context Record Address
  48.  
  49. Debugging Details:
  50. ------------------
  51.  
  52.  
  53. EXCEPTION_CODE: (NTSTATUS) 0x80000003 (2147483651) - {
  54.  
  55. FAULTING_IP:
  56. nt!DbgBreakPoint+0
  57. fffff800`046d4dd0 cc int 3
  58.  
  59. EXCEPTION_RECORD: fffff88004fdfbe8 -- (.exr 0xfffff88004fdfbe8)
  60. ExceptionAddress: fffff800046d4dd0 (nt!DbgBreakPoint)
  61. ExceptionCode: 80000003 (Break instruction exception)
  62. ExceptionFlags: 00000000
  63. NumberParameters: 1
  64. Parameter[0]: 0000000000000000
  65.  
  66. CONTEXT: fffff88004fdf440 -- (.cxr 0xfffff88004fdf440)
  67. rax=0000000000000000 rbx=fffffa800718c8b0 rcx=1f22ee23a0cc0000
  68. rdx=0000000000000008 rsi=0000057ff2dc4f78 rdi=fffffa800d23b3c0
  69. rip=fffff800046d4dd0 rsp=fffff88004fdfe28 rbp=fffff88000e7de50
  70. r8=0000000000000001 r9=fffff8000471a420 r10=0000000000000080
  71. r11=fffff88004fdfe28 r12=0000000000000001 r13=0000000000000000
  72. r14=fffffa800d23b3c0 r15=0000000000000000
  73. iopl=0 nv up ei pl nz na pe nc
  74. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000202
  75. nt!DbgBreakPoint:
  76. fffff800`046d4dd0 cc int 3
  77. Resetting default scope
  78.  
  79. CUSTOMER_CRASH_COUNT: 1
  80.  
  81. DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
  82.  
  83. BUGCHECK_STR: 0x7E
  84.  
  85. PROCESS_NAME: System
  86.  
  87. CURRENT_IRQL: 0
  88.  
  89. ERROR_CODE: (NTSTATUS) 0x80000003 - {
  90.  
  91. EXCEPTION_PARAMETER1: 0000000000000000
  92.  
  93. LAST_CONTROL_TRANSFER: from fffff88000e96028 to fffff800046d4dd0
  94.  
  95. STACK_TEXT:
  96. fffff880`04fdfe28 fffff880`00e96028 : fffff880`00e7db70 fffffa80`06a1eb50 fffff880`00e7de50 0000057f`f2dc4f78 : nt!DbgBreakPoint
  97. fffff880`04fdfe30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70
  98.  
  99.  
  100. FOLLOWUP_IP:
  101. Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
  102. fffff880`00e96028 488b442440 mov rax,qword ptr [rsp+40h]
  103.  
  104. SYMBOL_STACK_INDEX: 1
  105.  
  106. SYMBOL_NAME: Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
  107.  
  108. FOLLOWUP_NAME: MachineOwner
  109.  
  110. MODULE_NAME: Wdf01000
  111.  
  112. IMAGE_NAME: Wdf01000.sys
  113.  
  114. DEBUG_FLR_IMAGE_TIMESTAMP: 5010aa89
  115.  
  116. STACK_COMMAND: .cxr 0xfffff88004fdf440 ; kb
  117.  
  118. FAILURE_BUCKET_ID: X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
  119.  
  120. BUCKET_ID: X64_0x7E_Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+70
  121.  
  122. Followup: MachineOwner
  123. ---------
  124.  
  125. 3: kd> .ecxr
  126. Unable to get exception context, HRESULT 0x8000FFFF
  127. 3: kd> kb
  128. RetAddr : Args to Child : Call Site
  129. fffff880`00e96028 : fffff880`00e7db70 fffffa80`06a1eb50 fffff880`00e7de50 0000057f`f2dc4f78 : nt!DbgBreakPoint
  130. 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70
  131. 3: kd> dv
  132. Unable to enumerate locals, HRESULT 0x80004005
  133. Private symbols (symbols.pri) are required for locals.
  134. Type ".hh dbgerr005" for details.
  135. 3: kd> lmvm Wdf01000
  136. start end module name
  137. fffff880`00e7a000 fffff880`00f3c000 Wdf01000 (pdb symbols) d:\symbols\Wdf01000.pdb\FABEC58794454D0D9B539B58E2D0A0922\Wdf01000.pdb
  138. Loaded symbol image file: Wdf01000.sys
  139. Mapped memory image file: d:\symbols\Wdf01000.sys\5010AA89c2000\Wdf01000.sys
  140. Image path: \SystemRoot\system32\drivers\Wdf01000.sys
  141. Image name: Wdf01000.sys
  142. Timestamp: Thu Jul 26 10:25:13 2012 (5010AA89)
  143. CheckSum: 000CDBF1
  144. ImageSize: 000C2000
  145. File version: 1.11.9200.16384
  146. Product version: 1.11.9200.16384
  147. File flags: 0 (Mask 3F)
  148. File OS: 40004 NT Win32
  149. File type: 3.7 Driver
  150. File date: 00000000.00000000
  151. Translations: 0409.04b0
  152. CompanyName: Microsoft Corporation
  153. ProductName: Microsoft® Windows® Operating System
  154. InternalName: wdf01000.sys
  155. OriginalFilename: wdf01000.sys
  156. ProductVersion: 1.11.9200.16384
  157. FileVersion: 1.11.9200.16384 (win8_rtm.120725-1247)
  158. FileDescription: Kernel Mode Driver Framework Runtime
  159. LegalCopyright: © Microsoft Corporation. All rights reserved.
  160. 3: kd> .exr 0xfffff88004fdfbe8
  161. ExceptionAddress: fffff800046d4dd0 (nt!DbgBreakPoint)
  162. ExceptionCode: 80000003 (Break instruction exception)
  163. ExceptionFlags: 00000000
  164. NumberParameters: 1
  165. Parameter[0]: 0000000000000000
  166. 3: kd> .cxr 0xfffff88004fdf440
  167. rax=0000000000000000 rbx=fffffa800718c8b0 rcx=1f22ee23a0cc0000
  168. rdx=0000000000000008 rsi=0000057ff2dc4f78 rdi=fffffa800d23b3c0
  169. rip=fffff800046d4dd0 rsp=fffff88004fdfe28 rbp=fffff88000e7de50
  170. r8=0000000000000001 r9=fffff8000471a420 r10=0000000000000080
  171. r11=fffff88004fdfe28 r12=0000000000000001 r13=0000000000000000
  172. r14=fffffa800d23b3c0 r15=0000000000000000
  173. iopl=0 nv up ei pl nz na pe nc
  174. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000202
  175. nt!DbgBreakPoint:
  176. fffff800`046d4dd0 cc int 3
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement