BSOD when gaming (Possibly atikmdag.sys related?)

S

sheldonjace

Member
Joined
Feb 10, 2014
Posts
9
Issues and what I've tried:
-Issue: When running games on moderate to high graphic settings, my PC seems to handle everything flawlessly. No FPS drops, abnormal temps, stutters, etc. However after a random amount of time and in an assortment of different games, it will BlueScreen and reboot at some point. Whether it be 30min, 2hrs, 4hrs, etc...it will happen

-I've tried: Tried updating to latest ATI drivers using different methods (DriverSweeper, no CCC, etc). Fresh install of Windows 7 after formatting HDD. Kept my install minimal so the software I have currently installed is basically nothing. On this current fresh install I went for the latest beta ATI drivers (14.1?) just to see if it were the previous ones that caused the bug...no dice. Ran Memtest for 8 passes and returned 7 errors, so I tried a friends 1 stick of RAM...no dice.

I've included the attached files for BSOD info as recommended in this post: (jcgriff2's post​) View attachment BSOD info.zip

· OS: Windows 7
· x86 (32-bit) or x64?: x64
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?: Full Retail
· Age of system (hardware): Approx 5-6 months
· Age of OS installation - have you re-installed the OS?: 1 day

· CPU: AMD FX-6300
· Video Card: Gigabyte 7870ghz ed.· MotherBoard: Gigabyte 78lmt-usb3 Rev4.1
· Power Supply - brand & wattage: Silverstone 500w

(If this helps, this is my PCpartpicker list)
PCPartPicker part list / Price breakdown by merchant / Benchmarks


CPU: AMD FX-6300 3.5GHz 6-Core Processor (Purchased For $120.00)
CPU Cooler: Cooler Master Hyper 212 EVO 82.9 CFM Sleeve Bearing CPU Cooler (Purchased For $35.00)
Motherboard: Gigabyte GA-78LMT-USB3 Micro ATX AM3+ Motherboard (Purchased For $65.00)
Memory: Corsair Vengeance 8GB (2 x 4GB) DDR3-1600 Memory (Purchased For $89.99)
Storage: Western Digital Caviar Blue 500GB 3.5" 7200RPM Internal Hard Drive (Purchased For $55.00)
Storage: Western Digital Caviar Blue 640GB 3.5" 7200RPM Internal Hard Drive (Purchased For $0.00)
Video Card: Gigabyte Radeon HD 7870 2GB Video Card (Purchased For $230.00)
Case: Silverstone SG09B (Black) MicroATX Mini Tower Case (Purchased For $89.99)
Case Fan: Cooler Master Blade Master 40.8 CFM 80mm Fan (Purchased For $7.50)
Case Fan: Cooler Master Blade Master 54.8 CFM 92mm Fan (Purchased For $9.50)
Case Fan: Cooler Master Blade Master 54.8 CFM 92mm Fan (Purchased For $9.50)
Power Supply: Silverstone Strider Plus 500W 80+ Bronze Certified Fully-Modular ATX Power Supply (Purchased For $74.99)
Optical Drive: Samsung SN-208BB DVD/CD Writer (Purchased For $35.00)
Operating System: Microsoft Windows 7 Ultimate SP1 (OEM) (64-bit) (Purchased For $0.00)
Keyboard: Microsoft Keyboard 200 Wired Standard Keyboard (Purchased For $10.00)
Mouse: SteelSeries Kinzu V2 Blue Wired Optical Mouse (Purchased For $15.00)
Speakers: Cyber Acoustics CA3550RB 68W 2.1ch Speakers (Purchased For $35.00)
Headphones: SteelSeries Siberia v2 Headset (Purchased For $60.00)
Other: Silverstone PP05 Short Cable for PSU Set ($19.99)
Other: SteelSeries QcK Gaming Mouse Pad ($12.21)
Other: Samsung SyncMaster 2253BW (Purchased For $100.00)
Total: $1073.67
(Prices include shipping, taxes, and discounts when available.)
(Generated by PCPartPicker 2014-02-10 23:44 EST-0500)


