How I fixed crashes on my R9 290

Discussion created by kyrillik on Sep 29, 2016
Latest reply on Sep 25, 2018 by thegugi

My card is ASUS R9 290 DirectCU II OC (R9290-DC2OC-4GD5). It was working perfectly for the first year while I was using Catalyst drivers, but once I installed Crimson, I immediately started to get BSODs (thread stuck in device driver, atikmdag.sys). Those crashes happen both in Windows 7 and Windows 10, but only in 2D (browsing, working with files), randomly. NEVER in games, even the most demanding ones! But, once I exit the game to the desktop, I immediately get a crash. So it was obvious there were no problems with the hardware itself, but something wrong with the new drivers.


Once I reverted back to Catalyst, BSODs disappeared completely, so I was using those old drivers for the last 9 months. However they are outdated now and some games (like Battlefield 1 beta for example) refuse to start or have performance issues. So I had to find a solution, since AMD refuses to provide one (and there are loads of people having the same issues, judging from the forums).


The first thing I’ve tried is visiting the ASUS web site for an updated BIOS. However the latest BIOS version is dated June 2014 and it was already installed (way to screw over your customers, ASUS!)


Then I tried raising the 2D voltage with Afterburner. I had really high hopes for this, but surprisingly it didn’t help me at all – still BSODs.


Then I found out about the hilariously named app “ClockBlocker”. If you install it and set the DEFAULT rule to “Block” you essentially remove the 2D mode completely. The card raises the clocks, voltages and power limits to the maximum, even if no game is running. The crashes disappeared completely. However, this solution has obvious drawbacks – the card is running at full speed 100% of the time, so this means more heat, more noise, more power consumption and additional wear and tear. So I’ve decided to search for another solution.


And this solution is custom BIOS, since ASUS and AMD refuse to do their job (warning: flashing the wrong BIOS void the warranty and can brick your card, so stick to ClockBlocker unless you know what you’re doing). I’ve found a couple of custom BIOSes, flashed them, but they had no effect, I still got the same “thread stuck in device driver” BSODs. So I decided to make my own custom BIOS. I’ve backed up the existing BIOS, downloaded the program called “Hawaii BIOS Reader”, loaded my BIOS and started editing (don’t forget to save a second original copy, you will need it). First I’ve tried to change the 2D voltage, but apparently I did something wrong and this BIOS caused an immediate crash at Windows startup. So I reflashed a backup copy and returned to editing. This time I’ve tried raising the 2D video processor speed (the parameter is called “GPU Clock 3”) from default 300 to 450, and to my surprise, once again, the crashes disappeared. Actually, I still don’t quite understand why this helped (maybe raising the GPU clock also raised some other 2D parameters), but the system is rock solid for a week now.


This whole debacle left me VERY disappointed with AMD and ASUS. ASUS is just trash, quite simply. The card is still very capable, for example I play SW:Battlefront with all settings but AA set to Ultra at 2560x1080, and they stopped supporting it two years ago?? No more ASUS for me EVER, thank you very much. But AMD is just as guilty here. If ASUS doesn’t care if their cards are buggy, why not step up and release the BIOS yourselves?  Don’t you care that your reputation is destroyed here? The forums are FILLED with similar complaints, and that includes Sapphire and Gigabyte cards as well. OR, if BIOS option is not available, why not providing an alternative solution in drivers? Catalyst was very stable, so there’s gotta be a way to add a toggle in Crimson GUI to get a stable system even with old outdated BIOS. To be quite honest, the only reason why I still even consider buying AMD is my Freesync monitor. Otherwise I'd migrate to nVidia in a heartbeat.