What the bug actually did
The culprit is a small helper process most Radeon owners have never looked at. AMD confirmed the problem earlier this week, tracing it to the External Events Client Module (atieclxx.exe) in the 26.10.1 and 26.10.2 drivers. TechPowerUp describes the process as part of AMD's External Events Utility, which handles jobs like detecting monitors and responding to Radeon software hotkeys. Under the bug, it got stuck in a loop and kept writing data.
The amounts sound alarming once you multiply them out. User reports put the write rate anywhere from 0.3 MB/s to 5 MB/s, which works out to roughly 26 GB to 432 GB a day on a machine that's doing nothing. One widely shared measurement came from Tomasz Gawroński on X. PC Gamer reported that he saw atieclxx.exe log 19.5 GB of I/O writes in 12 hours. He also claimed the problem goes back to Adrenalin 26.7.1, released July 28. Ubergizmo reported that users have reported the behavior on the AMD community forum since at least July. AMD's own confirmation, as reported, names only 26.10.1 and 26.10.2. Treat the earlier start date as a user claim, not an official finding.
Summary: A background AMD process wrote to the system drive nonstop while the PC sat idle. AMD confirmed it in 26.10.1 and 26.10.2, and some users say it started earlier.
The "432 GB a day" figure needs some context
The headline numbers are rate estimates, not measured damage. The figures come from Windows' per-process I/O counters. VideoCardz notes that they do not necessarily represent physical NAND writes, and the actual impact on SSD endurance has not been established. Writes can be cached, combined or overwritten before they reach flash, so host-level I/O and real wear are not the same thing.
The 432 GB number also assumes a constant 5 MB/s for 24 hours, which was the worst user report. The low end, about 26 GB a day, is much more modest. NT Compatible offered some perspective: a typical 1 TB SSD is rated for around 600 TB of total writes, so a single drive won't die overnight.
That doesn't make the bug harmless. Some Reddit users told PC Gamer they were losing about 1% of SSD health per month. Those are anecdotes, not controlled tests, but a quiet, ongoing drain on a pricey NVMe drive is a real problem. It matters most on small-capacity drives with low endurance ratings.
Summary: Take the bug seriously, but don't panic. The big numbers are worst-case extrapolations of host I/O, not verified flash wear.
What Adrenalin 26.11.1 fixes
The release contains two related fixes:
- Idle writes: According to the release notes, the update addresses excessive writes to the system drive while the PC is idle on Radeon RX 7000 series cards and newer.
- Window movement: It also fixes a related case where excessive writes could show up while moving or resizing application windows. VideoCardz notes that AMD lists this separately and does not specify which graphics products are affected.
AMD only names a GPU generation for the idle fix, so older cards are a grey area. TechPowerUp points out that the release notes only mention RX 7000 and newer for the idle fix, so it isn't clear whether older Radeon cards were affected at all. Some RX 6600 XT and RX 6700 XT owners in TechPowerUp's comments said they couldn't reproduce the bug. PC Gamer's own tester couldn't reproduce it on his AMD system either.
One label to keep in mind: this is an optional driver, not a recommended (WHQL-track) release. VideoCardz's view is that although AMD labels this release as optional (so basically a hotfix), it includes official fixes for both causes of excessive drive writes.
Summary: 26.11.1 fixes idle writes on RX 7000 and newer, plus a window-resize trigger with no GPU limit stated.
How to check whether your PC is affected
You don't need any extra software. Task Manager can show it:
- Press Ctrl + Shift + Esc to open Task Manager.
- Go to the Details tab.
- Right-click any column header and choose Select columns.
- Turn on I/O Read Bytes and I/O Write Bytes.
- Sort by I/O Write Bytes and find atieclxx.exe.
- Leave the PC idle for a few minutes and watch the number.
The I/O Write Bytes column is a running total since the process started. A large number on its own proves nothing. What matters is whether it keeps climbing steadily while you aren't doing anything. Ubergizmo's rule of thumb: if atieclxx.exe stays near the top with steady writes, you're likely affected. If you want something more lasting than a quick check, write down your drive's health and total host writes in a SMART tool like CrystalDiskInfo now, then compare in a few weeks.
Summary: A rising counter at idle is the warning sign, not a big number on its own.
What to do now
If you're affected: install 26.11.1 through AMD Software or AMD's driver page, then repeat the Task Manager check. A counter that stops racing upward means the fix took.
If you used a workaround, undo it. Before the patch, affected users had to disable the External Events Utility, turn off Resizable BAR, or use a community-made open-source tool that blocks the writes. That tool is Radeon-atieclxx-SSD-Fix, released by ComputerBase forum member Necandi. Now that the official fix is out:
- If you disabled the service: Ubergizmo advises that after installing 26.11.1, set Startup type back to Automatic and start the service.
- If you turned off Resizable BAR: turn it back on in your BIOS/UEFI. TechPowerUp warned that leaving it off could cost performance.
- If you installed the community tool: We recommend the official update over third-party workarounds. That's VideoCardz's advice, and it's sensible. A hook that blocks a driver component's file activity is exactly what you'll forget about until it causes the next mystery bug.
If you're not affected: there's no rush. 26.11.1 has its own baggage. NT Compatible counts nine acknowledged "Known Issues," and several target brand-new hardware: the RX 9000 series and the newest Ryzen AI Max PRO CPUs. One example: users experiencing intermittent driver timeouts while playing War Thunder on Radeon RX 5000 series GPUs are advised to roll back to AMD Software: Adrenalin Edition 26.9.1. Read the known-issues list for your card and your main games before you update.
Reports also disagree on the minimum Windows 10 version. IT Home's summary says 1809 or later, but other readings of AMD's notes list 21H2 or later. If you're on an older Windows 10 build, check the release notes before installing.
Laptops and handhelds: AMD generally points laptop and all-in-one owners to drivers from their PC maker, since those are validated for that specific hardware. Check your OEM's support page first. If you need to roll back, AMD's Cleanup Utility is the clean way to remove a driver before going to an older version.
Summary: Affected users should update and undo any workarounds. Everyone else can wait for a recommended release if the known issues worry them.
Analysis: a slow fix for a quiet bug
Credit where it's due: once the reports went viral, AMD confirmed the bug, named the release that would fix it and shipped that release within days. That's how it should work. It's also how open communication works. Reddit sleuths found the cause, a forum modder shipped a stopgap, and the vendor followed with the official patch.
The timeline still looks less flattering than the "finally fixed" headlines. If the forum reports are right, this went on for months. One AMD representative told users last month the company was "looking into it." Ubergizmo reports the fix missed 26.10.2 before landing in 26.11.1.
This is the second year running that Windows users have had SSD health scares. Ubergizmo recalled that in 2025, Microsoft found no link between a Windows 11 update and reported SSD failures. Phison traced the failures it examined to pre-release engineering firmware. The AMD case is different because the vendor confirmed the bug. The broader lesson is to judge SSD scares by measurements, not viral screenshots.
The other lesson is about bloat. A process meant to watch for monitor changes and hotkeys has no business writing gigabytes to disk. Many TechPowerUp commenters said this is why they install drivers only, without the companion software. That isn't practical for everyone, since features like overlays and hotkeys depend on it. Still, every background helper is one more thing that can quietly misbehave.
Bottom line: Check Task Manager. If atieclxx.exe is climbing at idle, install Adrenalin 26.11.1 and undo any workarounds. If it isn't, read the known issues before you decide whether to update.
Correction (November 12, 2026): An earlier version of this article said Adrenalin 26.7.1 was released in June. AMD's release notes show it was released on July 28, 2026.