AMD confirms a Radeon driver bug that keeps writing to your SSD

The process behind it is called atieclxx.exe. It is the AMD External Events Client Module, a tiny background program. Its normal job is housekeeping for your display: noticing when a monitor is plugged in, handling Radeon Software hotkeys and some FreeSync plumbing.

On affected PCs, it never stops touching the system drive. Owners have measured sustained writes between 0.3 and 1.5 MB per second. At least one Reddit user logged around 5 MB per second while the machine sat idle.

Not long in headlines, but longer in practice. Reports have trickled in for months, across Windows 10 and Windows 11 and several Adrenalin releases. One user on X said the bug has been there since Adrenalin 26.7.1, released in June.

A post on the r/pcmasterrace forum on 8 November pushed it back into view. One owner there said the service had eaten roughly 1% of their SSD's reported health every month for 16 months. That is a single claim and nobody has verified it.

AMD has not denied any of it. On 21 October, a community representative known as AMD_Matt wrote that the company was "looking into it with the aim to resolve it in a future driver release."

Later, a second representative, AMD_Vik, tied the behavior to an interaction between the External Events Utility and Microsoft's PCIe filter driver. That is a piece of Windows that sits between the system and add-in hardware such as a graphics card. AMD_Vik said a fix had been submitted and pointed to Adrenalin 26.11.1.

What's next: the release is expected later in November, with no exact date. The current driver, Adrenalin 26.10.2 from 30 October, does not mention the problem in its notes.

Megabytes per second sound harmless, so here is the daily math if the service runs nonstop:

• 0.65 MB/s: about 56 GB a day, roughly 20 TB a year.
• 1.5 MB/s: about 130 GB a day, roughly 47 TB a year.
• 5 MB/s: about 432 GB a day, almost 158 TB a year.

Every SSD has a rating called TBW, short for terabytes written. It is how much data the maker promises the drive can take over its life. A common 1 TB drive carries a rating of about 600 TBW. At the low rate, the bug uses roughly 3% of that rating per year, which most people would never notice.

At the highest reported rate, it is closer to a quarter of the rating each year, before you install a single game. A small budget drive rated at 200 TBW would feel it much sooner.

In real life Think of a pencil that has to write a little every second, forever. One line a minute barely dents it. A page a minute and you are buying pencils by spring.

The catch: these are writes as Windows counts them, not what lands on the flash chips inside the drive. A drive's controller can absorb some small writes. Lots of tiny repeated writes can also make the real wear worse, a problem called write amplification.

Nobody has published a controlled test yet. And plenty of Radeon owners see nothing unusual at all. PC Gamer's own tester could not reproduce it on their AMD graphics card, so the problem does not hit every machine.

That is not fully settled. Early online reports spoke of many Radeon models. AMD's help page on the issue, as described by CNET, points only to Radeon RX 7000 and RX 9000 series cards. The page calls it "excessive SSD write activity" that happens when the system is idle.

It is also not the first time AMD software has been caught writing too much. A similar complaint last year said the company's chipset drivers kept rewriting a log file.

Ordinary owners did, not testers with lab gear. Redditors on r/pcmasterrace and the Radeon forum raised the alarm. A user named Tomasz Gawroński posted on X that atieclxx.exe had made 19.5 GB of writes on their machine in just 12 hours.

Another Redditor, Darklinkpower, said the driver ate about 1% of their SSD's health every month for 16 months. A second user reported a similar loss of roughly 1% a month. These are personal readings from drive health tools, so they show a pattern worth watching, not a proven rule.

AMD's own help page, as described by CNET, calls it "excessive SSD write activity" that happens when systems are idle. It says AMD is actively working toward a fix and that the page will be updated once there is a resolution.

SSDs have become expensive. Prices spiked sharply over the last couple of years, which means a worn-out drive costs more to replace than it once did. A bug that shortens a drive's life is a bigger annoyance in that market.

Gamers feel it too, because many keep one fast drive for Windows and games together. If that drive carries a steady stream of needless writes, every gigabyte counts a little more.

The timing is also awkward. AMD's current driver, Adrenalin 26.10.2, is only two weeks old and says nothing about the issue. Owners who updated hoping for a fix found nothing, which is why the forum posts spread fast.

The test takes about one minute:

1. Press Win + R, type resmon and press Enter.
2. Open the Disk tab.
3. Sort the list by the write column.
4. Leave the PC alone for a minute and watch.

If atieclxx.exe stays near the top with a steady stream of writes while you are idle, you are affected.

Two stopgaps exist, and neither is free:

• Disable the service: in services.msc, set the AMD External Events Utility to Disabled and restart. The writes stop, but Adrenalin hotkeys and some display behavior can break.
• Turn off Resizable BAR: this feature lets the processor see all of the graphics card's memory at once. Switching it off can cost speed in some games.

Some users also swapped to other drivers, which carries its own risks. Make a Windows restore point before trying any of this.

For most people on a decent drive, waiting a few weeks for Adrenalin 26.11.1 is the calm choice. If your boot drive is small and cheap, a check and a temporary fix make more sense.

• Check, don't panic: one minute in Resource Monitor tells you whether you are affected.
• Update soon: watch for Adrenalin 26.11.1 and install it when it appears.
• Mind small drives: budget drives with low endurance ratings feel this most.
• Be careful with workarounds: disabling the service can break hotkeys and display functions.