atikmdag.sys BSOD(s) amd r9 290

[Feevercz]

Hello guys,
I got a new gaming rig for about a month now and since the first boot I'm experiencing weird crashes. I have a BSOD every now and then (usually once a week or maybe more) during normal usage. Sometimes it strikes when I watch youtube videos, sometimes when I try to launch some game, or during the game. BSOD's crash minidumps are the only things I could get any info from, when I searched forums I found many similar problems and most of them were suggesting this fix: http://www.tomshardware.co.uk/answers/id-1656824/atikmdag-sys-error-bsod-startup.html

My specs are:
CPU: Intel Core i5-4440
Motherboard: MSI Z87-G43
RAM: A-Data XPG V1.0 8GB (2 x 4GB) DDR3-1600
SSD: Samsung 840 Pro Series 128GB
HDD: Seagate Barracuda 1TB 7200RPM
GPU: Asus R9 290 DirectCU II OC 4GB
PSU: SeaSonic 750W

But I couldn't find the exactly same issue, because besides those BSODs the much more common problem I am experiencing is when I try to run specific games like league of legends, or dead space (or it happens just randomly every few days during various actions) my monitor goes completely black (power diod is blinking) but the computer is still running and I am unable to do anything only to restart the computer and then it boots up normally.

Windows debugger tells me that the cause is atikmdag.sys, plus other various .sys depending on which minidump it is, but atikmdag.sys is in every single one, you can see it in this zip file which contains my minidump files

http://filedump.org/files/X7teQ61397590014.html

I tried reinstalling the OS, updated gpu drivers, used older drivers.
Before I reinstalled the OS the problem with monitor going black was always happening when using google chrome. One more thing I noticed is that when I try to run deadspace using windows troubleshooter in win xp sp2 compatibility mode it doesn't crash, but instead gives me error message "missing required file "ssleay32.dll"" but I have no idea if it has anything to do with my problem.

Thank You for any words of advice, I'm an IT newbie so don't be too technical on me please and I'm not native english speaker so forgive my grammar

 

[290x user]

Hi,

I have the same problem. R9 290x GPU. Got the BSOD with eror code 0xA0000001 and atikmdag.sys dxgmms1.sys and ntoskrnl.exe.

System only crashed when playing Flash games (Hearthstone Heroes of Warcraft), Youtube, Internet explorer, Flash websites. Never in games like BF4 or Watch_Dogs. I can replicate the BSOD when playing Hearthstone.

Things I've done so far.

- Reinstalled Windows 7 (about 10 times)
- Drivers 13.2, 14.4, 14.6 (with and without CCC)
- Tried my friends GPU (same model R9 290x)
- Bought new CPU, PSU, MB, Ram, HDD. (was planning on that anyway).
- Tried the atikmdag.sy_ trick (found on some forum)
- Tried different VBIOS versions and release dates (Asus, Club3D). They are all the same anyway/
- Tried the UBER mode on the GPU
- Tried with fresh W7 install, 14.4 driver and Hearthstone ONLY, still BSOD.

Yesterday I got my 1st BSOD since I build my system. By watching a youtube video. Same BSOD as I've had since I bought the R9 290x. Always the same error codes in minidump and bluescreenview.

At this point I'm able to say it has nothing to do with any of my hardware (except GPU itself) since I've bought a complete new build and still have the issue. BSOD happends with all driver versions I could find.

So either both the GPU's I've tried are defect, all the drivers are bugged, or the VBIOS of the GPU is just bad.
The BSOD only happens when the GPU is not doing much. GPU-Z it works at about 600mhz.

Contacted AMD, they suggested me to try all the tings I've allready tried or to RMA the card.
But I'm pretty sure they'll send the card back after a few weeks saying the card if working correctly..

I had the same issue, know what fixed mine?

Do you happen to use Google Chrome???
If you do, you need to MANUALLY install the latest Adobe Flash and Adobe Shockwave players. They should override Google chrpme's on their own, and I haven't had a crash since

Thanks for the reply. I don't use chrome. I've tried to run my computer with the bare minimum and it still crashed.
It hasn't happend for a few days now since i've disabled ULPS and Hardware acceleration in Flash. But still not sure it's fixed.

 

[Andys184]

It's running better now no crashes whatsoever. I just delete flash player since I don't really need it for anything I do.

 

[jkteddy77]

It's running better now no crashes whatsoever. I just delete flash player since I don't really need it for anything I do.

