Atikmg.sys bsod

writhziden · 03 Jul 2012

Beast52702 said:

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!

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.
Why are you waiting for 12.7? Why not try 12.6?
Memory can pass diagnostics and still be faulty: Finicky RAM.
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.

STOP 0x124:

Code:

--------------------------------------------
--------------------START-------------------
--------------------------------------------
Loading Dump File [D:\Kingston\BSODDmpFiles\Beast52702\062712-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 · 03 Jul 2012

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 · 03 Jul 2012

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 · 03 Jul 2012

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 · 03 Jul 2012

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.

Code:

Lycosa.sys Fri Jan 18 01:51:42 2008 (4790689E)
Rt64win7.sys Thu Feb 26 02:04:13 2009 (49A65B0D)
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)
cmudax3.sys Mon Nov 30 20:31:07 2009 (4B148DFB)
vHidDev.sys Mon Dec 21 06:49:58 2009 (4B2F7D06)
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)
nusb3hub.sys Thu Apr 22 19:34:35 2010 (4BD0F92B)
nusb3xhc.sys Thu Apr 22 19:34:36 2010 (4BD0F92C)
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)
RTCore64.sys Tue Sep 6 06:24:50 2011 (4E661112)
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