API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Mar 22nd, 2012
104
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 15.00 KB | None | 0 0
raw download clone embed print report
  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 [C:\*\032212-19125-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  9. Symbol search path is: *** Invalid ***
  10. ****************************************************************************
  11. * Symbol loading may be unreliable without a symbol search path. *
  12. * Use .symfix to have the debugger choose a symbol path. *
  13. * After setting your symbol path, use .reload to refresh symbol locations. *
  14. ****************************************************************************
  15. Executable search path is:
  16. *********************************************************************
  17. * Symbols can not be loaded because symbol path is not initialized. *
  18. * *
  19. * The Symbol Path can be set by: *
  20. * using the _NT_SYMBOL_PATH environment variable. *
  21. * using the -y <symbol_path> argument when starting the debugger. *
  22. * using .sympath and .sympath+ *
  23. *********************************************************************
  24. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  25. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  26. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  27. Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
  28. Product: WinNt, suite: TerminalServer SingleUserTS
  29. Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
  30. Machine Name:
  31. Kernel base = 0xfffff800`03000000 PsLoadedModuleList = 0xfffff800`03244650
  32. Debug session time: Thu Mar 22 00:24:52.663 2012 (UTC + 1:00)
  33. System Uptime: 0 days 0:40:56.036
  34. *********************************************************************
  35. * Symbols can not be loaded because symbol path is not initialized. *
  36. * *
  37. * The Symbol Path can be set by: *
  38. * using the _NT_SYMBOL_PATH environment variable. *
  39. * using the -y <symbol_path> argument when starting the debugger. *
  40. * using .sympath and .sympath+ *
  41. *********************************************************************
  42. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  43. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  44. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  45. Loading Kernel Symbols
  46. ...............................................................
  47. ................................................................
  48. ....................................................
  49. Loading User Symbols
  50. Loading unloaded module list
  51. ......
  52. Unable to load image \SystemRoot\system32\drivers\NETIO.SYS, Win32 error 0n2
  53. *** WARNING: Unable to verify timestamp for NETIO.SYS
  54. *** ERROR: Module load completed but symbols could not be loaded for NETIO.SYS
  55. ERROR: FindPlugIns 8007007b
  56. *******************************************************************************
  57. * *
  58. * Bugcheck Analysis *
  59. * *
  60. *******************************************************************************
  61.  
  62. Use !analyze -v to get detailed debugging information.
  63.  
  64. BugCheck 1000007E, {ffffffffc0000005, fffff880015377ba, fffff880031af6d8, fffff880031aef30}
  65.  
  66. *** WARNING: Unable to verify timestamp for mssmbios.sys
  67. *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
  68. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  69.  
  70. *************************************************************************
  71. *** ***
  72. *** ***
  73. *** Your debugger is not using the correct symbols ***
  74. *** ***
  75. *** In order for this command to work properly, your symbol path ***
  76. *** must point to .pdb files that have full type information. ***
  77. *** ***
  78. *** Certain .pdb files (such as the public OS symbols) do not ***
  79. *** contain the required information. Contact the group that ***
  80. *** provided you with these symbols if you need this command to ***
  81. *** work. ***
  82. *** ***
  83. *** Type referenced: nt!_KPRCB ***
  84. *** ***
  85. *************************************************************************
  86. *************************************************************************
  87. *** ***
  88. *** ***
  89. *** Your debugger is not using the correct symbols ***
  90. *** ***
  91. *** In order for this command to work properly, your symbol path ***
  92. *** must point to .pdb files that have full type information. ***
  93. *** ***
  94. *** Certain .pdb files (such as the public OS symbols) do not ***
  95. *** contain the required information. Contact the group that ***
  96. *** provided you with these symbols if you need this command to ***
  97. *** work. ***
  98. *** ***
  99. *** Type referenced: nt!_KPRCB ***
  100. *** ***
  101. *************************************************************************
  102. *************************************************************************
  103. *** ***
  104. *** ***
  105. *** Your debugger is not using the correct symbols ***
  106. *** ***
  107. *** In order for this command to work properly, your symbol path ***
  108. *** must point to .pdb files that have full type information. ***
  109. *** ***
  110. *** Certain .pdb files (such as the public OS symbols) do not ***
  111. *** contain the required information. Contact the group that ***
  112. *** provided you with these symbols if you need this command to ***
  113. *** work. ***
  114. *** ***
  115. *** Type referenced: nt!_KPRCB ***
  116. *** ***
  117. *************************************************************************
  118. Probably caused by : NETIO.SYS ( NETIO+117ba )
  119.  
  120. Followup: MachineOwner
  121. ---------
  122.  
  123. 0: kd> !analyze -v
  124. ERROR: FindPlugIns 8007007b
  125. *******************************************************************************
  126. * *
  127. * Bugcheck Analysis *
  128. * *
  129. *******************************************************************************
  130.  
  131. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
  132. This is a very common bugcheck. Usually the exception address pinpoints
  133. the driver/function that caused the problem. Always note this address
  134. as well as the link date of the driver/image that contains this address.
  135. Some common problems are exception code 0x80000003. This means a hard
  136. coded breakpoint or assertion was hit, but this system was booted
  137. /NODEBUG. This is not supposed to happen as developers should never have
  138. hardcoded breakpoints in retail code, but ...
  139. If this happens, make sure a debugger gets connected, and the
  140. system is booted /DEBUG. This will let us see why this breakpoint is
  141. happening.
  142. Arguments:
  143. Arg1: ffffffffc0000005, The exception code that was not handled
  144. Arg2: fffff880015377ba, The address that the exception occurred at
  145. Arg3: fffff880031af6d8, Exception Record Address
  146. Arg4: fffff880031aef30, Context Record Address
  147.  
  148. Debugging Details:
  149. ------------------
  150.  
  151. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  152.  
  153. *************************************************************************
  154. *** ***
  155. *** ***
  156. *** Your debugger is not using the correct symbols ***
  157. *** ***
  158. *** In order for this command to work properly, your symbol path ***
  159. *** must point to .pdb files that have full type information. ***
  160. *** ***
  161. *** Certain .pdb files (such as the public OS symbols) do not ***
  162. *** contain the required information. Contact the group that ***
  163. *** provided you with these symbols if you need this command to ***
  164. *** work. ***
  165. *** ***
  166. *** Type referenced: nt!_KPRCB ***
  167. *** ***
  168. *************************************************************************
  169. *************************************************************************
  170. *** ***
  171. *** ***
  172. *** Your debugger is not using the correct symbols ***
  173. *** ***
  174. *** In order for this command to work properly, your symbol path ***
  175. *** must point to .pdb files that have full type information. ***
  176. *** ***
  177. *** Certain .pdb files (such as the public OS symbols) do not ***
  178. *** contain the required information. Contact the group that ***
  179. *** provided you with these symbols if you need this command to ***
  180. *** work. ***
  181. *** ***
  182. *** Type referenced: nt!_KPRCB ***
  183. *** ***
  184. *************************************************************************
  185. *************************************************************************
  186. *** ***
  187. *** ***
  188. *** Your debugger is not using the correct symbols ***
  189. *** ***
  190. *** In order for this command to work properly, your symbol path ***
  191. *** must point to .pdb files that have full type information. ***
  192. *** ***
  193. *** Certain .pdb files (such as the public OS symbols) do not ***
  194. *** contain the required information. Contact the group that ***
  195. *** provided you with these symbols if you need this command to ***
  196. *** work. ***
  197. *** ***
  198. *** Type referenced: nt!_KPRCB ***
  199. *** ***
  200. *************************************************************************
  201.  
  202. ADDITIONAL_DEBUG_TEXT:
  203. Use '!findthebuild' command to search for the target build information.
  204. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
  205.  
  206. MODULE_NAME: NETIO
  207.  
  208. FAULTING_MODULE: fffff80003000000 nt
  209.  
  210. DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79381
  211.  
  212. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
  213.  
  214. FAULTING_IP:
  215. NETIO+117ba
  216. fffff880`015377ba 488b01 mov rax,qword ptr [rcx]
  217.  
  218. EXCEPTION_RECORD: fffff880031af6d8 -- (.exr 0xfffff880031af6d8)
  219. ExceptionAddress: fffff880015377ba (NETIO+0x00000000000117ba)
  220. ExceptionCode: c0000005 (Access violation)
  221. ExceptionFlags: 00000000
  222. NumberParameters: 2
  223. Parameter[0]: 0000000000000000
  224. Parameter[1]: 0000000000000000
  225. Attempt to read from address 0000000000000000
  226.  
  227. CONTEXT: fffff880031aef30 -- (.cxr 0xfffff880031aef30)
  228. rax=fffffa800a457920 rbx=fffffa80074b7a90 rcx=0000000000000000
  229. rdx=0000000000001000 rsi=00000000ffffff87 rdi=fffff880031af900
  230. rip=fffff880015377ba rsp=fffff880031af910 rbp=fffffa8008a2b000
  231. r8=fffff78000000320 r9=0000000000000002 r10=fffff800031f2b80
  232. r11=fffffa800712e7a0 r12=0000000000000000 r13=0000000000000000
  233. r14=0000000000000000 r15=0000000000000000
  234. iopl=0 nv up ei ng nz na po nc
  235. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
  236. NETIO+0x117ba:
  237. fffff880`015377ba 488b01 mov rax,qword ptr [rcx] ds:002b:00000000`00000000=????????????????
  238. Resetting default scope
  239.  
  240. CUSTOMER_CRASH_COUNT: 1
  241.  
  242. DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
  243.  
  244. BUGCHECK_STR: 0x7E
  245.  
  246. CURRENT_IRQL: 0
  247.  
  248. LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880015377ba
  249.  
  250. STACK_TEXT:
  251. fffff880`031af910 00000000`00000000 : fffff880`0182a7c2 fffffa80`206c644d fffff880`01533e21 fffffa80`07b7b700 : NETIO+0x117ba
  252.  
  253.  
  254. FOLLOWUP_IP:
  255. NETIO+117ba
  256. fffff880`015377ba 488b01 mov rax,qword ptr [rcx]
  257.  
  258. SYMBOL_STACK_INDEX: 0
  259.  
  260. SYMBOL_NAME: NETIO+117ba
  261.  
  262. FOLLOWUP_NAME: MachineOwner
  263.  
  264. IMAGE_NAME: NETIO.SYS
  265.  
  266. STACK_COMMAND: .cxr 0xfffff880031aef30 ; kb
  267.  
  268. BUCKET_ID: WRONG_SYMBOLS
  269.  
  270. Followup: MachineOwner
  271. ---------
  272.  
  273. 0: kd> lmvm NETIO
  274. start end module name
  275. fffff880`01526000 fffff880`01586000 NETIO T (no symbols)
  276. Loaded symbol image file: NETIO.SYS
  277. Image path: \SystemRoot\system32\drivers\NETIO.SYS
  278. Image name: NETIO.SYS
  279. Timestamp: Sat Nov 20 10:23:13 2010 (4CE79381)
  280. CheckSum: 00066D17
  281. ImageSize: 00060000
  282. Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!