If you just manually download the newest version does it still do so? I know it was a few older vversions that did it for me. Hasn't happened since April 2014... Hadn't had it one time in 4 months

 

[fir3w0rx]

What worked for me...

1. Uninstalled Catalyst Control Center (CCC).
2. Disabled Hardware Acceleration in Adobe Flash (mainly used for YouTube).

When I first got this gfx card (Gigabyte Radeon R9 290x), I was getting blue screens every 2-3 days on average. They would occur weather I'm running a high gfx demanding game or a game that can be run on 256 colors or YouTube videos. They didn't seem to occur when my PC was idle though. After doing the above 2 things, I haven't got a BSoD in months

My specs:
CPU: Intel Core i7 960 @ 3.2 GHz
OS: Win 7 Ultimate x64
GPU: Gigabyte Radeon R9 290x
GPU Driver: version 14.301.1001.0
PSU: 950 watts.
RAM: 12GB
Browser: Internet Explorer 11

 

[Andys184]

basically it was flash player and silverlight also uncheck global video in CCC, also uninstall windows media apps like calendar video photos whatever that comes with the bundle, usually has some kind of affect with the drivers.

 

[Feevercz]

Hello guys long time no see...
Well I haven't figure out this problem yet, I tried so many things that I don't even remember them.
When I first started to have this problem it was very frequent and I couldn't see any relations between them, then it got better.
I tried several things, some helped a bit, some made it worse.
One day I ordered a new pack of RAM, it was 16GB in 2x 8GB sticks (I tested my old RAM and they were completely OK) Immediatelly after I switched those RAMs BSODs stopped, I did know because before it there were a specific actions which always triggered BSOD, but since the new RAMs were in - no BSOD what so ever.

THE STRANGE thing is even when I swapped the RAMs to the old ones, the issue with BSOD was gone... I returned the new RAMs for the cash-back and the problem vanished for several months.
But one day I was watching a youtube video and shit got bad again - I saw so familliar blue screen.
Oh well now I surrendered and waste my time by trying to figure out the issue.
I only get BSOD when watching a video on facebook, or youtube. Sometimes I can watch for hours without a problem, but usually my PC crashes after few minutes of a flash based video.
I must say that it never happens during a movie, or playing any kind of a game, nor I had a BSOD in a different case than watching a Youtube, or fb video.

I'd like to hear any new suggestion what to try, something which I haven't read in this thread.

Thank you guys.

 

[jkteddy77]

Not sure what you have and haven't tried yet but I'll list them anyways, assuming you've tried some of these in the thread already

2. Uninstall old java/Shockwave/Adobe flash and install the latest of all screen. This BSOD was most caused for me by the internal media players that are incorporated into Google chrome. Using standalone versions seemed to play well with the drivers. Haven't had this BSOD in over a year. disabling flash hardware acceleration is an option, but that never helped me. Plus, video lags without at least some acceleration.

1. reinstall graphics drivers using DDU, or Display Driver Uninstaller. Let it reboot into safemode and remove all AMD drivers. Also repeat and remove Nvidia drivers if you've installed those drivers in the past on your PC.

3. Unlikely, but check your CCC if you still have it. Under the Video>Global Video tab, make sure that "Apply current video setting to internet video" is unchecked.

4. Turn you PC off. Remove your RAM sticks. Boot up the PC, but it will be stopped at the BIOS. It will likely not let you start, coming up with a RAM error. This way the PC will recognize there is no ram, and treat it like new RAM next time it senses some. Turn it back off. Replace your RAM and then try turning on. If replacing your RAM was the solution the first time, and the type of kit didn't matter, I have a hunch this may fix it again if nothing else did.

 

[Feevercz]

Not sure what you have and haven't tried yet but I'll list them anyways, assuming you've tried some of these in the thread already

2. Uninstall old java/Shockwave/Adobe flash and install the latest of all screen. This BSOD was most caused for me by the internal media players that are incorporated into Google chrome. Using standalone versions seemed to play well with the drivers. Haven't had this BSOD in over a year. disabling flash hardware acceleration is an option, but that never helped me. Plus, video lags without at least some acceleration.

1. reinstall graphics drivers using DDU, or Display Driver Uninstaller. Let it reboot into safemode and remove all AMD drivers. Also repeat and remove Nvidia drivers if you've installed those drivers in the past on your PC.

3. Unlikely, but check your CCC if you still have it. Under the Video>Global Video tab, make sure that "Apply current video setting to internet video" is unchecked.

