Home Technology Your AMD Driver Is Secretly Killing Your SSD While You Sleep –...

Technology

Your AMD Driver Is Secretly Killing Your SSD While You Sleep – Check In 60 Seconds (Fix For atieclxx.exe)

November 9, 2026

amd-radeon-driver-bug-ssd-writes-atieclxx-fix

Your PC is lying to you.

You close your games. You close Chrome. You go to bed. Your PC is “idle.” Fans quiet. Lights off.

But inside, a tiny AMD process is still awake. Writing. Writing. Writing. To your SSD. All night. Every night. For months.

And you would never know — until your SSD health drops 1%… then 2%… then 16%.

A bug in AMD’s Radeon driver (Adrenalin 26.6.4 to 26.10.2) makes a background service called AMD External Events Utility (atieclxx.exe) write to your SSD non-stop, even when idle — 0.3 to 1.5 MB/s for most people, up to 5 MB/s in the worst case. That’s 26GB to 432GB of useless writes PER DAY. AMD has acknowledged it. Fix is expected in Adrenalin 26.11.1 later in November 2026. It has NOT shipped yet. Check in 60 seconds with resmon, and use the safest workaround below if you’re affected. Don’t panic — not every Radeon PC is affected.

1. The Villain: A 20-Year-Old Process Named atieclxx.exe

Say it with me: ay-tee-ee-see-el-ex-ex-dot-exe

That’s AMD External Events Client Module. It’s part of AMD External Events Utility. It’s been in AMD drivers since the ATI days.

Its normal job is boring and useful:

Did you plug in a second monitor? Tell Windows.
Did you press Alt+R for Radeon Overlay? Open it.
Did FreeSync turn on/off? Sync the refresh rate.

That’s it. It should sit quietly, use 0% CPU, write 0 bytes to disk, until you actually DO something with your display.

But on affected PCs, it got stuck in a loop.

Imagine a kid asking: “Are we there yet? Are we there yet? Are we there yet?” — 5 times per second, forever, and writing down each question in a notebook. That’s what this bug does. It keeps asking Windows / the PCIe driver for something that doesn’t exist anymore, and logging the answer to disk.

2. Why Is It Looping? Two Theories, One Truth

AMD hasn’t published the exact code bug, but AMD rep AMD_Vik on Reddit and AMD_Matt on AMD’s forum gave us the official clue:

Official theory: Interaction between AMD External Events Utility and Microsoft’s PCIe filter driver. Something about how the GPU talks to the motherboard over PCIe keeps triggering a re-check, which writes a log, which triggers another re-check.

Community theory (from Reddit u/Spardax_117, u/videoismylife): After Adrenalin 26.3.1, AMD removed some old chipset driver files. The External Events Utility keeps looking for those missing amdkmpfd files, can’t find them, writes an error, tries again. Forever.

Both theories point to the same thing: It’s not your SSD. It’s not your GPU dying. It’s a dumb loop in software.

And this is the SECOND time this has happened. In Nov 2025, the same kind of loop was in AMD’s chipset driver. AMD fixed it in chipset driver 8.09.28.1124. Now it’s back, but in the GPU driver. Like a horror movie sequel.

3. How Bad Is It Really? Let’s Do The Math (No Hype)

HotHardware and others throw around “432GB per day!” — that’s the WORST case. Most people are much lower. Here’s the real table:

Write Speed (What You See In resmon)	Per Hour	Per Day (24h PC On)	Per Month	Who Gets This?
0.3 MB/s	1.1 GB	26 GB	0.8 TB	Most affected users — annoying, not deadly
0.65 MB/s	2.3 GB	56 GB	1.7 TB	Reddit user @GawroskiT — 19.5GB in 12 hours
1.0 MB/s	3.6 GB	86 GB	2.6 TB	Common middle case
1.5 MB/s	5.4 GB	130 GB	3.9 TB	High end, typical “bad” case
5.0 MB/s	18 GB	432 GB	13 TB	1 user — darklinkpower, RX 6700 XT, worst reported

So Will Your SSD Die?

Here’s where everyone else gets it wrong. They say “432GB per day = your SSD will die in 6 months!” That’s not how SSDs work.

SSDs have a rating called TBW = Total Bytes Written. It’s how much data the manufacturer guarantees you can write before the flash cells wear out.

Your SSD	Typical TBW	At 1 MB/s (2.6 TB/month)	At 5 MB/s (13 TB/month)
500GB Budget QLC (e.g. Crucial P3, WD Green)	150-300 TBW	5-10 years to hit TBW	1-2 years to hit TBW — DANGEROUS
1TB Mid-Range TLC (e.g. Samsung 990 EVO, WD SN850X)	600 TBW	19 years to hit TBW	3.8 years to hit TBW
1TB High-End (e.g. WD Black SN8100)	600-1200 TBW	19-38 years	3.8-7.7 years
2TB TLC	1200 TBW	38 years	7.7 years

