API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Jun 26th, 2017
62
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 24.84 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:\Windows\Minidump\111010-17877-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. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  26. Windows 7 Kernel Version 7600 MP (4 procs) Free x64
  27. Product: WinNt, suite: TerminalServer SingleUserTS
  28. Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
  29. Machine Name:
  30. Kernel base = 0xfffff800`02817000 PsLoadedModuleList = 0xfffff800`02a54e50
  31. Debug session time: Wed Nov 10 17:24:58.088 2010 (UTC + 1:00)
  32. System Uptime: 0 days 1:24:55.070
  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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  42. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  43. Loading Kernel Symbols
  44. ...............................................................
  45. ................................................................
  46. ....................
  47. Loading User Symbols
  48. Loading unloaded module list
  49. ....
  50. *******************************************************************************
  51. * *
  52. * Bugcheck Analysis *
  53. * *
  54. *******************************************************************************
  55.  
  56. Use !analyze -v to get detailed debugging information.
  57.  
  58. BugCheck A, {d8, e, 0, fffff800028b4873}
  59.  
  60. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  61.  
  62. *************************************************************************
  63. *** ***
  64. *** ***
  65. *** Your debugger is not using the correct symbols ***
  66. *** ***
  67. *** In order for this command to work properly, your symbol path ***
  68. *** must point to .pdb files that have full type information. ***
  69. *** ***
  70. *** Certain .pdb files (such as the public OS symbols) do not ***
  71. *** contain the required information. Contact the group that ***
  72. *** provided you with these symbols if you need this command to ***
  73. *** work. ***
  74. *** ***
  75. *** Type referenced: nt!_KPRCB ***
  76. *** ***
  77. *************************************************************************
  78. *************************************************************************
  79. *** ***
  80. *** ***
  81. *** Your debugger is not using the correct symbols ***
  82. *** ***
  83. *** In order for this command 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. *** Your debugger is not using the correct symbols ***
  98. *** ***
  99. *** In order for this command to work properly, your symbol path ***
  100. *** must point to .pdb files that have full type information. ***
  101. *** ***
  102. *** Certain .pdb files (such as the public OS symbols) do not ***
  103. *** contain the required information. Contact the group that ***
  104. *** provided you with these symbols if you need this command to ***
  105. *** work. ***
  106. *** ***
  107. *** Type referenced: nt!_KPRCB ***
  108. *** ***
  109. *************************************************************************
  110. *************************************************************************
  111. *** ***
  112. *** ***
  113. *** Your debugger is not using the correct symbols ***
  114. *** ***
  115. *** In order for this command to work properly, your symbol path ***
  116. *** must point to .pdb files that have full type information. ***
  117. *** ***
  118. *** Certain .pdb files (such as the public OS symbols) do not ***
  119. *** contain the required information. Contact the group that ***
  120. *** provided you with these symbols if you need this command to ***
  121. *** work. ***
  122. *** ***
  123. *** Type referenced: nt!KPRCB ***
  124. *** ***
  125. *************************************************************************
  126. *************************************************************************
  127. *** ***
  128. *** ***
  129. *** Your debugger is not using the correct symbols ***
  130. *** ***
  131. *** In order for this command 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. *** Your debugger is not using the correct symbols ***
  146. *** ***
  147. *** In order for this command to work properly, your symbol path ***
  148. *** must point to .pdb files that have full type information. ***
  149. *** ***
  150. *** Certain .pdb files (such as the public OS symbols) do not ***
  151. *** contain the required information. Contact the group that ***
  152. *** provided you with these symbols if you need this command to ***
  153. *** work. ***
  154. *** ***
  155. *** Type referenced: nt!_KPRCB ***
  156. *** ***
  157. *************************************************************************
  158. *************************************************************************
  159. *** ***
  160. *** ***
  161. *** Your debugger is not using the correct symbols ***
  162. *** ***
  163. *** In order for this command to work properly, your symbol path ***
  164. *** must point to .pdb files that have full type information. ***
  165. *** ***
  166. *** Certain .pdb files (such as the public OS symbols) do not ***
  167. *** contain the required information. Contact the group that ***
  168. *** provided you with these symbols if you need this command to ***
  169. *** work. ***
  170. *** ***
  171. *** Type referenced: nt!_KPRCB ***
  172. *** ***
  173. *************************************************************************
  174. *************************************************************************
  175. *** ***
  176. *** ***
  177. *** Your debugger is not using the correct symbols ***
  178. *** ***
  179. *** In order for this command 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. Probably caused by : ntoskrnl.exe ( nt+9d873 )
  191.  
  192. Followup: MachineOwner
  193. ---------
  194.  
  195. 0: kd> !analyze -v output
  196. *******************************************************************************
  197. * *
  198. * Bugcheck Analysis *
  199. * *
  200. *******************************************************************************
  201.  
  202. IRQL_NOT_LESS_OR_EQUAL (a)
  203. An attempt was made to access a pageable (or completely invalid) address at an
  204. interrupt request level (IRQL) that is too high. This is usually
  205. caused by drivers using improper addresses.
  206. If a kernel debugger is available get the stack backtrace.
  207. Arguments:
  208. Arg1: 00000000000000d8, memory referenced
  209. Arg2: 000000000000000e, IRQL
  210. Arg3: 0000000000000000, bitfield :
  211. bit 0 : value 0 = read operation, 1 = write operation
  212. bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
  213. Arg4: fffff800028b4873, address which referenced memory
  214.  
  215. Debugging Details:
  216. ------------------
  217.  
  218. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  219.  
  220. *************************************************************************
  221. *** ***
  222. *** ***
  223. *** Your debugger is not using the correct symbols ***
  224. *** ***
  225. *** In order for this command to work properly, your symbol path ***
  226. *** must point to .pdb files that have full type information. ***
  227. *** ***
  228. *** Certain .pdb files (such as the public OS symbols) do not ***
  229. *** contain the required information. Contact the group that ***
  230. *** provided you with these symbols if you need this command to ***
  231. *** work. ***
  232. *** ***
  233. *** Type referenced: nt!_KPRCB ***
  234. *** ***
  235. *************************************************************************
  236. *************************************************************************
  237. *** ***
  238. *** ***
  239. *** Your debugger is not using the correct symbols ***
  240. *** ***
  241. *** In order for this command to work properly, your symbol path ***
  242. *** must point to .pdb files that have full type information. ***
  243. *** ***
  244. *** Certain .pdb files (such as the public OS symbols) do not ***
  245. *** contain the required information. Contact the group that ***
  246. *** provided you with these symbols if you need this command to ***
  247. *** work. ***
  248. *** ***
  249. *** Type referenced: nt!KPRCB ***
  250. *** ***
  251. *************************************************************************
  252. *************************************************************************
  253. *** ***
  254. *** ***
  255. *** Your debugger is not using the correct symbols ***
  256. *** ***
  257. *** In order for this command to work properly, your symbol path ***
  258. *** must point to .pdb files that have full type information. ***
  259. *** ***
  260. *** Certain .pdb files (such as the public OS symbols) do not ***
  261. *** contain the required information. Contact the group that ***
  262. *** provided you with these symbols if you need this command to ***
  263. *** work. ***
  264. *** ***
  265. *** Type referenced: nt!_KPRCB ***
  266. *** ***
  267. *************************************************************************
  268. *************************************************************************
  269. *** ***
  270. *** ***
  271. *** Your debugger is not using the correct symbols ***
  272. *** ***
  273. *** In order for this command to work properly, your symbol path ***
  274. *** must point to .pdb files that have full type information. ***
  275. *** ***
  276. *** Certain .pdb files (such as the public OS symbols) do not ***
  277. *** contain the required information. Contact the group that ***
  278. *** provided you with these symbols if you need this command to ***
  279. *** work. ***
  280. *** ***
  281. *** Type referenced: nt!KPRCB ***
  282. *** ***
  283. *************************************************************************
  284. *************************************************************************
  285. *** ***
  286. *** ***
  287. *** Your debugger is not using the correct symbols ***
  288. *** ***
  289. *** In order for this command to work properly, your symbol path ***
  290. *** must point to .pdb files that have full type information. ***
  291. *** ***
  292. *** Certain .pdb files (such as the public OS symbols) do not ***
  293. *** contain the required information. Contact the group that ***
  294. *** provided you with these symbols if you need this command to ***
  295. *** work. ***
  296. *** ***
  297. *** Type referenced: nt!_KPRCB ***
  298. *** ***
  299. *************************************************************************
  300. *************************************************************************
  301. *** ***
  302. *** ***
  303. *** Your debugger is not using the correct symbols ***
  304. *** ***
  305. *** In order for this command to work properly, your symbol path ***
  306. *** must point to .pdb files that have full type information. ***
  307. *** ***
  308. *** Certain .pdb files (such as the public OS symbols) do not ***
  309. *** contain the required information. Contact the group that ***
  310. *** provided you with these symbols if you need this command to ***
  311. *** work. ***
  312. *** ***
  313. *** Type referenced: nt!_KPRCB ***
  314. *** ***
  315. *************************************************************************
  316. *************************************************************************
  317. *** ***
  318. *** ***
  319. *** Your debugger is not using the correct symbols ***
  320. *** ***
  321. *** In order for this command to work properly, your symbol path ***
  322. *** must point to .pdb files that have full type information. ***
  323. *** ***
  324. *** Certain .pdb files (such as the public OS symbols) do not ***
  325. *** contain the required information. Contact the group that ***
  326. *** provided you with these symbols if you need this command to ***
  327. *** work. ***
  328. *** ***
  329. *** Type referenced: nt!_KPRCB ***
  330. *** ***
  331. *************************************************************************
  332. *************************************************************************
  333. *** ***
  334. *** ***
  335. *** Your debugger is not using the correct symbols ***
  336. *** ***
  337. *** In order for this command to work properly, your symbol path ***
  338. *** must point to .pdb files that have full type information. ***
  339. *** ***
  340. *** Certain .pdb files (such as the public OS symbols) do not ***
  341. *** contain the required information. Contact the group that ***
  342. *** provided you with these symbols if you need this command to ***
  343. *** work. ***
  344. *** ***
  345. *** Type referenced: nt!_KPRCB ***
  346. *** ***
  347. *************************************************************************
  348.  
  349. ADDITIONAL_DEBUG_TEXT:
  350. Use '!findthebuild' command to search for the target build information.
  351. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
  352.  
  353. MODULE_NAME: nt
  354.  
  355. FAULTING_MODULE: fffff80002817000 nt
  356.  
  357. DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
  358.  
  359. READ_ADDRESS: unable to get nt!MmSpecialPoolStart
  360. unable to get nt!MmSpecialPoolEnd
  361. unable to get nt!MmPoolCodeStart
  362. unable to get nt!MmPoolCodeEnd
  363. 00000000000000d8
  364.  
  365. CURRENT_IRQL: 0
  366.  
  367. FAULTING_IP:
  368. nt+9d873
  369. fffff800`028b4873 498b02 mov rax,qword ptr [r10]
  370.  
  371. CUSTOMER_CRASH_COUNT: 1
  372.  
  373. DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
  374.  
  375. BUGCHECK_STR: 0xA
  376.  
  377. LAST_CONTROL_TRANSFER: from fffff80002886ca9 to fffff80002887740
  378.  
  379. STACK_TEXT:
  380. fffff880`091315e8 fffff800`02886ca9 : 00000000`0000000a 00000000`000000d8 00000000`0000000e 00000000`00000000 : nt+0x70740
  381. fffff880`091315f0 00000000`0000000a : 00000000`000000d8 00000000`0000000e 00000000`00000000 fffff800`028b4873 : nt+0x6fca9
  382. fffff880`091315f8 00000000`000000d8 : 00000000`0000000e 00000000`00000000 fffff800`028b4873 00000000`00000001 : 0xa
  383. fffff880`09131600 00000000`0000000e : 00000000`00000000 fffff800`028b4873 00000000`00000001 00000000`43a37bd6 : 0xd8
  384. fffff880`09131608 00000000`00000000 : fffff800`028b4873 00000000`00000001 00000000`43a37bd6 00000000`00000000 : 0xe
  385.  
  386.  
  387. STACK_COMMAND: .bugcheck ; kb
  388.  
  389. FOLLOWUP_IP:
  390. nt+9d873
  391. fffff800`028b4873 498b02 mov rax,qword ptr [r10]
  392.  
  393. SYMBOL_NAME: nt+9d873
  394.  
  395. FOLLOWUP_NAME: MachineOwner
  396.  
  397. IMAGE_NAME: ntoskrnl.exe
  398.  
  399. BUCKET_ID: WRONG_SYMBOLS
  400.  
  401. Followup: MachineOwner
  402. ---------
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!