API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Sep 4th, 2018
125
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.87 KB | None | 0 0
raw download clone embed print report
  1. Auto Dump Analyzer - Version: 0.8
  2. Time to analyze file(s): 00 hours and 10 minutes and 24 seconds
  3.  
  4. Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
  5. Copyright (c) Microsoft Corporation. All rights reserved.
  6.  
  7.  
  8. Loading Dump File [C:\Users\UserName\Desktop\Minidump\083118-8000-01.dmp]
  9. Mini Kernel Dump File: Only registers and stack trace are available
  10.  
  11. Symbol search path is: srv*
  12. Executable search path is:
  13. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  14. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  15. Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
  16. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  17. Built by: 9600.19101.amd64fre.winblue_ltsb_escrow.180718-1800
  18. Machine Name:
  19. Kernel base = 0xfffff802`2587e000 PsLoadedModuleList = 0xfffff802`25b42550
  20. Debug session time: Fri Aug 31 12:02:41.048 2018 (UTC - 4:00)
  21. System Uptime: 2 days 22:45:31.935
  22. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  23. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  24. Loading Kernel Symbols
  25. .
  26.  
  27. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
  28. Run !sym noisy before .reload to track down problems loading symbols.
  29.  
  30. ..............................................................
  31. ................................................................
  32. ....................................
  33. Loading User Symbols
  34. Loading unloaded module list
  35. ..................................................
  36.  
  37. ************* Symbol Loading Error Summary **************
  38. Module name Error
  39. ntoskrnl The system cannot find the file specified
  40.  
  41. 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.
  42. You should also verify that your symbol search path (.sympath) is correct.
  43. *******************************************************************************
  44. * *
  45. * Bugcheck Analysis *
  46. * *
  47. *******************************************************************************
  48.  
  49. Use !analyze -v to get detailed debugging information.
  50.  
  51. BugCheck A, {ffff9000205effff, 2, 0, fffff802259c1523}
  52.  
  53.  
  54.  
  55.  
  56.  
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.  
  64. Auto Dump Analyzer - Version: 0.8
  65. Time to analyze file(s): 00 hours and 16 minutes and 50 seconds
  66.  
  67. Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
  68. Copyright (c) Microsoft Corporation. All rights reserved.
  69.  
  70.  
  71. Loading Dump File [C:\Users\UserName\Desktop\Minidump\090218-5546-01.dmp]
  72. Mini Kernel Dump File: Only registers and stack trace are available
  73.  
  74. Symbol search path is: srv*
  75. Executable search path is:
  76. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  77. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  78. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  79. Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
  80. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  81. Built by: 9600.19101.amd64fre.winblue_ltsb_escrow.180718-1800
  82. Machine Name:
  83. Kernel base = 0xfffff800`5bc1b000 PsLoadedModuleList = 0xfffff800`5bedf550
  84. Debug session time: Sun Sep 2 03:16:51.144 2018 (UTC - 4:00)
  85. System Uptime: 0 days 22:06:05.914
  86. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  87. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  88. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  89. Loading Kernel Symbols
  90. .
  91.  
  92. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
  93. Run !sym noisy before .reload to track down problems loading symbols.
  94.  
  95. ..............................................................
  96. ................................................................
  97. ....................................
  98. Loading User Symbols
  99. Loading unloaded module list
  100. ..........................................
  101.  
  102. ************* Symbol Loading Error Summary **************
  103. Module name Error
  104. ntoskrnl The system cannot find the file specified
  105.  
  106. 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.
  107. You should also verify that your symbol search path (.sympath) is correct.
  108. *******************************************************************************
  109. * *
  110. * Bugcheck Analysis *
  111. * *
  112. *******************************************************************************
  113.  
  114. Use !analyze -v to get detailed debugging information.
  115.  
  116. BugCheck A, {fffff000d94d9198, 2, 0, fffff8005bc48c2a}
  117.  
  118. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  119.  
  120. *************************************************************************
  121. *** ***
  122. *** ***
  123. *** Either you specified an unqualified symbol, or your debugger ***
  124. *** doesn't have full symbol information. Unqualified symbol ***
  125. *** resolution is turned off by default. Please either specify a ***
  126. *** fully qualified symbol module!symbolname, or enable resolution ***
  127. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  128. *** enabling unqualified symbol resolution with network symbol ***
  129. *** server shares in the symbol path may cause the debugger to ***
  130. *** appear to hang for long periods of time when an incorrect ***
  131. *** symbol name is typed or the network symbol server is down. ***
  132. *** ***
  133. *** For some commands 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. Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!5B4FFF2E77F000 )
  146.  
  147. Followup: MachineOwner
  148. ---------
  149.  
  150. 6: kd> !analyze -v
  151. *******************************************************************************
  152. * *
  153. * Bugcheck Analysis *
  154. * *
  155. *******************************************************************************
  156.  
  157. IRQL_NOT_LESS_OR_EQUAL (a)
  158. An attempt was made to access a pageable (or completely invalid) address at an
  159. interrupt request level (IRQL) that is too high. This is usually
  160. caused by drivers using improper addresses.
  161. If a kernel debugger is available get the stack backtrace.
  162. Arguments:
  163. Arg1: fffff000d94d9198, memory referenced
  164. Arg2: 0000000000000002, IRQL
  165. Arg3: 0000000000000000, bitfield :
  166. bit 0 : value 0 = read operation, 1 = write operation
  167. bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
  168. Arg4: fffff8005bc48c2a, address which referenced memory
  169.  
  170. Debugging Details:
  171. ------------------
  172.  
  173. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  174.  
  175. *************************************************************************
  176. *** ***
  177. *** ***
  178. *** Either you specified an unqualified symbol, or your debugger ***
  179. *** doesn't have full symbol information. Unqualified symbol ***
  180. *** resolution is turned off by default. Please either specify a ***
  181. *** fully qualified symbol module!symbolname, or enable resolution ***
  182. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  183. *** enabling unqualified symbol resolution with network symbol ***
  184. *** server shares in the symbol path may cause the debugger to ***
  185. *** appear to hang for long periods of time when an incorrect ***
  186. *** symbol name is typed or the network symbol server is down. ***
  187. *** ***
  188. *** For some commands 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. *************************************************************************
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!