AMD Adrenalin version 26.5.1, released on May 6, has introduced a critical bug affecting the Zero RPM cooling feature on several graphics cards. Users on Reddit reported that after a monitor resumes from sleep or is powered back on, the GPU fans fail to spin up even when temperatures rise, despite the setting being enabled. This malfunction prevents proper heat dissipation during demanding tasks, posing a risk of thermal throttling, performance loss, or potential hardware damage. The Zero RPM feature is designed to keep fans stationary during light usage for silent operation, activating them only when temperatures exceed a specific threshold. However, the driver update causes this logic to break after display sleep cycles. While the fans remain off, the GPU temperature climbs silently. This issue is particularly dangerous for users in hot climates where passive cooling is less effective. At least five owners have confirmed the problem, noting that the fans stay idle even when gaming or running intensive workloads. Currently, there is no official patch in the subsequent 26.5.2 driver release, which lists no fixes for this specific cooling failure. Users seeking immediate relief have identified a few workarounds, though none are entirely satisfactory. The most direct solution is restarting the computer whenever the monitor wakes from sleep, forcing the fans to initialize correctly. This method is cumbersome for frequent users. Alternatively, users can disable the Zero RPM feature entirely, but this sacrifices the silent operation benefits. A more technical approach involves using a third-party utility like Display Driver Uninstaller (DDU) to perform a clean offline installation of the drivers. This removes all traces of the buggy software, potentially resolving the conflict. Another option is to roll back to a previous driver version, such as Adrenalin 26.3.1, which does not appear to contain the Zero RPM bug. However, this comes with the drawback of losing newer optimizations, features, and security patches included in the latest releases. AMD has not yet acknowledged the issue or provided a timeline for a fix. Evelyne-Tourneciel, the user who first reported the bug, confirmed the report was sent to the company but received no response. Experts recommend that affected users submit detailed bug reports to AMD to help prioritize a resolution. Until a software update addresses the glitch, owners of affected hardware must weigh the risks of overheating against the inconvenience of using manual workarounds.