API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Sep 25th, 2014
76
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 17.90 KB | None | 0 0
raw download clone embed print report
  1.  
  2. Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [C:\Users\Freddy\Desktop\MEMORY.DMP]
  7. Kernel Bitmap Dump File: Only kernel address space is 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. *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
  25. Windows 8 Kernel Version 9600 MP (4 procs) Free x64
  26. Product: WinNt, suite: TerminalServer SingleUserTS
  27. Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
  28. Machine Name:
  29. Kernel base = 0xfffff802`0400a000 PsLoadedModuleList = 0xfffff802`042ce990
  30. Debug session time: Thu Sep 25 21:41:13.925 2014 (UTC + 2:00)
  31. System Uptime: 2 days 12:04:06.615
  32. *********************************************************************
  33. * Symbols can not be loaded because symbol path is not initialized. *
  34. * *
  35. * The Symbol Path can be set by: *
  36. * using the _NT_SYMBOL_PATH environment variable. *
  37. * using the -y <symbol_path> argument when starting the debugger. *
  38. * using .sympath and .sympath+ *
  39. *********************************************************************
  40. *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
  41. Loading Kernel Symbols
  42. ...............................................................
  43. ............................................Page 10d002 not present in the dump file. Type ".hh dbgerr004" for details
  44. ....................
  45. .......................
  46. Loading User Symbols
  47. PEB is paged out (Peb.Ldr = 00007ff6`f3dd3018). Type ".hh dbgerr001" for details
  48. Loading unloaded module list
  49. ...................
  50.  
  51. ************* Symbol Loading Error Summary **************
  52. Module name Error
  53. ntkrnlmp The system cannot find the file specified
  54.  
  55. You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
  56. You should also verify that your symbol search path (.sympath) is correct.
  57. *******************************************************************************
  58. * *
  59. * Bugcheck Analysis *
  60. * *
  61. *******************************************************************************
  62.  
  63. Use !analyze -v to get detailed debugging information.
  64.  
  65. BugCheck 13C, {ffffe00006adb5c0, 1, 0, 0}
  66.  
  67. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  68.  
  69. Page 10d002 not present in the dump file. Type ".hh dbgerr004" for details
  70. *************************************************************************
  71. *** ***
  72. *** ***
  73. *** Either you specified an unqualified symbol, or your debugger ***
  74. *** doesn't have full symbol information. Unqualified symbol ***
  75. *** resolution is turned off by default. Please either specify a ***
  76. *** fully qualified symbol module!symbolname, or enable resolution ***
  77. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  78. *** enabling unqualified symbol resolution with network symbol ***
  79. *** server shares in the symbol path may cause the debugger to ***
  80. *** appear to hang for long periods of time when an incorrect ***
  81. *** symbol name is typed or the network symbol server is down. ***
  82. *** ***
  83. *** For some commands to work properly, your symbol path ***
  84. *** must point to .pdb files that have full type information. ***
  85. *** ***
  86. *** Certain .pdb files (such as the public OS symbols) do not ***
  87. *** contain the required information. Contact the group that ***
  88. *** provided you with these symbols if you need this command to ***
  89. *** work. ***
  90. *** ***
  91. *** Type referenced: nt!_KPRCB ***
  92. *** ***
  93. *************************************************************************
  94. *************************************************************************
  95. *** ***
  96. *** ***
  97. *** Either you specified an unqualified symbol, or your debugger ***
  98. *** doesn't have full symbol information. Unqualified symbol ***
  99. *** resolution is turned off by default. Please either specify a ***
  100. *** fully qualified symbol module!symbolname, or enable resolution ***
  101. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  102. *** enabling unqualified symbol resolution with network symbol ***
  103. *** server shares in the symbol path may cause the debugger to ***
  104. *** appear to hang for long periods of time when an incorrect ***
  105. *** symbol name is typed or the network symbol server is down. ***
  106. *** ***
  107. *** For some commands 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. *************************************************************************
  119. *** ***
  120. *** ***
  121. *** Either you specified an unqualified symbol, or your debugger ***
  122. *** doesn't have full symbol information. Unqualified symbol ***
  123. *** resolution is turned off by default. Please either specify a ***
  124. *** fully qualified symbol module!symbolname, or enable resolution ***
  125. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  126. *** enabling unqualified symbol resolution with network symbol ***
  127. *** server shares in the symbol path may cause the debugger to ***
  128. *** appear to hang for long periods of time when an incorrect ***
  129. *** symbol name is typed or the network symbol server is down. ***
  130. *** ***
  131. *** For some commands to work properly, your symbol path ***
  132. *** must point to .pdb files that have full type information. ***
  133. *** ***
  134. *** Certain .pdb files (such as the public OS symbols) do not ***
  135. *** contain the required information. Contact the group that ***
  136. *** provided you with these symbols if you need this command to ***
  137. *** work. ***
  138. *** ***
  139. *** Type referenced: nt!_KPRCB ***
  140. *** ***
  141. *************************************************************************
  142. *************************************************************************
  143. *** ***
  144. *** ***
  145. *** Either you specified an unqualified symbol, or your debugger ***
  146. *** doesn't have full symbol information. Unqualified symbol ***
  147. *** resolution is turned off by default. Please either specify a ***
  148. *** fully qualified symbol module!symbolname, or enable resolution ***
  149. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  150. *** enabling unqualified symbol resolution with network symbol ***
  151. *** server shares in the symbol path may cause the debugger to ***
  152. *** appear to hang for long periods of time when an incorrect ***
  153. *** symbol name is typed or the network symbol server is down. ***
  154. *** ***
  155. *** For some commands to work properly, your symbol path ***
  156. *** must point to .pdb files that have full type information. ***
  157. *** ***
  158. *** Certain .pdb files (such as the public OS symbols) do not ***
  159. *** contain the required information. Contact the group that ***
  160. *** provided you with these symbols if you need this command to ***
  161. *** work. ***
  162. *** ***
  163. *** Type referenced: nt!KPRCB ***
  164. *** ***
  165. *************************************************************************
  166. *************************************************************************
  167. *** ***
  168. *** ***
  169. *** Either you specified an unqualified symbol, or your debugger ***
  170. *** doesn't have full symbol information. Unqualified symbol ***
  171. *** resolution is turned off by default. Please either specify a ***
  172. *** fully qualified symbol module!symbolname, or enable resolution ***
  173. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  174. *** enabling unqualified symbol resolution with network symbol ***
  175. *** server shares in the symbol path may cause the debugger to ***
  176. *** appear to hang for long periods of time when an incorrect ***
  177. *** symbol name is typed or the network symbol server is down. ***
  178. *** ***
  179. *** For some commands to work properly, your symbol path ***
  180. *** must point to .pdb files that have full type information. ***
  181. *** ***
  182. *** Certain .pdb files (such as the public OS symbols) do not ***
  183. *** contain the required information. Contact the group that ***
  184. *** provided you with these symbols if you need this command to ***
  185. *** work. ***
  186. *** ***
  187. *** Type referenced: nt!_KPRCB ***
  188. *** ***
  189. *************************************************************************
  190. *************************************************************************
  191. *** ***
  192. *** ***
  193. *** Either you specified an unqualified symbol, or your debugger ***
  194. *** doesn't have full symbol information. Unqualified symbol ***
  195. *** resolution is turned off by default. Please either specify a ***
  196. *** fully qualified symbol module!symbolname, or enable resolution ***
  197. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  198. *** enabling unqualified symbol resolution with network symbol ***
  199. *** server shares in the symbol path may cause the debugger to ***
  200. *** appear to hang for long periods of time when an incorrect ***
  201. *** symbol name is typed or the network symbol server is down. ***
  202. *** ***
  203. *** For some commands to work properly, your symbol path ***
  204. *** must point to .pdb files that have full type information. ***
  205. *** ***
  206. *** Certain .pdb files (such as the public OS symbols) do not ***
  207. *** contain the required information. Contact the group that ***
  208. *** provided you with these symbols if you need this command to ***
  209. *** work. ***
  210. *** ***
  211. *** Type referenced: nt!_KPRCB ***
  212. *** ***
  213. *************************************************************************
  214. *************************************************************************
  215. *** ***
  216. *** ***
  217. *** Either you specified an unqualified symbol, or your debugger ***
  218. *** doesn't have full symbol information. Unqualified symbol ***
  219. *** resolution is turned off by default. Please either specify a ***
  220. *** fully qualified symbol module!symbolname, or enable resolution ***
  221. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  222. *** enabling unqualified symbol resolution with network symbol ***
  223. *** server shares in the symbol path may cause the debugger to ***
  224. *** appear to hang for long periods of time when an incorrect ***
  225. *** symbol name is typed or the network symbol server is down. ***
  226. *** ***
  227. *** For some commands to work properly, your symbol path ***
  228. *** must point to .pdb files that have full type information. ***
  229. *** ***
  230. *** Certain .pdb files (such as the public OS symbols) do not ***
  231. *** contain the required information. Contact the group that ***
  232. *** provided you with these symbols if you need this command to ***
  233. *** work. ***
  234. *** ***
  235. *** Type referenced: nt!_KPRCB ***
  236. *** ***
  237. *************************************************************************
  238. *************************************************************************
  239. *** ***
  240. *** ***
  241. *** Either you specified an unqualified symbol, or your debugger ***
  242. *** doesn't have full symbol information. Unqualified symbol ***
  243. *** resolution is turned off by default. Please either specify a ***
  244. *** fully qualified symbol module!symbolname, or enable resolution ***
  245. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  246. *** enabling unqualified symbol resolution with network symbol ***
  247. *** server shares in the symbol path may cause the debugger to ***
  248. *** appear to hang for long periods of time when an incorrect ***
  249. *** symbol name is typed or the network symbol server is down. ***
  250. *** ***
  251. *** For some commands to work properly, your symbol path ***
  252. *** must point to .pdb files that have full type information. ***
  253. *** ***
  254. *** Certain .pdb files (such as the public OS symbols) do not ***
  255. *** contain the required information. Contact the group that ***
  256. *** provided you with these symbols if you need this command to ***
  257. *** work. ***
  258. *** ***
  259. *** Type referenced: nt!_KPRCB ***
  260. *** ***
  261. *************************************************************************
  262. Probably caused by : ntkrnlmp.exe ( nt!NtVdmControl+6ae9d )
  263.  
  264. Followup: MachineOwner
  265. ---------
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!