Atikmg.sys bsod

[Beast52702]

I just wanted to know if this is hardware or driver related.

Thanks!

BugCheck 116, {fffffa80080fa4e0, fffff88004351768, 0, d}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : atikmpag.sys ( atikmpag+8768 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80080fa4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004351768, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP:
atikmpag+8768
fffff880`04351768 4055 push rbp

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`021689c8 fffff880`02d0a000 : 00000000`00000116 fffffa80`080fa4e0 fffff880`04351768 00000000`00000000 : nt!KeBugCheckEx
fffff880`021689d0 fffff880`02d09d87 : fffff880`04351768 fffffa80`080fa4e0 fffffa80`083c1ab0 fffffa80`08648410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02168a10 fffff880`02db0f07 : fffffa80`080fa4e0 00000000`00000000 fffffa80`083c1ab0 fffffa80`08648410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`02168a40 fffff880`02ddab75 : 00000000`ffffffff 00000000`015d5e05 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02168b20 fffff880`02dd92bb : 00000000`00000102 00000000`00000003 00000000`015d5e05 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02168b50 fffff880`02dac2c6 : ffffffff`ff676980 fffffa80`08648410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02168bf0 fffff880`02dd8e7a : 00000000`00000000 fffffa80`08feb980 00000000`00000080 fffffa80`08648410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02168d00 fffff800`03723e6a : 00000000`fffffc32 fffffa80`08b21b50 fffffa80`06a0b040 fffffa80`08b21b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02168d40 fffff800`0347dec6 : fffff880`02f64180 fffffa80`08b21b50 fffff880`02f6efc0 fffff880`02168e40 : nt!PspSystemThreadStartup+0x5a
fffff880`02168d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+8768
fffff880`04351768 4055 push rbp

SYMBOL_NAME: atikmpag+8768

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f7e4294

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

 

[Layback Bear]

This is not down my alley but I did find this.
AMD Catalyst

 

[writhziden]

In addition to Layback Bear's excellent link: How to troubleshoot “Display driver stopped responding and has recovered”, ATIKMDAG.sys type errors


If you need further help, please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html to help us help you.

 

[Beast52702]

In reference to Layback bear: Thank you for the assist but that link is not strictly applicable as I am running an AMD hd 7950.

I was running computations on my video card when this occurred. My system has been running computations 24/7 for days on end without issue, except this one. *Note* my temps have never exceeded 64 C while at full load for days, as monitored by HW monitor, HWinfo64, and aida64extreme (love this iceQ cooler).

The BSOD attachments are attached. I was just checking if anyone could offhandedly tell me what they thought from that WinDebug script.

The pertinent dump is attached separately, Thanks!

 

[Layback Bear]

I have read some where that MSI Afterburner can cause this problem.

 

[Beast52702]

If it was afterburner wouldn't this be a recurring issue? I have literally run my card at 99% load for 7 days straight with afterburner, BOINC (Berkeley Distributed computing application), and HWinfo64 running the entire time without even a hiccup. So all of a sudden Afterburner just got angry?

7 days+ at full load is more than extensive as far as driver/hardware stability is concerned, that I know. Is there any clue in the dump as to what else could have caused this, or is it effectively just a generic "video driver error"?

 

[Jonathan_King]

It's unfortunately a generic video card error. Given your drivers are fairly up-to-date, I'd suspect it's a hardware flaw. You may try decreasing the clock speed on the GPU for now, or RMAing it if it's still under warranty. A driver update won't hurt but I doubt it will help.

 

[writhziden]

What driver version do you currently have installed? The newer graphics cards have had a lot of problems and the latest driver update was supposed to resolve those. A 0x116 was commonplace with those cards with 12.4 or 12.5 installed, especially if running multiple monitors.


Device Concerns

AODDriver4.1	ROOT\LEGACY_AODDRIVER4.1\0000	This device is not present, is not working properly, or does not have all its drivers installed.

• Use the following sites to help with the AODDriver4.1 issue. Rage3D Discussion Area - View Single Post - The AODDriver4.1 service failed .... Cat 12.2 megaproblems
  
  http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html may help supplement the steps in that link.

Software Concerns:

Start Menu\Programs\MSI Afterburner	BEAST\Michael:Start Menu\Programs\MSI Afterburner	BEAST\Michael
Start Menu\Programs\MSI Kombustor 2.3	Public:Start Menu\Programs\MSI Kombustor 2.3	Public

• MSI Afterburner/RivaTuner is known to cause instability with systems. Please remove the software.
  
  Software based overclocking is not reliable because it does not provide the proper voltage settings through the BIOS for the overclock to work.

Analysis

BugCheck 0x124

You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for the crash.
​

 

[Beast52702]

What is AOD driver, if I do not need it I will completely remove it. Please advise.

Hopefully this BSOD is from Catalyst 12.4 being my current driver version. I am upgrading to 12.7 as soon as it is no longer a beta driver.

-My memory is confirmed stable using Memtest86+ for at least 7 full passes (about 7-9 hrs). and win-diagnostic comes up with nothing.

-CPU is prime stable for 12+ hours and never exceeds 50 C as monitored by HWmonitor

-GPU/VGA is 8 hours furmark extreme burn stable, never exceeding 70 C, How would you recommend I OC my VGA through the Bios???

-If you are referring to old dump files for the 0x124 bugcheck then it is probably from Overclocking. As I stated before, no other dump is pertinent as all the most recent ones except 7-1-12 are from known cause. The rest are all much older and have been dealt with.

Thanks!

 

[Layback Bear]

I mentioned MSI After Burner because of the problems I had with it dropping my video driver and recovering in a second or so. No blue screen. If I wasn't there to see it I would of never known it happened. Of course that doesn't mean you have the same problem. I removed it REVO and all its settings I it hasn't happened again. Removing it for testing helps others help you. You can always install it again if you so desire.

 

[writhziden]

What is AOD driver, if I do not need it I will completely remove it. Please advise.

Hopefully this BSOD is from Catalyst 12.4 being my current driver version. I am upgrading to 12.7 as soon as it is no longer a beta driver.

-My memory is confirmed stable using Memtest86+ for at least 7 full passes (about 7-9 hrs). and win-diagnostic comes up with nothing.

-CPU is prime stable for 12+ hours and never exceeds 50 C as monitored by HWmonitor

-GPU/VGA is 8 hours furmark extreme burn stable, never exceeding 70 C, How would you recommend I OC my VGA through the Bios???

-If you are referring to old dump files for the 0x124 bugcheck then it is probably from Overclocking. As I stated before, no other dump is pertinent as all the most recent ones except 7-1-12 are from known cause. The rest are all much older and have been dealt with.

Thanks!

1. AODDriver often comes with AMD Overdrive or AMD Vision Engine Control Center/Catalyst Control Center. You probably have a corrupted version from an older install of your drivers/software.
   
   
2. Why are you waiting for 12.7? Why not try 12.6?
   
   
3. Memory can pass diagnostics and still be faulty: Finicky RAM.
   
   
4. I do not recommend overclocking your VGA at all for the time being until you are running stable again. When you do overclock, it should be done with the AMD software, not 3rd party software.
   
   
5. STOP 0x124:
   
   

   --------------------------------------------
   --------------------START-------------------
   --------------------------------------------
   Loading Dump File [D:\Kingston\BSODDmpFiles\Beast52702\[B][COLOR="Red"]062712[/COLOR][/B]-21668-01.dmp]
   
   Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
   
   System Uptime: 0 days 0:06:45.016
   
   BugCheck 124, {0, fffffa800835f028, b66cc000, 135}
   
   Probably caused by : AuthenticAMD
   
   WHEA_UNCORRECTABLE_ERROR (124)
   
   DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
   
   PROCESS_NAME:  3DMark11Worklo
   
   STACK_TEXT:  
   fffff880`031dda88 fffff800`03419a3b : 00000000`00000124 00000000`00000000 fffffa80`0835f028 00000000`b66cc000 : nt!KeBugCheckEx
   
   fffff880`031dda88 fffff800`03419a3b : 00000000`00000124 00000000`00000000 fffffa80`0835f028 00000000`b66cc000 : nt!KeBugCheckEx
   fffff880`031dda90 fffff800`035dcb03 : 00000000`00000001 fffffa80`0842bea0 00000000`00000000 fffffa80`0842bef0 : hal!HalBugCheckSystem+0x1e3
   
   fffff880`031dda90 fffff800`035dcb03 : 00000000`00000001 fffffa80`0842bea0 00000000`00000000 fffffa80`0842bef0 : hal!HalBugCheckSystem+0x1e3
   fffff880`031ddad0 fffff800`03419700 : 00000000`00000728 fffffa80`0842bea0 fffff880`031dde30 00000000`1c667700 : nt!WheaReportHwError+0x263
   fffff880`031ddb30 fffff800`03419052 : fffffa80`0842bea0 fffff880`031dde30 fffffa80`0842bea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
   fffff880`031ddc80 fffff800`0340ce8f : 00000000`000000eb 00000000`00000001 fffff880`031ddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
   fffff880`031ddcc0 fffff800`034cdaac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
   fffff880`031ddcf0 fffff800`034cd913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
   fffff880`031dde30 00000001`4006341e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
   00000000`08a0fa90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`4006341e
   
   
   FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
   
   --------------------------------------------
   ---------------------END--------------------
   --------------------------------------------

   The 0x124 BugCheck was from your most recent crash (included in the reports you gave us) that occurred June 27th. Do you have a more recent crash than that?
   
   Your 0x116 was from June 8th, which was even longer ago.​

 

[Beast52702]

I will uninstall afterburner if necessary. I am trying to recreate the same dump. I have been running computations again with all settings and applications running the same as on 7-1-12. It has been at full load for over 12 hours with no issue, same clocks and voltages, no BSOD. A bit odd.

Should I enable driver verifier?

@Writh: the separate attachment on my second post is the minidump file from 7-1-12.

12.7 because it has performance improvements and 12.4 is stable with the computation software I use.

For the time being lets ignore the RAM, I am pretty good with hardware and I did not fully elucidate all the stability testing that I have done on all pieces of my system. It is the software side that I am not as savvy on.

 

[writhziden]

Ah, okay. I missed the latest .dmp. It is very similar to the other .dmp I have, though, and is also a 0x116 as you said.

Interesting the system is stable. Keep monitoring, and let us know if you get further crashes. You may consider updating to 12.6 at some point to see if it helps.

 

[Beast52702]

I will keep her stressing and get back to you guys. I am also going to see what is up with the AOD driver as you mentioned before. Any advice on whether or not to turn on Driver verifier to try to induce a driver crash? Thank you guys for the help.

I'll be in touch,

MP

 

[writhziden]

Driver Verifier probably will not yield anything useful at this time. For now, I think your best bet is to keep trying different graphics card drivers. Your crashes indicate that you likely have a graphics card driver conflict and not another underlying driver problem.

3rd Party Drivers:

Here is a list of your 3rd Party drivers. I have highlighted those that may pose problems in red; you should update them if possible.

[B][COLOR="RED"]Lycosa.sys Fri Jan 18 01:51:42 2008 (4790689E)[/COLOR][/B]
[B][COLOR="RED"]Rt64win7.sys Thu Feb 26 02:04:13 2009 (49A65B0D)[/COLOR][/B]
lirsgt.sys Sun May 17 07:06:57 2009 (4A100BF1)
atksgt.sys Sun May 17 07:36:34 2009 (4A1012E2)
GEARAspiWDM.sys Mon May 18 06:17:04 2009 (4A1151C0)
[B][COLOR="RED"]cmudax3.sys Mon Nov 30 20:31:07 2009 (4B148DFB)[/COLOR][/B]
[B][COLOR="RED"]vHidDev.sys Mon Dec 21 06:49:58 2009 (4B2F7D06)[/COLOR][/B]
amdiox64.sys Thu Feb 18 08:17:53 2010 (4B7D5A21)
amdxata.sys Fri Mar 19 10:18:18 2010 (4BA3A3CA)
danew.sys Tue Mar 23 02:37:33 2010 (4BA87DCD)
[B][COLOR="RED"]nusb3hub.sys Thu Apr 22 19:34:35 2010 (4BD0F92B)[/COLOR][/B]
[B][COLOR="RED"]nusb3xhc.sys Thu Apr 22 19:34:36 2010 (4BD0F92C)[/COLOR][/B]
cpuz133_x64.sys Tue May 11 03:58:57 2010 (4BE92A61)
ElbyCDIO.sys Thu Dec 16 15:58:13 2010 (4D0A9985)
VClone.sys Sat Jan 15 09:21:04 2011 (4D31C970)
RtHDMIVX.sys Wed Jul 6 04:09:50 2011 (4E14346E)
[B][COLOR="RED"]RTCore64.sys Tue Sep 6 06:24:50 2011 (4E661112)[/COLOR][/B]
AODDriver2.sys Tue Mar 6 02:55:00 2012 (4F55DEF4)
cpuz135_x64.sys Fri Mar 9 01:56:55 2012 (4F59C5D7)
MpFilter.sys Fri Mar 9 04:05:26 2012 (4F59E3F6)
atikmpag.sys Thu Apr 5 19:10:44 2012 (4F7E4294)
atikmdag.sys Thu Apr 5 19:48:25 2012 (4F7E4B69)
HWiNFO64A.SYS Thu May 10 07:05:19 2012 (4FABBD0F)

Lycosa.sys
Rt64win7.sys
lirsgt.sys
atksgt.sys
GEARAspiWDM.sys
cmudax3.sys
vHidDev.sys
amdiox64.sys
amdxata.sys
danew.sys
nusb3hub.sys
nusb3xhc.sys
cpuz133_x64.sys
ElbyCDIO.sys
VClone.sys
RtHDMIVX.sys
RTCore64.sys - If you do insist on continuing to use MSI Afterburner, at least make sure it is up to date. There is an update to the software from 2012.
AODDriver2.sys
cpuz135_x64.sys
MpFilter.sys
atikmpag.sys
atikmdag.sys
HWiNFO64A.SYS​