AMD Radeon GPU Driver Update Breaks Zero RPM Mode for Several Users

AMD’s second-latest GPU driver update, version 26.5.1 WHQL, is causing issues with the Zero RPM mode on many graphics cards. Zero RPM is a feature found in most modern dedicated graphics cards, allowing the GPU to be passively cooled by its heatsink when idling. This means that when the graphics load is low, temperatures remain low, eliminating the need to spin the fans. This helps preserve fan longevity and reduces system noise. However, when temperatures rise above a certain threshold, Zero RPM is disabled, and the GPU’s fans begin to spin to maintain stability. Interestingly, several users are reporting that updating to the Adrenalin 26.5.1 drivers is causing the Zero RPM mode to malfunction in a specific way.

When users upgrade from Adrenalin 26.3.1 to the 26.5.1 WHQL drivers, Reddit users report that Zero RPM doesn’t function as expected. Once the monitor goes to sleep, Zero RPM is activated as it should be. However, when the monitor is turned back on, Zero RPM remains active and does not deactivate, leading to a situation where GPU temperatures can rise while the GPU is stuck in Zero RPM mode. There are two solutions to this issue: one is immediate, and the other requires a fresh driver installation. Users can either reboot the system to restore normal operation or use the AMD driver removal tool or Display Driver Uninstaller (DDU) to completely remove all older GPU fan profiles and settings. This means that old fan profiles from the previous driver version must be reset with each new driver installation.

While this issue can be resolved, it is not particularly user-friendly. Many users report that the only way to fix it is by using DDU to remove old drivers and install the latest driver version, or by rolling back to the 26.3.1 drivers. Some have explicitly turned off Zero RPM mode to avoid these problems. Even though AMD released Adrenalin 26.5.2 WHQL drivers yesterday, there were no noticeable fixes for the Zero RPM mode issue. Perhaps the next release will provide a solution, or there may not be enough cases worldwide to prompt a fix. Please share your experiences in the comments.