BSOD - Atikmdag.sys + ntoskrnl.exe when playing games, please help!

Scott94

Distinguished
Jan 5, 2012
47
0
18,530
Hopefully someone can solve this once and for all.

When playing Diablo 3 (just lost a hardcore character due to this) my computer crashes to Blue Screen quite often.

In blue screen viewer the cause are : atikmdag.sys + ntoskrnl.exe

==================================================
Dump File : 070214-41605-01.dmp
Crash Time : 02/07/2014 16:49:16
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`0f15ddbb
Parameter 3 : fffff880`057fe228
Parameter 4 : fffff880`057fda80
Caused By Driver : atikmdag.sys
Caused By Address : atikmdag.sys+128f6f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : atikmdag.sys+c7dbb
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070214-41605-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,528
Dump File Time : 02/07/2014 16:50:35
==================================================

I have tried re setting my graphics card... tried completely wiping my hard drive and starting with new drivers. Have tried cleaning my drive re-installing the ATI drivers. Is it just a faulty card?

Is it something to do with my BIOS? Do I need to up date them? Are my motherboard and graphics card not compatible? Should I just buy a nvidia card? (Could it be that I run two mac screens?)


Current comp specs:

I5 3570k
Windows 7
AMD 7870
Gigabyte Z77 D3H (04/25/2012 BIOS)
Ram - 8gb Mushkin
 
Solution
Well, the cause seems easy to diagnose:

Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Which essentially means a kernel level thread died and took the OS down with it. The first Parameter is the important one, and its (as expected) C0000005: STATUS_ACCESS_VIOLATION, meaning RAM got corrupted. And every time, it was the AMD GPU driver that caused the problem. So that probably rules out a problem with the RAM, and points directly at the GPU. Either you ran into a driver bug (they do happen), you overheated the GPU and it locked up, or there is a physical problem with the GPU itself.

First thing, use the latest stable driver. If you are already using that, go back one rev. Also check temps while gaming to make sure they don't...

Scott94

Distinguished
Jan 5, 2012
47
0
18,530
Tried this fix and it happened again:

==================================================
Dump File : 070214-41605-01.dmp
Crash Time : 02/07/2014 16:49:16
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`0f15ddbb
Parameter 3 : fffff880`057fe228
Parameter 4 : fffff880`057fda80
Caused By Driver : atikmdag.sys
Caused By Address : atikmdag.sys+128f6f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : atikmdag.sys+c7dbb
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070214-41605-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,528
Dump File Time : 02/07/2014 16:50:35
==================================================


Any solutions? Is the graphics card just busted?
 

Scott94

Distinguished
Jan 5, 2012
47
0
18,530
So ... as a solution tonight I tried to disable hardware acceleration in my control panel and the button in troubleshooting is grayed out (Also my two monitors are under 'Generic PnP' monitors. But I currently use one Apple Cinema Display and the other is a smaller apple flat screen.

So I tried running Diablo 3 in XP compatibility mode - still crashed. I usually watch catch up t.v. on my other monitor at the same time as playing. But can play for hours and it doesnt crash then suddenly it crashes. Tonight my program had finished on catch up tv before it decided to crash.


==================================================
Dump File : 070814-31028-01.dmp
Crash Time : 08/07/2014 00:37:21
Bug Check String :
Bug Check Code : 0xa0000001
Parameter 1 : 00000000`00000005
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : atikmdag.sys
Caused By Address : atikmdag.sys+28ece
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070814-31028-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 276,528
Dump File Time : 08/07/2014 00:38:40
==================================================

Any other guesses? ... Will buying a NVIDIA GTX 770 fix this issue?

 
Well, the cause seems easy to diagnose:

Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Which essentially means a kernel level thread died and took the OS down with it. The first Parameter is the important one, and its (as expected) C0000005: STATUS_ACCESS_VIOLATION, meaning RAM got corrupted. And every time, it was the AMD GPU driver that caused the problem. So that probably rules out a problem with the RAM, and points directly at the GPU. Either you ran into a driver bug (they do happen), you overheated the GPU and it locked up, or there is a physical problem with the GPU itself.

First thing, use the latest stable driver. If you are already using that, go back one rev. Also check temps while gaming to make sure they don't get too high (90C is my personal redline; they can handle more, but that's pushing it). If temps are OK and changing the driver doesn't fix the problem, then its likely you have a physical GPU problem. Contact the manufacturer of the card and request an RMA. Shouldn't be that hard, since the dumps clearly point at the GPU, rather then another system component.
 
Solution