Advertisement
Guest User

BSOD

a guest
Jan 15th, 2014
129
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 13.04 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 [C:\Windows\Minidump\011514-32027-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  9. DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`01b34022?
  10. DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`00225842?
  11. Symbol search path is: *** Invalid ***
  12. ****************************************************************************
  13. * Symbol loading may be unreliable without a symbol search path. *
  14. * Use .symfix to have the debugger choose a symbol path. *
  15. * After setting your symbol path, use .reload to refresh symbol locations. *
  16. ****************************************************************************
  17. Executable search path is:
  18. *********************************************************************
  19. * Symbols can not be loaded because symbol path is not initialized. *
  20. * *
  21. * The Symbol Path can be set by: *
  22. * using the _NT_SYMBOL_PATH environment variable. *
  23. * using the -y <symbol_path> argument when starting the debugger. *
  24. * using .sympath and .sympath+ *
  25. *********************************************************************
  26. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  27. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  28. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  29. Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
  30. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  31. Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
  32. Machine Name:
  33. Kernel base = 0xfffff800`03213000 PsLoadedModuleList = 0xfffff800`034566d0
  34. Debug session time: Wed Jan 15 04:05:50.379 2014 (UTC - 6:00)
  35. System Uptime: 0 days 4:25:39.173
  36. *********************************************************************
  37. * Symbols can not be loaded because symbol path is not initialized. *
  38. * *
  39. * The Symbol Path can be set by: *
  40. * using the _NT_SYMBOL_PATH environment variable. *
  41. * using the -y <symbol_path> argument when starting the debugger. *
  42. * using .sympath and .sympath+ *
  43. *********************************************************************
  44. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  45. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  46. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  47. Loading Kernel Symbols
  48. ...............................................................
  49. ................................................................
  50. ....................
  51. Loading User Symbols
  52. Loading unloaded module list
  53. .......
  54. *******************************************************************************
  55. * *
  56. * Bugcheck Analysis *
  57. * *
  58. *******************************************************************************
  59.  
  60. Use !analyze -v to get detailed debugging information.
  61.  
  62. BugCheck 1000009F, {4, 258, fffffa8006cff040, fffff80000b9c3d0}
  63.  
  64. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  65.  
  66. *************************************************************************
  67. *** ***
  68. *** ***
  69. *** Your debugger is not using the correct symbols ***
  70. *** ***
  71. *** In order for this command to work properly, your symbol path ***
  72. *** must point to .pdb files that have full type information. ***
  73. *** ***
  74. *** Certain .pdb files (such as the public OS symbols) do not ***
  75. *** contain the required information. Contact the group that ***
  76. *** provided you with these symbols if you need this command to ***
  77. *** work. ***
  78. *** ***
  79. *** Type referenced: nt!_ETHREAD ***
  80. *** ***
  81. *************************************************************************
  82. *************************************************************************
  83. *** ***
  84. *** ***
  85. *** Your debugger is not using the correct symbols ***
  86. *** ***
  87. *** In order for this command to work properly, your symbol path ***
  88. *** must point to .pdb files that have full type information. ***
  89. *** ***
  90. *** Certain .pdb files (such as the public OS symbols) do not ***
  91. *** contain the required information. Contact the group that ***
  92. *** provided you with these symbols if you need this command to ***
  93. *** work. ***
  94. *** ***
  95. *** Type referenced: nt!_ETHREAD ***
  96. *** ***
  97. *************************************************************************
  98. *************************************************************************
  99. *** ***
  100. *** ***
  101. *** Your debugger is not using the correct symbols ***
  102. *** ***
  103. *** In order for this command to work properly, your symbol path ***
  104. *** must point to .pdb files that have full type information. ***
  105. *** ***
  106. *** Certain .pdb files (such as the public OS symbols) do not ***
  107. *** contain the required information. Contact the group that ***
  108. *** provided you with these symbols if you need this command to ***
  109. *** work. ***
  110. *** ***
  111. *** Type referenced: nt!_TRIAGE_9F_PNP ***
  112. *** ***
  113. *************************************************************************
  114. *************************************************************************
  115. *** ***
  116. *** ***
  117. *** Your debugger is not using the correct symbols ***
  118. *** ***
  119. *** In order for this command to work properly, your symbol path ***
  120. *** must point to .pdb files that have full type information. ***
  121. *** ***
  122. *** Certain .pdb files (such as the public OS symbols) do not ***
  123. *** contain the required information. Contact the group that ***
  124. *** provided you with these symbols if you need this command to ***
  125. *** work. ***
  126. *** ***
  127. *** Type referenced: nt!_TRIAGE_PNP_DEVICE_COMPLETION_QUEUE ***
  128. *** ***
  129. *************************************************************************
  130. *************************************************************************
  131. *** ***
  132. *** ***
  133. *** Your debugger is not using the correct symbols ***
  134. *** ***
  135. *** In order for this command to work properly, your symbol path ***
  136. *** must point to .pdb files that have full type information. ***
  137. *** ***
  138. *** Certain .pdb files (such as the public OS symbols) do not ***
  139. *** contain the required information. Contact the group that ***
  140. *** provided you with these symbols if you need this command to ***
  141. *** work. ***
  142. *** ***
  143. *** Type referenced: nt!_TRIAGE_PNP_DEVICE_COMPLETION_REQUEST ***
  144. *** ***
  145. *************************************************************************
  146. *************************************************************************
  147. *** ***
  148. *** ***
  149. *** Your debugger is not using the correct symbols ***
  150. *** ***
  151. *** In order for this command to work properly, your symbol path ***
  152. *** must point to .pdb files that have full type information. ***
  153. *** ***
  154. *** Certain .pdb files (such as the public OS symbols) do not ***
  155. *** contain the required information. Contact the group that ***
  156. *** provided you with these symbols if you need this command to ***
  157. *** work. ***
  158. *** ***
  159. *** Type referenced: nt!_KPRCB ***
  160. *** ***
  161. *************************************************************************
  162. *************************************************************************
  163. *** ***
  164. *** ***
  165. *** Your debugger is not using the correct symbols ***
  166. *** ***
  167. *** In order for this command to work properly, your symbol path ***
  168. *** must point to .pdb files that have full type information. ***
  169. *** ***
  170. *** Certain .pdb files (such as the public OS symbols) do not ***
  171. *** contain the required information. Contact the group that ***
  172. *** provided you with these symbols if you need this command to ***
  173. *** work. ***
  174. *** ***
  175. *** Type referenced: nt!_KPRCB ***
  176. *** ***
  177. *************************************************************************
  178. *************************************************************************
  179. *** ***
  180. *** ***
  181. *** Your debugger is not using the correct symbols ***
  182. *** ***
  183. *** In order for this command to work properly, your symbol path ***
  184. *** must point to .pdb files that have full type information. ***
  185. *** ***
  186. *** Certain .pdb files (such as the public OS symbols) do not ***
  187. *** contain the required information. Contact the group that ***
  188. *** provided you with these symbols if you need this command to ***
  189. *** work. ***
  190. *** ***
  191. *** Type referenced: nt!_KPRCB ***
  192. *** ***
  193. *************************************************************************
  194. Probably caused by : ntoskrnl.exe ( nt+78a8a )
  195.  
  196. Followup: MachineOwner
  197. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement