AMD Radeon Driver Bug Wrote to Your SSD: What 26.11.1 Fixes
AMD confirmed a Radeon driver bug that kept writing small amounts of data to the system SSD, even at idle. Adrenalin 26.11.1 fixes it.

AMD has confirmed a Radeon graphics driver bug that caused a background Windows service to continuously write small amounts of data to the system drive, even while a PC sat idle, and the company's own release notes for AMD Software: Adrenalin Edition 26.11.1 list the fix under "Fixed Issues" as of November 12, 2026. Third-party monitoring by reviewers and users pegged the continuous write rate at roughly 0.6 to 5 MB/s, which can add up to tens of gigabytes a day on a system that is otherwise doing nothing — a pattern that raised concerns about accelerated SSD wear long before AMD shipped a patch.
The short version:
- What broke: A background Radeon driver component kept writing to the system SSD even at idle and during routine window moves/resizes.
- Which process: Independent testing identified the culprit as the AMD External Events Utility (the
atieclxx.exeprocess installed with Radeon drivers). - How much data: Reported continuous rates of about 0.6–5 MB/s in third-party testing — AMD's own notes don't publish a figure.
- The fix: AMD Software: Adrenalin Edition 26.11.1, an "Optional" (non-WHQL) driver dated November 12, 2026.
- Who's covered: AMD's release notes specifically name Radeon RX 7000 series graphics products "and above."
What was actually happening to Radeon users' SSDs
Over the past several months, Radeon owners using various builds of AMD Software: Adrenalin Edition began noticing their system drive's activity light staying lit, and disk-monitoring tools showing steady write activity, even when no games were running and the PC was sitting at the desktop. The writes weren't large individually, but they were constant — accumulating over a day, a week, and a year into a meaningfully larger total write volume than a typical idle Windows PC should generate.
AMD's own fixed-issues list for Adrenalin 26.11.1 describes the problem in plain terms: "Excessive writes to the system drive may be observed while the system is idle on Radeon RX 7000 series graphics products and above," and separately, "Excessive writes to the system drive may be observed while moving or resizing application windows." Those two sentences, taken directly from AMD's published release notes, are the closest thing to an official description of the bug that AMD has put on the record.
Which driver component was responsible
AMD's release notes don't name a specific executable, but independent testing and driver-file monitoring by multiple outlets converged on the same culprit: a background service commonly referred to as the AMD External Events Utility, which runs as the process atieclxx.exe (AMD External Events Client Module). That service ships with Radeon drivers to handle hot-plug and display-detection events — tasks like noticing when a monitor is connected or a laptop lid is closed — and it is not something most users would normally think to look for in Task Manager.
The working theory reported across testing circles pointed to an interaction between that utility and a Microsoft PCIe filter driver, which caused the service to repeatedly rewrite small log or state files rather than updating them in memory only when something actually changed. Because AMD's own notes don't spell out the root cause, that explanation should be treated as the best available account from cross-checked third-party testing rather than AMD's verbatim diagnosis.
How much data was being written
Figures varied depending on the system and the monitoring window, but third-party testing that tracked the affected process over time converged on a range of roughly 0.6 MB/s to 5 MB/s of continuous writes while idle. At the low end of that range, a PC left on overnight could still rack up several gigabytes of unnecessary writes before anyone sat back down at the keyboard. At the high end, some testers reported daily totals in the tens of gigabytes.
It's worth being precise about what that does and doesn't mean. Modern consumer SSDs are typically rated for hundreds of terabytes of total written data (TBW) over their warrantied lifespan, so a few extra gigabytes a day is unlikely to meaningfully shorten the life of most drives used for a few years. The bigger practical issues were the ones affected users actually noticed: constant disk-activity-light flicker, background write amplification on drives already near capacity, and — for anyone tracking SSD health metrics closely — a steadily climbing "total bytes written" counter that didn't match their actual usage.
How the story developed
Reports of unusual, constant disk writes tied to Radeon drivers trace back further than most people realized once the issue became widely discussed — isolated user reports describing persistent I/O from AMD's external-events component go back months, well before it became a mainstream story. The issue picked up broader attention through the autumn of 2026 as more users compared notes on forums and social media and found the same process behaving the same way across very different hardware configurations, which ruled out a single bad machine or a one-off Windows update as the cause.
That pattern of independent, reproducible reports from unrelated systems is what pushed the issue from "one person's weird Task Manager reading" to something AMD needed to formally address. By the time AMD's Adrenalin 26.10.2 driver shipped in late October 2026, the issue still wasn't listed in that release's fixed-issues section, which is why coverage through early November continued treating it as unresolved. AMD's November 12, 2026 release notes for 26.11.1 are the first place the company has put a fix for this specific symptom on the record in its own documentation.
Which drivers had the bug, and which one fixes it
AMD's release notes identify the fix as shipping in Adrenalin 26.11.1, released as an "Optional" driver (meaning it hasn't gone through AMD's full WHQL certification process) dated November 12, 2026. The notes list two related entries under "Fixed Issues" for that release, both tied to excessive system-drive writes on Radeon RX 7000 series graphics products and above.
| Driver / status | SSD write issue | What to do |
|---|---|---|
| Adrenalin builds prior to 26.11.1 | Continuous idle writes and window-resize writes reported by users and independent testing | Update to 26.11.1 or later when convenient; a temporary service-disable workaround trades off some Radeon features |
| Adrenalin 26.11.1 (Optional, Nov. 12, 2026) | Listed as fixed in AMD's official release notes for idle writes and window-resize writes | Install via AMD Software or AMD's support site; use the AMD Cleanup Utility if downgrading afterward |
| Future WHQL driver after 26.11.1 | Expected to carry the same fix forward once certified | No action beyond normal driver updates |
Because 26.11.1 is an Optional release rather than a WHQL-certified one, it's aimed at users who want the fix immediately; AMD typically folds Optional-driver fixes into the next fully certified release as well.
What AMD's release notes actually say
The full "Fixed Issues" entry on AMD's own Adrenalin Edition 26.11.1 release notes page (article number RN-RAD-WIN-26-11-1, last updated November 12, 2026) reads:
"Excessive writes to the system drive may be observed while the system is idle on Radeon™ RX 7000 series graphics products and above. Excessive writes to the system drive may be observed while moving or resizing application windows."
That's the entirety of AMD's own public wording on the issue at the time of writing — it confirms the symptom and the affected product tier (RX 7000 series and newer) without naming the specific background process or citing a write-rate figure. Anyone who wants the primary account of what AMD fixed, as opposed to third-party reconstructions of it, should treat that release-notes entry as the authoritative source.
How to tell if you were affected, and how to update
If you want to check your own system before or after updating, Windows' Resource Monitor (Disk tab) or Task Manager's "I/O Write Bytes" column (enabled via the column picker on the Details/Processes tab) will show ongoing write activity by process. Watching that column for a few idle minutes is enough to see whether any background process is writing continuously.
To install the fix:
- Open AMD Software: Adrenalin Edition and check for updates, or download 26.11.1 directly from AMD's AMD Drivers and Support page.
- If you're coming from a build where you'd already applied a manual workaround (such as disabling the AMD External Events Utility service in Windows Services, or using a third-party tool that restricted the process's write permissions), re-enable the service or remove the workaround after installing 26.11.1 so Radeon features that depend on it — including some hotkey and display-detection behavior — work normally again.
- If you plan to roll back to an older driver for any reason, AMD recommends using the AMD Cleanup Utility first to avoid leftover driver conflicts, and AMD's official install guide walks through a clean installation step by step.
What's still outstanding in 26.11.1
AMD's release notes for 26.11.1 list several unrelated known issues that remain open, including an intermittent driver timeout in War Thunder on Radeon RX 5000 series cards (AMD recommends Adrenalin 26.9.1 for users hitting that specific problem), a possible crash or timeout in Cyberpunk 2077 under certain upscaling and frame-generation combinations on some RX 9000 series cards, and AMD Smart Access Memory becoming disabled after installation on Windows 10 systems. None of those are connected to the SSD-write fix, but anyone updating specifically to resolve the write issue should check whether any of the other listed known issues apply to their own game library before assuming 26.11.1 is a clean update in every respect.
Should you actually be worried about SSD wear
The honest answer is: probably not seriously, but it was a real and unnecessary cost. Consumer SSDs are built with endurance ratings measured in the hundreds of terabytes, and even the higher end of the reported write rates — a few tens of gigabytes a day — would take years to meaningfully eat into that budget on its own. The more legitimate complaints were about principle and transparency: a driver quietly generating background wear that users never opted into, didn't benefit from, and in many cases didn't even know was happening until they went looking for it. That's a reasonable thing for AMD to have fixed, independent of whether any specific drive was actually at risk.
How this compares to AMD's rival driver releases
The framing here is different from most driver news. Nvidia's recent GeForce updates, including the driver covering World of Warcraft support fixes and the one addressing new games and known issues, have mostly been about day-one game compatibility and performance tuning. AMD's Adrenalin 26.11.1, by contrast, is a reliability fix — it doesn't add game support or performance claims; its entire news value is that it stops a driver component from doing something it shouldn't have been doing in the background. That's a less glamorous category of update, but for anyone who was watching their drive's write counter climb for no reason, it's the more consequential one.
What you should do next
If you're running a Radeon RX 7000 series card or newer and haven't updated recently, installing Adrenalin 26.11.1 (or whatever later driver eventually supersedes it with the same fix carried forward) addresses the specific issue AMD has acknowledged. If you're on an older Radeon generation, AMD's own notes don't list your card under the fix, so there's less reason to assume the same bug applied to you in the first place — though it doesn't hurt to spot-check Task Manager's I/O column regardless. And if you'd previously applied a manual workaround, remember to reverse it after updating so you're not running a redundant fix on top of AMD's official one.
Frequently asked questions
See the questions and answers below for quick reference on the most common follow-up questions about this issue.
Frequently asked questions
What was the AMD Radeon SSD write bug?
AMD's Adrenalin graphics drivers contained a bug where a background component kept writing small amounts of data to the system SSD continuously, even while the PC was idle. AMD's own release notes for Adrenalin 26.11.1 list the fix under 'Fixed Issues,' describing excessive writes to the system drive at idle and during window moves/resizes.
Which process was responsible for the extra SSD writes?
AMD's release notes don't name a specific process, but independent testing and driver-file monitoring identified the AMD External Events Utility, which runs as atieclxx.exe, as the component generating the continuous writes.
Which Radeon graphics cards were affected?
AMD's official release notes specifically name Radeon RX 7000 series graphics products 'and above' as the scope of the fix. AMD's documentation does not list older Radeon generations as affected by this particular fix.
How much data was actually being written to the SSD?
AMD hasn't published a specific figure. Independent third-party testing reported continuous write rates of roughly 0.6 to 5 MB/s while the system was idle, which can total tens of gigabytes over a day on some systems.
Does Adrenalin 26.11.1 completely fix the issue?
AMD's release notes list the excessive-write issue under 'Fixed Issues' for 26.11.1, released November 12, 2026 as an Optional (non-WHQL) driver. That is AMD's official position; as with any driver fix, results can vary by individual configuration.
Should I worry about permanent SSD damage from this bug?
Most consumer SSDs are rated for hundreds of terabytes of total writes over their lifespan, so the reported write volumes are unlikely to meaningfully shorten a typical drive's life. The bigger issue was unnecessary, unacknowledged background wear rather than imminent drive failure.
Sources
Mara Lindqvist edits the hardware desk. She covers graphics cards, processors, memory and storage, the foundries and chip designers behind them, and what the numbers on a spec sheet mean for people choosing a PC. Specifications in her stories come from manufacturer spec pages and datasheets.
