AMD Radeon Crimson Driver 15.12 will not install. Need Help, PLZ!

a_dumb_noob2

Reputable
Oct 30, 2015
20
0
4,510
Hi, my system specs are as follows:

Intel i7-4790k @ 4.0Ghz
16GB 1866Mhz DDR3 HyperX Fury RAM
ASUS z97 Deluxe USB 3.1 Motherboard
120GB Boot Kingston SSD and 1TB Storage Seagate HDD
MSI Radeon R9 390X @ 1080Mhz/1500Mhz (core/memory)
Cooler Master 850W PSU

I'm trying to install the AMD display driver version 15.12 on my computer and it constantly fails installation. Furthermore, whenever I try to uninstall the few things that did install (essentially everything except the display driver and HDMI audio driver) using the AMD uninstall manager, it will freeze the computer and I have to hard reset using the power button. I had also gotten a BSoD earlier that said "Page fault in nonpaged area". When I analyzed the MEMORY.DMP file using WinDbg, it pointed at atikmdag.sys as being the possible culprit and since then I have completely gotten rid of every trace of the AMD display drivers as far as I know. Please keep in mind that this BSoD had occured before I was unable to unistall and since then I have done a complete unistall by booting into safe mode and using driver sweeper and ccleaner to both get rid of the AMD driver and clean up the registry. I had to unistall that way because of the fact that the unistall manager would cause my computer to freeze. At this point, the system is running but I don't know how stable it is (despite the fact that I'm fairly sure the BSoDs were display driver related) and it requires a display driver to be of any real use to me since this in fact my gaming PC. Please help if you can. I would like to install a AMD Crimson display driver so that I can play games on this baby and it doesn't seem to be cooperating!

Anyways, thanks in advance for any replies!
 
Solution
So if I read that correctly you've completely removed all traces of AMD drivers and are now running the system with the standard AMD graphics drivers that you get through windows update when you boot the system?
Seen as you have used driver sweeper and are now back to scratch have you since tried installing the latest drivers?

The blue screen you're getting in relation to "page fault in non-paged area" means your system is trying to access some cells on your ram but it's failing to do so. This is caused by faulty ram but I don't think that is the case as you're also getting the atikmdag.sys problems.
So first and foremost clock back your graphics card to defaults and then give it another shot using the 15.12 driver and if that does not...

l1ghtm4st3r

Distinguished
Mar 3, 2012
200
0
18,760
So if I read that correctly you've completely removed all traces of AMD drivers and are now running the system with the standard AMD graphics drivers that you get through windows update when you boot the system?
Seen as you have used driver sweeper and are now back to scratch have you since tried installing the latest drivers?

The blue screen you're getting in relation to "page fault in non-paged area" means your system is trying to access some cells on your ram but it's failing to do so. This is caused by faulty ram but I don't think that is the case as you're also getting the atikmdag.sys problems.
So first and foremost clock back your graphics card to defaults and then give it another shot using the 15.12 driver and if that does not work on your system uninstall that fully (regular uninstall + safe mode driver sweeper as you did) and maybe try the newer 16.1 hotfix driver and see if that does anything.

If you get bsods still then you may just have to dial back the driver to the one you were using before you hit the blue screens.
 
Solution

vulcangrey

Reputable
Aug 7, 2014
52
0
4,660
I wouldn't use the Crimson drivers, I have had tons of problems with all version of Crimson!! I just rolled back the the last 15.11 Catalyst driver, and that is working much better for my two R9 290's which are essentially the same as the R9 390 and your R9 390X.
 

a_dumb_noob2

Reputable
Oct 30, 2015
20
0
4,510
I've marked a best solution. However, I eventually just reinstalled Windows and got around the issue that way. I marked best solution because it seems like it may work for others more committed to solving the problem without re-imaging their hard drive.