4. Turn you PC off. Remove your RAM sticks. Boot up the PC, but it will be stopped at the BIOS. It will likely not let you start, coming up with a RAM error. This way the PC will recognize there is no ram, and treat it like new RAM next time it senses some. Turn it back off. Replace your RAM and then try turning on. If replacing your RAM was the solution the first time, and the type of kit didn't matter, I have a hunch this may fix it again if nothing else did.

Well I uninstalled shockwave/java/flash and now I have been watching a yt videos for over an hour and no crash so far.

BUT

I did this step few months ago to no avail, so not sure if this is not just a false posssitive.

I will report after few days to be sure, or after another crash.
But for now thank you.

-------------------------
UPDATE:
Well today I got the BSOD again after watching a yt vid for a few minutes.

It was 2 days without it after uninstalling shockwave, java and flash.
So I proceeded to trying a new drivers and bios.

First I put a fresh install of newest AMD drivers (15.7.) for r9 2xx series using DDU in safe mode.
// I also tries this SEVERAL times, but any new installation oif different drivers make this problem much worse, I start to get wierd BSOD (the image is shattered) from just having a browser open or so, which never happened before.
So i rolled back to my only "stable" driver version:

After that I tried to put a new version of bios for my MOBO, so I flashed it to A.7 version (from A.4).
So far I haven't watched any videos, nor experience any BSOD, so I will report if there was any progression after I have some data to report.

My next step (if BSOD will occur again) is to remove RAMs and put them back (as suggested by jkteddy77).

 

[Feevercz]

I am also not sure if my setting in bios are OK.
I followed some advices online how to setup it right, but because im not really sure what options do what, maybe I have something wrong.
Please check it: http://imgur.com/a/KyCs5

 

[jkteddy77]

Your BIOS looks default, and should be running fine. Only thing I would recommend with the BIOS is customizing the Dram Frequency and Dram Timing.