Translation: If you have a good 1TB TLC SSD and you’re at 1 MB/s, this bug is annoying but it will NOT kill your drive before you upgrade your PC anyway. If you have a cheap 128GB / 256GB QLC drive in a budget laptop, or you leave your PC on 24/7 at 5 MB/s, this bug CAN actually eat a meaningful chunk of your drive’s life.

And one more nuance: Windows Resource Monitor counts host writes — what Windows SENDS to the SSD. The SSD controller caches, compresses, and spreads that out. Not every byte Windows sends = 1 byte of flash wear. So real NAND wear is LESS than the resmon number. How much less? Nobody knows, because AMD and SSD makers haven’t tested it.

That famous “1% health loss per month for 16 months” claim? That’s ONE user (darklinkpower on r/pcmasterrace, Nov 8, 2026). It’s not a scientific study. His drive health % is a vendor estimate, not a direct measure of dead cells. Don’t use it to predict YOUR drive. Use YOUR drive’s health % instead.

4. Check Your PC In 60 Seconds (Do This NOW)

Don’t guess. Don’t panic. Check.

Step 1: Close your games, browsers, downloads. Let your PC sit idle for 1 minute.

Step 2: Press Win + R, type resmon, press Enter.

Step 3: Click the Disk tab. Click Write (B/sec) to sort by biggest writer.

Step 4: Look for atieclxx.exe or atiesrxx.exe.

What you want to see: 0 B/sec, or a tiny spike every few seconds, then back to 0. That’s normal.

What means you’re affected: atieclxx.exe writing steadily — 300,000 B/sec (0.3 MB/s) to 5,000,000 B/sec (5 MB/s) — for 60+ seconds straight while you do NOTHING.

Bonus check — SSD Health: Download CrystalDiskInfo (free) or check your SSD maker’s tool (Samsung Magician, WD Dashboard, Crucial Storage Executive). Look at Health % and Total Host Writes. Write down today’s number. Check again in 7 days. If Host Writes jumped by 500GB+ and you barely used your PC, that’s the bug.

5. Who Is Affected? (And Who Is SAFE?)

	Affected?
Windows 10 / 11 + AMD Radeon GPU (RX 6000, RX 7000, RX 9000 series)	YES — possible. Reports on RX 6700 XT, RX 7800 XT, RX 9060 XT, RX 9070 XT
Adrenalin 26.6.4, 26.7.1, 26.8.1, 26.9.2, 26.10.1, 26.10.2	YES — reported. 26.10.2 (Oct 30) does NOT fix it
Adrenalin 25.12.1, 26.2.2	NO — reported clean by multiple users
Ryzen APU / Integrated Graphics (780M, 890M)	MAYBE — same driver, but fewer reports. Check anyway.
Linux + AMD GPU	SAFE. Linux uses AMDGPU + Mesa, not Adrenalin. Zero reports.
NVIDIA / Intel GPU	SAFE. This is AMD-only.
AMD CPU + NVIDIA GPU	SAFE from this bug (but check chipset driver 8.09.28.1124 is updated for the old 2025 bug)

Key point: NOT every Radeon PC is affected. Some users on 26.10.2 see ZERO writes. Some on 26.8.1 see 5 MB/s. There’s no clear pattern — maybe it’s ReBAR on/off, maybe it’s multi-monitor, maybe it’s PCIe filter driver version. That’s why you must check YOUR PC, not trust a headline.

6. The 3 Fixes — Ranked Safest To Riskiest

Fix #1: Disable AMD External Events Utility (SAFEST, Do This First)

Works for: Most affected users. Risk: Low.

Press Win + R, type services.msc, Enter
2. Find AMD External Events Utility
3. Right-click > Properties > Startup type: Disabled > Stop > OK
4. Reboot. Check resmon again — writes should be 0.

What breaks? Adrenalin hotkeys (Alt+R, Alt+Z) may stop working. Some FreeSync setups may not auto-detect monitor changes. Some users report FreeSync still works fine. One user reported Lossless Scaling 2x frame-gen got unstable on RX 6700 XT.

What does NOT break? Gaming performance, FPS, drivers, display output. Your games will still run.

To undo: Set it back to Automatic, reboot. Easy.

Fix #2: Disable Resizable BAR / ReBAR in BIOS (MEDIUM)

Works for: Some users, not all. AMD_Vik himself said this should work around it. Risk: Medium — you lose performance.

