On November 9, 2026, PC Gamer reported that Windows PCs with AMD Radeon GPUs running AMD Adrenalin software may be wearing out their SSDs through a background process called atieclxx.exe.
AMD representatives have acknowledged reports of excessive writes from that process and say a fix is coming, but AMD hasn’t confirmed that those writes have caused measurable SSD-health damage. The “1% SSD health per month” figure comes from user reports and doesn’t hold for every system.
What Happened: The AMD GPU Driver SSD Health Bug
AMD Software: Adrenalin Edition is AMD’s free driver and control-panel package for Radeon graphics on Windows. It handles driver updates, performance tuning, and the overlay. Inside it is the AMD External Events Client Module, which runs as atieclxx.exe and handles low-level system and hardware events for the driver.
Some users trace the problem to Adrenalin Edition 26.7.1, though available reporting doesn’t establish that version as the confirmed starting point. AMD’s own release notes list 26.7.1 with a release date of July 28, 2026, not June as some posts claim.
Users say that starting around that version, atieclxx.exe writes far more data to disk than it should. SSDs have a finite write budget, so sustained junk writes can shorten a drive’s life.
No AMD-published support article, release note, or wear analysis specifically addressing this issue appears in available coverage. AMD’s statements come from community forum representatives AMD_Matt and AMD_Vik, as reported by PC Gamer.
They say a fix has been submitted and should land in a future Adrenalin release, reportedly 26.11.1, later in November 2026. There’s no exact release date. According to Hardware Busters, citing VideoCardz, AMD_Vik traced the behavior to an interaction between AMD’s External Events Utility and Microsoft’s PCIe filter driver. Microsoft hasn’t commented.
Who this affects
The reports cover Windows PCs with AMD Radeon GPUs, with TechPowerUp specifically identifying versions 26.10.1 and 26.10.2 along with several intermediate releases. Even within that group, the bug isn’t universal. PC Gamer couldn’t reproduce it on its own AMD test system.
How It Stacks Up
The scary number spreading online is the 1% monthly figure. Here’s where each data point actually comes from.
| Claim | Source | Verified? |
|---|---|---|
| ~1% SSD health lost per month | Reddit user reports (r/pcmasterrace) | No, anecdotal |
| 1% lost over 16 months | Another Reddit user, per PC Gamer | No, anecdotal |
19.5 GB written by atieclxx.exe in 12 hours | X post | No, single user |
| Bug reproduced on a test system | PC Gamer | No, it didn’t reproduce |
| Fix submitted, targeting 26.11.1 | AMD forum reps, via PC Gamer | Acknowledged, date unconfirmed |
The spread matters. One unverified user report describes losing about 1% of SSD health a month. Another unverified report describes losing that same 1% over 16 months. That’s a 16x gap, and nobody has published controlled measurements to settle it.
The 19.5 GB figure, from a single unverified X post, was measured over 12 hours. Projected around the clock, it would work out to roughly 39 GB a day. How much that matters depends on the drive’s rated endurance (TBW), how long the writes continue, and the rest of your workload.
But it’s one machine, measured by its owner, with no independent confirmation of the figure.
For alternatives, there’s no clean switch. This reporting focuses on AMD Radeon software and doesn’t establish whether NVIDIA’s GeForce drivers have any comparable issue.
Based on available coverage, AMD hasn’t named an officially recommended rollback version, so picking an older driver means guessing.
The Reaction
On X, according to an automated search digest of posts compiled for this story (individual posts aren’t linked here), the mood is alarmed but not divided. One post warned of idle writes up to 5 MB/s, which that user said works out to hundreds of GB a day. That digest isn’t a complete or reproducible sample, so it can’t show that no one pushed back. The 19.5 GB-in-12-hours post became a common reference point.
That consensus has a weakness. Most of it repeats the same handful of user numbers, and the worst-case 5 MB/s figure doesn’t line up with the 16-month report. Loud agreement isn’t the same as measured data. The volume of reposts makes the bug feel bigger and more uniform than the evidence shows.
What To Do Next
Check whether your own PC is affected before you change anything. Press Win + R, type resmon, and open the Disk tab. Under Processes with Disk Activity, look for atieclxx.exe (or the related atiesrxx.exe service) and its Write (B/sec) value. A process that keeps writing steadily while your PC sits idle is the pattern users describe.
Other apps and Windows itself also write in the background, so idle writes alone don’t prove you’re hitting the AMD bug.
Then check your SSD’s health and total host writes in your drive maker’s utility, such as Samsung Magician or Crucial Storage Executive. Note the numbers and look again in a week.
That gives you your own data instead of a stranger’s. Keep in mind that the health percentage is each drive maker’s own wear estimate, not a universal scale, and the exact labels differ by tool, so total host writes is the more comparable number. A week of readings shows how much is being written, but on its own it can’t prove flash wear or pin the cause on AMD’s utility.
Our Take
Install the fix when it ships, pause on panic, and skip unofficial workarounds. AMD has acknowledged the excessive-write behavior from atieclxx.exe, which makes it more than a rumor, but AMD hasn’t confirmed any resulting SSD-health degradation.
The damage figures are anecdotal and vary wildly, and PC Gamer’s own system was fine.
Rolling back has a real cost. Based on available coverage, AMD hasn’t named a safe rollback version. Older releases may also lack game fixes and other changes AMD has shipped since. Killing or disabling atieclxx.exe isn’t an AMD-endorsed step, and it could break driver features you rely on.
How worried should you be? Mildly, unless your own monitoring shows heavy idle writes. Short-term risk to most drives can’t be inferred from the available reports, but sustained extra writes do consume drive endurance and are worth watching.
If your drive is already low on health, back it up to an external backup drive now. That’s cheap insurance whatever the cause.
Wrapping Up
Check atieclxx.exe in Resource Monitor once. Install Adrenalin 26.11.1 when AMD releases it and its notes confirm the fix; until then, monitor sustained writes.
Roll back only if you see sustained idle writes and your SSD’s health is visibly sliding week to week, knowing you’re choosing an unendorsed version. Stay put and wait for the patch if the process looks quiet. If your health numbers keep dropping after the fix lands, suspect the drive itself and start pricing an SSD upgrade.