API tools faq
paste
Advertisement
Guest User

crash dump

a guest
Aug 13th, 2015
197
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 37.01 KB | None | 0 0
raw download clone embed print report
  1.  
  2. Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [C:\Users\dt\Desktop\081415-3468-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  9. Symbol search path is: *** Invalid ***
  10. ****************************************************************************
  11. * Symbol loading may be unreliable without a symbol search path. *
  12. * Use .symfix to have the debugger choose a symbol path. *
  13. * After setting your symbol path, use .reload to refresh symbol locations. *
  14. ****************************************************************************
  15. Executable search path is:
  16. *********************************************************************
  17. * Symbols can not be loaded because symbol path is not initialized. *
  18. * *
  19. * The Symbol Path can be set by: *
  20. * using the _NT_SYMBOL_PATH environment variable. *
  21. * using the -y <symbol_path> argument when starting the debugger. *
  22. * using .sympath and .sympath+ *
  23. *********************************************************************
  24. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  25. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  26. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  27. Windows 8 Kernel Version 9600 MP (2 procs) Free x64
  28. Product: WinNt, suite: TerminalServer SingleUserTS
  29. Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
  30. Machine Name:
  31. Kernel base = 0xfffff800`ae281000 PsLoadedModuleList = 0xfffff800`ae545990
  32. Debug session time: Thu Aug 13 23:19:39.985 2015 (UTC + 2:00)
  33. System Uptime: 0 days 0:01:37.647
  34. *********************************************************************
  35. * Symbols can not be loaded because symbol path is not initialized. *
  36. * *
  37. * The Symbol Path can be set by: *
  38. * using the _NT_SYMBOL_PATH environment variable. *
  39. * using the -y <symbol_path> argument when starting the debugger. *
  40. * using .sympath and .sympath+ *
  41. *********************************************************************
  42. Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
  43. *** WARNING: Unable to verify timestamp for ntoskrnl.exe
  44. *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
  45. Loading Kernel Symbols
  46. ...............................................................
  47. ................................................................
  48. ........
  49. Loading User Symbols
  50. Loading unloaded module list
  51. .........
  52.  
  53. ************* Symbol Loading Error Summary **************
  54. Module name Error
  55. ntoskrnl The system cannot find the file specified
  56.  
  57. 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.
  58. You should also verify that your symbol search path (.sympath) is correct.
  59. *** WARNING: Unable to verify timestamp for atikmdag.sys
  60. *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
  61. *******************************************************************************
  62. * *
  63. * Bugcheck Analysis *
  64. * *
  65. *******************************************************************************
  66.  
  67. Use !analyze -v to get detailed debugging information.
  68.  
  69. BugCheck 1000007E, {ffffffffc0000096, fffff8000349dc07, ffffd00023427b88, ffffd00023427390}
  70.  
  71. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  72.  
  73. *************************************************************************
  74. *** ***
  75. *** ***
  76. *** Either you specified an unqualified symbol, or your debugger ***
  77. *** doesn't have full symbol information. Unqualified symbol ***
  78. *** resolution is turned off by default. Please either specify a ***
  79. *** fully qualified symbol module!symbolname, or enable resolution ***
  80. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  81. *** enabling unqualified symbol resolution with network symbol ***
  82. *** server shares in the symbol path may cause the debugger to ***
  83. *** appear to hang for long periods of time when an incorrect ***
  84. *** symbol name is typed or the network symbol server is down. ***
  85. *** ***
  86. *** For some commands to work properly, your symbol path ***
  87. *** must point to .pdb files that have full type information. ***
  88. *** ***
  89. *** Certain .pdb files (such as the public OS symbols) do not ***
  90. *** contain the required information. Contact the group that ***
  91. *** provided you with these symbols if you need this command to ***
  92. *** work. ***
  93. *** ***
  94. *** Type referenced: nt!_KPRCB ***
  95. *** ***
  96. *************************************************************************
  97. *************************************************************************
  98. *** ***
  99. *** ***
  100. *** Either you specified an unqualified symbol, or your debugger ***
  101. *** doesn't have full symbol information. Unqualified symbol ***
  102. *** resolution is turned off by default. Please either specify a ***
  103. *** fully qualified symbol module!symbolname, or enable resolution ***
  104. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  105. *** enabling unqualified symbol resolution with network symbol ***
  106. *** server shares in the symbol path may cause the debugger to ***
  107. *** appear to hang for long periods of time when an incorrect ***
  108. *** symbol name is typed or the network symbol server is down. ***
  109. *** ***
  110. *** For some commands to work properly, your symbol path ***
  111. *** must point to .pdb files that have full type information. ***
  112. *** ***
  113. *** Certain .pdb files (such as the public OS symbols) do not ***
  114. *** contain the required information. Contact the group that ***
  115. *** provided you with these symbols if you need this command to ***
  116. *** work. ***
  117. *** ***
  118. *** Type referenced: nt!KPRCB ***
  119. *** ***
  120. *************************************************************************
  121. *************************************************************************
  122. *** ***
  123. *** ***
  124. *** Either you specified an unqualified symbol, or your debugger ***
  125. *** doesn't have full symbol information. Unqualified symbol ***
  126. *** resolution is turned off by default. Please either specify a ***
  127. *** fully qualified symbol module!symbolname, or enable resolution ***
  128. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  129. *** enabling unqualified symbol resolution with network symbol ***
  130. *** server shares in the symbol path may cause the debugger to ***
  131. *** appear to hang for long periods of time when an incorrect ***
  132. *** symbol name is typed or the network symbol server is down. ***
  133. *** ***
  134. *** For some commands to work properly, your symbol path ***
  135. *** must point to .pdb files that have full type information. ***
  136. *** ***
  137. *** Certain .pdb files (such as the public OS symbols) do not ***
  138. *** contain the required information. Contact the group that ***
  139. *** provided you with these symbols if you need this command to ***
  140. *** work. ***
  141. *** ***
  142. *** Type referenced: nt!_KPRCB ***
  143. *** ***
  144. *************************************************************************
  145. *************************************************************************
  146. *** ***
  147. *** ***
  148. *** Either you specified an unqualified symbol, or your debugger ***
  149. *** doesn't have full symbol information. Unqualified symbol ***
  150. *** resolution is turned off by default. Please either specify a ***
  151. *** fully qualified symbol module!symbolname, or enable resolution ***
  152. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  153. *** enabling unqualified symbol resolution with network symbol ***
  154. *** server shares in the symbol path may cause the debugger to ***
  155. *** appear to hang for long periods of time when an incorrect ***
  156. *** symbol name is typed or the network symbol server is down. ***
  157. *** ***
  158. *** For some commands to work properly, your symbol path ***
  159. *** must point to .pdb files that have full type information. ***
  160. *** ***
  161. *** Certain .pdb files (such as the public OS symbols) do not ***
  162. *** contain the required information. Contact the group that ***
  163. *** provided you with these symbols if you need this command to ***
  164. *** work. ***
  165. *** ***
  166. *** Type referenced: nt!KPRCB ***
  167. *** ***
  168. *************************************************************************
  169. *************************************************************************
  170. *** ***
  171. *** ***
  172. *** Either you specified an unqualified symbol, or your debugger ***
  173. *** doesn't have full symbol information. Unqualified symbol ***
  174. *** resolution is turned off by default. Please either specify a ***
  175. *** fully qualified symbol module!symbolname, or enable resolution ***
  176. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  177. *** enabling unqualified symbol resolution with network symbol ***
  178. *** server shares in the symbol path may cause the debugger to ***
  179. *** appear to hang for long periods of time when an incorrect ***
  180. *** symbol name is typed or the network symbol server is down. ***
  181. *** ***
  182. *** For some commands to work properly, your symbol path ***
  183. *** must point to .pdb files that have full type information. ***
  184. *** ***
  185. *** Certain .pdb files (such as the public OS symbols) do not ***
  186. *** contain the required information. Contact the group that ***
  187. *** provided you with these symbols if you need this command to ***
  188. *** work. ***
  189. *** ***
  190. *** Type referenced: nt!_KPRCB ***
  191. *** ***
  192. *************************************************************************
  193. *************************************************************************
  194. *** ***
  195. *** ***
  196. *** Either you specified an unqualified symbol, or your debugger ***
  197. *** doesn't have full symbol information. Unqualified symbol ***
  198. *** resolution is turned off by default. Please either specify a ***
  199. *** fully qualified symbol module!symbolname, or enable resolution ***
  200. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  201. *** enabling unqualified symbol resolution with network symbol ***
  202. *** server shares in the symbol path may cause the debugger to ***
  203. *** appear to hang for long periods of time when an incorrect ***
  204. *** symbol name is typed or the network symbol server is down. ***
  205. *** ***
  206. *** For some commands to work properly, your symbol path ***
  207. *** must point to .pdb files that have full type information. ***
  208. *** ***
  209. *** Certain .pdb files (such as the public OS symbols) do not ***
  210. *** contain the required information. Contact the group that ***
  211. *** provided you with these symbols if you need this command to ***
  212. *** work. ***
  213. *** ***
  214. *** Type referenced: nt!_KPRCB ***
  215. *** ***
  216. *************************************************************************
  217. *************************************************************************
  218. *** ***
  219. *** ***
  220. *** Either you specified an unqualified symbol, or your debugger ***
  221. *** doesn't have full symbol information. Unqualified symbol ***
  222. *** resolution is turned off by default. Please either specify a ***
  223. *** fully qualified symbol module!symbolname, or enable resolution ***
  224. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  225. *** enabling unqualified symbol resolution with network symbol ***
  226. *** server shares in the symbol path may cause the debugger to ***
  227. *** appear to hang for long periods of time when an incorrect ***
  228. *** symbol name is typed or the network symbol server is down. ***
  229. *** ***
  230. *** For some commands to work properly, your symbol path ***
  231. *** must point to .pdb files that have full type information. ***
  232. *** ***
  233. *** Certain .pdb files (such as the public OS symbols) do not ***
  234. *** contain the required information. Contact the group that ***
  235. *** provided you with these symbols if you need this command to ***
  236. *** work. ***
  237. *** ***
  238. *** Type referenced: nt!_KPRCB ***
  239. *** ***
  240. *************************************************************************
  241. *************************************************************************
  242. *** ***
  243. *** ***
  244. *** Either you specified an unqualified symbol, or your debugger ***
  245. *** doesn't have full symbol information. Unqualified symbol ***
  246. *** resolution is turned off by default. Please either specify a ***
  247. *** fully qualified symbol module!symbolname, or enable resolution ***
  248. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  249. *** enabling unqualified symbol resolution with network symbol ***
  250. *** server shares in the symbol path may cause the debugger to ***
  251. *** appear to hang for long periods of time when an incorrect ***
  252. *** symbol name is typed or the network symbol server is down. ***
  253. *** ***
  254. *** For some commands to work properly, your symbol path ***
  255. *** must point to .pdb files that have full type information. ***
  256. *** ***
  257. *** Certain .pdb files (such as the public OS symbols) do not ***
  258. *** contain the required information. Contact the group that ***
  259. *** provided you with these symbols if you need this command to ***
  260. *** work. ***
  261. *** ***
  262. *** Type referenced: nt!_KPRCB ***
  263. *** ***
  264. *************************************************************************
  265. Probably caused by : atikmdag.sys ( atikmdag+1dac07 )
  266.  
  267. Followup: MachineOwner
  268. ---------
  269.  
  270. 0: kd> !analyze -v
  271. *******************************************************************************
  272. * *
  273. * Bugcheck Analysis *
  274. * *
  275. *******************************************************************************
  276.  
  277. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
  278. This is a very common bugcheck. Usually the exception address pinpoints
  279. the driver/function that caused the problem. Always note this address
  280. as well as the link date of the driver/image that contains this address.
  281. Some common problems are exception code 0x80000003. This means a hard
  282. coded breakpoint or assertion was hit, but this system was booted
  283. /NODEBUG. This is not supposed to happen as developers should never have
  284. hardcoded breakpoints in retail code, but ...
  285. If this happens, make sure a debugger gets connected, and the
  286. system is booted /DEBUG. This will let us see why this breakpoint is
  287. happening.
  288. Arguments:
  289. Arg1: ffffffffc0000096, The exception code that was not handled
  290. Arg2: fffff8000349dc07, The address that the exception occurred at
  291. Arg3: ffffd00023427b88, Exception Record Address
  292. Arg4: ffffd00023427390, Context Record Address
  293.  
  294. Debugging Details:
  295. ------------------
  296.  
  297. ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
  298.  
  299. *************************************************************************
  300. *** ***
  301. *** ***
  302. *** Either you specified an unqualified symbol, or your debugger ***
  303. *** doesn't have full symbol information. Unqualified symbol ***
  304. *** resolution is turned off by default. Please either specify a ***
  305. *** fully qualified symbol module!symbolname, or enable resolution ***
  306. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  307. *** enabling unqualified symbol resolution with network symbol ***
  308. *** server shares in the symbol path may cause the debugger to ***
  309. *** appear to hang for long periods of time when an incorrect ***
  310. *** symbol name is typed or the network symbol server is down. ***
  311. *** ***
  312. *** For some commands to work properly, your symbol path ***
  313. *** must point to .pdb files that have full type information. ***
  314. *** ***
  315. *** Certain .pdb files (such as the public OS symbols) do not ***
  316. *** contain the required information. Contact the group that ***
  317. *** provided you with these symbols if you need this command to ***
  318. *** work. ***
  319. *** ***
  320. *** Type referenced: nt!_KPRCB ***
  321. *** ***
  322. *************************************************************************
  323. *************************************************************************
  324. *** ***
  325. *** ***
  326. *** Either you specified an unqualified symbol, or your debugger ***
  327. *** doesn't have full symbol information. Unqualified symbol ***
  328. *** resolution is turned off by default. Please either specify a ***
  329. *** fully qualified symbol module!symbolname, or enable resolution ***
  330. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  331. *** enabling unqualified symbol resolution with network symbol ***
  332. *** server shares in the symbol path may cause the debugger to ***
  333. *** appear to hang for long periods of time when an incorrect ***
  334. *** symbol name is typed or the network symbol server is down. ***
  335. *** ***
  336. *** For some commands to work properly, your symbol path ***
  337. *** must point to .pdb files that have full type information. ***
  338. *** ***
  339. *** Certain .pdb files (such as the public OS symbols) do not ***
  340. *** contain the required information. Contact the group that ***
  341. *** provided you with these symbols if you need this command to ***
  342. *** work. ***
  343. *** ***
  344. *** Type referenced: nt!KPRCB ***
  345. *** ***
  346. *************************************************************************
  347. *************************************************************************
  348. *** ***
  349. *** ***
  350. *** Either you specified an unqualified symbol, or your debugger ***
  351. *** doesn't have full symbol information. Unqualified symbol ***
  352. *** resolution is turned off by default. Please either specify a ***
  353. *** fully qualified symbol module!symbolname, or enable resolution ***
  354. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  355. *** enabling unqualified symbol resolution with network symbol ***
  356. *** server shares in the symbol path may cause the debugger to ***
  357. *** appear to hang for long periods of time when an incorrect ***
  358. *** symbol name is typed or the network symbol server is down. ***
  359. *** ***
  360. *** For some commands to work properly, your symbol path ***
  361. *** must point to .pdb files that have full type information. ***
  362. *** ***
  363. *** Certain .pdb files (such as the public OS symbols) do not ***
  364. *** contain the required information. Contact the group that ***
  365. *** provided you with these symbols if you need this command to ***
  366. *** work. ***
  367. *** ***
  368. *** Type referenced: nt!_KPRCB ***
  369. *** ***
  370. *************************************************************************
  371. *************************************************************************
  372. *** ***
  373. *** ***
  374. *** Either you specified an unqualified symbol, or your debugger ***
  375. *** doesn't have full symbol information. Unqualified symbol ***
  376. *** resolution is turned off by default. Please either specify a ***
  377. *** fully qualified symbol module!symbolname, or enable resolution ***
  378. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  379. *** enabling unqualified symbol resolution with network symbol ***
  380. *** server shares in the symbol path may cause the debugger to ***
  381. *** appear to hang for long periods of time when an incorrect ***
  382. *** symbol name is typed or the network symbol server is down. ***
  383. *** ***
  384. *** For some commands to work properly, your symbol path ***
  385. *** must point to .pdb files that have full type information. ***
  386. *** ***
  387. *** Certain .pdb files (such as the public OS symbols) do not ***
  388. *** contain the required information. Contact the group that ***
  389. *** provided you with these symbols if you need this command to ***
  390. *** work. ***
  391. *** ***
  392. *** Type referenced: nt!KPRCB ***
  393. *** ***
  394. *************************************************************************
  395. *************************************************************************
  396. *** ***
  397. *** ***
  398. *** Either you specified an unqualified symbol, or your debugger ***
  399. *** doesn't have full symbol information. Unqualified symbol ***
  400. *** resolution is turned off by default. Please either specify a ***
  401. *** fully qualified symbol module!symbolname, or enable resolution ***
  402. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  403. *** enabling unqualified symbol resolution with network symbol ***
  404. *** server shares in the symbol path may cause the debugger to ***
  405. *** appear to hang for long periods of time when an incorrect ***
  406. *** symbol name is typed or the network symbol server is down. ***
  407. *** ***
  408. *** For some commands to work properly, your symbol path ***
  409. *** must point to .pdb files that have full type information. ***
  410. *** ***
  411. *** Certain .pdb files (such as the public OS symbols) do not ***
  412. *** contain the required information. Contact the group that ***
  413. *** provided you with these symbols if you need this command to ***
  414. *** work. ***
  415. *** ***
  416. *** Type referenced: nt!_KPRCB ***
  417. *** ***
  418. *************************************************************************
  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: nt!_KPRCB ***
  441. *** ***
  442. *************************************************************************
  443. *************************************************************************
  444. *** ***
  445. *** ***
  446. *** Either you specified an unqualified symbol, or your debugger ***
  447. *** doesn't have full symbol information. Unqualified symbol ***
  448. *** resolution is turned off by default. Please either specify a ***
  449. *** fully qualified symbol module!symbolname, or enable resolution ***
  450. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  451. *** enabling unqualified symbol resolution with network symbol ***
  452. *** server shares in the symbol path may cause the debugger to ***
  453. *** appear to hang for long periods of time when an incorrect ***
  454. *** symbol name is typed or the network symbol server is down. ***
  455. *** ***
  456. *** For some commands to work properly, your symbol path ***
  457. *** must point to .pdb files that have full type information. ***
  458. *** ***
  459. *** Certain .pdb files (such as the public OS symbols) do not ***
  460. *** contain the required information. Contact the group that ***
  461. *** provided you with these symbols if you need this command to ***
  462. *** work. ***
  463. *** ***
  464. *** Type referenced: nt!_KPRCB ***
  465. *** ***
  466. *************************************************************************
  467. *************************************************************************
  468. *** ***
  469. *** ***
  470. *** Either you specified an unqualified symbol, or your debugger ***
  471. *** doesn't have full symbol information. Unqualified symbol ***
  472. *** resolution is turned off by default. Please either specify a ***
  473. *** fully qualified symbol module!symbolname, or enable resolution ***
  474. *** of unqualified symbols by typing ".symopt- 100". Note that ***
  475. *** enabling unqualified symbol resolution with network symbol ***
  476. *** server shares in the symbol path may cause the debugger to ***
  477. *** appear to hang for long periods of time when an incorrect ***
  478. *** symbol name is typed or the network symbol server is down. ***
  479. *** ***
  480. *** For some commands to work properly, your symbol path ***
  481. *** must point to .pdb files that have full type information. ***
  482. *** ***
  483. *** Certain .pdb files (such as the public OS symbols) do not ***
  484. *** contain the required information. Contact the group that ***
  485. *** provided you with these symbols if you need this command to ***
  486. *** work. ***
  487. *** ***
  488. *** Type referenced: nt!_KPRCB ***
  489. *** ***
  490. *************************************************************************
  491.  
  492. ADDITIONAL_DEBUG_TEXT:
  493. You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
  494.  
  495. FAULTING_MODULE: fffff800ae281000 nt
  496.  
  497. DEBUG_FLR_IMAGE_TIMESTAMP: 55c03174
  498.  
  499. EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {EXCEPTION} Privileged instruction.
  500.  
  501. FAULTING_IP:
  502. atikmdag+1dac07
  503. fffff800`0349dc07 0f33 rdpmc
  504.  
  505. EXCEPTION_RECORD: ffffd00023427b88 -- (.exr 0xffffd00023427b88)
  506. ExceptionAddress: fffff8000349dc07 (atikmdag+0x00000000001dac07)
  507. ExceptionCode: c0000096
  508. ExceptionFlags: 00000000
  509. NumberParameters: 0
  510.  
  511. CONTEXT: ffffd00023427390 -- (.cxr 0xffffd00023427390;r)
  512. rax=ffffffff05f9e652 rbx=ffffffff05f9e652 rcx=0000000000000000
  513. rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
  514. rip=fffff8000349dc07 rsp=ffffd00023427dc8 rbp=ffffd00023427f80
  515. r8=0000000000000001 r9=0000000000100000 r10=0000000000000000
  516. r11=ffffffff05f9e652 r12=0000000000000001 r13=0000000000000000
  517. r14=0000000000000000 r15=0000000000000000
  518. iopl=0 nv up ei ng nz na pe nc
  519. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
  520. atikmdag+0x1dac07:
  521. fffff800`0349dc07 0f33 rdpmc
  522. Last set context:
  523. rax=ffffffff05f9e652 rbx=ffffffff05f9e652 rcx=0000000000000000
  524. rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
  525. rip=fffff8000349dc07 rsp=ffffd00023427dc8 rbp=ffffd00023427f80
  526. r8=0000000000000001 r9=0000000000100000 r10=0000000000000000
  527. r11=ffffffff05f9e652 r12=0000000000000001 r13=0000000000000000
  528. r14=0000000000000000 r15=0000000000000000
  529. iopl=0 nv up ei ng nz na pe nc
  530. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
  531. atikmdag+0x1dac07:
  532. fffff800`0349dc07 0f33 rdpmc
  533. Resetting default scope
  534.  
  535. CUSTOMER_CRASH_COUNT: 1
  536.  
  537. DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
  538.  
  539. BUGCHECK_STR: AV
  540.  
  541. CURRENT_IRQL: 0
  542.  
  543. ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
  544.  
  545. LAST_CONTROL_TRANSFER: from fffff80003493d1b to fffff8000349dc07
  546.  
  547. STACK_TEXT:
  548. ffffd000`23427dc8 fffff800`03493d1b : ffffd000`22f28000 00000000`0000c000 ffffd000`23427f80 fffff800`04058b2c : atikmdag+0x1dac07
  549. ffffd000`23427dd0 ffffd000`22f28000 : 00000000`0000c000 ffffd000`23427f80 fffff800`04058b2c 00000000`00001549 : atikmdag+0x1d0d1b
  550. ffffd000`23427dd8 00000000`0000c000 : ffffd000`23427f80 fffff800`04058b2c 00000000`00001549 ffffe000`014a9010 : 0xffffd000`22f28000
  551. ffffd000`23427de0 ffffd000`23427f80 : fffff800`04058b2c 00000000`00001549 ffffe000`014a9010 00000000`00000000 : 0xc000
  552. ffffd000`23427de8 fffff800`04058b2c : 00000000`00001549 ffffe000`014a9010 00000000`00000000 0000001f`23428360 : 0xffffd000`23427f80
  553. ffffd000`23427df0 00000000`00001549 : ffffe000`014a9010 00000000`00000000 0000001f`23428360 00000013`00000008 : atikmdag+0xd95b2c
  554. ffffd000`23427df8 ffffe000`014a9010 : 00000000`00000000 0000001f`23428360 00000013`00000008 00001549`00000001 : 0x1549
  555. ffffd000`23427e00 00000000`00000000 : 0000001f`23428360 00000013`00000008 00001549`00000001 00000000`00000000 : 0xffffe000`014a9010
  556.  
  557.  
  558. FOLLOWUP_IP:
  559. atikmdag+1dac07
  560. fffff800`0349dc07 0f33 rdpmc
  561.  
  562. SYMBOL_STACK_INDEX: 0
  563.  
  564. SYMBOL_NAME: atikmdag+1dac07
  565.  
  566. FOLLOWUP_NAME: MachineOwner
  567.  
  568. MODULE_NAME: atikmdag
  569.  
  570. IMAGE_NAME: atikmdag.sys
  571.  
  572. STACK_COMMAND: .cxr 0xffffd00023427390 ; kb
  573.  
  574. BUCKET_ID: WRONG_SYMBOLS
  575.  
  576. FAILURE_BUCKET_ID: WRONG_SYMBOLS
  577.  
  578. ANALYSIS_SOURCE: KM
  579.  
  580. FAILURE_ID_HASH_STRING: km:wrong_symbols
  581.  
  582. FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
  583.  
  584. Followup: MachineOwner
  585. ---------
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!