API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Mar 23rd, 2014
199
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 15.19 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\jon\Desktop\032314-21216-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 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. Machine Name:
  30. Kernel base = 0xfffff800`01c5a000 PsLoadedModuleList = 0xfffff800`01e9d6d0
  31. Debug session time: Sun Mar 23 21:05:59.693 2014 (UTC + 0:00)
  32. System Uptime: 0 days 0:00:07.396
  33. *********************************************************************
  34. * Symbols can not be loaded because symbol path is not initialized. *
  35. * *
  36. * The Symbol Path can be set by: *
  37. * using the _NT_SYMBOL_PATH environment variable. *
  38. * using the -y <symbol_path> argument when starting the debugger. *
  39. * using .sympath and .sympath+ *
  40. *********************************************************************
  41. Unable to load image ntoskrnl.exe, Win32 error 0n2
  42. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  43. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  44. Loading Kernel Symbols
  45. ..................................................
  46. Loading User Symbols
  47. Mini Kernel Dump does not contain unloaded driver list
  48. *******************************************************************************
  49. * *
  50. * Bugcheck Analysis *
  51. * *
  52. *******************************************************************************
  53.  
  54. Use !analyze -v to get detailed debugging information.
  55.  
  56. BugCheck 124, {0, fffffa8007766038, 0, 0}
  57.  
  58. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  59.  
  60. *************************************************************************
  61. *** ***
  62. *** ***
  63. *** Your debugger is not using the correct symbols ***
  64. *** ***
  65. *** In order for this command to work properly, your symbol path ***
  66. *** must point to .pdb files that have full type information. ***
  67. *** ***
  68. *** Certain .pdb files (such as the public OS symbols) do not ***
  69. *** contain the required information. Contact the group that ***
  70. *** provided you with these symbols if you need this command to ***
  71. *** work. ***
  72. *** ***
  73. *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
  74. *** ***
  75. *************************************************************************
  76. *************************************************************************
  77. *** ***
  78. *** ***
  79. *** Your debugger is not using the correct symbols ***
  80. *** ***
  81. *** In order for this command to work properly, your symbol path ***
  82. *** must point to .pdb files that have full type information. ***
  83. *** ***
  84. *** Certain .pdb files (such as the public OS symbols) do not ***
  85. *** contain the required information. Contact the group that ***
  86. *** provided you with these symbols if you need this command to ***
  87. *** work. ***
  88. *** ***
  89. *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
  90. *** ***
  91. *************************************************************************
  92. Unable to load image PSHED.dll, Win32 error 0n2
  93. *** WARNING: Unable to verify timestamp for PSHED.dll
  94. *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
  95. *************************************************************************
  96. *** ***
  97. *** ***
  98. *** Your debugger is not using the correct symbols ***
  99. *** ***
  100. *** In order for this command to work properly, your symbol path ***
  101. *** must point to .pdb files that have full type information. ***
  102. *** ***
  103. *** Certain .pdb files (such as the public OS symbols) do not ***
  104. *** contain the required information. Contact the group that ***
  105. *** provided you with these symbols if you need this command to ***
  106. *** work. ***
  107. *** ***
  108. *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
  109. *** ***
  110. *************************************************************************
  111. *************************************************************************
  112. *** ***
  113. *** ***
  114. *** Your debugger is not using the correct symbols ***
  115. *** ***
  116. *** In order for this command to work properly, your symbol path ***
  117. *** must point to .pdb files that have full type information. ***
  118. *** ***
  119. *** Certain .pdb files (such as the public OS symbols) do not ***
  120. *** contain the required information. Contact the group that ***
  121. *** provided you with these symbols if you need this command to ***
  122. *** work. ***
  123. *** ***
  124. *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
  125. *** ***
  126. *************************************************************************
  127. *************************************************************************
  128. *** ***
  129. *** ***
  130. *** Your debugger is not using the correct symbols ***
  131. *** ***
  132. *** In order for this command to work properly, your symbol path ***
  133. *** must point to .pdb files that have full type information. ***
  134. *** ***
  135. *** Certain .pdb files (such as the public OS symbols) do not ***
  136. *** contain the required information. Contact the group that ***
  137. *** provided you with these symbols if you need this command to ***
  138. *** work. ***
  139. *** ***
  140. *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
  141. *** ***
  142. *************************************************************************
  143. *************************************************************************
  144. *** ***
  145. *** ***
  146. *** Your debugger is not using the correct symbols ***
  147. *** ***
  148. *** In order for this command to work properly, your symbol path ***
  149. *** must point to .pdb files that have full type information. ***
  150. *** ***
  151. *** Certain .pdb files (such as the public OS symbols) do not ***
  152. *** contain the required information. Contact the group that ***
  153. *** provided you with these symbols if you need this command to ***
  154. *** work. ***
  155. *** ***
  156. *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
  157. *** ***
  158. *************************************************************************
  159. *************************************************************************
  160. *** ***
  161. *** ***
  162. *** Your debugger is not using the correct symbols ***
  163. *** ***
  164. *** In order for this command to work properly, your symbol path ***
  165. *** must point to .pdb files that have full type information. ***
  166. *** ***
  167. *** Certain .pdb files (such as the public OS symbols) do not ***
  168. *** contain the required information. Contact the group that ***
  169. *** provided you with these symbols if you need this command to ***
  170. *** work. ***
  171. *** ***
  172. *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
  173. *** ***
  174. *************************************************************************
  175. *************************************************************************
  176. *** ***
  177. *** ***
  178. *** Your debugger is not using the correct symbols ***
  179. *** ***
  180. *** In order for this command to work properly, your symbol path ***
  181. *** must point to .pdb files that have full type information. ***
  182. *** ***
  183. *** Certain .pdb files (such as the public OS symbols) do not ***
  184. *** contain the required information. Contact the group that ***
  185. *** provided you with these symbols if you need this command to ***
  186. *** work. ***
  187. *** ***
  188. *** Type referenced: nt!_KPRCB ***
  189. *** ***
  190. *************************************************************************
  191. *************************************************************************
  192. *** ***
  193. *** ***
  194. *** Your debugger is not using the correct symbols ***
  195. *** ***
  196. *** In order for this command to work properly, your symbol path ***
  197. *** must point to .pdb files that have full type information. ***
  198. *** ***
  199. *** Certain .pdb files (such as the public OS symbols) do not ***
  200. *** contain the required information. Contact the group that ***
  201. *** provided you with these symbols if you need this command to ***
  202. *** work. ***
  203. *** ***
  204. *** Type referenced: nt!_KPRCB ***
  205. *** ***
  206. *************************************************************************
  207. *************************************************************************
  208. *** ***
  209. *** ***
  210. *** Your debugger is not using the correct symbols ***
  211. *** ***
  212. *** In order for this command to work properly, your symbol path ***
  213. *** must point to .pdb files that have full type information. ***
  214. *** ***
  215. *** Certain .pdb files (such as the public OS symbols) do not ***
  216. *** contain the required information. Contact the group that ***
  217. *** provided you with these symbols if you need this command to ***
  218. *** work. ***
  219. *** ***
  220. *** Type referenced: nt!_KPRCB ***
  221. *** ***
  222. *************************************************************************
  223. Probably caused by : hardware
  224.  
  225. Followup: MachineOwner
  226. ---------
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!