Some Radeon owners on Windows have spotted a small but nonstop stream of disk writes from a background AMD driver process, and AMD staff say a fix is due in Adrenalin 26.11.1 this month. Five minutes with Windows’ own tools will tell you whether your PC is affected, and the math says there’s no reason to panic.
Users have reported the behavior on the AMD community forum since at least July. A Reddit PSA on Nov 8 brought it back into view, and Tom’s Hardware, VideoCardz and others have since picked it up.
Who is affected
The process is atieclxx.exe, listed in Task Manager as “AMD External Events Client Module”. It belongs to the AMD External Events Utility service installed with Radeon drivers, which press reports say handles monitor detection, display hotkeys and FreeSync.
User reports name Adrenalin 26.5.2, 26.6.4, 26.9.2, 26.10.1 and 26.10.2, mostly on Windows 11, with fewer reports on Windows 10. AMD hasn’t published a list of affected versions, and the 26.10.1 and 26.10.2 release notes don’t mention the issue. Several users on 26.10.x see normal activity, so it’s not every Radeon PC. Reported rates mostly fall between 0.3 and 1.5 MB/s, with one user reporting about 5 MB/s.
On Oct 21, an AMD representative replied on AMD’s community forum: “Yes. We’re looking into it with the aim to resolve it in a future driver release,” Tom’s Hardware reported. VideoCardz identifies that staffer as AMD_Matt. AMD_Vik later told Reddit users the cause is an interaction between atieclxx.exe and Microsoft’s PCIe filter driver, according to VideoCardz and Joho no Todai. Joho quotes Vik saying the fix missed 26.10.2 and is due in 26.11.1 this month.
How to check your PC
- Close games, browsers and sync apps, then let the PC idle a few minutes.
- Press Win + R, type resmon and press Enter. On the Disk tab, sort “Processes with Disk Activity” by Write (B/sec). If atieclxx.exe stays near the top with steady writes, you’re likely affected.
- In Task Manager (Ctrl + Shift + Esc), watch the Disk column for “AMD External Events Client Module”, or add “I/O write bytes” in the Details tab for a running total.
- Open CrystalDiskInfo and note the health percentage and “Total Host Writes”. Check again 24 hours later for a daily figure. Drive makers’ tools such as Samsung Magician and Crucial Storage Executive also report drive health.
How to stop it
The real fix is Adrenalin 26.11.1, which wasn’t on amd.com as of Monday morning. When it lands, get it through AMD Software or AMD’s driver page, and look for the disk-write fix in the release notes. AMD recommends OEM drivers for laptops, so laptop owners should check their maker’s site too. Our GPU driver update guide covers the basics.
Until then, some users stop the service. This is a user workaround, not AMD advice:
- Press Win + R, type services.msc and press Enter.
- Find “AMD External Events Utility” and click Stop.
- To keep it off after a reboot, set Startup type to Manual or Disabled.
- After installing 26.11.1, set Startup type back to Automatic and start the service.
There are trade-offs. Users report Adrenalin hotkeys stop working. Reports on FreeSync conflict: some users say it keeps working, while Wccftech says stopping the service can interfere with it. VideoCardz notes the workaround doesn’t help in every case. According to Joho no Todai, AMD_Vik also said disabling Resizable BAR in the BIOS works around it, at some cost to game performance. I’d measure first and only touch services if the numbers look high.
Why this isn’t an emergency
These are host writes. Nobody has measured actual flash wear from this bug. At 1.5 MB/s nonstop, that’s about 130 GB a day, or 47 TB a year. A 1TB Samsung 990 PRO is rated for 600 TBW, so reaching that rating would take about 12.7 years, and that assumes the PC runs 24/7. A PC used 8 hours a day writes a third as much. TBW is a warranty rating, not a failure point.
Budget drives deserve a closer look. The Crucial P3 1TB is rated for 220 TBW, which 1.5 MB/s would reach in about 4.6 years of nonstop running. The widely shared claim of 1% SSD health lost per month comes from one unnamed user, and Tom’s Hardware says it hasn’t been independently confirmed.
Storage scares aren’t new. In 2025, a Windows 11 update was blamed for SSD failures, but Microsoft later said it found no connection, and Phison traced the failures it examined to pre-release engineering firmware that retail drives don’t use, The Verge reported. The AMD issue is real, but by the numbers it is modest. Check once, write the numbers down, and install 26.11.1 when it ships.