API tools faq
paste
Advertisement
Vavun

Untitled

Vavun
Jan 9th, 2018
499
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 54.63 KB | None | 0 0
raw download clone embed print report
  1.  
  2. Microsoft (R) Windows Debugger Version 10.0.16299.15 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [D:\Desktop\102816-20046-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. Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
  13.  
  14. ************* Path validation summary **************
  15. Response Time (ms) Location
  16. Deferred srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
  17. Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
  18. Executable search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
  19. Unable to load image \SystemRoot\system32\xNtKrnl.exe, Win32 error 0n2
  20. *** WARNING: Unable to verify timestamp for xNtKrnl.exe
  21. *** ERROR: Module load completed but symbols could not be loaded for xNtKrnl.exe
  22. Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
  23. Product: WinNt, suite: TerminalServer SingleUserTS
  24. Built by: 7601.23564.amd64fre.win7sp1_ldr.160930-0600
  25. Machine Name:
  26. Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`030a4730
  27. Debug session time: Thu Oct 27 23:05:42.888 2016 (UTC + 3:00)
  28. System Uptime: 2 days 5:15:28.700
  29. Unable to load image \SystemRoot\system32\xNtKrnl.exe, Win32 error 0n2
  30. *** WARNING: Unable to verify timestamp for xNtKrnl.exe
  31. *** ERROR: Module load completed but symbols could not be loaded for xNtKrnl.exe
  32. Loading Kernel 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. xNtKrnl 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 116, {fffffa801db354e0, fffff8800fdb57cc, 0, 2}
  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!_KPRCB ***
  249. *** ***
  250. *************************************************************************
  251. *** WARNING: Unable to verify timestamp for nvlddmkm.sys
  252. *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
  253. *************************************************************************
  254. *** ***
  255. *** ***
  256. *** Either you specified an unqualified symbol, or your debugger ***
  257. *** doesn't have full symbol information. Unqualified symbol ***
  258. *** resolution is turned off by default. Please either specify a ***
  259. *** fully qualified symbol module!symbolname, or enable resolution ***
  260. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  261. *** enabling unqualified symbol resolution with network symbol ***
  262. *** server shares in the symbol path may cause the debugger to ***
  263. *** appear to hang for long periods of time when an incorrect ***
  264. *** symbol name is typed or the network symbol server is down. ***
  265. *** ***
  266. *** For some commands to work properly, your symbol path ***
  267. *** must point to .pdb files that have full type information. ***
  268. *** ***
  269. *** Certain .pdb files (such as the public OS symbols) do not ***
  270. *** contain the required information. Contact the group that ***
  271. *** provided you with these symbols if you need this command to ***
  272. *** work. ***
  273. *** ***
  274. *** Type referenced: nt!_KPRCB ***
  275. *** ***
  276. *************************************************************************
  277. *************************************************************************
  278. *** ***
  279. *** ***
  280. *** Either you specified an unqualified symbol, or your debugger ***
  281. *** doesn't have full symbol information. Unqualified symbol ***
  282. *** resolution is turned off by default. Please either specify a ***
  283. *** fully qualified symbol module!symbolname, or enable resolution ***
  284. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  285. *** enabling unqualified symbol resolution with network symbol ***
  286. *** server shares in the symbol path may cause the debugger to ***
  287. *** appear to hang for long periods of time when an incorrect ***
  288. *** symbol name is typed or the network symbol server is down. ***
  289. *** ***
  290. *** For some commands to work properly, your symbol path ***
  291. *** must point to .pdb files that have full type information. ***
  292. *** ***
  293. *** Certain .pdb files (such as the public OS symbols) do not ***
  294. *** contain the required information. Contact the group that ***
  295. *** provided you with these symbols if you need this command to ***
  296. *** work. ***
  297. *** ***
  298. *** Type referenced: nt!_KTHREAD ***
  299. *** ***
  300. *************************************************************************
  301. *************************************************************************
  302. *** ***
  303. *** ***
  304. *** Either you specified an unqualified symbol, or your debugger ***
  305. *** doesn't have full symbol information. Unqualified symbol ***
  306. *** resolution is turned off by default. Please either specify a ***
  307. *** fully qualified symbol module!symbolname, or enable resolution ***
  308. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  309. *** enabling unqualified symbol resolution with network symbol ***
  310. *** server shares in the symbol path may cause the debugger to ***
  311. *** appear to hang for long periods of time when an incorrect ***
  312. *** symbol name is typed or the network symbol server is down. ***
  313. *** ***
  314. *** For some commands to work properly, your symbol path ***
  315. *** must point to .pdb files that have full type information. ***
  316. *** ***
  317. *** Certain .pdb files (such as the public OS symbols) do not ***
  318. *** contain the required information. Contact the group that ***
  319. *** provided you with these symbols if you need this command to ***
  320. *** work. ***
  321. *** ***
  322. *** Type referenced: nt!_KPRCB ***
  323. *** ***
  324. *************************************************************************
  325. *************************************************************************
  326. *** ***
  327. *** ***
  328. *** Either you specified an unqualified symbol, or your debugger ***
  329. *** doesn't have full symbol information. Unqualified symbol ***
  330. *** resolution is turned off by default. Please either specify a ***
  331. *** fully qualified symbol module!symbolname, or enable resolution ***
  332. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  333. *** enabling unqualified symbol resolution with network symbol ***
  334. *** server shares in the symbol path may cause the debugger to ***
  335. *** appear to hang for long periods of time when an incorrect ***
  336. *** symbol name is typed or the network symbol server is down. ***
  337. *** ***
  338. *** For some commands to work properly, your symbol path ***
  339. *** must point to .pdb files that have full type information. ***
  340. *** ***
  341. *** Certain .pdb files (such as the public OS symbols) do not ***
  342. *** contain the required information. Contact the group that ***
  343. *** provided you with these symbols if you need this command to ***
  344. *** work. ***
  345. *** ***
  346. *** Type referenced: nt!_KPRCB ***
  347. *** ***
  348. *************************************************************************
  349. Probably caused by : ntoskrnl.wrong.symbols.exe ( nt_wrong_symbols!57EE7D5A5E6000 )
  350.  
  351. Followup: MachineOwner
  352. ---------
  353.  
  354. 3: kd> kd: Reading initial command '!analyze -v; !cpuid; !sysinfo cpuinfo; !sysinfo cpuspeed; !sysinfo machineid; q'
  355. *******************************************************************************
  356. * *
  357. * Bugcheck Analysis *
  358. * *
  359. *******************************************************************************
  360.  
  361. VIDEO_TDR_FAILURE (116)
  362. Attempt to reset the display driver and recover from timeout failed.
  363. Arguments:
  364. Arg1: fffffa801db354e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
  365. Arg2: fffff8800fdb57cc, The pointer into responsible device driver module (e.g. owner tag).
  366. Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
  367. Arg4: 0000000000000002, Optional internal context dependent data.
  368.  
  369. Debugging Details:
  370. ------------------
  371.  
  372. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  373.  
  374. *************************************************************************
  375. *** ***
  376. *** ***
  377. *** Either you specified an unqualified symbol, or your debugger ***
  378. *** doesn't have full symbol information. Unqualified symbol ***
  379. *** resolution is turned off by default. Please either specify a ***
  380. *** fully qualified symbol module!symbolname, or enable resolution ***
  381. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  382. *** enabling unqualified symbol resolution with network symbol ***
  383. *** server shares in the symbol path may cause the debugger to ***
  384. *** appear to hang for long periods of time when an incorrect ***
  385. *** symbol name is typed or the network symbol server is down. ***
  386. *** ***
  387. *** For some commands to work properly, your symbol path ***
  388. *** must point to .pdb files that have full type information. ***
  389. *** ***
  390. *** Certain .pdb files (such as the public OS symbols) do not ***
  391. *** contain the required information. Contact the group that ***
  392. *** provided you with these symbols if you need this command to ***
  393. *** work. ***
  394. *** ***
  395. *** Type referenced: nt!_KPRCB ***
  396. *** ***
  397. *************************************************************************
  398. *************************************************************************
  399. *** ***
  400. *** ***
  401. *** Either you specified an unqualified symbol, or your debugger ***
  402. *** doesn't have full symbol information. Unqualified symbol ***
  403. *** resolution is turned off by default. Please either specify a ***
  404. *** fully qualified symbol module!symbolname, or enable resolution ***
  405. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  406. *** enabling unqualified symbol resolution with network symbol ***
  407. *** server shares in the symbol path may cause the debugger to ***
  408. *** appear to hang for long periods of time when an incorrect ***
  409. *** symbol name is typed or the network symbol server is down. ***
  410. *** ***
  411. *** For some commands to work properly, your symbol path ***
  412. *** must point to .pdb files that have full type information. ***
  413. *** ***
  414. *** Certain .pdb files (such as the public OS symbols) do not ***
  415. *** contain the required information. Contact the group that ***
  416. *** provided you with these symbols if you need this command to ***
  417. *** work. ***
  418. *** ***
  419. *** Type referenced: nt!KPRCB ***
  420. *** ***
  421. *************************************************************************
  422. *************************************************************************
  423. *** ***
  424. *** ***
  425. *** Either you specified an unqualified symbol, or your debugger ***
  426. *** doesn't have full symbol information. Unqualified symbol ***
  427. *** resolution is turned off by default. Please either specify a ***
  428. *** fully qualified symbol module!symbolname, or enable resolution ***
  429. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  430. *** enabling unqualified symbol resolution with network symbol ***
  431. *** server shares in the symbol path may cause the debugger to ***
  432. *** appear to hang for long periods of time when an incorrect ***
  433. *** symbol name is typed or the network symbol server is down. ***
  434. *** ***
  435. *** For some commands to work properly, your symbol path ***
  436. *** must point to .pdb files that have full type information. ***
  437. *** ***
  438. *** Certain .pdb files (such as the public OS symbols) do not ***
  439. *** contain the required information. Contact the group that ***
  440. *** provided you with these symbols if you need this command to ***
  441. *** work. ***
  442. *** ***
  443. *** Type referenced: nt!_KPRCB ***
  444. *** ***
  445. *************************************************************************
  446. *************************************************************************
  447. *** ***
  448. *** ***
  449. *** Either you specified an unqualified symbol, or your debugger ***
  450. *** doesn't have full symbol information. Unqualified symbol ***
  451. *** resolution is turned off by default. Please either specify a ***
  452. *** fully qualified symbol module!symbolname, or enable resolution ***
  453. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  454. *** enabling unqualified symbol resolution with network symbol ***
  455. *** server shares in the symbol path may cause the debugger to ***
  456. *** appear to hang for long periods of time when an incorrect ***
  457. *** symbol name is typed or the network symbol server is down. ***
  458. *** ***
  459. *** For some commands to work properly, your symbol path ***
  460. *** must point to .pdb files that have full type information. ***
  461. *** ***
  462. *** Certain .pdb files (such as the public OS symbols) do not ***
  463. *** contain the required information. Contact the group that ***
  464. *** provided you with these symbols if you need this command to ***
  465. *** work. ***
  466. *** ***
  467. *** Type referenced: nt!KPRCB ***
  468. *** ***
  469. *************************************************************************
  470. *************************************************************************
  471. *** ***
  472. *** ***
  473. *** Either you specified an unqualified symbol, or your debugger ***
  474. *** doesn't have full symbol information. Unqualified symbol ***
  475. *** resolution is turned off by default. Please either specify a ***
  476. *** fully qualified symbol module!symbolname, or enable resolution ***
  477. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  478. *** enabling unqualified symbol resolution with network symbol ***
  479. *** server shares in the symbol path may cause the debugger to ***
  480. *** appear to hang for long periods of time when an incorrect ***
  481. *** symbol name is typed or the network symbol server is down. ***
  482. *** ***
  483. *** For some commands to work properly, your symbol path ***
  484. *** must point to .pdb files that have full type information. ***
  485. *** ***
  486. *** Certain .pdb files (such as the public OS symbols) do not ***
  487. *** contain the required information. Contact the group that ***
  488. *** provided you with these symbols if you need this command to ***
  489. *** work. ***
  490. *** ***
  491. *** Type referenced: nt!_KPRCB ***
  492. *** ***
  493. *************************************************************************
  494. *************************************************************************
  495. *** ***
  496. *** ***
  497. *** Either you specified an unqualified symbol, or your debugger ***
  498. *** doesn't have full symbol information. Unqualified symbol ***
  499. *** resolution is turned off by default. Please either specify a ***
  500. *** fully qualified symbol module!symbolname, or enable resolution ***
  501. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  502. *** enabling unqualified symbol resolution with network symbol ***
  503. *** server shares in the symbol path may cause the debugger to ***
  504. *** appear to hang for long periods of time when an incorrect ***
  505. *** symbol name is typed or the network symbol server is down. ***
  506. *** ***
  507. *** For some commands to work properly, your symbol path ***
  508. *** must point to .pdb files that have full type information. ***
  509. *** ***
  510. *** Certain .pdb files (such as the public OS symbols) do not ***
  511. *** contain the required information. Contact the group that ***
  512. *** provided you with these symbols if you need this command to ***
  513. *** work. ***
  514. *** ***
  515. *** Type referenced: nt!_EPROCESS ***
  516. *** ***
  517. *************************************************************************
  518. *************************************************************************
  519. *** ***
  520. *** ***
  521. *** Either you specified an unqualified symbol, or your debugger ***
  522. *** doesn't have full symbol information. Unqualified symbol ***
  523. *** resolution is turned off by default. Please either specify a ***
  524. *** fully qualified symbol module!symbolname, or enable resolution ***
  525. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  526. *** enabling unqualified symbol resolution with network symbol ***
  527. *** server shares in the symbol path may cause the debugger to ***
  528. *** appear to hang for long periods of time when an incorrect ***
  529. *** symbol name is typed or the network symbol server is down. ***
  530. *** ***
  531. *** For some commands to work properly, your symbol path ***
  532. *** must point to .pdb files that have full type information. ***
  533. *** ***
  534. *** Certain .pdb files (such as the public OS symbols) do not ***
  535. *** contain the required information. Contact the group that ***
  536. *** provided you with these symbols if you need this command to ***
  537. *** work. ***
  538. *** ***
  539. *** Type referenced: nt!_KPRCB ***
  540. *** ***
  541. *************************************************************************
  542. *************************************************************************
  543. *** ***
  544. *** ***
  545. *** Either you specified an unqualified symbol, or your debugger ***
  546. *** doesn't have full symbol information. Unqualified symbol ***
  547. *** resolution is turned off by default. Please either specify a ***
  548. *** fully qualified symbol module!symbolname, or enable resolution ***
  549. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  550. *** enabling unqualified symbol resolution with network symbol ***
  551. *** server shares in the symbol path may cause the debugger to ***
  552. *** appear to hang for long periods of time when an incorrect ***
  553. *** symbol name is typed or the network symbol server is down. ***
  554. *** ***
  555. *** For some commands to work properly, your symbol path ***
  556. *** must point to .pdb files that have full type information. ***
  557. *** ***
  558. *** Certain .pdb files (such as the public OS symbols) do not ***
  559. *** contain the required information. Contact the group that ***
  560. *** provided you with these symbols if you need this command to ***
  561. *** work. ***
  562. *** ***
  563. *** Type referenced: nt!_KPRCB ***
  564. *** ***
  565. *************************************************************************
  566. *************************************************************************
  567. *** ***
  568. *** ***
  569. *** Either you specified an unqualified symbol, or your debugger ***
  570. *** doesn't have full symbol information. Unqualified symbol ***
  571. *** resolution is turned off by default. Please either specify a ***
  572. *** fully qualified symbol module!symbolname, or enable resolution ***
  573. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  574. *** enabling unqualified symbol resolution with network symbol ***
  575. *** server shares in the symbol path may cause the debugger to ***
  576. *** appear to hang for long periods of time when an incorrect ***
  577. *** symbol name is typed or the network symbol server is down. ***
  578. *** ***
  579. *** For some commands to work properly, your symbol path ***
  580. *** must point to .pdb files that have full type information. ***
  581. *** ***
  582. *** Certain .pdb files (such as the public OS symbols) do not ***
  583. *** contain the required information. Contact the group that ***
  584. *** provided you with these symbols if you need this command to ***
  585. *** work. ***
  586. *** ***
  587. *** Type referenced: nt!_KPRCB ***
  588. *** ***
  589. *************************************************************************
  590. *************************************************************************
  591. *** ***
  592. *** ***
  593. *** Either you specified an unqualified symbol, or your debugger ***
  594. *** doesn't have full symbol information. Unqualified symbol ***
  595. *** resolution is turned off by default. Please either specify a ***
  596. *** fully qualified symbol module!symbolname, or enable resolution ***
  597. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  598. *** enabling unqualified symbol resolution with network symbol ***
  599. *** server shares in the symbol path may cause the debugger to ***
  600. *** appear to hang for long periods of time when an incorrect ***
  601. *** symbol name is typed or the network symbol server is down. ***
  602. *** ***
  603. *** For some commands to work properly, your symbol path ***
  604. *** must point to .pdb files that have full type information. ***
  605. *** ***
  606. *** Certain .pdb files (such as the public OS symbols) do not ***
  607. *** contain the required information. Contact the group that ***
  608. *** provided you with these symbols if you need this command to ***
  609. *** work. ***
  610. *** ***
  611. *** Type referenced: nt!_KTHREAD ***
  612. *** ***
  613. *************************************************************************
  614. *************************************************************************
  615. *** ***
  616. *** ***
  617. *** Either you specified an unqualified symbol, or your debugger ***
  618. *** doesn't have full symbol information. Unqualified symbol ***
  619. *** resolution is turned off by default. Please either specify a ***
  620. *** fully qualified symbol module!symbolname, or enable resolution ***
  621. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  622. *** enabling unqualified symbol resolution with network symbol ***
  623. *** server shares in the symbol path may cause the debugger to ***
  624. *** appear to hang for long periods of time when an incorrect ***
  625. *** symbol name is typed or the network symbol server is down. ***
  626. *** ***
  627. *** For some commands to work properly, your symbol path ***
  628. *** must point to .pdb files that have full type information. ***
  629. *** ***
  630. *** Certain .pdb files (such as the public OS symbols) do not ***
  631. *** contain the required information. Contact the group that ***
  632. *** provided you with these symbols if you need this command to ***
  633. *** work. ***
  634. *** ***
  635. *** Type referenced: nt!_KPRCB ***
  636. *** ***
  637. *************************************************************************
  638. *************************************************************************
  639. *** ***
  640. *** ***
  641. *** Either you specified an unqualified symbol, or your debugger ***
  642. *** doesn't have full symbol information. Unqualified symbol ***
  643. *** resolution is turned off by default. Please either specify a ***
  644. *** fully qualified symbol module!symbolname, or enable resolution ***
  645. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  646. *** enabling unqualified symbol resolution with network symbol ***
  647. *** server shares in the symbol path may cause the debugger to ***
  648. *** appear to hang for long periods of time when an incorrect ***
  649. *** symbol name is typed or the network symbol server is down. ***
  650. *** ***
  651. *** For some commands to work properly, your symbol path ***
  652. *** must point to .pdb files that have full type information. ***
  653. *** ***
  654. *** Certain .pdb files (such as the public OS symbols) do not ***
  655. *** contain the required information. Contact the group that ***
  656. *** provided you with these symbols if you need this command to ***
  657. *** work. ***
  658. *** ***
  659. *** Type referenced: nt!_KPRCB ***
  660. *** ***
  661. *************************************************************************
  662.  
  663. DUMP_CLASS: 1
  664.  
  665. DUMP_QUALIFIER: 400
  666.  
  667. BUILD_VERSION_STRING: 7601.23564.amd64fre.win7sp1_ldr.160930-0600
  668.  
  669. SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
  670.  
  671. SYSTEM_PRODUCT_NAME: To be filled by O.E.M.
  672.  
  673. SYSTEM_SKU: To be filled by O.E.M.
  674.  
  675. SYSTEM_VERSION: To be filled by O.E.M.
  676.  
  677. BIOS_VENDOR: American Megatrends Inc.
  678.  
  679. BIOS_VERSION: F7
  680.  
  681. BIOS_DATE: 08/24/2012
  682.  
  683. BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
  684.  
  685. BASEBOARD_PRODUCT: Z77P-D3
  686.  
  687. BASEBOARD_VERSION: x.x
  688.  
  689. ADDITIONAL_DEBUG_TEXT:
  690. You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
  691.  
  692. WRONG_SYMBOLS_TIMESTAMP: 57ee7d5a
  693.  
  694. WRONG_SYMBOLS_SIZE: 5e6000
  695.  
  696. FAULTING_MODULE: fffff80002e62000 nt
  697.  
  698. DEBUG_FLR_IMAGE_TIMESTAMP: 57ee7d5a
  699.  
  700. DUMP_TYPE: 2
  701.  
  702. BUGCHECK_P1: fffffa801db354e0
  703.  
  704. BUGCHECK_P2: fffff8800fdb57cc
  705.  
  706. BUGCHECK_P3: 0
  707.  
  708. BUGCHECK_P4: 2
  709.  
  710. FAULTING_IP:
  711. nvlddmkm+1547cc
  712. fffff880`0fdb57cc 48ff256dca7200 jmp qword ptr [nvlddmkm+0x881240 (fffff880`104e2240)]
  713.  
  714. CPU_COUNT: 4
  715.  
  716. CPU_MHZ: ce7
  717.  
  718. CPU_VENDOR: GenuineIntel
  719.  
  720. CPU_FAMILY: 6
  721.  
  722. CPU_MODEL: 2a
  723.  
  724. CPU_STEPPING: 7
  725.  
  726. CPU_MICROCODE: 0,0,0,0 (F,M,S,R) SIG: 28'00000000 (cache) 0'00000000 (init)
  727.  
  728. CUSTOMER_CRASH_COUNT: 1
  729.  
  730. CURRENT_IRQL: 0
  731.  
  732. ANALYSIS_SESSION_HOST: VAVUN-DESKTOP
  733.  
  734. ANALYSIS_SESSION_TIME: 01-10-2018 08:33:51.0758
  735.  
  736. ANALYSIS_VERSION: 10.0.16299.15 amd64fre
  737.  
  738. STACK_TEXT:
  739. fffff880`03806888 fffff880`1095b1f0 : 00000000`00000116 fffffa80`1db354e0 fffff880`0fdb57cc 00000000`00000000 : nt+0x6f440
  740. fffff880`03806890 fffff880`1095aefa : fffff880`0fdb57cc fffffa80`1db354e0 fffffa80`11e6ad50 fffffa80`11e8f410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
  741. fffff880`038068d0 fffff880`0fc0ffbf : fffffa80`1db354e0 00000000`00000000 fffffa80`11e6ad50 fffffa80`11e8f410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
  742. fffff880`03806900 fffff880`0fc39d09 : 00000000`ffffffff 00000000`00bb881c 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
  743. fffff880`038069e0 fffff880`0fc3844f : 00000000`00000102 00000000`00000000 00000000`00bb881c 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
  744. fffff880`03806a10 fffff880`0fc0b2e6 : ffffffff`ff676980 fffffa80`11e8f410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
  745. fffff880`03806ab0 fffff880`0fc3800e : 00000000`00000000 fffffa80`189f36a0 00000000`00000080 fffffa80`11e8f410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
  746. fffff880`03806bc0 fffff800`0316d29a : 00000000`fffffc32 fffffa80`11e948b0 fffffa80`0c76d040 fffffa80`11e948b0 : dxgmms1!VidSchiWorkerThread+0xba
  747. fffff880`03806c00 00000000`fffffc32 : fffffa80`11e948b0 fffffa80`0c76d040 fffffa80`11e948b0 fffffa80`0c76d040 : nt+0x30b29a
  748. fffff880`03806c08 fffffa80`11e948b0 : fffffa80`0c76d040 fffffa80`11e948b0 fffffa80`0c76d040 00000000`00000000 : 0xfffffc32
  749. fffff880`03806c10 fffffa80`0c76d040 : fffffa80`11e948b0 fffffa80`0c76d040 00000000`00000000 00000000`00000000 : 0xfffffa80`11e948b0
  750. fffff880`03806c18 fffffa80`11e948b0 : fffffa80`0c76d040 00000000`00000000 00000000`00000000 fffff800`02ec36e6 : 0xfffffa80`0c76d040
  751. fffff880`03806c20 fffffa80`0c76d040 : 00000000`00000000 00000000`00000000 fffff800`02ec36e6 fffff880`009eb180 : 0xfffffa80`11e948b0
  752. fffff880`03806c28 00000000`00000000 : 00000000`00000000 fffff800`02ec36e6 fffff880`009eb180 fffffa80`11e948b0 : 0xfffffa80`0c76d040
  753.  
  754.  
  755. THREAD_SHA1_HASH_MOD_FUNC: 43ddc415ece026d081f52f3f362a4e8fc085215c
  756.  
  757. THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 41b180ae85df9e77385d0ba0bcf304e32dd725a0
  758.  
  759. THREAD_SHA1_HASH_MOD: d7976a974b3a43b3067131cc477ad653132b3df6
  760.  
  761. FOLLOWUP_IP:
  762. nvlddmkm+1547cc
  763. fffff880`0fdb57cc 48ff256dca7200 jmp qword ptr [nvlddmkm+0x881240 (fffff880`104e2240)]
  764.  
  765. FAULT_INSTR_CODE: 6d25ff48
  766.  
  767. FOLLOWUP_NAME: MachineOwner
  768.  
  769. STACK_COMMAND: .thread ; .cxr ; kb
  770.  
  771. BUGCHECK_STR: 57EE7D5A
  772.  
  773. EXCEPTION_CODE: (NTSTATUS) 0x57ee7d5a - <Unable to get error code text>
  774.  
  775. EXCEPTION_CODE_STR: 57EE7D5A
  776.  
  777. EXCEPTION_STR: WRONG_SYMBOLS
  778.  
  779. PROCESS_NAME: ntoskrnl.wrong.symbols.exe
  780.  
  781. IMAGE_NAME: ntoskrnl.wrong.symbols.exe
  782.  
  783. MODULE_NAME: nt_wrong_symbols
  784.  
  785. SYMBOL_NAME: nt_wrong_symbols!57EE7D5A5E6000
  786.  
  787. BUCKET_ID: WRONG_SYMBOLS_X64_7601.23564.amd64fre.win7sp1_ldr.160930-0600_TIMESTAMP_160930-145730
  788.  
  789. DEFAULT_BUCKET_ID: WRONG_SYMBOLS_X64_7601.23564.amd64fre.win7sp1_ldr.160930-0600_TIMESTAMP_160930-145730
  790.  
  791. PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
  792.  
  793. FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_7601.23564.amd64fre.win7sp1_ldr.160930-0600_TIMESTAMP_160930-145730_57EE7D5A_nt_wrong_symbols!57EE7D5A5E6000
  794.  
  795. TARGET_TIME: 2016-10-27T20:05:42.000Z
  796.  
  797. OSBUILD: 7601
  798.  
  799. OSSERVICEPACK: 1000
  800.  
  801. SERVICEPACK_NUMBER: 0
  802.  
  803. OS_REVISION: 0
  804.  
  805. SUITE_MASK: 272
  806.  
  807. PRODUCT_TYPE: 1
  808.  
  809. OSPLATFORM_TYPE: x64
  810.  
  811. OSNAME: Windows 7
  812.  
  813. OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
  814.  
  815. OS_LOCALE:
  816.  
  817. USER_LCID: 0
  818.  
  819. OSBUILD_TIMESTAMP: 2016-09-30 17:57:30
  820.  
  821. BUILDDATESTAMP_STR: 160930-0600
  822.  
  823. BUILDLAB_STR: win7sp1_ldr
  824.  
  825. BUILDOSVER_STR: 6.1.7601.23564.amd64fre.win7sp1_ldr.160930-0600
  826.  
  827. ANALYSIS_SESSION_ELAPSED_TIME: 10b4
  828.  
  829. ANALYSIS_SOURCE: KM
  830.  
  831. FAILURE_ID_HASH_STRING: km:wrong_symbols_x64_7601.23564.amd64fre.win7sp1_ldr.160930-0600_timestamp_160930-145730_57ee7d5a_nt_wrong_symbols!57ee7d5a5e6000
  832.  
  833. FAILURE_ID_HASH: {05978981-f025-5046-3fe4-4b08fb64063e}
  834.  
  835. Followup: MachineOwner
  836. ---------
  837.  
  838. Unable to get information for processor 0
  839. Unable to get information for processor 1
  840. Unable to get information for processor 2
  841. *************************************************************************
  842. *** ***
  843. *** ***
  844. *** Either you specified an unqualified symbol, or your debugger ***
  845. *** doesn't have full symbol information. Unqualified symbol ***
  846. *** resolution is turned off by default. Please either specify a ***
  847. *** fully qualified symbol module!symbolname, or enable resolution ***
  848. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  849. *** enabling unqualified symbol resolution with network symbol ***
  850. *** server shares in the symbol path may cause the debugger to ***
  851. *** appear to hang for long periods of time when an incorrect ***
  852. *** symbol name is typed or the network symbol server is down. ***
  853. *** ***
  854. *** For some commands to work properly, your symbol path ***
  855. *** must point to .pdb files that have full type information. ***
  856. *** ***
  857. *** Certain .pdb files (such as the public OS symbols) do not ***
  858. *** contain the required information. Contact the group that ***
  859. *** provided you with these symbols if you need this command to ***
  860. *** work. ***
  861. *** ***
  862. *** Type referenced: nt!_KPRCB ***
  863. *** ***
  864. *************************************************************************
  865. CP F/M/S Manufacturer MHz
  866. 3 6,42,7 GenuineIntel 3303
  867. [CPU Information]
  868. ~MHz = REG_DWORD 3303
  869. Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
  870. Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
  871. Identifier = REG_SZ Intel64 Family 6 Model 42 Stepping 7
  872. ProcessorNameString = REG_SZ Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
  873. Update Signature = REG_BINARY 0,0,0,0,28,0,0,0
  874. Update Status = REG_DWORD 2
  875. VendorIdentifier = REG_SZ GenuineIntel
  876. MSR8B = REG_QWORD 2800000000
  877. CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
  878. MaxSpeed: 3300
  879. CurrentSpeed: 3303
  880. Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=3161]
  881. BiosMajorRelease = 4
  882. BiosMinorRelease = 6
  883. BiosVendor = American Megatrends Inc.
  884. BiosVersion = F7
  885. BiosReleaseDate = 08/24/2012
  886. SystemManufacturer = Gigabyte Technology Co., Ltd.
  887. SystemProductName = To be filled by O.E.M.
  888. SystemFamily = To be filled by O.E.M.
  889. SystemVersion = To be filled by O.E.M.
  890. SystemSKU = To be filled by O.E.M.
  891. BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
  892. BaseBoardProduct = Z77P-D3
  893. BaseBoardVersion = x.x
  894. quit:
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!