Skip to content

Journal

AMD driver bug wears out storage drives. A Radeon graphics software glitch continuously writes data even when idle.

AMD driver bug wears out storage drives. A Radeon graphics software glitch continuously writes data even when idle.Technology

AMD staff have acknowledged a Radeon driver bug that keeps writing to the system drive while a PC sits idle. The process named in the reports is atieclxx.exe, from the AMD External Events Utility, and the fix they have named is Adrenalin 26.11.1. As of 11 November 2026 that driver was still described as due later in the month, with no day given.

AMD driver bug wears out storage drives. A Radeon graphics software glitch continuously writes data even when idle. The notes below separate what AMD’s representatives have said from user measurements, and from arithmetic that reviewers added on top. Bdeb Technology has not reproduced the writes on a test PC.

AMD driver bug wears out storage drives. A Radeon graphics software glitch continuously writes data even when idle.

VideoCardz, writing on 9 November 2026, is the clearest public account of the company replies. TechPowerUp published its own write-up on 10 November and said it had spoken with AMD. Neither piece is an AMD support bulletin. AMD has not posted a release note for the fix, because the driver that is supposed to contain it is not out.

What keeps writing

The process is the AMD External Events Client Module, atieclxx.exe. It belongs to the AMD External Events Utility, a Windows service installed with Radeon software. VideoCardz describes that service as handling monitor detection and Radeon software hotkeys. TechSpot, citing AMD’s own description of the process, adds FreeSync to that list.

AMD representative AMD_Matt said in October that the company was investigating, with the aim of fixing it in a future driver. AMD_Vik later said the behaviour comes from an interaction between the External Events Utility and Microsoft’s PCIe filter driver, that a fix had been submitted, and that Adrenalin 26.11.1 should contain it. He also said he could not give a day, only that it would be this month. VideoCardz and TechSpot both report that account. HotHardware described a different mechanism, a search for chipset files removed after driver 26.3.1. That is a user-forum theory, not the explanation AMD_Vik gave.

How much gets written

FigureWho measured or calculated itWhat it is
0.3 to 1.5 MB/sUser reports, collected by VideoCardzThe range most reports give for continuous writes
5 MB/sOne Reddit report, via VideoCardzThe high end of the reported rates
About 432 GB a day, nearly 13 TB a monthVideoCardz, from the 5 MB/s reportArithmetic for uninterrupted writing. VideoCardz says this is not a count of physical NAND writes, and that the effect on drive endurance is not established
19.5 GB in 12 hours, then a rate of 0.65 MB/sTomasz Gawroński, 9 November 2026, quoted by VideoCardzOne machine on Adrenalin 26.10.1 and 26.10.2. He put the sustained rate at 56 GB a day
About 1 percent of reported SSD health each month, for 16 monthsA Radeon owner, reported by Tom’s HardwareA health-percentage claim from one owner, not a lab measurement

TechPowerUp summarises the same reports as dozens of gigabytes written for no useful purpose. The wear claim in the headline is what owners are worried about. What is established is continuous writing on some PCs. What is not established, VideoCardz says outright, is how much of that traffic becomes wear on the flash itself.

Which driver, and the fix

The reports VideoCardz and TechPowerUp rely on name Adrenalin 26.10.1 and 26.10.2. VideoCardz also says the bug does not show up on every Radeon PC, including some machines still on 26.10.2, and that it has been reported across more than one Adrenalin release and more than one Windows version. The 26.10.2 release notes do not list a fix. On the same VideoCardz page, the current Radeon driver in its driver list is 26.10.2 Optional, dated 30 October 2026. Adrenalin 26.11.1 was not in that list on 11 November 2026.

Tom’s Hardware uses different version strings for the same episode. It says reports include Adrenalin 26.19.2, and it calls the 30 October release notes Adrenalin 26.20.2. That does not match the 26.10.2 label on VideoCardz’s driver list. AMD has not posted a bulletin that picks one numbering. The fix VideoCardz and TechPowerUp both attribute to AMD staff is still 26.11.1.

Until that driver appears, the check is Windows Resource Monitor. Press Win+R, type resmon, open the Disk tab, and sort by write. The name to look for is atieclxx.exe, writing steadily while the PC is idle. A short burst while a window moves is a different, older complaint. This bug is the write that does not stop.

Owners on the threads those sites cite have reported two temporary workarounds: disabling the AMD External Events Utility service, or turning off Resizable BAR in the BIOS. VideoCardz says neither works in every reported case. Disabling the service can stop Adrenalin hotkeys and some display behaviour. Turning off Resizable BAR can cost gaming performance. AMD has not published either step as the remedy. The remedy it has named is the driver.

This is a graphics-driver fault on Windows, not a model or an editor fault. If the same PC is the one you use for an AI coding tool, the machine setup notes are in Cursor’s Windows setup, and the separate question of which tool to run on it is in how to choose an AI coding tool.

Sources

  • VideoCardz, 9 November 2026. AMD_Matt, AMD_Vik, the PCIe filter explanation, Adrenalin 26.11.1, the write rates, the 432 GB estimate, the Gawroński measurement, and the two workarounds.
  • TechPowerUp, 10 November 2026. Confirms 26.10.1, 26.10.2, atieclxx.exe, and 26.11.1, and says the site spoke with AMD.
  • TechSpot. The log folder it reports, and the same AMD_Vik account of the PCIe filter driver.
  • Tom’s Hardware. The owner who reported about 1 percent of SSD health gone each month for 16 months, and the conflicting 26.19.2 and 26.20.2 version strings.
  • HotHardware. A conflicting account that blames a search for chipset files removed after driver 26.3.1.

AMD driver bug wears out storage drives. A Radeon graphics software glitch continuously writes data even when idle.

AMD staff have confirmed a Radeon bug in which atieclxx.exe, part of the AMD External Events Utility, writes to the system drive continuously, including while the PC is idle. Reported rates run from 0.3 MB/s to 5 MB/s. AMD_Vik has said Adrenalin 26.11.1 should fix it, later in November 2026, with no day named. VideoCardz says the effect on actual flash wear is not established. One owner told Tom’s Hardware the drive’s reported health fell about 1 percent a month for 16 months.

How do I check whether my PC is affected?

Open Resource Monitor with Win+R and resmon, then the Disk tab, and sort by write. Look for atieclxx.exe writing steadily while the PC is idle. VideoCardz says some Radeon PCs on Adrenalin 26.10.2 show no unusual writing.

Should I disable the AMD External Events Utility?

AMD has not published that as the fix. Owners report that stopping the service, or turning off Resizable BAR, can halt the writes, and that neither works in every case. Stopping the service can disable Adrenalin hotkeys and some display behaviour. The fix AMD has named is Adrenalin 26.11.1.

Need this done for your business?

No published packages. A written quote within 24 hours. Worldwide delivery.

Chat on WhatsApp