AMD Radeon Driver Bug Forces Constant SSD Writes via Atieclxx.exe

A persistent bug in AMD’s Radeon driver software is forcing solid-state drives into a cycle of constant, high-frequency write operations.

Even when computers are left idle, the atieclxx.exe process—a core component of the AMD External Events Utility—is repeatedly overwriting files within the Windows system profile. The versions 26.10.1 and 26.10.2 of the drivers are primarily affected by this defect.

Data Overload Risks

The scale of the issue was first identified on Reddit, where users traced the continuous disk activity to the specific AMD utility. While many affected machines record write speeds between 0.3 and 1.5 MB/s, some users have measured activity as high as 5 MB/s.

At that upper limit, a machine left running continuously could record up to 432 GB of data per day, totaling approximately 13 TB of writes every month. To put these figures into perspective, 5 MB/s equates to roughly 18 GB per hour, which is equivalent to installing a game like Doom the Dark Ages two and a half times every hour if the process remains active.

For those experiencing lower activity rates of 1.5 MB/s, the impact still reaches approximately 130 GB per day. This activity remains minimal compared to the maximum bandwidth of a standard SSD, which typically fluctuates between 450 and 500 MB/s, yet it can generate several terabytes of data by the end of a day if the bug persists throughout the machine’s uptime.

Engineering Conflict Identified

AMD acknowledged the defect on October 21. On the company’s official community forum, a representative identified as AMD_Matt said the engineering team was investigating the behavior. AMD had been aware of the issue for several weeks before the public acknowledgment.

A subsequent update from a representative identified as AMD_Vik attributed the issue to a conflict between the AMD utility and Microsoft’s PCIe filtering driver.

Detecting the Atieclxx.Exe Loop Using Resource Monitor

The technical fault involves the 660 KB atieclxx.exe executable copying itself from the driver directory to a Windows system profile, a loop that can trigger every second. To identify if their hardware is affected, users can run the resmon command and check the “Disk” tab for high write volumes linked to the process.

In the Resource Monitor, users are advised to click the “Write” column to sort processes by the amount of data being written. If the process appears at the top of the list while the computer is idle, the machine is affected.

A user-developed tool, “Radeon-atieclxx-SSD-Fix,” attempts to stop the activity by modifying Windows file permissions. While this prevents the SYSTEM account from overwriting the file, the developer said that it is a third-party intervention rather than an official fix from AMD.

Long-Term Drive Longevity

While the volume of data writes is significant, the actual impact on hardware remains a subject of debate. One Radeon owner reported their findings to PC Gamer: “Je viens de découvrir que le pilote grignote 1 % de la santé de mon SSD chaque mois, depuis 16 mois” (I just discovered that the driver has been nibbling away 1% of my SSD’s health every month for 16 months).

A typical 1 TB consumer SSD is often rated for a Total Bytes Written (TBW) figure of 600 TB.

Users looking to halt the activity immediately can disable the “AMD External Events Utility” service via the Windows Services manager or, in some cases, disable Resizable BAR in the BIOS, though the latter does not function on all systems and may reduce performance. Users are advised to re-enable these features once the 26.11.1 driver is installed.