AMD’s release notes dated November 12, 2026, introduce AMD Software: Adrenalin Edition 26.11.1 Optional for Windows. It fixes a Radeon driver bug where the AMD External Events Utility (atieclxx.exe) kept writing to your system drive while the PC sat idle.
What Happened: AMD’s Radeon Driver SSD Write Bug Fix
According to AMD’s 26.11.1 Optional release notes, the driver fixes two related problems. The first is excessive writes to the system drive at idle. The second is extra writes triggered when you move or resize an application window.
According to secondary reporting from TechPowerUp and lowyat.net, the idle bug traces to atieclxx.exe, AMD’s background process that handles events like FreeSync and Radeon hotkeys. Those reports describe the process writing small chunks of data to disk repeatedly, even when nothing was happening on screen.
AMD’s own release notes confirm the excessive-write behavior at idle but don’t document that process-level detail themselves. It’s worth keeping AMD’s confirmed description of the bug separate from what outside outlets pieced together about the mechanism.
AMD’s release notes list driver version 26.20.15.16 (Windows Driver Store version 32.0.32015.16001) for Radeon graphics in this build. It’s free, and you download it from AMD’s support pages like any other Adrenalin release.
Who This Affects
AMD’s SSD Write Issue FAQ (PA-365) scopes the problem to Radeon RX 7000-series and newer GPUs. It names the RX 7000 and RX 9000 families specifically.
AMD’s release notes list support for Windows 11 version 21H2 and later and 64-bit Windows 10 version 21H2 and later, though AMD adds that operating system support may vary by Radeon product.
If you run an older Radeon card, AMD’s documentation doesn’t name it. Reports also suggest the bug didn’t show up on every RX 7000 or RX 9000 system, so check the FAQ before assuming you were hit.
How It Stacks Up
The scary numbers you’ve seen come from users and secondary coverage, not AMD. TechPowerUp and lowyat.net relayed reported rates of roughly 0.3 MB/s to 5 MB/s. If that ran nonstop all day, it would add up to about 26 GB to 432 GB of writes.
Real systems don’t sit idle 24 hours a day, and rates varied by setup. AMD’s confirmed statements center on the bug and the fix, not on quantifying wear or on reports of failed drives.
Before the driver landed, owners had three stopgaps. Here’s how they compare with the official fix:
| Option | What it does | Downside | Source |
|---|---|---|---|
| Adrenalin 26.11.1 Optional | Fixes idle writes and window move/resize writes | Optional release; the usual non-WHQL caveat applies | AMD release notes |
| Disable AMD External Events Utility | Reported to stop the writes right away | Reported to disrupt FreeSync and Radeon hotkeys | lowyat.net |
| Disable Resizable BAR in firmware | May reduce the writes, per community reports | May affect gaming performance on some systems | lowyat.net |
| Open-source file-permission tool | Blocks writes to the targeted file while keeping the service running | Unofficial stopgap and unnecessary now | TechPowerUp |
Adrenalin 26.11.1 Optional carries AMD’s Optional label rather than WHQL certification, a distinction both TechPowerUp and lowyat.net note in their coverage. If your system isn’t showing the excessive writes, you can reasonably wait for a WHQL-certified release instead.
The AEEU and Resizable BAR workarounds above come from community and press reporting rather than AMD itself, and they haven’t been validated the way AMD’s driver fix has. Treat them as stopgaps rather than an equivalent alternative to installing 26.11.1.
The Reaction
Reaction is still forming. Tech news accounts on X have been sharing the fix and urging RX 7000 and RX 9000 owners to install it. On Reddit, an r/Amd thread tracked AMD’s confirmation of the bug.
What to Do Next
Install Adrenalin 26.11.1 Optional, restart your PC, and confirm the idle writes have stopped before touching anything else. Only then reverse the workarounds you applied, ideally one at a time while watching disk activity after each change rather than undoing everything at once.
Because it’s an Optional release, you can download it directly from AMD’s support site rather than wait for it to surface through Windows Update or AMD’s regular notifications.
- Install Adrenalin 26.11.1 Optional and restart your PC.
- Confirm disk activity has returned to normal before undoing any workaround.
- If you disabled the AMD External Events Utility, re-enable it in Services (
services.msc) so FreeSync and hotkeys work again. - If you turned off Resizable BAR in your motherboard firmware, turn it back on.
- Check that Smart Access Memory shows as enabled in AMD Software.
That last check matters most on Windows 10. AMD’s 26.11.1 release notes list a known issue where Smart Access Memory may become disabled after driver installation on Windows 10 systems, so confirm the setting even if you never touched Resizable BAR.
Our Take
Verdict: Install now. Worry a little, not a lot.
Based on how SSD write endurance works, repeated small writes typically contribute to gradual wear rather than sudden failure. SSDs are rated for a set amount of total writes, and a stray background process eats into that budget.
A few months at the reported rates is a real cost, but modern drives have plenty of headroom for most owners. The cited reporting does not document a confirmed drive failure tied to this bug.
If you want peace of mind, open an SSD health tool and look at total bytes written and remaining life. Healthy readings mean you can move on. If the numbers look worse than your usage explains, back up to an external SSD and start pricing a replacement NVMe SSD before it becomes urgent.
Wrapping Up
Adrenalin 26.11.1 Optional is the fix. Once installed, the workarounds in the table above are no longer needed, though you’ll still want to manually restore any settings you changed.
Install it, re-enable whatever you switched off, and confirm Smart Access Memory survived. The next time you spot constant disk activity on an idle PC, open Task Manager’s Processes tab, sort by Disk, and see which process is writing. That’s one way to identify a process causing unexpected disk activity.
