API tools faq
paste
Advertisement
SaintAnd

BSOD-pervomay

SaintAnd
Oct 11th, 2019
292
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 25.60 KB | None | 0 0
raw download clone embed print report
  1.  
  2. Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [C:\Users\...\101019-24180-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  9.  
  10. ************* Path validation summary **************
  11. Response Time (ms) Location
  12. OK C:\symbols
  13. Symbol search path is: C:\symbols
  14. Executable search path is:
  15. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  16. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  17. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  18. Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
  19. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  20. Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
  21. Machine Name:
  22. Kernel base = 0xfffff800`03e59000 PsLoadedModuleList = 0xfffff800`0409d890
  23. Debug session time: Thu Oct 10 17:12:55.236 2019 (UTC + 4:00)
  24. System Uptime: 0 days 0:06:38.282
  25. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  26. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  27. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  28. Loading Kernel Symbols
  29. .
  30.  
  31. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
  32. Run !sym noisy before .reload to track down problems loading symbols.
  33.  
  34. ..............................................................
  35. ................................................................
  36. ............................
  37. Loading User Symbols
  38. Loading unloaded module list
  39. ......
  40.  
  41. ************* Symbol Loading Error Summary **************
  42. Module name Error
  43. ntoskrnl The system cannot find the file specified
  44.  
  45. 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.
  46. You should also verify that your symbol search path (.sympath) is correct.
  47. *******************************************************************************
  48. * *
  49. * Bugcheck Analysis *
  50. * *
  51. *******************************************************************************
  52.  
  53. Use !analyze -v to get detailed debugging information.
  54.  
  55. BugCheck 44, {fffffa8007283010, ec0, 0, 0}
  56.  
  57. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  58.  
  59. *************************************************************************
  60. *** ***
  61. *** ***
  62. *** Either you specified an unqualified symbol, or your debugger ***
  63. *** doesn't have full symbol information. Unqualified symbol ***
  64. *** resolution is turned off by default. Please either specify a ***
  65. *** fully qualified symbol module!symbolname, or enable resolution ***
  66. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  67. *** enabling unqualified symbol resolution with network symbol ***
  68. *** server shares in the symbol path may cause the debugger to ***
  69. *** appear to hang for long periods of time when an incorrect ***
  70. *** symbol name is typed or the network symbol server is down. ***
  71. *** ***
  72. *** For some commands to work properly, your symbol path ***
  73. *** must point to .pdb files that have full type information. ***
  74. *** ***
  75. *** Certain .pdb files (such as the public OS symbols) do not ***
  76. *** contain the required information. Contact the group that ***
  77. *** provided you with these symbols if you need this command to ***
  78. *** work. ***
  79. *** ***
  80. *** Type referenced: nt!_KPRCB ***
  81. *** ***
  82. *************************************************************************
  83. *************************************************************************
  84. *** ***
  85. *** ***
  86. *** Either you specified an unqualified symbol, or your debugger ***
  87. *** doesn't have full symbol information. Unqualified symbol ***
  88. *** resolution is turned off by default. Please either specify a ***
  89. *** fully qualified symbol module!symbolname, or enable resolution ***
  90. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  91. *** enabling unqualified symbol resolution with network symbol ***
  92. *** server shares in the symbol path may cause the debugger to ***
  93. *** appear to hang for long periods of time when an incorrect ***
  94. *** symbol name is typed or the network symbol server is down. ***
  95. *** ***
  96. *** For some commands to work properly, your symbol path ***
  97. *** must point to .pdb files that have full type information. ***
  98. *** ***
  99. *** Certain .pdb files (such as the public OS symbols) do not ***
  100. *** contain the required information. Contact the group that ***
  101. *** provided you with these symbols if you need this command to ***
  102. *** work. ***
  103. *** ***
  104. *** Type referenced: nt!KPRCB ***
  105. *** ***
  106. *************************************************************************
  107. *************************************************************************
  108. *** ***
  109. *** ***
  110. *** Either you specified an unqualified symbol, or your debugger ***
  111. *** doesn't have full symbol information. Unqualified symbol ***
  112. *** resolution is turned off by default. Please either specify a ***
  113. *** fully qualified symbol module!symbolname, or enable resolution ***
  114. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  115. *** enabling unqualified symbol resolution with network symbol ***
  116. *** server shares in the symbol path may cause the debugger to ***
  117. *** appear to hang for long periods of time when an incorrect ***
  118. *** symbol name is typed or the network symbol server is down. ***
  119. *** ***
  120. *** For some commands to work properly, your symbol path ***
  121. *** must point to .pdb files that have full type information. ***
  122. *** ***
  123. *** Certain .pdb files (such as the public OS symbols) do not ***
  124. *** contain the required information. Contact the group that ***
  125. *** provided you with these symbols if you need this command to ***
  126. *** work. ***
  127. *** ***
  128. *** Type referenced: nt!_KPRCB ***
  129. *** ***
  130. *************************************************************************
  131. *************************************************************************
  132. *** ***
  133. *** ***
  134. *** Either you specified an unqualified symbol, or your debugger ***
  135. *** doesn't have full symbol information. Unqualified symbol ***
  136. *** resolution is turned off by default. Please either specify a ***
  137. *** fully qualified symbol module!symbolname, or enable resolution ***
  138. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  139. *** enabling unqualified symbol resolution with network symbol ***
  140. *** server shares in the symbol path may cause the debugger to ***
  141. *** appear to hang for long periods of time when an incorrect ***
  142. *** symbol name is typed or the network symbol server is down. ***
  143. *** ***
  144. *** For some commands to work properly, your symbol path ***
  145. *** must point to .pdb files that have full type information. ***
  146. *** ***
  147. *** Certain .pdb files (such as the public OS symbols) do not ***
  148. *** contain the required information. Contact the group that ***
  149. *** provided you with these symbols if you need this command to ***
  150. *** work. ***
  151. *** ***
  152. *** Type referenced: nt!KPRCB ***
  153. *** ***
  154. *************************************************************************
  155. *************************************************************************
  156. *** ***
  157. *** ***
  158. *** Either you specified an unqualified symbol, or your debugger ***
  159. *** doesn't have full symbol information. Unqualified symbol ***
  160. *** resolution is turned off by default. Please either specify a ***
  161. *** fully qualified symbol module!symbolname, or enable resolution ***
  162. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  163. *** enabling unqualified symbol resolution with network symbol ***
  164. *** server shares in the symbol path may cause the debugger to ***
  165. *** appear to hang for long periods of time when an incorrect ***
  166. *** symbol name is typed or the network symbol server is down. ***
  167. *** ***
  168. *** For some commands to work properly, your symbol path ***
  169. *** must point to .pdb files that have full type information. ***
  170. *** ***
  171. *** Certain .pdb files (such as the public OS symbols) do not ***
  172. *** contain the required information. Contact the group that ***
  173. *** provided you with these symbols if you need this command to ***
  174. *** work. ***
  175. *** ***
  176. *** Type referenced: nt!_KPRCB ***
  177. *** ***
  178. *************************************************************************
  179. *************************************************************************
  180. *** ***
  181. *** ***
  182. *** Either you specified an unqualified symbol, or your debugger ***
  183. *** doesn't have full symbol information. Unqualified symbol ***
  184. *** resolution is turned off by default. Please either specify a ***
  185. *** fully qualified symbol module!symbolname, or enable resolution ***
  186. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  187. *** enabling unqualified symbol resolution with network symbol ***
  188. *** server shares in the symbol path may cause the debugger to ***
  189. *** appear to hang for long periods of time when an incorrect ***
  190. *** symbol name is typed or the network symbol server is down. ***
  191. *** ***
  192. *** For some commands to work properly, your symbol path ***
  193. *** must point to .pdb files that have full type information. ***
  194. *** ***
  195. *** Certain .pdb files (such as the public OS symbols) do not ***
  196. *** contain the required information. Contact the group that ***
  197. *** provided you with these symbols if you need this command to ***
  198. *** work. ***
  199. *** ***
  200. *** Type referenced: nt!_EPROCESS ***
  201. *** ***
  202. *************************************************************************
  203. *************************************************************************
  204. *** ***
  205. *** ***
  206. *** Either you specified an unqualified symbol, or your debugger ***
  207. *** doesn't have full symbol information. Unqualified symbol ***
  208. *** resolution is turned off by default. Please either specify a ***
  209. *** fully qualified symbol module!symbolname, or enable resolution ***
  210. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  211. *** enabling unqualified symbol resolution with network symbol ***
  212. *** server shares in the symbol path may cause the debugger to ***
  213. *** appear to hang for long periods of time when an incorrect ***
  214. *** symbol name is typed or the network symbol server is down. ***
  215. *** ***
  216. *** For some commands to work properly, your symbol path ***
  217. *** must point to .pdb files that have full type information. ***
  218. *** ***
  219. *** Certain .pdb files (such as the public OS symbols) do not ***
  220. *** contain the required information. Contact the group that ***
  221. *** provided you with these symbols if you need this command to ***
  222. *** work. ***
  223. *** ***
  224. *** Type referenced: nt!_KPRCB ***
  225. *** ***
  226. *************************************************************************
  227. *************************************************************************
  228. *** ***
  229. *** ***
  230. *** Either you specified an unqualified symbol, or your debugger ***
  231. *** doesn't have full symbol information. Unqualified symbol ***
  232. *** resolution is turned off by default. Please either specify a ***
  233. *** fully qualified symbol module!symbolname, or enable resolution ***
  234. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  235. *** enabling unqualified symbol resolution with network symbol ***
  236. *** server shares in the symbol path may cause the debugger to ***
  237. *** appear to hang for long periods of time when an incorrect ***
  238. *** symbol name is typed or the network symbol server is down. ***
  239. *** ***
  240. *** For some commands to work properly, your symbol path ***
  241. *** must point to .pdb files that have full type information. ***
  242. *** ***
  243. *** Certain .pdb files (such as the public OS symbols) do not ***
  244. *** contain the required information. Contact the group that ***
  245. *** provided you with these symbols if you need this command to ***
  246. *** work. ***
  247. *** ***
  248. *** Type referenced: nt!_IRP ***
  249. *** ***
  250. *************************************************************************
  251. *************************************************************************
  252. *** ***
  253. *** ***
  254. *** Either you specified an unqualified symbol, or your debugger ***
  255. *** doesn't have full symbol information. Unqualified symbol ***
  256. *** resolution is turned off by default. Please either specify a ***
  257. *** fully qualified symbol module!symbolname, or enable resolution ***
  258. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  259. *** enabling unqualified symbol resolution with network symbol ***
  260. *** server shares in the symbol path may cause the debugger to ***
  261. *** appear to hang for long periods of time when an incorrect ***
  262. *** symbol name is typed or the network symbol server is down. ***
  263. *** ***
  264. *** For some commands to work properly, your symbol path ***
  265. *** must point to .pdb files that have full type information. ***
  266. *** ***
  267. *** Certain .pdb files (such as the public OS symbols) do not ***
  268. *** contain the required information. Contact the group that ***
  269. *** provided you with these symbols if you need this command to ***
  270. *** work. ***
  271. *** ***
  272. *** Type referenced: nt!_KPRCB ***
  273. *** ***
  274. *************************************************************************
  275. *************************************************************************
  276. *** ***
  277. *** ***
  278. *** Either you specified an unqualified symbol, or your debugger ***
  279. *** doesn't have full symbol information. Unqualified symbol ***
  280. *** resolution is turned off by default. Please either specify a ***
  281. *** fully qualified symbol module!symbolname, or enable resolution ***
  282. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  283. *** enabling unqualified symbol resolution with network symbol ***
  284. *** server shares in the symbol path may cause the debugger to ***
  285. *** appear to hang for long periods of time when an incorrect ***
  286. *** symbol name is typed or the network symbol server is down. ***
  287. *** ***
  288. *** For some commands to work properly, your symbol path ***
  289. *** must point to .pdb files that have full type information. ***
  290. *** ***
  291. *** Certain .pdb files (such as the public OS symbols) do not ***
  292. *** contain the required information. Contact the group that ***
  293. *** provided you with these symbols if you need this command to ***
  294. *** work. ***
  295. *** ***
  296. *** Type referenced: nt!_KPRCB ***
  297. *** ***
  298. *************************************************************************
  299. *************************************************************************
  300. *** ***
  301. *** ***
  302. *** Either you specified an unqualified symbol, or your debugger ***
  303. *** doesn't have full symbol information. Unqualified symbol ***
  304. *** resolution is turned off by default. Please either specify a ***
  305. *** fully qualified symbol module!symbolname, or enable resolution ***
  306. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  307. *** enabling unqualified symbol resolution with network symbol ***
  308. *** server shares in the symbol path may cause the debugger to ***
  309. *** appear to hang for long periods of time when an incorrect ***
  310. *** symbol name is typed or the network symbol server is down. ***
  311. *** ***
  312. *** For some commands to work properly, your symbol path ***
  313. *** must point to .pdb files that have full type information. ***
  314. *** ***
  315. *** Certain .pdb files (such as the public OS symbols) do not ***
  316. *** contain the required information. Contact the group that ***
  317. *** provided you with these symbols if you need this command to ***
  318. *** work. ***
  319. *** ***
  320. *** Type referenced: nt!_KTHREAD ***
  321. *** ***
  322. *************************************************************************
  323. *************************************************************************
  324. *** ***
  325. *** ***
  326. *** Either you specified an unqualified symbol, or your debugger ***
  327. *** doesn't have full symbol information. Unqualified symbol ***
  328. *** resolution is turned off by default. Please either specify a ***
  329. *** fully qualified symbol module!symbolname, or enable resolution ***
  330. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  331. *** enabling unqualified symbol resolution with network symbol ***
  332. *** server shares in the symbol path may cause the debugger to ***
  333. *** appear to hang for long periods of time when an incorrect ***
  334. *** symbol name is typed or the network symbol server is down. ***
  335. *** ***
  336. *** For some commands to work properly, your symbol path ***
  337. *** must point to .pdb files that have full type information. ***
  338. *** ***
  339. *** Certain .pdb files (such as the public OS symbols) do not ***
  340. *** contain the required information. Contact the group that ***
  341. *** provided you with these symbols if you need this command to ***
  342. *** work. ***
  343. *** ***
  344. *** Type referenced: nt!_KPRCB ***
  345. *** ***
  346. *************************************************************************
  347. *************************************************************************
  348. *** ***
  349. *** ***
  350. *** Either you specified an unqualified symbol, or your debugger ***
  351. *** doesn't have full symbol information. Unqualified symbol ***
  352. *** resolution is turned off by default. Please either specify a ***
  353. *** fully qualified symbol module!symbolname, or enable resolution ***
  354. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  355. *** enabling unqualified symbol resolution with network symbol ***
  356. *** server shares in the symbol path may cause the debugger to ***
  357. *** appear to hang for long periods of time when an incorrect ***
  358. *** symbol name is typed or the network symbol server is down. ***
  359. *** ***
  360. *** For some commands to work properly, your symbol path ***
  361. *** must point to .pdb files that have full type information. ***
  362. *** ***
  363. *** Certain .pdb files (such as the public OS symbols) do not ***
  364. *** contain the required information. Contact the group that ***
  365. *** provided you with these symbols if you need this command to ***
  366. *** work. ***
  367. *** ***
  368. *** Type referenced: nt!_KPRCB ***
  369. *** ***
  370. *************************************************************************
  371. Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!54D0317D5E7000 )
  372.  
  373. Followup: MachineOwner
  374. ---------
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!