Reboot > Press Del / F2 to enter BIOS / UEFI
2. Find Resizable BAR / Smart Access Memory (SAM) — usually under Advanced > PCI Subsystem
3. Set to Disabled
4. Save & Exit. Check resmon.

Downside: ReBAR / SAM gives you 5-15% more FPS in many games. Turning it off to fix a 1 MB/s write is like cutting off your leg to fix a shoe. Only do this if Fix #1 didn’t work AND you can’t wait for 26.11.1.

Fix #3: Copy 3 Old Files From Driver 26.3.1 (RISKIEST, Only If You’re Tech-Savvy)

Works for: Several Reddit users confirmed. Risk: HIGH — AMD has NOT officially recommended this. You are manually hacking driver files.

Download Adrenalin 26.3.1 driver package (don’t install it, just extract with 7-Zip)
2. Find amdkmpfd.ctz, amdkmpfd.itz, amdkmpfd.stz
3. Copy them to C:\Windows\System32\AMD\amdkmpfd\
4. Reboot. Check resmon.

Why this works (theory): It gives the Utility the files it’s looking for, so it stops looping.

Why we DON’T recommend it for most people: If you copy the wrong version, or Windows Update overwrites it, or you mess up System32, you can cause driver crashes / BSOD. And you’ll have to redo it after every driver update. Wait for the official fix unless you know what you’re doing and you backed up.

What NOT to do: Don’t roll back to a random old driver from a sketchy site. Don’t download “atieclxx.exe fixer” tools. Don’t reinstall Windows. This is a 1-service bug, not a Windows problem.

7. When Will AMD Actually Fix It?

Date	What Happened
July 2026	First reports on AMD forum — RX 7800 XT, 2 MB/s writes
Oct 21, 2026	AMD_Matt on AMD forum: “We’re investigating, aim to fix in future driver”
Oct 30, 2026	Adrenalin 26.10.2 releases — NO fix, not even mentioned in release notes
Nov 8, 2026	Reddit PSA by darklinkpower on r/pcmasterrace goes viral — 1% / month claim, 5 MB/s proof
Nov 9, 2026	AMD_Vik on Reddit: Fix submitted, low-risk, missed 26.10.2 cutoff, should be in 26.11.1
Late Nov 2026 (Expected)	Adrenalin 26.11.1 — EXPECTED FIX. No exact date yet. Check release notes for “External Events Utility” or “SSD writes”

Our advice: Don’t install 26.11.1 on day 1 blindly. Wait 24 hours, check Reddit / AMD forum for “26.11.1 fixed my atieclxx writes” confirmations, THEN install. AMD has missed this fix once already.

8. What If Your SSD Is Already Damaged?

Good news: SSDs don’t die suddenly from writes. They degrade slowly.

Health 100% to 90%: Totally normal. You’re fine. Just fix the bug.
Health 90% to 80%: Still fine for years. Backup your important files (you should anyway).
Health below 70%: Start planning a replacement in the next 6-12 months. Don’t panic, but don’t ignore it.
Health below 50%: Replace soon. Clone your drive to a new SSD.

And backup: This bug is the perfect reminder — if your photos / work / game saves are only on one SSD, you’re one bug away from losing them. Get a $30 external HDD or use Google Drive / OneDrive for the important stuff. Do it today, not after a failure.

Is my SSD going to die tomorrow?

No. Even at 5 MB/s, it takes years to hit TBW on a good 1TB drive. Check resmon, apply Fix #1 if needed, wait for 26.11.1. You’re not in an emergency.

Should I stop using my PC until the fix?

No. Just disable the service if you’re affected. Your PC is safe to use.

Does this affect my games / FPS?

The bug itself doesn’t lower FPS — it’s just writing to disk in background. But if your SSD is at 90-100% utilization from the bug, games may stutter on loading. Fix #1 will fix that.

I have AMD CPU + NVIDIA GPU. Am I affected?

No, from this GPU bug. But update your AMD chipset driver to 8.09.28.1124 or newer — that fixed the OLD 2025 version of this bug.

I disabled the service and FreeSync stopped working. What now?

Re-enable the service (Automatic), reboot, and use Fix #2 (disable ReBAR) OR just wait for 26.11.1 and leave your PC on less (don’t leave it on 24/7). You can also set Windows Power to sleep after 30 min idle — that stops the writes because the PC sleeps.

Bottom Line: Your GPU driver has a dumb loop that writes junk to your SSD while you sleep. It’s not killing your drive tomorrow, but it’s not okay either. Take 60 seconds to check resmon. If atieclxx.exe is writing non-stop, disable the service, wait for Adrenalin 26.11.1, and re-check. That’s it. No reinstall, no new SSD, no panic.