Radeon owners who leave their PCs idle may have been wearing out their SSDs without playing anything. The culprit, according to a wave of reports that peaked on Reddit on November 8, is AMD's External Events Utility, a component installed alongside the company's Adrenalin GPU drivers, which appears to keep writing data to the system drive even when the computer is barely being used. AMD has acknowledged the reports and says a fix should arrive in the next driver release.
What the users measured
The numbers in the reports are specific. Reddit user darklinkpower, who flagged the issue on r/pcmasterrace, wrote that "the driver eats up 1% of my SSD health every month for 16 months." Another user reported sustained writes of roughly 5 MB/s on an idle machine, and Tomasz Gawroński, posting on X, measured 19.5 GB of I/O writes from the atieclxx.exe process on his machine in just 12 hours. ZDNET's reporting on AMD's official forum thread found users citing sustained write rates between 0.3 and 1.5 MB/s months after installing a Radeon 9060 XT. At 5 MB/s, a drive would receive about 18 GB of host writes per hour, roughly 432 GB in a day, close to 13 TB over a month of uninterrupted activity.
How much of that traffic actually shortens the drive's life is unresolved. SSD controllers use caching and wear-leveling to manage incoming writes, so reported activity does not map one-to-one onto NAND wear, and the 1% of health per month figure has yet to be independently confirmed. The pattern is also inconsistent: PC Gamer's own AMD-equipped staff could not reproduce the problem on their machines, reports span multiple driver versions including Adrenalin 26.19.2 and older releases, and AMD's October 30 release notes for 26.20.2 do not mention it. ZDNET traces the first forum complaints to July; PC Gamer's sources point to Adrenalin 26.7.1, released in June, as the version where the bug appeared.
AMD's answer, and the stopgaps
A company representative signing as AMD_Matt replied to a user on the AMD community forums on October 21: "We're looking into it with the aim to resolve it in a future driver release." Another representative, AMD_Vik, later apologized on Reddit and said the disk write issue "should be fixed" in Adrenalin 26.11.1, which PC Gamer reports is expected later this month. No exact date has been published.
Users have found two stopgaps, both with costs. Disabling the External Events Utility in Windows Services appears to halt the excessive writes, but commenters warn it can take FreeSync support down with it and cause display glitches on hot-swapped screens. Disabling Resizable BAR, which another user found stopped the disk activity entirely, gives back nothing: ReBAR lets the CPU reach graphics memory more efficiently and can lift gaming performance. This is the second consecutive autumn with a write-happy AMD component; last November a chipset driver was caught rewriting a log file every time on-screen elements moved. The checks users are running now, sorting the Disk tab of Resource Monitor by write activity and watching for the atieclxx.exe and atiesrxx.exe processes, cost nothing.
The financial sting is real timing. Memory pricing has spent the autumn in disarray, enough that prebuilt pricing only looks fair because the parts market is a mess and a new memory design was enough to knock Micron, Samsung and SK Hynix down. Drives are expensive to replace right now, which is precisely why a utility burning through a year of NAND endurance without permission has drawn this much attention.
Source: Tom's Hardware, PC Gamer, ZDNET