API tools faq
paste
Disconsented

Untitled

Disconsented
Jul 8th, 2013
176
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 14.53 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:\Users\James\Downloads\070813-29936-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 (8 procs) Free x64
  28. Product: WinNt, suite: TerminalServer SingleUserTS
  29. Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
  30. Machine Name:
  31. Kernel base = 0xfffff800`02c54000 PsLoadedModuleList = 0xfffff800`02e97670
  32. Debug session time: Mon Jul 8 18:15:27.179 2013 (UTC + 12:00)
  33. System Uptime: 0 days 0:00:26.053
  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\igdpmd64.sys, Win32 error 0n2
  53. *** WARNING: Unable to verify timestamp for igdpmd64.sys
  54. *** ERROR: Module load completed but symbols could not be loaded for igdpmd64.sys
  55. *******************************************************************************
  56. * *
  57. * Bugcheck Analysis *
  58. * *
  59. *******************************************************************************
  60.  
  61. Use !analyze -v to get detailed debugging information.
  62.  
  63. BugCheck 1000007E, {ffffffffc0000005, fffff8800804efb4, fffff8800335a818, fffff8800335a070}
  64.  
  65. *** WARNING: Unable to verify timestamp for mssmbios.sys
  66. *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
  67. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  68.  
  69. *************************************************************************
  70. *** ***
  71. *** ***
  72. *** Your debugger is not using the correct symbols ***
  73. *** ***
  74. *** In order for this command to work properly, your symbol path ***
  75. *** must point to .pdb files that have full type information. ***
  76. *** ***
  77. *** Certain .pdb files (such as the public OS symbols) do not ***
  78. *** contain the required information. Contact the group that ***
  79. *** provided you with these symbols if you need this command to ***
  80. *** work. ***
  81. *** ***
  82. *** Type referenced: nt!_KPRCB ***
  83. *** ***
  84. *************************************************************************
  85. *************************************************************************
  86. *** ***
  87. *** ***
  88. *** Your debugger is not using the correct symbols ***
  89. *** ***
  90. *** In order for this command to work properly, your symbol path ***
  91. *** must point to .pdb files that have full type information. ***
  92. *** ***
  93. *** Certain .pdb files (such as the public OS symbols) do not ***
  94. *** contain the required information. Contact the group that ***
  95. *** provided you with these symbols if you need this command to ***
  96. *** work. ***
  97. *** ***
  98. *** Type referenced: nt!_KPRCB ***
  99. *** ***
  100. *************************************************************************
  101. *************************************************************************
  102. *** ***
  103. *** ***
  104. *** Your debugger is not using the correct symbols ***
  105. *** ***
  106. *** In order for this command to work properly, your symbol path ***
  107. *** must point to .pdb files that have full type information. ***
  108. *** ***
  109. *** Certain .pdb files (such as the public OS symbols) do not ***
  110. *** contain the required information. Contact the group that ***
  111. *** provided you with these symbols if you need this command to ***
  112. *** work. ***
  113. *** ***
  114. *** Type referenced: nt!_KPRCB ***
  115. *** ***
  116. *************************************************************************
  117. Probably caused by : igdpmd64.sys ( igdpmd64+36fb4 )
  118.  
  119. Followup: MachineOwner
  120. ---------
  121.  
  122. 4: kd> !analyze -v
  123. *******************************************************************************
  124. * *
  125. * Bugcheck Analysis *
  126. * *
  127. *******************************************************************************
  128.  
  129. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
  130. This is a very common bugcheck. Usually the exception address pinpoints
  131. the driver/function that caused the problem. Always note this address
  132. as well as the link date of the driver/image that contains this address.
  133. Some common problems are exception code 0x80000003. This means a hard
  134. coded breakpoint or assertion was hit, but this system was booted
  135. /NODEBUG. This is not supposed to happen as developers should never have
  136. hardcoded breakpoints in retail code, but ...
  137. If this happens, make sure a debugger gets connected, and the
  138. system is booted /DEBUG. This will let us see why this breakpoint is
  139. happening.
  140. Arguments:
  141. Arg1: ffffffffc0000005, The exception code that was not handled
  142. Arg2: fffff8800804efb4, The address that the exception occurred at
  143. Arg3: fffff8800335a818, Exception Record Address
  144. Arg4: fffff8800335a070, Context Record Address
  145.  
  146. Debugging Details:
  147. ------------------
  148.  
  149. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  150.  
  151. *************************************************************************
  152. *** ***
  153. *** ***
  154. *** Your debugger is not using the correct symbols ***
  155. *** ***
  156. *** In order for this command to work properly, your symbol path ***
  157. *** must point to .pdb files that have full type information. ***
  158. *** ***
  159. *** Certain .pdb files (such as the public OS symbols) do not ***
  160. *** contain the required information. Contact the group that ***
  161. *** provided you with these symbols if you need this command to ***
  162. *** work. ***
  163. *** ***
  164. *** Type referenced: nt!_KPRCB ***
  165. *** ***
  166. *************************************************************************
  167. *************************************************************************
  168. *** ***
  169. *** ***
  170. *** Your debugger is not using the correct symbols ***
  171. *** ***
  172. *** In order for this command to work properly, your symbol path ***
  173. *** must point to .pdb files that have full type information. ***
  174. *** ***
  175. *** Certain .pdb files (such as the public OS symbols) do not ***
  176. *** contain the required information. Contact the group that ***
  177. *** provided you with these symbols if you need this command to ***
  178. *** work. ***
  179. *** ***
  180. *** Type referenced: nt!_KPRCB ***
  181. *** ***
  182. *************************************************************************
  183. *************************************************************************
  184. *** ***
  185. *** ***
  186. *** Your debugger is not using the correct symbols ***
  187. *** ***
  188. *** In order for this command to work properly, your symbol path ***
  189. *** must point to .pdb files that have full type information. ***
  190. *** ***
  191. *** Certain .pdb files (such as the public OS symbols) do not ***
  192. *** contain the required information. Contact the group that ***
  193. *** provided you with these symbols if you need this command to ***
  194. *** work. ***
  195. *** ***
  196. *** Type referenced: nt!_KPRCB ***
  197. *** ***
  198. *************************************************************************
  199.  
  200. ADDITIONAL_DEBUG_TEXT:
  201. Use '!findthebuild' command to search for the target build information.
  202. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
  203.  
  204. FAULTING_MODULE: fffff80002c54000 nt
  205.  
  206. DEBUG_FLR_IMAGE_TIMESTAMP: 4e4152eb
  207.  
  208. EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
  209.  
  210. FAULTING_IP:
  211. igdpmd64+36fb4
  212. fffff880`0804efb4 ff5070 call qword ptr [rax+70h]
  213.  
  214. EXCEPTION_RECORD: fffff8800335a818 -- (.exr 0xfffff8800335a818)
  215. ExceptionAddress: fffff8800804efb4 (igdpmd64+0x0000000000036fb4)
  216. ExceptionCode: c0000005 (Access violation)
  217. ExceptionFlags: 00000000
  218. NumberParameters: 2
  219. Parameter[0]: 0000000000000000
  220. Parameter[1]: 00000000001f458e
  221. Attempt to read from address 00000000001f458e
  222.  
  223. CONTEXT: fffff8800335a070 -- (.cxr 0xfffff8800335a070)
  224. rax=00000000001f451e rbx=fffff8800335aaa0 rcx=fffffa8008feb180
  225. rdx=b40031ce2807aabd rsi=fffffa8008feb180 rdi=00000000c00000bb
  226. rip=fffff8800804efb4 rsp=fffff8800335aa50 rbp=fffff88008018000
  227. r8=46fbb3f9fde5bba4 r9=0000000000000000 r10=0000000000000018
  228. r11=fffff8800335aac8 r12=0000000000000001 r13=fffffa800a079130
  229. r14=fffffa800904b190 r15=0000000000000038
  230. iopl=0 nv up ei pl nz na po nc
  231. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
  232. igdpmd64+0x36fb4:
  233. fffff880`0804efb4 ff5070 call qword ptr [rax+70h] ds:002b:00000000`001f458e=????????????????
  234. Resetting default scope
  235.  
  236. CUSTOMER_CRASH_COUNT: 1
  237.  
  238. DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
  239.  
  240. BUGCHECK_STR: 0x7E
  241.  
  242. CURRENT_IRQL: 0
  243.  
  244. LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800804efb4
  245.  
  246. STACK_TEXT:
  247. fffff880`0335aa50 00000000`00000000 : fffffa80`0a2d5000 fffff880`0335aa90 fffff880`06d5d9e7 fffffa80`09170d40 : igdpmd64+0x36fb4
  248.  
  249.  
  250. FOLLOWUP_IP:
  251. igdpmd64+36fb4
  252. fffff880`0804efb4 ff5070 call qword ptr [rax+70h]
  253.  
  254. SYMBOL_STACK_INDEX: 0
  255.  
  256. SYMBOL_NAME: igdpmd64+36fb4
  257.  
  258. FOLLOWUP_NAME: MachineOwner
  259.  
  260. MODULE_NAME: igdpmd64
  261.  
  262. IMAGE_NAME: igdpmd64.sys
  263.  
  264. STACK_COMMAND: .cxr 0xfffff8800335a070 ; kb
  265.  
  266. BUCKET_ID: WRONG_SYMBOLS
  267.  
  268. Followup: MachineOwner
  269. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
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!