API tools faq
paste
Advertisement
mariuszklama

bluescreen 6

mariuszklama
Jul 19th, 2023
14
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 51.73 KB | None | 0 0
raw download clone embed print report
  1.  
  2. ************* Preparing the environment for Debugger Extensions Gallery repositories **************
  3. ExtensionRepository : Implicit
  4. UseExperimentalFeatureForNugetShare : false
  5. AllowNugetExeUpdate : false
  6. AllowNugetMSCredentialProviderInstall : false
  7. AllowParallelInitializationOfLocalRepositories : true
  8.  
  9. -- Configuring repositories
  10. ----> Repository : LocalInstalled, Enabled: true
  11. ----> Repository : UserExtensions, Enabled: true
  12.  
  13. >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
  14.  
  15. ************* Waiting for Debugger Extensions Gallery to Initialize **************
  16.  
  17. >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
  18. ----> Repository : UserExtensions, Enabled: true, Packages count: 0
  19. ----> Repository : LocalInstalled, Enabled: true, Packages count: 36
  20.  
  21. Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
  22. Copyright (c) Microsoft Corporation. All rights reserved.
  23.  
  24.  
  25. Loading Dump File [C:\Windows\Minidump\071923-9812-01.dmp]
  26. Mini Kernel Dump File: Only registers and stack trace are available
  27.  
  28.  
  29. ************* Path validation summary **************
  30. Response Time (ms) Location
  31. Deferred srv*
  32. Symbol search path is: srv*
  33. Executable search path is:
  34. *************************************************************************
  35. *** ***
  36. *** ***
  37. *** Either you specified an unqualified symbol, or your debugger ***
  38. *** doesn't have full symbol information. Unqualified symbol ***
  39. *** resolution is turned off by default. Please either specify a ***
  40. *** fully qualified symbol module!symbolname, or enable resolution ***
  41. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  42. *** enabling unqualified symbol resolution with network symbol ***
  43. *** server shares in the symbol path may cause the debugger to ***
  44. *** appear to hang for long periods of time when an incorrect ***
  45. *** symbol name is typed or the network symbol server is down. ***
  46. *** ***
  47. *** For some commands to work properly, your symbol path ***
  48. *** must point to .pdb files that have full type information. ***
  49. *** ***
  50. *** Certain .pdb files (such as the public OS symbols) do not ***
  51. *** contain the required information. Contact the group that ***
  52. *** provided you with these symbols if you need this command to ***
  53. *** work. ***
  54. *** ***
  55. *** Type referenced: nt!_EPROCESS ***
  56. *** ***
  57. *************************************************************************
  58. Windows 10 Kernel Version 19041 MP (12 procs) Free x64
  59. Product: WinNt, suite: TerminalServer SingleUserTS
  60. Kernel base = 0xfffff807`4fc00000 PsLoadedModuleList = 0xfffff807`5082a2f0
  61. Debug session time: Wed Jul 19 15:37:25.104 2023 (UTC + 2:00)
  62. System Uptime: 0 days 0:18:24.676
  63. *************************************************************************
  64. *** ***
  65. *** ***
  66. *** Either you specified an unqualified symbol, or your debugger ***
  67. *** doesn't have full symbol information. Unqualified symbol ***
  68. *** resolution is turned off by default. Please either specify a ***
  69. *** fully qualified symbol module!symbolname, or enable resolution ***
  70. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  71. *** enabling unqualified symbol resolution with network symbol ***
  72. *** server shares in the symbol path may cause the debugger to ***
  73. *** appear to hang for long periods of time when an incorrect ***
  74. *** symbol name is typed or the network symbol server is down. ***
  75. *** ***
  76. *** For some commands to work properly, your symbol path ***
  77. *** must point to .pdb files that have full type information. ***
  78. *** ***
  79. *** Certain .pdb files (such as the public OS symbols) do not ***
  80. *** contain the required information. Contact the group that ***
  81. *** provided you with these symbols if you need this command to ***
  82. *** work. ***
  83. *** ***
  84. *** Type referenced: nt!_EPROCESS ***
  85. *** ***
  86. *************************************************************************
  87. Loading Kernel Symbols
  88. ...............................................................
  89. ................................................................
  90. ........................................................
  91. Loading User Symbols
  92. PEB is paged out (Peb.Ldr = 00000000`0020a018). Type ".hh dbgerr001" for details
  93. Loading unloaded module list
  94. ..........
  95.  
  96. ************* Symbol Loading Error Summary **************
  97. Module name Error
  98. ntkrnlmp The system cannot find the file specified
  99.  
  100. 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.
  101. You should also verify that your symbol search path (.sympath) is correct.
  102. For analysis of this file, run !analyze -v
  103. nt!KeBugCheckEx:
  104. fffff807`4fffbbf0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffab81`96e94940=????????????????
  105. 5: kd> !analyze -v
  106. *******************************************************************************
  107. * *
  108. * Bugcheck Analysis *
  109. * *
  110. *******************************************************************************
  111.  
  112. WHEA_UNCORRECTABLE_ERROR (124)
  113. A fatal hardware error has occurred. Parameter 1 identifies the type of error
  114. source that reported the error. Parameter 2 holds the address of the
  115. nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
  116. Arguments:
  117. Arg1: 0000000000000000, Machine Check Exception
  118. Arg2: ffffc90ed4004028, Address of the nt!_WHEA_ERROR_RECORD structure.
  119. Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value.
  120. Arg4: 0000000001010135, Low order 32-bits of the MCi_STATUS value.
  121.  
  122. Debugging Details:
  123. ------------------
  124.  
  125. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  126.  
  127. *************************************************************************
  128. *** ***
  129. *** ***
  130. *** Either you specified an unqualified symbol, or your debugger ***
  131. *** doesn't have full symbol information. Unqualified symbol ***
  132. *** resolution is turned off by default. Please either specify a ***
  133. *** fully qualified symbol module!symbolname, or enable resolution ***
  134. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  135. *** enabling unqualified symbol resolution with network symbol ***
  136. *** server shares in the symbol path may cause the debugger to ***
  137. *** appear to hang for long periods of time when an incorrect ***
  138. *** symbol name is typed or the network symbol server is down. ***
  139. *** ***
  140. *** For some commands to work properly, your symbol path ***
  141. *** must point to .pdb files that have full type information. ***
  142. *** ***
  143. *** Certain .pdb files (such as the public OS symbols) do not ***
  144. *** contain the required information. Contact the group that ***
  145. *** provided you with these symbols if you need this command to ***
  146. *** work. ***
  147. *** ***
  148. *** Type referenced: nt!_IMAGE_DOS_HEADER ***
  149. *** ***
  150. *************************************************************************
  151. *************************************************************************
  152. *** ***
  153. *** ***
  154. *** Either you specified an unqualified symbol, or your debugger ***
  155. *** doesn't have full symbol information. Unqualified symbol ***
  156. *** resolution is turned off by default. Please either specify a ***
  157. *** fully qualified symbol module!symbolname, or enable resolution ***
  158. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  159. *** enabling unqualified symbol resolution with network symbol ***
  160. *** server shares in the symbol path may cause the debugger to ***
  161. *** appear to hang for long periods of time when an incorrect ***
  162. *** symbol name is typed or the network symbol server is down. ***
  163. *** ***
  164. *** For some commands to work properly, your symbol path ***
  165. *** must point to .pdb files that have full type information. ***
  166. *** ***
  167. *** Certain .pdb files (such as the public OS symbols) do not ***
  168. *** contain the required information. Contact the group that ***
  169. *** provided you with these symbols if you need this command to ***
  170. *** work. ***
  171. *** ***
  172. *** Type referenced: nt!_IMAGE_DOS_HEADER ***
  173. *** ***
  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!_IMAGE_DOS_HEADER ***
  197. *** ***
  198. *************************************************************************
  199. *************************************************************************
  200. *** ***
  201. *** ***
  202. *** Either you specified an unqualified symbol, or your debugger ***
  203. *** doesn't have full symbol information. Unqualified symbol ***
  204. *** resolution is turned off by default. Please either specify a ***
  205. *** fully qualified symbol module!symbolname, or enable resolution ***
  206. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  207. *** enabling unqualified symbol resolution with network symbol ***
  208. *** server shares in the symbol path may cause the debugger to ***
  209. *** appear to hang for long periods of time when an incorrect ***
  210. *** symbol name is typed or the network symbol server is down. ***
  211. *** ***
  212. *** For some commands to work properly, your symbol path ***
  213. *** must point to .pdb files that have full type information. ***
  214. *** ***
  215. *** Certain .pdb files (such as the public OS symbols) do not ***
  216. *** contain the required information. Contact the group that ***
  217. *** provided you with these symbols if you need this command to ***
  218. *** work. ***
  219. *** ***
  220. *** Type referenced: nt!_IMAGE_DOS_HEADER ***
  221. *** ***
  222. *************************************************************************
  223. *************************************************************************
  224. *** ***
  225. *** ***
  226. *** Either you specified an unqualified symbol, or your debugger ***
  227. *** doesn't have full symbol information. Unqualified symbol ***
  228. *** resolution is turned off by default. Please either specify a ***
  229. *** fully qualified symbol module!symbolname, or enable resolution ***
  230. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  231. *** enabling unqualified symbol resolution with network symbol ***
  232. *** server shares in the symbol path may cause the debugger to ***
  233. *** appear to hang for long periods of time when an incorrect ***
  234. *** symbol name is typed or the network symbol server is down. ***
  235. *** ***
  236. *** For some commands to work properly, your symbol path ***
  237. *** must point to .pdb files that have full type information. ***
  238. *** ***
  239. *** Certain .pdb files (such as the public OS symbols) do not ***
  240. *** contain the required information. Contact the group that ***
  241. *** provided you with these symbols if you need this command to ***
  242. *** work. ***
  243. *** ***
  244. *** Type referenced: nt!_IMAGE_DOS_HEADER ***
  245. *** ***
  246. *************************************************************************
  247. *************************************************************************
  248. *** ***
  249. *** ***
  250. *** Either you specified an unqualified symbol, or your debugger ***
  251. *** doesn't have full symbol information. Unqualified symbol ***
  252. *** resolution is turned off by default. Please either specify a ***
  253. *** fully qualified symbol module!symbolname, or enable resolution ***
  254. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  255. *** enabling unqualified symbol resolution with network symbol ***
  256. *** server shares in the symbol path may cause the debugger to ***
  257. *** appear to hang for long periods of time when an incorrect ***
  258. *** symbol name is typed or the network symbol server is down. ***
  259. *** ***
  260. *** For some commands to work properly, your symbol path ***
  261. *** must point to .pdb files that have full type information. ***
  262. *** ***
  263. *** Certain .pdb files (such as the public OS symbols) do not ***
  264. *** contain the required information. Contact the group that ***
  265. *** provided you with these symbols if you need this command to ***
  266. *** work. ***
  267. *** ***
  268. *** Type referenced: nt!_IMAGE_DOS_HEADER ***
  269. *** ***
  270. *************************************************************************
  271. *************************************************************************
  272. *** ***
  273. *** ***
  274. *** Either you specified an unqualified symbol, or your debugger ***
  275. *** doesn't have full symbol information. Unqualified symbol ***
  276. *** resolution is turned off by default. Please either specify a ***
  277. *** fully qualified symbol module!symbolname, or enable resolution ***
  278. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  279. *** enabling unqualified symbol resolution with network symbol ***
  280. *** server shares in the symbol path may cause the debugger to ***
  281. *** appear to hang for long periods of time when an incorrect ***
  282. *** symbol name is typed or the network symbol server is down. ***
  283. *** ***
  284. *** For some commands to work properly, your symbol path ***
  285. *** must point to .pdb files that have full type information. ***
  286. *** ***
  287. *** Certain .pdb files (such as the public OS symbols) do not ***
  288. *** contain the required information. Contact the group that ***
  289. *** provided you with these symbols if you need this command to ***
  290. *** work. ***
  291. *** ***
  292. *** Type referenced: nt!_IMAGE_DOS_HEADER ***
  293. *** ***
  294. *************************************************************************
  295. *************************************************************************
  296. *** ***
  297. *** ***
  298. *** Either you specified an unqualified symbol, or your debugger ***
  299. *** doesn't have full symbol information. Unqualified symbol ***
  300. *** resolution is turned off by default. Please either specify a ***
  301. *** fully qualified symbol module!symbolname, or enable resolution ***
  302. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  303. *** enabling unqualified symbol resolution with network symbol ***
  304. *** server shares in the symbol path may cause the debugger to ***
  305. *** appear to hang for long periods of time when an incorrect ***
  306. *** symbol name is typed or the network symbol server is down. ***
  307. *** ***
  308. *** For some commands to work properly, your symbol path ***
  309. *** must point to .pdb files that have full type information. ***
  310. *** ***
  311. *** Certain .pdb files (such as the public OS symbols) do not ***
  312. *** contain the required information. Contact the group that ***
  313. *** provided you with these symbols if you need this command to ***
  314. *** work. ***
  315. *** ***
  316. *** Type referenced: nt!_IMAGE_DOS_HEADER ***
  317. *** ***
  318. *************************************************************************
  319. *************************************************************************
  320. *** ***
  321. *** ***
  322. *** Either you specified an unqualified symbol, or your debugger ***
  323. *** doesn't have full symbol information. Unqualified symbol ***
  324. *** resolution is turned off by default. Please either specify a ***
  325. *** fully qualified symbol module!symbolname, or enable resolution ***
  326. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  327. *** enabling unqualified symbol resolution with network symbol ***
  328. *** server shares in the symbol path may cause the debugger to ***
  329. *** appear to hang for long periods of time when an incorrect ***
  330. *** symbol name is typed or the network symbol server is down. ***
  331. *** ***
  332. *** For some commands to work properly, your symbol path ***
  333. *** must point to .pdb files that have full type information. ***
  334. *** ***
  335. *** Certain .pdb files (such as the public OS symbols) do not ***
  336. *** contain the required information. Contact the group that ***
  337. *** provided you with these symbols if you need this command to ***
  338. *** work. ***
  339. *** ***
  340. *** Type referenced: nt!_IMAGE_DOS_HEADER ***
  341. *** ***
  342. *************************************************************************
  343. *************************************************************************
  344. *** ***
  345. *** ***
  346. *** Either you specified an unqualified symbol, or your debugger ***
  347. *** doesn't have full symbol information. Unqualified symbol ***
  348. *** resolution is turned off by default. Please either specify a ***
  349. *** fully qualified symbol module!symbolname, or enable resolution ***
  350. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  351. *** enabling unqualified symbol resolution with network symbol ***
  352. *** server shares in the symbol path may cause the debugger to ***
  353. *** appear to hang for long periods of time when an incorrect ***
  354. *** symbol name is typed or the network symbol server is down. ***
  355. *** ***
  356. *** For some commands to work properly, your symbol path ***
  357. *** must point to .pdb files that have full type information. ***
  358. *** ***
  359. *** Certain .pdb files (such as the public OS symbols) do not ***
  360. *** contain the required information. Contact the group that ***
  361. *** provided you with these symbols if you need this command to ***
  362. *** work. ***
  363. *** ***
  364. *** Type referenced: nt!_IMAGE_DOS_HEADER ***
  365. *** ***
  366. *************************************************************************
  367. *************************************************************************
  368. *** ***
  369. *** ***
  370. *** Either you specified an unqualified symbol, or your debugger ***
  371. *** doesn't have full symbol information. Unqualified symbol ***
  372. *** resolution is turned off by default. Please either specify a ***
  373. *** fully qualified symbol module!symbolname, or enable resolution ***
  374. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  375. *** enabling unqualified symbol resolution with network symbol ***
  376. *** server shares in the symbol path may cause the debugger to ***
  377. *** appear to hang for long periods of time when an incorrect ***
  378. *** symbol name is typed or the network symbol server is down. ***
  379. *** ***
  380. *** For some commands to work properly, your symbol path ***
  381. *** must point to .pdb files that have full type information. ***
  382. *** ***
  383. *** Certain .pdb files (such as the public OS symbols) do not ***
  384. *** contain the required information. Contact the group that ***
  385. *** provided you with these symbols if you need this command to ***
  386. *** work. ***
  387. *** ***
  388. *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
  389. *** ***
  390. *************************************************************************
  391. *************************************************************************
  392. *** ***
  393. *** ***
  394. *** Either you specified an unqualified symbol, or your debugger ***
  395. *** doesn't have full symbol information. Unqualified symbol ***
  396. *** resolution is turned off by default. Please either specify a ***
  397. *** fully qualified symbol module!symbolname, or enable resolution ***
  398. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  399. *** enabling unqualified symbol resolution with network symbol ***
  400. *** server shares in the symbol path may cause the debugger to ***
  401. *** appear to hang for long periods of time when an incorrect ***
  402. *** symbol name is typed or the network symbol server is down. ***
  403. *** ***
  404. *** For some commands to work properly, your symbol path ***
  405. *** must point to .pdb files that have full type information. ***
  406. *** ***
  407. *** Certain .pdb files (such as the public OS symbols) do not ***
  408. *** contain the required information. Contact the group that ***
  409. *** provided you with these symbols if you need this command to ***
  410. *** work. ***
  411. *** ***
  412. *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
  413. *** ***
  414. *************************************************************************
  415. Could not get address of nt!KdVersionBlock.
  416. Could not get address of nt!KdVersionBlock.
  417. Could not get address of nt!KdVersionBlock.
  418. Could not get address of nt!KdVersionBlock.
  419. *************************************************************************
  420. *** ***
  421. *** ***
  422. *** Either you specified an unqualified symbol, or your debugger ***
  423. *** doesn't have full symbol information. Unqualified symbol ***
  424. *** resolution is turned off by default. Please either specify a ***
  425. *** fully qualified symbol module!symbolname, or enable resolution ***
  426. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  427. *** enabling unqualified symbol resolution with network symbol ***
  428. *** server shares in the symbol path may cause the debugger to ***
  429. *** appear to hang for long periods of time when an incorrect ***
  430. *** symbol name is typed or the network symbol server is down. ***
  431. *** ***
  432. *** For some commands to work properly, your symbol path ***
  433. *** must point to .pdb files that have full type information. ***
  434. *** ***
  435. *** Certain .pdb files (such as the public OS symbols) do not ***
  436. *** contain the required information. Contact the group that ***
  437. *** provided you with these symbols if you need this command to ***
  438. *** work. ***
  439. *** ***
  440. *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
  441. *** ***
  442. *************************************************************************
  443. Could not get address of nt!KdVersionBlock.
  444. Could not get address of nt!KdVersionBlock.
  445. *************************************************************************
  446. *** ***
  447. *** ***
  448. *** Either you specified an unqualified symbol, or your debugger ***
  449. *** doesn't have full symbol information. Unqualified symbol ***
  450. *** resolution is turned off by default. Please either specify a ***
  451. *** fully qualified symbol module!symbolname, or enable resolution ***
  452. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  453. *** enabling unqualified symbol resolution with network symbol ***
  454. *** server shares in the symbol path may cause the debugger to ***
  455. *** appear to hang for long periods of time when an incorrect ***
  456. *** symbol name is typed or the network symbol server is down. ***
  457. *** ***
  458. *** For some commands to work properly, your symbol path ***
  459. *** must point to .pdb files that have full type information. ***
  460. *** ***
  461. *** Certain .pdb files (such as the public OS symbols) do not ***
  462. *** contain the required information. Contact the group that ***
  463. *** provided you with these symbols if you need this command to ***
  464. *** work. ***
  465. *** ***
  466. *** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
  467. *** ***
  468. *************************************************************************
  469. *************************************************************************
  470. *** ***
  471. *** ***
  472. *** Either you specified an unqualified symbol, or your debugger ***
  473. *** doesn't have full symbol information. Unqualified symbol ***
  474. *** resolution is turned off by default. Please either specify a ***
  475. *** fully qualified symbol module!symbolname, or enable resolution ***
  476. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  477. *** enabling unqualified symbol resolution with network symbol ***
  478. *** server shares in the symbol path may cause the debugger to ***
  479. *** appear to hang for long periods of time when an incorrect ***
  480. *** symbol name is typed or the network symbol server is down. ***
  481. *** ***
  482. *** For some commands to work properly, your symbol path ***
  483. *** must point to .pdb files that have full type information. ***
  484. *** ***
  485. *** Certain .pdb files (such as the public OS symbols) do not ***
  486. *** contain the required information. Contact the group that ***
  487. *** provided you with these symbols if you need this command to ***
  488. *** work. ***
  489. *** ***
  490. *** Type referenced: nt!_KPRCB ***
  491. *** ***
  492. *************************************************************************
  493. *************************************************************************
  494. *** ***
  495. *** ***
  496. *** Either you specified an unqualified symbol, or your debugger ***
  497. *** doesn't have full symbol information. Unqualified symbol ***
  498. *** resolution is turned off by default. Please either specify a ***
  499. *** fully qualified symbol module!symbolname, or enable resolution ***
  500. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  501. *** enabling unqualified symbol resolution with network symbol ***
  502. *** server shares in the symbol path may cause the debugger to ***
  503. *** appear to hang for long periods of time when an incorrect ***
  504. *** symbol name is typed or the network symbol server is down. ***
  505. *** ***
  506. *** For some commands to work properly, your symbol path ***
  507. *** must point to .pdb files that have full type information. ***
  508. *** ***
  509. *** Certain .pdb files (such as the public OS symbols) do not ***
  510. *** contain the required information. Contact the group that ***
  511. *** provided you with these symbols if you need this command to ***
  512. *** work. ***
  513. *** ***
  514. *** Type referenced: nt!KPRCB ***
  515. *** ***
  516. *************************************************************************
  517. *************************************************************************
  518. *** ***
  519. *** ***
  520. *** Either you specified an unqualified symbol, or your debugger ***
  521. *** doesn't have full symbol information. Unqualified symbol ***
  522. *** resolution is turned off by default. Please either specify a ***
  523. *** fully qualified symbol module!symbolname, or enable resolution ***
  524. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  525. *** enabling unqualified symbol resolution with network symbol ***
  526. *** server shares in the symbol path may cause the debugger to ***
  527. *** appear to hang for long periods of time when an incorrect ***
  528. *** symbol name is typed or the network symbol server is down. ***
  529. *** ***
  530. *** For some commands to work properly, your symbol path ***
  531. *** must point to .pdb files that have full type information. ***
  532. *** ***
  533. *** Certain .pdb files (such as the public OS symbols) do not ***
  534. *** contain the required information. Contact the group that ***
  535. *** provided you with these symbols if you need this command to ***
  536. *** work. ***
  537. *** ***
  538. *** Type referenced: nt!_KPRCB ***
  539. *** ***
  540. *************************************************************************
  541. *************************************************************************
  542. *** ***
  543. *** ***
  544. *** Either you specified an unqualified symbol, or your debugger ***
  545. *** doesn't have full symbol information. Unqualified symbol ***
  546. *** resolution is turned off by default. Please either specify a ***
  547. *** fully qualified symbol module!symbolname, or enable resolution ***
  548. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  549. *** enabling unqualified symbol resolution with network symbol ***
  550. *** server shares in the symbol path may cause the debugger to ***
  551. *** appear to hang for long periods of time when an incorrect ***
  552. *** symbol name is typed or the network symbol server is down. ***
  553. *** ***
  554. *** For some commands to work properly, your symbol path ***
  555. *** must point to .pdb files that have full type information. ***
  556. *** ***
  557. *** Certain .pdb files (such as the public OS symbols) do not ***
  558. *** contain the required information. Contact the group that ***
  559. *** provided you with these symbols if you need this command to ***
  560. *** work. ***
  561. *** ***
  562. *** Type referenced: nt!KPRCB ***
  563. *** ***
  564. *************************************************************************
  565. *************************************************************************
  566. *** ***
  567. *** ***
  568. *** Either you specified an unqualified symbol, or your debugger ***
  569. *** doesn't have full symbol information. Unqualified symbol ***
  570. *** resolution is turned off by default. Please either specify a ***
  571. *** fully qualified symbol module!symbolname, or enable resolution ***
  572. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  573. *** enabling unqualified symbol resolution with network symbol ***
  574. *** server shares in the symbol path may cause the debugger to ***
  575. *** appear to hang for long periods of time when an incorrect ***
  576. *** symbol name is typed or the network symbol server is down. ***
  577. *** ***
  578. *** For some commands to work properly, your symbol path ***
  579. *** must point to .pdb files that have full type information. ***
  580. *** ***
  581. *** Certain .pdb files (such as the public OS symbols) do not ***
  582. *** contain the required information. Contact the group that ***
  583. *** provided you with these symbols if you need this command to ***
  584. *** work. ***
  585. *** ***
  586. *** Type referenced: nt!_KPRCB ***
  587. *** ***
  588. *************************************************************************
  589. *************************************************************************
  590. *** ***
  591. *** ***
  592. *** Either you specified an unqualified symbol, or your debugger ***
  593. *** doesn't have full symbol information. Unqualified symbol ***
  594. *** resolution is turned off by default. Please either specify a ***
  595. *** fully qualified symbol module!symbolname, or enable resolution ***
  596. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  597. *** enabling unqualified symbol resolution with network symbol ***
  598. *** server shares in the symbol path may cause the debugger to ***
  599. *** appear to hang for long periods of time when an incorrect ***
  600. *** symbol name is typed or the network symbol server is down. ***
  601. *** ***
  602. *** For some commands to work properly, your symbol path ***
  603. *** must point to .pdb files that have full type information. ***
  604. *** ***
  605. *** Certain .pdb files (such as the public OS symbols) do not ***
  606. *** contain the required information. Contact the group that ***
  607. *** provided you with these symbols if you need this command to ***
  608. *** work. ***
  609. *** ***
  610. *** Type referenced: nt!_EPROCESS ***
  611. *** ***
  612. *************************************************************************
  613. *************************************************************************
  614. *** ***
  615. *** ***
  616. *** Either you specified an unqualified symbol, or your debugger ***
  617. *** doesn't have full symbol information. Unqualified symbol ***
  618. *** resolution is turned off by default. Please either specify a ***
  619. *** fully qualified symbol module!symbolname, or enable resolution ***
  620. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  621. *** enabling unqualified symbol resolution with network symbol ***
  622. *** server shares in the symbol path may cause the debugger to ***
  623. *** appear to hang for long periods of time when an incorrect ***
  624. *** symbol name is typed or the network symbol server is down. ***
  625. *** ***
  626. *** For some commands to work properly, your symbol path ***
  627. *** must point to .pdb files that have full type information. ***
  628. *** ***
  629. *** Certain .pdb files (such as the public OS symbols) do not ***
  630. *** contain the required information. Contact the group that ***
  631. *** provided you with these symbols if you need this command to ***
  632. *** work. ***
  633. *** ***
  634. *** Type referenced: nt!_KPRCB ***
  635. *** ***
  636. *************************************************************************
  637. *************************************************************************
  638. *** ***
  639. *** ***
  640. *** Either you specified an unqualified symbol, or your debugger ***
  641. *** doesn't have full symbol information. Unqualified symbol ***
  642. *** resolution is turned off by default. Please either specify a ***
  643. *** fully qualified symbol module!symbolname, or enable resolution ***
  644. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  645. *** enabling unqualified symbol resolution with network symbol ***
  646. *** server shares in the symbol path may cause the debugger to ***
  647. *** appear to hang for long periods of time when an incorrect ***
  648. *** symbol name is typed or the network symbol server is down. ***
  649. *** ***
  650. *** For some commands to work properly, your symbol path ***
  651. *** must point to .pdb files that have full type information. ***
  652. *** ***
  653. *** Certain .pdb files (such as the public OS symbols) do not ***
  654. *** contain the required information. Contact the group that ***
  655. *** provided you with these symbols if you need this command to ***
  656. *** work. ***
  657. *** ***
  658. *** Type referenced: nt!_KPRCB ***
  659. *** ***
  660. *************************************************************************
  661. *************************************************************************
  662. *** ***
  663. *** ***
  664. *** Either you specified an unqualified symbol, or your debugger ***
  665. *** doesn't have full symbol information. Unqualified symbol ***
  666. *** resolution is turned off by default. Please either specify a ***
  667. *** fully qualified symbol module!symbolname, or enable resolution ***
  668. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  669. *** enabling unqualified symbol resolution with network symbol ***
  670. *** server shares in the symbol path may cause the debugger to ***
  671. *** appear to hang for long periods of time when an incorrect ***
  672. *** symbol name is typed or the network symbol server is down. ***
  673. *** ***
  674. *** For some commands to work properly, your symbol path ***
  675. *** must point to .pdb files that have full type information. ***
  676. *** ***
  677. *** Certain .pdb files (such as the public OS symbols) do not ***
  678. *** contain the required information. Contact the group that ***
  679. *** provided you with these symbols if you need this command to ***
  680. *** work. ***
  681. *** ***
  682. *** Type referenced: nt!_KPRCB ***
  683. *** ***
  684. *************************************************************************
  685. *************************************************************************
  686. *** ***
  687. *** ***
  688. *** Either you specified an unqualified symbol, or your debugger ***
  689. *** doesn't have full symbol information. Unqualified symbol ***
  690. *** resolution is turned off by default. Please either specify a ***
  691. *** fully qualified symbol module!symbolname, or enable resolution ***
  692. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  693. *** enabling unqualified symbol resolution with network symbol ***
  694. *** server shares in the symbol path may cause the debugger to ***
  695. *** appear to hang for long periods of time when an incorrect ***
  696. *** symbol name is typed or the network symbol server is down. ***
  697. *** ***
  698. *** For some commands to work properly, your symbol path ***
  699. *** must point to .pdb files that have full type information. ***
  700. *** ***
  701. *** Certain .pdb files (such as the public OS symbols) do not ***
  702. *** contain the required information. Contact the group that ***
  703. *** provided you with these symbols if you need this command to ***
  704. *** work. ***
  705. *** ***
  706. *** Type referenced: nt!_KPRCB ***
  707. *** ***
  708. *************************************************************************
  709.  
  710. KEY_VALUES_STRING: 1
  711.  
  712. Key : Analysis.CPU.mSec
  713. Value: 61
  714.  
  715. Key : Analysis.Elapsed.mSec
  716. Value: 70
  717.  
  718. Key : Analysis.IO.Other.Mb
  719. Value: 0
  720.  
  721. Key : Analysis.IO.Read.Mb
  722. Value: 0
  723.  
  724. Key : Analysis.IO.Write.Mb
  725. Value: 0
  726.  
  727. Key : Analysis.Init.CPU.mSec
  728. Value: 218
  729.  
  730. Key : Analysis.Init.Elapsed.mSec
  731. Value: 15706
  732.  
  733. Key : Analysis.Memory.CommitPeak.Mb
  734. Value: 76
  735.  
  736. Key : Bugcheck.Code.LegacyAPI
  737. Value: 0x124
  738.  
  739. Key : Dump.Attributes.AsUlong
  740. Value: 8
  741.  
  742. Key : Dump.Attributes.KernelGeneratedTriageDump
  743. Value: 1
  744.  
  745. Key : Failure.Bucket
  746. Value: WRONG_SYMBOLS_X64_10.0.19041.2787_(WinBuild.160101.0800)_TIMESTAMP_1C64B2DC_nt_wrong_symbols!1C64B2DC1046000
  747.  
  748. Key : Failure.Hash
  749. Value: {f6dae536-b645-d1f2-43e4-7d3d1534b5bc}
  750.  
  751.  
  752. BUGCHECK_CODE: 124
  753.  
  754. BUGCHECK_P1: 0
  755.  
  756. BUGCHECK_P2: ffffc90ed4004028
  757.  
  758. BUGCHECK_P3: bc000800
  759.  
  760. BUGCHECK_P4: 1010135
  761.  
  762. FILE_IN_CAB: 071923-9812-01.dmp
  763.  
  764. ADDITIONAL_DEBUG_TEXT:
  765. You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
  766.  
  767. WRONG_SYMBOLS_TIMESTAMP: 1c64b2dc
  768.  
  769. WRONG_SYMBOLS_SIZE: 1046000
  770.  
  771. FAULTING_MODULE: fffff8074fc00000 nt
  772.  
  773. DUMP_FILE_ATTRIBUTES: 0x8
  774. Kernel Generated Triage Dump
  775.  
  776. BLACKBOXNTFS: 1 (!blackboxntfs)
  777.  
  778.  
  779. BLACKBOXPNP: 1 (!blackboxpnp)
  780.  
  781.  
  782. BLACKBOXWINLOGON: 1
  783.  
  784. CUSTOMER_CRASH_COUNT: 1
  785.  
  786. STACK_TEXT:
  787. ffffab81`96e94938 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
  788.  
  789.  
  790. STACK_COMMAND: .cxr; .ecxr ; kb
  791.  
  792. EXCEPTION_CODE_STR: 1C64B2DC
  793.  
  794. EXCEPTION_STR: WRONG_SYMBOLS
  795.  
  796. PROCESS_NAME: ntoskrnl.wrong.symbols.exe
  797.  
  798. IMAGE_NAME: ntoskrnl.wrong.symbols.exe
  799.  
  800. MODULE_NAME: nt_wrong_symbols
  801.  
  802. SYMBOL_NAME: nt_wrong_symbols!1C64B2DC1046000
  803.  
  804. FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_10.0.19041.2787_(WinBuild.160101.0800)_TIMESTAMP_1C64B2DC_nt_wrong_symbols!1C64B2DC1046000
  805.  
  806. OSPLATFORM_TYPE: x64
  807.  
  808. OSNAME: Windows 10
  809.  
  810. FAILURE_ID_HASH: {f6dae536-b645-d1f2-43e4-7d3d1534b5bc}
  811.  
  812. Followup: MachineOwner
  813. ---------
  814.  
  815.  
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!