I'm begging for help at this point! I have plans to upgrade to a Mid ATX tower/Motherboard/maybe PSU soon but I really don't want to upgrade if I can't find out what the true cause of this issue is. Whether it be strictly software/driver related or hardware related.

I greatly appreciate advance!
 
Hi,

Both of the attached DMP files are of the Unknown bugcheck code (a0000001) bug check.

This is an AMD/ATI-based only bug check. If we take a look at the call stack:

Code: 
4: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0305b5d8 fffff880`1302924e : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0305b5e0 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : [COLOR=#ff0000][I][B]atikmdag+0x2824e[/B][/I][/COLOR]
fffff880`0305b5e8 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`08e19000 : 0xa0000001
fffff880`0305b5f0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`08e19000 00000000`00000000 : 0x5

We can see that the AMD/ATI video driver called directly into KeBugCheckEx without performing Windows' usual exception handling, fault tolerance checks, etc. 9 times out of 10, this bug check usually indicates a faulty video card itself. However, certain software causing conflicts and corruption is possible as well depending.

----------------

1. AODDriver2.sys is listed and loaded in the modules list, which is the AMD Overdrive; also in EasyTune6 for Gigabyte motherboard driver. It's well known to cause crashes, so please remove the software ASAP.

2. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows

3. If you're still crashing after both of the above, re-run Memtest for NO LESS than ~8 passes and tell me the results.

Regards,

Patrick
 
That was an amazingly fast response! Thanks a bunch, I'll get to work on those steps now and report back.

In regards to step 1. Prior to doing a fresh install of Windows, I had read about some issues with EasyTune6 software and chose not to even install it this time. In fact, the only Gigabyte software I installed was "FaceWizard" which is basically just a MB Boot Logo changing program. Should I remove FaceWizard? Otherwise how would I target and remove the AODDriver2.sys otherwise?

Thanks again!

Also I just ran this Memtest about 45 minutes ago I think? It's the first time I've seen errors when running Memtest with these sticks and currently they are in slots 1&3 on the Mobo

IMG_20140210_213410.jpg
 
My pleasure!

In regards to step 1. Prior to doing a fresh install of Windows, I had read about some issues with EasyTune6 software and chose not to even install it this time. In fact, the only Gigabyte software I installed was "FaceWizard" which is basically just a MB Boot Logo changing program. Should I remove FaceWizard? Otherwise how would I target and remove the AODDriver2.sys otherwise?
Click to expand...

Yes, uninstall it. After you uninstall it, navigate to C:\Windows\System32\Drivers and check if AODDriver2.sys is listed still. If it is, rename it to .old. Before doing so however, you may want to make a restore point to be safe - Windows 7 - START | type create | select "Create a Restore Point"

Regarding your Memtest screenshot, one error is bad. We don't want any whatsoever. Reset the system to full defaults (either clear CMOS or load optimized defaults) and run the test again. If it fails, change DRAM from Auto to XMP. If that fails, the memory is faulty and you'll want to contact the manufacturer for an RMA. It's usually pointless to test one stick at a time as the manufacturer always wants the entire kit back whilst they send you a new kit to avoid compatibility issues.

Regards,

Patrick
 
Patrick said:
Hi,

Both of the attached DMP files are of the Unknown bugcheck code (a0000001) bug check.

This is an AMD/ATI-based only bug check. If we take a look at the call stack:

Code: 
4: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0305b5d8 fffff880`1302924e : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0305b5e0 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : [COLOR=#ff0000][I][B]atikmdag+0x2824e[/B][/I][/COLOR]
fffff880`0305b5e8 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`08e19000 : 0xa0000001
fffff880`0305b5f0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`08e19000 00000000`00000000 : 0x5

We can see that the AMD/ATI video driver called directly into KeBugCheckEx without performing Windows' usual exception handling, fault tolerance checks, etc. 9 times out of 10, this bug check usually indicates a faulty video card itself. However, certain software causing conflicts and corruption is possible as well depending.

----------------

