AMD Radeon Drivers Write to SSDs Around the Clock; Fix Targets Adrenalin 26.11.1

A bug in AMD's Radeon Adrenalin drivers on Windows writes to the system drive continuously, even when the PC sits idle, and a fix has probably missed the cutoff for the next driver release. AMD has confirmed the problem. VideoCardz reports the company is targeting Adrenalin 26.11.1 for the correction. AMD has not given a release date.

The culprit is the AMD External Events Utility, a background service whose client process, atieclxx.exe, shows up in Resource Monitor's disk tab and simply refuses to stop. AMD_Matt, an AMD representative on the company's community forum, replied to users in October: "Yes. We're looking into it with the aim to resolve it in a future driver release."

AMD_Vik, another AMD representative, later offered more detail on Reddit. The problem appears to come from an interaction between the utility and Microsoft's PCIe filter driver. A fix has likely been committed, he said, but "might have missed the cutoff for the next driver release." Software release trains wait for no bug.

How much data is actually being written?

Users have reported the issue on Windows 10 and Windows 11, across several Radeon cards and several Adrenalin releases. AMD has not said which driver versions are affected.

The measured rates vary:

• Most reports put the writes at 0.3 to 1.5 MB/s.
• One user measured roughly 5 MB/s.
• Sustained around the clock, 5 MB/s would add up to approximately 432 GB per day — comparable to writing a full 400 GB drive every 24 hours.

That 432 GB figure deserves a caveat. These are host-side writes, and nobody has demonstrated how much actually reaches the NAND flash or shortens drive life. Compression, wear leveling and drive-side caching all sit between the counter and the silicon. The effect on SSD wear remains unproven.

The Adrenalin 26.10.2 release notes do not mention the issue, which tells you where the fix did not land.

What can users do until the patch arrives?

Users have suggested two workarounds, and AMD has endorsed neither. One is stopping the External Events Utility in services.msc, which can break Adrenalin hotkeys and affect FreeSync. The other is disabling Resizable BAR in the BIOS, which can cost gaming performance. Choose between convenience and flash cells.

There is also precedent for the pattern. Users previously reported similar constant log-file writes tied to AMD's chipset driver. A background service that logs with enthusiasm is, it seems, a recurring character in the Radeon ecosystem.

What happens next?

The fix is committed, by AMD's own account, and the target is Adrenalin 26.11.1. Until that release ships, Radeon owners who notice sustained disk activity from atieclxx.exe can measure their own write rates, weigh the unendorsed workarounds, and wait. If AMD hits its target driver, the utility should finally learn to sit still.