Owners of AMD-based Windows PCs have been quietly burning through their SSDs' write endurance for months, according to a report by heise online, because of a defect in the company's Radeon Adrenalin graphics driver.
The culprit is the "AMD External Events Utility", a service that monitors display events and GPU functions; its processes atieclxx.exe and atiesrxx.exe are the ones seen writing continuously. The trail started with a Reddit user who noticed his SSD health score falling by roughly one percent a month over 16 months. Other users then reported constant write rates between 0.3 and 5 MB/s — at the top end, more than 400 GB written per day.
An independent developer traced the behaviour with Windows Event Tracing and found that atieclxx.exe copies itself — about 660 KB — every second from the driver folder to C:\Windows\System32\config\systemprofile\AppData\Local\AMD. Left running, that adds up to roughly 56 GB per day. The service also searches for installation files of the amdkmpfd filter driver, which belongs to Smart Access Memory — which is why disabling Resizable BAR in the BIOS helps some users.
AMD has confirmed the bug in its forum and on Reddit and says a corrected version is expected in driver 26.11.1, but no date has been set. Windows 10 and Windows 11 systems across several driver versions are affected, though not all. Users can check without extra software using the built-in Resource Monitor (resmon), sorting the disk tab by write bytes per second: if atieclxx.exe stays at the top, the machine is affected.
Community workarounds have side effects — stopping the service can break FreeSync and frame pacing, and switching off Resizable BAR costs performance. The developer's tool, Radeon-atieclxx-SSD-Fix, now at version 2.1 and published under the MIT licence on GitHub, instead denies the SYSTEM account permission to overwrite that single copied file, leaving FreeSync, frame pacing and hotkeys untouched. A scheduled task re-applies the protection after driver updates and lifts it once AMD patches the fault. The author notes the limits: other driver versions may behave differently, the tool does not start where PowerShell signature enforcement is on, and the damage estimate is just that.
For modern TLC drives with a healthy TBW budget the bug is rarely fatal, but for small QLC drives in laptops the arithmetic looks very different — and a manufacturer shipping a driver this broken, fixed first by a volunteer, is an uncomfortable look for AMD's quality control.