1. AODDriver2.sys is listed and loaded in the modules list, which is the AMD Overdrive; also in EasyTune6 for Gigabyte motherboard driver. It's well known to cause crashes, so please remove the software ASAP.

2. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows

3. If you're still crashing after both of the above, re-run Memtest for NO LESS than ~8 passes and tell me the results.

Regards,

Patrick
Click to expand...

So far I've just done these steps and I've yet to replicate the BSOD. I haven't been gaming but I ran Unigine Heaven benchmarks back to back for about 1 hour with ranging settings and it's been just fine!
I didn't save the benchmarks on accident but the results were pretty decent.

Ran on Ultra, 4xMSAA, Tessellation on Normal w/an Avg of 47.5fps and the rest of the benchmarks fell in that range with varying settings. GPU never peaked above 60c. I've yet to Re-run Memtest or reset the bios to defaults. I'll do that now.
 
Patrick said:
:grin1:

Keep me updated.

Regards,

Patrick
Click to expand...

Sorry I'm just now responding. I fell asleep waiting for Memtest to complete at least 8 passes. Woke up to find some REALLY bad results!

I loaded optimized defaults instead of clearing CMOS completely, then ran Memtest. Is there a possibility that my Mobo could be the issue instead of the RAM?

IMG_20140211_064141.jpg
 
I went ahead and just RMA'd the RAM with Corsair. I'm going to keep trying to replicate the BSOD issue though in the meantime to rule out the possibility of the GPU being the stem of the problem.

Any other tips/advice to give? Overall just really appreciate your help and this site in general.
 
Since you have bad RAM, there's really no way 'around' that in the meantime, as that could be the underlying problem. Wait for the new RAM to arrive.

Regards,

Patrick
 
If need be, I can use a friends RAM and GPU to test out those two components? I was able to replicate the BSOD after the 3 steps I completed last night. Just took about 45min of Unigine Heaven on Ultra. Same BSOD info I believe.

I'm just anxious to find out if it's the GPU, RAM, Mobo, etc that's the true cause. Given that the RAM is bad, I'm hoping that's a resolve. The only problem is that I got a BSOD when using my friends RAM that has no issues at all in his rig.
 
One at a time, don't make major changes. If you're going to use your friend's RAM, only install the RAM, not the GPU as well. Ensure that when you install your friend's RAM, you clear the CMOS afterwards.

Regards,

Patrick
 
Patrick said:
One at a time, don't make major changes. If you're going to use your friend's RAM, only install the RAM, not the GPU as well. Ensure that when you install your friend's RAM, you clear the CMOS afterwards.

Regards,

Patrick
Click to expand...

I swapped my Corsair (2x4gb) out for some PNY (1x4gb) that a friend had, cleared the CMOS, and have been running just about every GPU test I can think of. I've ran Furmark's benchmark multiple times including one 15min test (GPU got up to 68c which is the hottest I've seen that card run), Unigine Heaven for 45min-1hr and Unigine Valley 1hr+.....No blue screens!!!!

Unigine Heaven crashed once but it just went straight back to the desktop with no other issues.

So, based on your steps/advice I've placed a RMA order for new RAM and I'm hoping that solves the issue.

Is there anything else I should be doing to try and replicate the BSOD issue with the new RAM to see if the GPU is faulty or not? Are the tests I'm running a good sign that it's not the GPU?
 
Good work, if you haven't crashed in instances in which you have been, it's likely solved. I'd keep using the system as you regularly would, and keep me updated.

Regards,

Patrick
 
Well, my joyous feeling of thinking the issue was resolved ended today after playing about 1.5hrs of Trine 2. Got a Blue Screen once again.

Here is the new data I pulled for this crash: View attachment MORE BSOD INFO YAY.zip

At this point can I start pointing fingers at the GPU? I guess I should probably Memtest this stick of RAM I got from a friend but it was working perfectly fine in his system before he upgraded to a different set so I didn't even think about doing that yet.

Thanks in advance for any help you can give, again. I definitely owe you some beer!
 
It's either the GPU or the RAM, but most likely the former, as it's another *a0000001 bug check. I would Memtest again just to be safe, yes.

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top