AMD has acknowledged a Radeon driver bug that keeps some PCs writing to their SSDs while they sit idle, and a fix has not yet shipped. Reported write rates are steady and unnecessary, but the effect on drive lifespan has not been proven.
The activity comes from AMD External Events Utility, whose atieclxx.exe process handles hotkeys and FreeSync. The company said on Reddit that an infinite loop in the driver keeps the drive busy.
Not every Radeon system appears affected, so owners should confirm the behaviour on their own machines before changing anything.
According to Digital Trends, users caught the process writing roughly 0.3 to 1.5 MB/s on most PCs and up to 5 MB/s in the worst report. The data consists mainly of driver diagnostics, status checks and system event logs.
At 0.3 MB/s, that adds up to about 26 GB a day. At 5 MB/s, it rises to about 432 GB a day, or nearly 13 TB a month. Digital Trends compared those figures with a typical 500GB SSD rated for around 300 TBW and arrived at between 3.16% and 52.56% of its rated endurance per year.
Those numbers are a worst-case illustration, not a forecast. They assume writing around the clock, and the 5 MB/s rate comes from a single report. They also count what Windows sends to the drive, not what physically lands on the flash chips, so actual wear remains unproven.
An AMD representative, AMD_Matt, acknowledged the problem in October. Another, AMD_Vik, later said a colleague had submitted a low-risk fix and that he hoped to ship it very soon.
Adrenalin 26.10.2, released on October 30, does not mention the fix. Vik told a user he thinks it will arrive in the very next release, but there is no official date.
To check a PC, press Win + R, type resmon, open the Disk tab and look for steady writes from atieclxx.exe. Two workarounds have been reported, and neither is a clean fix: stopping the service in services.msc can break FreeSync behaviour and Adrenalin hotkeys, while turning off Resizable BAR may reduce gaming performance.
Digital Trends advises against changing anything unless the writes are confirmed. For AMD, the open questions are when the fixed driver ships and whether the company will say how much real wear the bug caused.
