ATIKMDAG.SYS blue screen

miasmablk

Reputable
Feb 17, 2014
3
0
4,510
Hello I've just completed building my first gaming PC which I was expecting to be a fun and exciting experience, however I've been plagued with nothing but BSOD problems. to be exact what happens is: I set my cards to crossfire in CCC and go to launch a game such as Metro Last Light or Crysis 3 my system then immediately crashes and I am faced with the BSOD.
****Pictured****
IMG_20140216_141124.jpg


The thing is both cards work fine when not in Xfire and I have tested each in independently in their own pci-e X16 slot, I even switched them around both cards and both slots seem fine?

Also have tried:

1.) Fresh driver install after system format
2) Fresh driver install using Guru3d driver sweeper
3.) atikmdag.sy_ expansion method
4.) Proprietary drivers
5.) New Crossfire Bridge

System Specs:

- Xeon E3 1230v3
- 2x Gigabyte r9 270x 2gb
- 8gb Crucial Ballistix XT Sport @ 1600mhz
- Msi z87-g45 Gaming Mobo
- WD 1Tb Caviar Blue 7200rpm
- XFX PRO 850w XXX (80+ bronze)



 
Solution
I just discovered another conflict on mine. It blue screened on me again last night. Spent today tracking it down. It's my printer driver. When I print, it gets hung in memory, and then when I play Tomb Raider, it crashes. The BSOD reports the ATIKMDAG.SYS issue, but when I examine the crash dump, I find the only locked up driver is the printer driver. This is the first time I've used the printer in several weeks. Doesn't matter if I scan, print, or fax through it, I can't play Tomb Raider until I reboot to clear it up.

I was able to clear up my issue with the printer driver by completely removing all AMD drivers from my system, including chipset drivers. I then installed Catalyst 14.1 Beta followed by reinstalling the chipset...

rhapdog

Distinguished
Jan 14, 2014
164
0
18,760
Just a shot in the dark here, but I've read other people's complaints where they had to disable Overdrive for their 270x to stop the blue screens, and that it was a driver issue causing it. Latest stable drivers definitely have some issues, as do the latest beta. If you have overdrive enabled, you might try to disable it just to see if it makes it go away. It has worked for others, but you know how that goes... what works for one doesn't always work for another.

My new ASUS grahpics card was causing BSODs, and after researching the event viewer and analyzing the crash dump, I discovered it was a conflict between an AMD monitor program and the ASUS monitor program. I uninstalled the ASUS monitor and had to disable Overdrive as well, then the blue screens stopped. It is a driver issue for sure on my end, but it was these 2 programs that triggered the bug in the driver.
 

miasmablk

Reputable
Feb 17, 2014
3
0
4,510



Thanks for the quick response Rhapdog, I have Overdrive disabled as well as OC genie, I will definitely check out my crash dumps again as well as event viewer and look for a similar conflict, because as of right now im at a total loss :( whats worse I just got my razer sabertooth in the mail and now it's not working !!!

 

rhapdog

Distinguished
Jan 14, 2014
164
0
18,760
I just discovered another conflict on mine. It blue screened on me again last night. Spent today tracking it down. It's my printer driver. When I print, it gets hung in memory, and then when I play Tomb Raider, it crashes. The BSOD reports the ATIKMDAG.SYS issue, but when I examine the crash dump, I find the only locked up driver is the printer driver. This is the first time I've used the printer in several weeks. Doesn't matter if I scan, print, or fax through it, I can't play Tomb Raider until I reboot to clear it up.

I was able to clear up my issue with the printer driver by completely removing all AMD drivers from my system, including chipset drivers. I then installed Catalyst 14.1 Beta followed by reinstalling the chipset drivers. It now works. I used AMD Cleanup Util 1.2.1.0 to do it. Be careful if you use that utility, though, because if you are on Windows 8, it will remove Admin rights from all administrative accounts, causing you to have a severe headache with a possible Win8 reinstall if you can't do a system restore back.

Make sure to set a restore point before removing and reinstalling drivers. 14.1 Beta has fixed my issue so far as I can tell.
 
Solution