API tools faq
paste
Guest User

Untitled

a guest
Feb 7th, 2015
230
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 13.96 KB | None | 0 0
raw download clone embed print report
  1.  
  2. Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [C:\Windows\Minidump\020715-21703-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 9600 MP (8 procs) Free x64
  28. Product: WinNt, suite: TerminalServer SingleUserTS
  29. Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
  30. Machine Name:
  31. Kernel base = 0xfffff801`be886000 PsLoadedModuleList = 0xfffff801`beb502d0
  32. Debug session time: Sat Feb 7 19:02:14.389 2015 (GMT+1)
  33. System Uptime: 0 days 1:45:55.173
  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. *******************************************************************************
  53. * *
  54. * Bugcheck Analysis *
  55. * *
  56. *******************************************************************************
  57.  
  58. Use !analyze -v to get detailed debugging information.
  59.  
  60. BugCheck F7, {6febda6f8045, 6feada6f8045, ffff901525907fba, 0}
  61.  
  62. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  63.  
  64. *************************************************************************
  65. *** ***
  66. *** ***
  67. *** Your debugger is not using the correct symbols ***
  68. *** ***
  69. *** In order for this command to work properly, your symbol path ***
  70. *** must point to .pdb files that have full type information. ***
  71. *** ***
  72. *** Certain .pdb files (such as the public OS symbols) do not ***
  73. *** contain the required information. Contact the group that ***
  74. *** provided you with these symbols if you need this command to ***
  75. *** work. ***
  76. *** ***
  77. *** Type referenced: nt!_KPRCB ***
  78. *** ***
  79. *************************************************************************
  80. *************************************************************************
  81. *** ***
  82. *** ***
  83. *** Your debugger is not using the correct symbols ***
  84. *** ***
  85. *** In order for this command to work properly, your symbol path ***
  86. *** must point to .pdb files that have full type information. ***
  87. *** ***
  88. *** Certain .pdb files (such as the public OS symbols) do not ***
  89. *** contain the required information. Contact the group that ***
  90. *** provided you with these symbols if you need this command to ***
  91. *** work. ***
  92. *** ***
  93. *** Type referenced: nt!KPRCB ***
  94. *** ***
  95. *************************************************************************
  96. *************************************************************************
  97. *** ***
  98. *** ***
  99. *** Your debugger is not using the correct symbols ***
  100. *** ***
  101. *** In order for this command to work properly, your symbol path ***
  102. *** must point to .pdb files that have full type information. ***
  103. *** ***
  104. *** Certain .pdb files (such as the public OS symbols) do not ***
  105. *** contain the required information. Contact the group that ***
  106. *** provided you with these symbols if you need this command to ***
  107. *** work. ***
  108. *** ***
  109. *** Type referenced: nt!_KPRCB ***
  110. *** ***
  111. *************************************************************************
  112. *************************************************************************
  113. *** ***
  114. *** ***
  115. *** Your debugger is not using the correct symbols ***
  116. *** ***
  117. *** In order for this command to work properly, your symbol path ***
  118. *** must point to .pdb files that have full type information. ***
  119. *** ***
  120. *** Certain .pdb files (such as the public OS symbols) do not ***
  121. *** contain the required information. Contact the group that ***
  122. *** provided you with these symbols if you need this command to ***
  123. *** work. ***
  124. *** ***
  125. *** Type referenced: nt!KPRCB ***
  126. *** ***
  127. *************************************************************************
  128. *************************************************************************
  129. *** ***
  130. *** ***
  131. *** Your debugger is not using the correct symbols ***
  132. *** ***
  133. *** In order for this command to work properly, your symbol path ***
  134. *** must point to .pdb files that have full type information. ***
  135. *** ***
  136. *** Certain .pdb files (such as the public OS symbols) do not ***
  137. *** contain the required information. Contact the group that ***
  138. *** provided you with these symbols if you need this command to ***
  139. *** work. ***
  140. *** ***
  141. *** Type referenced: nt!_KPRCB ***
  142. *** ***
  143. *************************************************************************
  144. *************************************************************************
  145. *** ***
  146. *** ***
  147. *** Your debugger is not using the correct symbols ***
  148. *** ***
  149. *** In order for this command to work properly, your symbol path ***
  150. *** must point to .pdb files that have full type information. ***
  151. *** ***
  152. *** Certain .pdb files (such as the public OS symbols) do not ***
  153. *** contain the required information. Contact the group that ***
  154. *** provided you with these symbols if you need this command to ***
  155. *** work. ***
  156. *** ***
  157. *** Type referenced: nt!_KPRCB ***
  158. *** ***
  159. *************************************************************************
  160. *************************************************************************
  161. *** ***
  162. *** ***
  163. *** Your debugger is not using the correct symbols ***
  164. *** ***
  165. *** In order for this command to work properly, your symbol path ***
  166. *** must point to .pdb files that have full type information. ***
  167. *** ***
  168. *** Certain .pdb files (such as the public OS symbols) do not ***
  169. *** contain the required information. Contact the group that ***
  170. *** provided you with these symbols if you need this command to ***
  171. *** work. ***
  172. *** ***
  173. *** Type referenced: nt!_KPRCB ***
  174. *** ***
  175. *************************************************************************
  176. *************************************************************************
  177. *** ***
  178. *** ***
  179. *** Your debugger is not using the correct symbols ***
  180. *** ***
  181. *** In order for this command to work properly, your symbol path ***
  182. *** must point to .pdb files that have full type information. ***
  183. *** ***
  184. *** Certain .pdb files (such as the public OS symbols) do not ***
  185. *** contain the required information. Contact the group that ***
  186. *** provided you with these symbols if you need this command to ***
  187. *** work. ***
  188. *** ***
  189. *** Type referenced: nt!_KPRCB ***
  190. *** ***
  191. *************************************************************************
  192. *********************************************************************
  193. * Symbols can not be loaded because symbol path is not initialized. *
  194. * *
  195. * The Symbol Path can be set by: *
  196. * using the _NT_SYMBOL_PATH environment variable. *
  197. * using the -y <symbol_path> argument when starting the debugger. *
  198. * using .sympath and .sympath+ *
  199. *********************************************************************
  200. *********************************************************************
  201. * Symbols can not be loaded because symbol path is not initialized. *
  202. * *
  203. * The Symbol Path can be set by: *
  204. * using the _NT_SYMBOL_PATH environment variable. *
  205. * using the -y <symbol_path> argument when starting the debugger. *
  206. * using .sympath and .sympath+ *
  207. *********************************************************************
  208. Probably caused by : ntoskrnl.exe ( nt+153fa0 )
  209.  
  210. Followup: MachineOwner
  211. ---------
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!