Check your RAM, see what it's default clock is (1333mhz, 1600mhz, 1866mhz, etc) info can be found with the RAM's original packaging, or if you can find the EXACT model number of your RAM online.
Your BIOS may have a utility that can read you this info as well. (I think MSI's is called Memory-Z if yours has it)

Then set your Dram Frequency to that. (Dram Frequency is the line highlighted in red in the picture below)
The BIOS auto'd it to 1333, but it may be running slower than it should be.
for example, my bios sets mine to 1600mhz, but it's rated at 1866mhz.

Also set your Dram CAS Timing yourself as well. (green arrows) This info is often found alongside your RAM's Reference rated clock rate.
https://i.imgur.com/taayIaw.png
For example, mine should be set to 9-10-9-28, but my defualt BIOS sets it at 11-10-11-28 for some reason.
While these "safer" automatic timings can be more stable, they can also cause weird issues like this if they are too far off of their manufacturer rated timings and Dram frequency.

This might be what's causing such weird behavior with your graphics drivers, as I see no other reason for these BSOD's to still be happening for you.

 

[Feevercz]

Your BIOS looks default, and should be running fine. Only thing I would recommend with the BIOS is customizing the Dram Frequency and Dram Timing.

Check your RAM, see what it's default clock is (1333mhz, 1600mhz, 1866mhz, etc) info can be found with the RAM's original packaging, or if you can find the EXACT model number of your RAM online.
Your BIOS may have a utility that can read you this info as well. (I think MSI's is called Memory-Z if yours has it)

Then set your Dram Frequency to that. (Dram Frequency is the line highlighted in red in the picture below)
The BIOS auto'd it to 1333, but it may be running slower than it should be.
for example, my bios sets mine to 1600mhz, but it's rated at 1866mhz.

Also set your Dram CAS Timing yourself as well. (green arrows) This info is often found alongside your RAM's Reference rated clock rate.
https://i.imgur.com/taayIaw.png
For example, mine should be set to 9-10-9-28, but my defualt BIOS sets it at 11-10-11-28 for some reason.
While these "safer" automatic timings can be more stable, they can also cause weird issues like this if they are too far off of their manufacturer rated timings and Dram frequency.

This might be what's causing such weird behavior with your graphics drivers, as I see no other reason for these BSOD's to still be happening for you.

OK So my RAMs are:
Beast - 8GB Kit* (2x4GB) - DDR3 2400MHz CL11 Intel XMP DIMM
Part Number: HX324C11T3K2/8
Specs: DDR3, 2400MHz, CL11, 1.65V, Unbuffered, Spec Sheet PDF
Timings: 2400MHz, 11-13-14, 1.65V; 2133MHz, 11-13-13, 1.6V

So I set the X.M.P profile 1 (2400Mhz, CL 11-13-14, 1,65V)
I also set manualy the Dram frequency to 2400Mhz.

Under the Dram timing I had only options linked, unlinked and auto, so I left it to auto, since linked/unlinked only opened a advanced options with tens of changable data which I wasnt comfortable to change (also most of them were just for read).

I wasnt able to manually change the Dram Voltage, which was shown to be set to 1,59V (it was grayed out and I could just read the value). But above below the X.M.P options it showed that it is set to 1.65V as it should be, so I'll see.

Will report later how it all worked out.

Thank you for your continuous help, it is much appreciated.
snapshot of cpu-z /memory

dont know about the timing, manufacturer pdf said it should be 11-13-14...


UPDATE:
Had a BSOD withing few seconds after watching a yt video.
Turned the OC off back to previous settings

 

[jkteddy77]

Your BIOS looks default, and should be running fine. Only thing I would recommend with the BIOS is customizing the Dram Frequency and Dram Timing.

Check your RAM, see what it's default clock is (1333mhz, 1600mhz, 1866mhz, etc) info can be found with the RAM's original packaging, or if you can find the EXACT model number of your RAM online.
Your BIOS may have a utility that can read you this info as well. (I think MSI's is called Memory-Z if yours has it)

Then set your Dram Frequency to that. (Dram Frequency is the line highlighted in red in the picture below)
The BIOS auto'd it to 1333, but it may be running slower than it should be.
for example, my bios sets mine to 1600mhz, but it's rated at 1866mhz.

Also set your Dram CAS Timing yourself as well. (green arrows) This info is often found alongside your RAM's Reference rated clock rate.
https://i.imgur.com/taayIaw.png
For example, mine should be set to 9-10-9-28, but my defualt BIOS sets it at 11-10-11-28 for some reason.
While these "safer" automatic timings can be more stable, they can also cause weird issues like this if they are too far off of their manufacturer rated timings and Dram frequency.

This might be what's causing such weird behavior with your graphics drivers, as I see no other reason for these BSOD's to still be happening for you.

OK So my RAMs are:
Beast - 8GB Kit* (2x4GB) - DDR3 2400MHz CL11 Intel XMP DIMM
Part Number: HX324C11T3K2/8
Specs: DDR3, 2400MHz, CL11, 1.65V, Unbuffered, Spec Sheet PDF
Timings: 2400MHz, 11-13-14, 1.65V; 2133MHz, 11-13-13, 1.6V

So I set the X.M.P profile 1 (2400Mhz, CL 11-13-14, 1,65V)
I also set manualy the Dram frequency to 2400Mhz.

Under the Dram timing I had only options linked, unlinked and auto, so I left it to auto, since linked/unlinked only opened a advanced options with tens of changable data which I wasnt comfortable to change (also most of them were just for read).

I wasnt able to manually change the Dram Voltage, which was shown to be set to 1,59V (it was grayed out and I could just read the value). But above below the X.M.P options it showed that it is set to 1.65V as it should be, so I'll see.

Will report later how it all worked out.

Thank you for your continuous help, it is much appreciated.
snapshot of cpu-z /memory

dont know about the timing, manufacturer pdf said it should be 11-13-14...


UPDATE:
Had a BSOD withing few seconds after watching a yt video.
Turned the OC off back to previous settings

Hmm, this may sound like an unlikely question, but is your RAM compatible with your Mobo? All Mobo's have a list of compatible RAM in their Manuel, so check your mobo's paper manual or download a digital manual from your mobo's support page. It's a Z87 mobo, so I'd assume it is, but I don't have many more ideas as to why you are still getting BSOD's

 

[fir3w0rx]

Crash logs after a BSoD often point to certain files or drivers. But in some cases, the root cause of the BSoD is actually an overheating CPU (which is probably why it's not functioning properly and generating inaccurate error logs). Check it's temperature when using hardware acceleration, Catalyst Control Center/AMD Settings, converting files, or anything else that could possibly cause your CPU to work harder. Anything above 80 degrees celsius (176 F) is too hot.

If it IS getting too hot, check that your thermal paste hasn't dried up. If the paste is ok but your CPU is still overheating, then you'll have to get a better cooler.