This site may earn affiliate commissions from the links on this page. Terms of use.

Last week, nosotros covered AMD's new Radeon Scarlet driver software and the bevy of improvements the visitor had delivered. It now seems that an unwelcome bug crept into the release besides, with some users reporting abnormally low fan speeds in the wake of the announcement.

Exactly what caused the issues is yet unclear, since information technology didn't affect every user or any specific menu platform. AMD has acknowledged the problem and promised a hotfix for today, stating: "AMD is aware of isolated reports of low fan states following the installation of Radeon Software 'Crimson Edition' on select Radeon GPUs. Its technology teams accept identified and addressed this consequence, and AMD intends to release a hotfix on amd.com this coming Monday, November 30th."

AMD's new Overdrive panel.

AMD's new Overdrive panel.

We spoke to sources at AMD, who told u.s. the problem is a rare outlier that may exist caused by a conflict with a previous commuter uninstall. 3rd party software that adjusts fan speeds appears to function properly, as does manually setting the fan speed in the AMD Overdrive console. Instructions for how to enable a temporary hotfix (before AMD patches the event) can be found here. Exist advised that if you get this route, y'all'll demand to re-enable the change after every reboot.

Some users are reporting that the trouble has killed cards, but it's not clear why this would be happening. Both AMD and Nvidia cards incorporate thermal trip protections that yank downwardly a GPU's operating speed and voltage, including an emergency shutdown characteristic in extreme cases. These protections are implemented in hardware and supercede any driver settings — users aren't supposed to be able to impale a carte du jour by slamming the accelerator to the floor. You can still kill a GPU by overvolting and overclocking information technology over a period of time, provided you keep it cool plenty to avoid the thermal trips, merely that'southward non what's existence described here.

This seems a good time to note that we recommend all users perform a complete uninstall of any graphics driver prior to installing a new version. Information technology doesn't thing if you're moving between driver sets on the same card, or if you lot are swapping between Teams Red and Green. Personally, I adopt Display Driver Uninstaller (DDU), available at Guru3D.

I recommend uninstalling the vendor driver using the default uninstall utility provided. In one case that completes, run DDU. It volition ask if yous wish to reboot into Safe Mode. Do so. In one case in safe mode, choose the appropriate vendor (AMD, Intel, Nvidia), and choose 1 of the three options: You can make clean and restart the arrangement, clean out driver cruft without restarting, or clean the driver cruft and so shut down. Choose whichever choice suits your needs, then reboot and install the new driver package.

It's possible that this would also solve the bug that AMD identified in Crimson, since that issue is tied to a trouble with a previous GPU installation, so if yous're having the twenty% issue, you could endeavor this route to gear up it. On the other paw, the company is planning a hotfix release for today, then waiting to make certain you become the official solution isn't necessarily a bad idea. Either way, when upgrading video card drivers, we recommend taking the additional steps to ensure a proper installation procedure.