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

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

Exactly what caused the bug is still unclear, since it didn't affect every user or any specific carte du jour platform. AMD has acknowledged the problem and promised a hotfix for today, stating: "AMD is aware of isolated reports of depression fan states following the installation of Radeon Software 'Crimson Edition' on select Radeon GPUs. Its technology teams take identified and addressed this issue, and AMD intends to release a hotfix on amd.com this coming Mon, November 30th."

AMD's new Overdrive panel.

AMD'southward new Overdrive panel.

Nosotros spoke to sources at AMD, who told u.s.a. the problem is a rare outlier that may be caused past a conflict with a previous driver uninstall. Tertiary political party software that adjusts fan speeds appears to office 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 issue) tin can exist institute here. Exist advised that if you get this route, y'all'll need to re-enable the change later every reboot.

Some users are reporting that the problem has killed cards, but it'due south not articulate why this would be happening. Both AMD and Nvidia cards incorporate thermal trip protections that yank down a GPU'southward operating speed and voltage, including an emergency shutdown feature in farthermost cases. These protections are implemented in hardware and supersede any driver settings — users aren't supposed to exist able to impale a card past slamming the accelerator to the flooring. You lot can nevertheless kill a GPU by overvolting and overclocking it over a period of time, provided you lot keep it absurd enough to avoid the thermal trips, but that's not what's being described hither.

This seems a good fourth dimension to note that we recommend all users perform a complete uninstall of whatsoever graphics commuter prior to installing a new version. It doesn't affair if you're moving between driver sets on the aforementioned card, or if y'all are swapping between Teams Ruby-red and Light-green. Personally, I prefer Display Driver Uninstaller (DDU), available at Guru3D.

I recommend uninstalling the vendor driver using the default uninstall utility provided. Once that completes, run DDU. It will ask if yous wish to reboot into Safe Way. Do so. Once in safe mode, choose the appropriate vendor (AMD, Intel, Nvidia), and choose one of the three options: Yous tin can clean and restart the organization, make clean out driver cruft without restarting, or clean the driver cruft and and so shut downwardly. Cull whichever option suits your needs, then reboot and install the new driver package.

Information technology's possible that this would also solve the bug that AMD identified in Reddish, since that issue is tied to a problem with a previous GPU installation, then if you're having the 20% issue, you could try this route to fix it. On the other manus, the company is planning a hotfix release for today, so waiting to make certain you lot become the official solution isn't necessarily a bad idea. Either way, when upgrading video carte drivers, we recommend taking the additional steps to ensure a proper installation process.