AMD released its Adrenalin Edition 26.11.1 optional driver today, closing a bug that flooded SSDs with excessive background writes. The culprit was atieclxx.exe, a utility that fell into an infinite loop and generated roughly 55 GB of daily writes on RX 7000 series and newer cards. Before this fix, affected users leaned on community workarounds like the open-source atieclxx-fix tool, which AMD now officially recommends replacing. Despite the win, the driver still ships with nine acknowledged known issues targeting flagship RX 9000 cards and the newest Ryzen AI processors.

AMD Software: Adrenalin Edition 26.11.1 finally stops a driver bug from quietly eating your SSD

AMD's optional hotfix closes a long-running loop that flooded drives with unnecessary writes and it's not even the only bug shipping.

Today, AMD pushed an optional update to its Adrenalin Edition driver suite. Version 26.11.1. It isn't the flashiest release of the year, but it does something a lot of people have waited weeks for. It stops a background utility from hammering your SSD 24 hours a day.

The SSD-write loop has been AMD's most public headache for months. A Reddit user named darklinkpower reignited the fire on November 8 with a PSA on r/pcmasterrace, and the fallout rippled across forums, hardware subreddits, and a fair chunk of social media. AMD had acknowledged the problem back in October. It simply hadn't shipped the fix until now.

Keep in mind that this is a targeted hotfix, not a performance boost. There's no new game support, no optimizations, nothing to push your frames higher. Its whole reason for existing is to repair damage. The bug, the fix, and the community workaround

The utility behind all of this is atieclxx.exe, part of the AMD External Events Utility. It handles display stuff: monitor detection, hotkeys, FreeSync, and frame pacing. The sort of thing you never notice until it starts misbehaving.

In the affected systems it apparently fell into an infinite write loop, copying its own 677 KB program file into a Windows system-profile folder roughly once per second. The path is C:\Windows\System32\config\systemprofile\AppData\Local\AMD\atieclxx.exe.

Not cheap. At that measured rate the loop generates about 55 GB of writes per day. That's roughly 13 TB a month, or about 20 TB a year. A typical 1 TB SSD is rated for around 600 TB of total writes, so a single drive won't die overnight. Cheap, small drives are rated far lower, and the wasted traffic is pure.

The root cause, per an open-source analysis behind the GitHub project candygoogy/atieclxx-fix, is essentially a botched install step. The utility keeps trying to install the amdkmpfd PCI filter driver, but current Adrenalin packages point it at setup files it no longer ships. Every attempt fails. It just retries. Forever.

A neat trick for software, if you want to call it that.

26.11.1 addresses two things, both tied to that same bug. Excessive writes while idle affects RX 7000 series and newer. The second is a window-move/resize variant, where dragging a window triggers the same flood.

For the record, AMD maintains a dedicated FAQ (PA-365) directing RX 7000 and RX 9000 users straight at 26.11.1 as the solution, and it wants anyone who already applied a workaround to restore default settings first.

The community was clearly faster than AMD's release cadence. A modder known as Necandi released an open-source tool, Radeon-atieclxx-SSD-Fix, that stops the writes without killing the External Events Utility outright.

It works through file permissions rather than by nuking the service. It denies the SYSTEM account write and delete access to the copied exe, so when the utility tries its once-a-second copy, Windows refuses before anything lands on disk.

The clever part is that FreeSync and VRR keep working. Killing the service entirely breaks variable refresh rate, as several users discovered the hard way. A scheduled task re-checks protection every 30 minutes, so the fix survives driver updates and lifts itself once AMD's corrected driver shows up.

It does modify file permissions and needs admin rights, and AMD notes the workaround hasn't been independently verified. If you're keeping score, the official fix is preferable now that it exists.

Nine known issues still on the bus

Here's where it gets mixed. For all its goodwill, 26.11.1 ships with nine acknowledged "Known Issues," and several target brand-new hardware: the RX 9000 series and the newest Ryzen AI Max PRO CPUs.

You've got intermittent crashes in Assassin's Creed's Black Flag Resynced on RX 7000 cards, driver timeouts in War Thunder on RX 5000 series (AMD points you back to 26.9.1), and a Cyberpunk 2077 crash tied to combining FSR, Anti-Lag, and in-game frame generation during video playback. There are black screens on Gears of War: Reloaded, visual corruption on hair in Phantom Blade Zero, and a Smart Access Memory quirk on Windows 10 systems.

Nine problems on flagship gear. That's a lot of open doors for a release you'd otherwise call a clean win.

If you own an RX 7000 or newer and have watched your drive's health percentage bleed out, then install it. 26.11.1 is the fix AMD promised back in October, and it removes the need to disable critical display services or poke at BIOS settings like Resizable BAR. It's arguably competing with those messy community hacks on merit now.

If you're unaffected, the update stays optional for a reason. Though those known issues above may nudge some people toward it anyway.

AMD did get caught out twice on this. A nearly identical pattern showed up back in November 2024, when moving or resizing on-screen elements triggered repeated logfile writes to C:\Windows\System32\AMD\EEUDumps\. So impatience wasn't exactly rewarded the first time around.

Head here for the full release notes.