API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Jan 17th, 2018
107
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 31.36 KB | None | 0 0
raw download clone embed print report
  1. : kd> !analyze -v
  2. *******************************************************************************
  3. * *
  4. * Bugcheck Analysis *
  5. * *
  6. *******************************************************************************
  7.  
  8. WHEA_UNCORRECTABLE_ERROR (124)
  9. A fatal hardware error has occurred. Parameter 1 identifies the type of error
  10. source that reported the error. Parameter 2 holds the address of the
  11. WHEA_ERROR_RECORD structure that describes the error conditon.
  12. Arguments:
  13. Arg1: 0000000000000000, Machine Check Exception
  14. Arg2: ffffb603ddbf5028, Address of the WHEA_ERROR_RECORD structure.
  15. Arg3: 00000000f2001180, High order 32-bits of the MCi_STATUS value.
  16. Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
  17.  
  18. Debugging Details:
  19. ------------------
  20.  
  21. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  22.  
  23. *************************************************************************
  24. *** ***
  25. *** ***
  26. *** Either you specified an unqualified symbol, or your debugger ***
  27. *** doesn't have full symbol information. Unqualified symbol ***
  28. *** resolution is turned off by default. Please either specify a ***
  29. *** fully qualified symbol module!symbolname, or enable resolution ***
  30. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  31. *** enabling unqualified symbol resolution with network symbol ***
  32. *** server shares in the symbol path may cause the debugger to ***
  33. *** appear to hang for long periods of time when an incorrect ***
  34. *** symbol name is typed or the network symbol server is down. ***
  35. *** ***
  36. *** For some commands to work properly, your symbol path ***
  37. *** must point to .pdb files that have full type information. ***
  38. *** ***
  39. *** Certain .pdb files (such as the public OS symbols) do not ***
  40. *** contain the required information. Contact the group that ***
  41. *** provided you with these symbols if you need this command to ***
  42. *** work. ***
  43. *** ***
  44. *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
  45. *** ***
  46. *************************************************************************
  47. *************************************************************************
  48. *** ***
  49. *** ***
  50. *** Either you specified an unqualified symbol, or your debugger ***
  51. *** doesn't have full symbol information. Unqualified symbol ***
  52. *** resolution is turned off by default. Please either specify a ***
  53. *** fully qualified symbol module!symbolname, or enable resolution ***
  54. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  55. *** enabling unqualified symbol resolution with network symbol ***
  56. *** server shares in the symbol path may cause the debugger to ***
  57. *** appear to hang for long periods of time when an incorrect ***
  58. *** symbol name is typed or the network symbol server is down. ***
  59. *** ***
  60. *** For some commands to work properly, your symbol path ***
  61. *** must point to .pdb files that have full type information. ***
  62. *** ***
  63. *** Certain .pdb files (such as the public OS symbols) do not ***
  64. *** contain the required information. Contact the group that ***
  65. *** provided you with these symbols if you need this command to ***
  66. *** work. ***
  67. *** ***
  68. *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
  69. *** ***
  70. *************************************************************************
  71. *************************************************************************
  72. *** ***
  73. *** ***
  74. *** Either you specified an unqualified symbol, or your debugger ***
  75. *** doesn't have full symbol information. Unqualified symbol ***
  76. *** resolution is turned off by default. Please either specify a ***
  77. *** fully qualified symbol module!symbolname, or enable resolution ***
  78. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  79. *** enabling unqualified symbol resolution with network symbol ***
  80. *** server shares in the symbol path may cause the debugger to ***
  81. *** appear to hang for long periods of time when an incorrect ***
  82. *** symbol name is typed or the network symbol server is down. ***
  83. *** ***
  84. *** For some commands to work properly, your symbol path ***
  85. *** must point to .pdb files that have full type information. ***
  86. *** ***
  87. *** Certain .pdb files (such as the public OS symbols) do not ***
  88. *** contain the required information. Contact the group that ***
  89. *** provided you with these symbols if you need this command to ***
  90. *** work. ***
  91. *** ***
  92. *** Type referenced: nt!_KPRCB ***
  93. *** ***
  94. *************************************************************************
  95. *************************************************************************
  96. *** ***
  97. *** ***
  98. *** Either you specified an unqualified symbol, or your debugger ***
  99. *** doesn't have full symbol information. Unqualified symbol ***
  100. *** resolution is turned off by default. Please either specify a ***
  101. *** fully qualified symbol module!symbolname, or enable resolution ***
  102. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  103. *** enabling unqualified symbol resolution with network symbol ***
  104. *** server shares in the symbol path may cause the debugger to ***
  105. *** appear to hang for long periods of time when an incorrect ***
  106. *** symbol name is typed or the network symbol server is down. ***
  107. *** ***
  108. *** For some commands to work properly, your symbol path ***
  109. *** must point to .pdb files that have full type information. ***
  110. *** ***
  111. *** Certain .pdb files (such as the public OS symbols) do not ***
  112. *** contain the required information. Contact the group that ***
  113. *** provided you with these symbols if you need this command to ***
  114. *** work. ***
  115. *** ***
  116. *** Type referenced: nt!KPRCB ***
  117. *** ***
  118. *************************************************************************
  119. *************************************************************************
  120. *** ***
  121. *** ***
  122. *** Either you specified an unqualified symbol, or your debugger ***
  123. *** doesn't have full symbol information. Unqualified symbol ***
  124. *** resolution is turned off by default. Please either specify a ***
  125. *** fully qualified symbol module!symbolname, or enable resolution ***
  126. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  127. *** enabling unqualified symbol resolution with network symbol ***
  128. *** server shares in the symbol path may cause the debugger to ***
  129. *** appear to hang for long periods of time when an incorrect ***
  130. *** symbol name is typed or the network symbol server is down. ***
  131. *** ***
  132. *** For some commands to work properly, your symbol path ***
  133. *** must point to .pdb files that have full type information. ***
  134. *** ***
  135. *** Certain .pdb files (such as the public OS symbols) do not ***
  136. *** contain the required information. Contact the group that ***
  137. *** provided you with these symbols if you need this command to ***
  138. *** work. ***
  139. *** ***
  140. *** Type referenced: nt!_KPRCB ***
  141. *** ***
  142. *************************************************************************
  143. *************************************************************************
  144. *** ***
  145. *** ***
  146. *** Either you specified an unqualified symbol, or your debugger ***
  147. *** doesn't have full symbol information. Unqualified symbol ***
  148. *** resolution is turned off by default. Please either specify a ***
  149. *** fully qualified symbol module!symbolname, or enable resolution ***
  150. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  151. *** enabling unqualified symbol resolution with network symbol ***
  152. *** server shares in the symbol path may cause the debugger to ***
  153. *** appear to hang for long periods of time when an incorrect ***
  154. *** symbol name is typed or the network symbol server is down. ***
  155. *** ***
  156. *** For some commands to work properly, your symbol path ***
  157. *** must point to .pdb files that have full type information. ***
  158. *** ***
  159. *** Certain .pdb files (such as the public OS symbols) do not ***
  160. *** contain the required information. Contact the group that ***
  161. *** provided you with these symbols if you need this command to ***
  162. *** work. ***
  163. *** ***
  164. *** Type referenced: nt!KPRCB ***
  165. *** ***
  166. *************************************************************************
  167. *************************************************************************
  168. *** ***
  169. *** ***
  170. *** Either you specified an unqualified symbol, or your debugger ***
  171. *** doesn't have full symbol information. Unqualified symbol ***
  172. *** resolution is turned off by default. Please either specify a ***
  173. *** fully qualified symbol module!symbolname, or enable resolution ***
  174. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  175. *** enabling unqualified symbol resolution with network symbol ***
  176. *** server shares in the symbol path may cause the debugger to ***
  177. *** appear to hang for long periods of time when an incorrect ***
  178. *** symbol name is typed or the network symbol server is down. ***
  179. *** ***
  180. *** For some commands to work properly, your symbol path ***
  181. *** must point to .pdb files that have full type information. ***
  182. *** ***
  183. *** Certain .pdb files (such as the public OS symbols) do not ***
  184. *** contain the required information. Contact the group that ***
  185. *** provided you with these symbols if you need this command to ***
  186. *** work. ***
  187. *** ***
  188. *** Type referenced: nt!_KPRCB ***
  189. *** ***
  190. *************************************************************************
  191. *************************************************************************
  192. *** ***
  193. *** ***
  194. *** Either you specified an unqualified symbol, or your debugger ***
  195. *** doesn't have full symbol information. Unqualified symbol ***
  196. *** resolution is turned off by default. Please either specify a ***
  197. *** fully qualified symbol module!symbolname, or enable resolution ***
  198. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  199. *** enabling unqualified symbol resolution with network symbol ***
  200. *** server shares in the symbol path may cause the debugger to ***
  201. *** appear to hang for long periods of time when an incorrect ***
  202. *** symbol name is typed or the network symbol server is down. ***
  203. *** ***
  204. *** For some commands to work properly, your symbol path ***
  205. *** must point to .pdb files that have full type information. ***
  206. *** ***
  207. *** Certain .pdb files (such as the public OS symbols) do not ***
  208. *** contain the required information. Contact the group that ***
  209. *** provided you with these symbols if you need this command to ***
  210. *** work. ***
  211. *** ***
  212. *** Type referenced: nt!_EPROCESS ***
  213. *** ***
  214. *************************************************************************
  215. *************************************************************************
  216. *** ***
  217. *** ***
  218. *** Either you specified an unqualified symbol, or your debugger ***
  219. *** doesn't have full symbol information. Unqualified symbol ***
  220. *** resolution is turned off by default. Please either specify a ***
  221. *** fully qualified symbol module!symbolname, or enable resolution ***
  222. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  223. *** enabling unqualified symbol resolution with network symbol ***
  224. *** server shares in the symbol path may cause the debugger to ***
  225. *** appear to hang for long periods of time when an incorrect ***
  226. *** symbol name is typed or the network symbol server is down. ***
  227. *** ***
  228. *** For some commands to work properly, your symbol path ***
  229. *** must point to .pdb files that have full type information. ***
  230. *** ***
  231. *** Certain .pdb files (such as the public OS symbols) do not ***
  232. *** contain the required information. Contact the group that ***
  233. *** provided you with these symbols if you need this command to ***
  234. *** work. ***
  235. *** ***
  236. *** Type referenced: nt!_KPRCB ***
  237. *** ***
  238. *************************************************************************
  239. *************************************************************************
  240. *** ***
  241. *** ***
  242. *** Either you specified an unqualified symbol, or your debugger ***
  243. *** doesn't have full symbol information. Unqualified symbol ***
  244. *** resolution is turned off by default. Please either specify a ***
  245. *** fully qualified symbol module!symbolname, or enable resolution ***
  246. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  247. *** enabling unqualified symbol resolution with network symbol ***
  248. *** server shares in the symbol path may cause the debugger to ***
  249. *** appear to hang for long periods of time when an incorrect ***
  250. *** symbol name is typed or the network symbol server is down. ***
  251. *** ***
  252. *** For some commands to work properly, your symbol path ***
  253. *** must point to .pdb files that have full type information. ***
  254. *** ***
  255. *** Certain .pdb files (such as the public OS symbols) do not ***
  256. *** contain the required information. Contact the group that ***
  257. *** provided you with these symbols if you need this command to ***
  258. *** work. ***
  259. *** ***
  260. *** Type referenced: nt!_KPRCB ***
  261. *** ***
  262. *************************************************************************
  263. *************************************************************************
  264. *** ***
  265. *** ***
  266. *** Either you specified an unqualified symbol, or your debugger ***
  267. *** doesn't have full symbol information. Unqualified symbol ***
  268. *** resolution is turned off by default. Please either specify a ***
  269. *** fully qualified symbol module!symbolname, or enable resolution ***
  270. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  271. *** enabling unqualified symbol resolution with network symbol ***
  272. *** server shares in the symbol path may cause the debugger to ***
  273. *** appear to hang for long periods of time when an incorrect ***
  274. *** symbol name is typed or the network symbol server is down. ***
  275. *** ***
  276. *** For some commands to work properly, your symbol path ***
  277. *** must point to .pdb files that have full type information. ***
  278. *** ***
  279. *** Certain .pdb files (such as the public OS symbols) do not ***
  280. *** contain the required information. Contact the group that ***
  281. *** provided you with these symbols if you need this command to ***
  282. *** work. ***
  283. *** ***
  284. *** Type referenced: nt!_KPRCB ***
  285. *** ***
  286. *************************************************************************
  287. *************************************************************************
  288. *** ***
  289. *** ***
  290. *** Either you specified an unqualified symbol, or your debugger ***
  291. *** doesn't have full symbol information. Unqualified symbol ***
  292. *** resolution is turned off by default. Please either specify a ***
  293. *** fully qualified symbol module!symbolname, or enable resolution ***
  294. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  295. *** enabling unqualified symbol resolution with network symbol ***
  296. *** server shares in the symbol path may cause the debugger to ***
  297. *** appear to hang for long periods of time when an incorrect ***
  298. *** symbol name is typed or the network symbol server is down. ***
  299. *** ***
  300. *** For some commands to work properly, your symbol path ***
  301. *** must point to .pdb files that have full type information. ***
  302. *** ***
  303. *** Certain .pdb files (such as the public OS symbols) do not ***
  304. *** contain the required information. Contact the group that ***
  305. *** provided you with these symbols if you need this command to ***
  306. *** work. ***
  307. *** ***
  308. *** Type referenced: nt!_KPRCB ***
  309. *** ***
  310. *************************************************************************
  311. *************************************************************************
  312. *** ***
  313. *** ***
  314. *** Either you specified an unqualified symbol, or your debugger ***
  315. *** doesn't have full symbol information. Unqualified symbol ***
  316. *** resolution is turned off by default. Please either specify a ***
  317. *** fully qualified symbol module!symbolname, or enable resolution ***
  318. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  319. *** enabling unqualified symbol resolution with network symbol ***
  320. *** server shares in the symbol path may cause the debugger to ***
  321. *** appear to hang for long periods of time when an incorrect ***
  322. *** symbol name is typed or the network symbol server is down. ***
  323. *** ***
  324. *** For some commands to work properly, your symbol path ***
  325. *** must point to .pdb files that have full type information. ***
  326. *** ***
  327. *** Certain .pdb files (such as the public OS symbols) do not ***
  328. *** contain the required information. Contact the group that ***
  329. *** provided you with these symbols if you need this command to ***
  330. *** work. ***
  331. *** ***
  332. *** Type referenced: nt!_KTHREAD ***
  333. *** ***
  334. *************************************************************************
  335. *************************************************************************
  336. *** ***
  337. *** ***
  338. *** Either you specified an unqualified symbol, or your debugger ***
  339. *** doesn't have full symbol information. Unqualified symbol ***
  340. *** resolution is turned off by default. Please either specify a ***
  341. *** fully qualified symbol module!symbolname, or enable resolution ***
  342. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  343. *** enabling unqualified symbol resolution with network symbol ***
  344. *** server shares in the symbol path may cause the debugger to ***
  345. *** appear to hang for long periods of time when an incorrect ***
  346. *** symbol name is typed or the network symbol server is down. ***
  347. *** ***
  348. *** For some commands to work properly, your symbol path ***
  349. *** must point to .pdb files that have full type information. ***
  350. *** ***
  351. *** Certain .pdb files (such as the public OS symbols) do not ***
  352. *** contain the required information. Contact the group that ***
  353. *** provided you with these symbols if you need this command to ***
  354. *** work. ***
  355. *** ***
  356. *** Type referenced: nt!_KPRCB ***
  357. *** ***
  358. *************************************************************************
  359. *************************************************************************
  360. *** ***
  361. *** ***
  362. *** Either you specified an unqualified symbol, or your debugger ***
  363. *** doesn't have full symbol information. Unqualified symbol ***
  364. *** resolution is turned off by default. Please either specify a ***
  365. *** fully qualified symbol module!symbolname, or enable resolution ***
  366. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  367. *** enabling unqualified symbol resolution with network symbol ***
  368. *** server shares in the symbol path may cause the debugger to ***
  369. *** appear to hang for long periods of time when an incorrect ***
  370. *** symbol name is typed or the network symbol server is down. ***
  371. *** ***
  372. *** For some commands to work properly, your symbol path ***
  373. *** must point to .pdb files that have full type information. ***
  374. *** ***
  375. *** Certain .pdb files (such as the public OS symbols) do not ***
  376. *** contain the required information. Contact the group that ***
  377. *** provided you with these symbols if you need this command to ***
  378. *** work. ***
  379. *** ***
  380. *** Type referenced: nt!_KPRCB ***
  381. *** ***
  382. *************************************************************************
  383.  
  384. KEY_VALUES_STRING: 1
  385.  
  386.  
  387. TIMELINE_ANALYSIS: 1
  388.  
  389.  
  390. DUMP_CLASS: 1
  391.  
  392. DUMP_QUALIFIER: 400
  393.  
  394. BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834
  395.  
  396. SYSTEM_MANUFACTURER: System manufacturer
  397.  
  398. SYSTEM_PRODUCT_NAME: System Product Name
  399.  
  400. SYSTEM_SKU: SKU
  401.  
  402. SYSTEM_VERSION: System Version
  403.  
  404. BIOS_VENDOR: American Megatrends Inc.
  405.  
  406. BIOS_VERSION: 3501
  407.  
  408. BIOS_DATE: 06/23/2017
  409.  
  410. BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
  411.  
  412. BASEBOARD_PRODUCT: Z170 PRO GAMING/AURA
  413.  
  414. BASEBOARD_VERSION: Rev X.0x
  415.  
  416. ADDITIONAL_DEBUG_TEXT:
  417. You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
  418.  
  419. WRONG_SYMBOLS_TIMESTAMP: 58ccba4c
  420.  
  421. WRONG_SYMBOLS_SIZE: 889000
  422.  
  423. FAULTING_MODULE: fffff800c4099000 nt
  424.  
  425. DEBUG_FLR_IMAGE_TIMESTAMP: 58ccba4c
  426.  
  427. DUMP_TYPE: 2
  428.  
  429. BUGCHECK_P1: 0
  430.  
  431. BUGCHECK_P2: ffffb603ddbf5028
  432.  
  433. BUGCHECK_P3: f2001180
  434.  
  435. BUGCHECK_P4: 10005
  436.  
  437. BUGCHECK_STR: 58CCBA4C
  438.  
  439. CPU_COUNT: 4
  440.  
  441. CPU_MHZ: ed0
  442.  
  443. CPU_VENDOR: GenuineIntel
  444.  
  445. CPU_FAMILY: 6
  446.  
  447. CPU_MODEL: 9e
  448.  
  449. CPU_STEPPING: 9
  450.  
  451. CPU_MICROCODE: 0,0,0,0 (F,M,S,R) SIG: 42'00000000 (cache) 0'00000000 (init)
  452.  
  453. BLACKBOXBSD: 1 (!blackboxbsd)
  454.  
  455.  
  456. CUSTOMER_CRASH_COUNT: 1
  457.  
  458. CURRENT_IRQL: 0
  459.  
  460. ANALYSIS_SESSION_HOST: GENIE
  461.  
  462. ANALYSIS_SESSION_TIME: 01-18-2018 01:08:40.0636
  463.  
  464. ANALYSIS_VERSION: 10.0.17061.1000 amd64fre
  465.  
  466. STACK_TEXT:
  467. fffff800`c6250a38 fffff800`c40565cf : 00000000`00000124 00000000`00000000 ffffb603`ddbf5028 00000000`f2001180 : nt+0x16bfd0
  468. fffff800`c6250a40 fffff800`c42f4fbd : ffffb603`ddbf5028 ffffb603`dcdce1d0 ffffb603`dcdce1d0 ffffb603`dcdce1d0 : hal!HalBugCheckSystem+0xcf
  469. fffff800`c6250a80 ffffb603`ddbf5028 : ffffb603`dcdce1d0 ffffb603`dcdce1d0 ffffb603`dcdce1d0 00000000`00000000 : nt+0x25bfbd
  470. fffff800`c6250a88 ffffb603`dcdce1d0 : ffffb603`dcdce1d0 ffffb603`dcdce1d0 00000000`00000000 fffff800`c42f4d42 : 0xffffb603`ddbf5028
  471. fffff800`c6250a90 ffffb603`dcdce1d0 : ffffb603`dcdce1d0 00000000`00000000 fffff800`c42f4d42 00000243`a28f8a98 : 0xffffb603`dcdce1d0
  472. fffff800`c6250a98 ffffb603`dcdce1d0 : 00000000`00000000 fffff800`c42f4d42 00000243`a28f8a98 fffff800`c6250e70 : 0xffffb603`dcdce1d0
  473. fffff800`c6250aa0 00000000`00000000 : fffff800`c42f4d42 00000243`a28f8a98 fffff800`c6250e70 00000243`a18f18d0 : 0xffffb603`dcdce1d0
  474.  
  475.  
  476. THREAD_SHA1_HASH_MOD_FUNC: 4367c15b1832150ac74d2cf4fd070be633180022
  477.  
  478. THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 373df9e331dabe282bd16cad790bf2ecd84c3482
  479.  
  480. THREAD_SHA1_HASH_MOD: 00a5f7c7239365b45d5c0fb0a1611ed95434d430
  481.  
  482. FOLLOWUP_NAME: MachineOwner
  483.  
  484. STACK_COMMAND: .thread ; .cxr ; kb
  485.  
  486. EXCEPTION_CODE: (NTSTATUS) 0x58ccba4c - <Unable to get error code text>
  487.  
  488. EXCEPTION_CODE_STR: 58CCBA4C
  489.  
  490. EXCEPTION_STR: WRONG_SYMBOLS
  491.  
  492. PROCESS_NAME: ntoskrnl.wrong.symbols.exe
  493.  
  494. IMAGE_NAME: ntoskrnl.wrong.symbols.exe
  495.  
  496. MODULE_NAME: nt_wrong_symbols
  497.  
  498. SYMBOL_NAME: nt_wrong_symbols!58CCBA4C889000
  499.  
  500. BUCKET_ID: WRONG_SYMBOLS_X64_15063.0.amd64fre.rs2_release.170317-1834_TIMESTAMP_170318-044044
  501.  
  502. DEFAULT_BUCKET_ID: WRONG_SYMBOLS_X64_15063.0.amd64fre.rs2_release.170317-1834_TIMESTAMP_170318-044044
  503.  
  504. PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
  505.  
  506. FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_15063.0.amd64fre.rs2_release.170317-1834_TIMESTAMP_170318-044044_58CCBA4C_nt_wrong_symbols!58CCBA4C889000
  507.  
  508. TARGET_TIME: 2018-01-17T23:49:06.000Z
  509.  
  510. OSBUILD: 15063
  511.  
  512. OSSERVICEPACK: 0
  513.  
  514. SERVICEPACK_NUMBER: 0
  515.  
  516. OS_REVISION: 0
  517.  
  518. SUITE_MASK: 272
  519.  
  520. PRODUCT_TYPE: 1
  521.  
  522. OSPLATFORM_TYPE: x64
  523.  
  524. OSNAME: Windows 10
  525.  
  526. OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
  527.  
  528. OS_LOCALE:
  529.  
  530. USER_LCID: 0
  531.  
  532. OSBUILD_TIMESTAMP: 2017-03-18 05:40:44
  533.  
  534. BUILDDATESTAMP_STR: 170317-1834
  535.  
  536. BUILDLAB_STR: rs2_release
  537.  
  538. BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834
  539.  
  540. ANALYSIS_SESSION_ELAPSED_TIME: 3730
  541.  
  542. ANALYSIS_SOURCE: KM
  543.  
  544. FAILURE_ID_HASH_STRING: km:wrong_symbols_x64_15063.0.amd64fre.rs2_release.170317-1834_timestamp_170318-044044_58ccba4c_nt_wrong_symbols!58ccba4c889000
  545.  
  546. FAILURE_ID_HASH: {da658d9e-592c-6006-339c-d8e2d505eb75}
  547.  
  548. Followup: MachineOwner
  549. ---------
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!