Radeon Users Get a Stopgap Open-Source Fix for AMD's SSD Write Bug
AMD's Radeon SSD write bug now has a community workaround that doesn't require disabling the External Events Utility.
Why am I seeing this Ranked on source trust — TechPowerUp
It ranks mainly on source trust: TechPowerUp is the most reliable outlet we track on this subject, and is the only one on the story so far.
Single-sourced. No second organisation has confirmed it yet.
Link-outLink-out, because only one organisation carries it and no first-party source is on it. Link-out means we point at the publisher and say nothing of our own.
| Factor | Weight | Score | Contribution | Where it came from |
|---|---|---|---|---|
| Corroboration | 0.35 | 0.39 | +0.135 29% | 1 independent org on the story. Tier-3 aggregators never corroborate — they can show something is circulating, never that it is true. |
| Source trustleads | 0.25 | 0.80 | +0.200 42% | TechPowerUp is the highest-trust source on this story. Trust is taken from the best source, not averaged. |
| Pickup rate | 0.20 | 0.00 | +0.000 0% | One counted organisation, so there is no spread to measure — nothing has picked this up to set a rate. |
| Freshness | 0.20 | 0.69 | +0.138 29% | Halves every 10 hours from the newest item on the story. This is the only factor that rewards a story for nothing more than being recent. |
Corroboration counts distinct organisations, once each, and only from tiers 1 and 2. Freshness halves every 10 hours, so this ranking is a snapshot and will differ at the next build.
AMD's Radeon driver contains a bug where the atieclxx.exe service repeatedly copies itself to the Windows system folder, generating between 56 GB and 432 GB of storage writes daily depending on system configuration. A community developer has released Radeon-atieclxx-SSD-Fix, an open-source tool that blocks these writes by restricting file permissions while keeping the service active.
The tool prevents the executable from being copied by denying the system account write access to the target file. Unlike previous workarounds that required disabling the External Events Utility entirely, this approach preserves functionality for FreeSync, frame pacing, and Radeon hotkeys. The tool also estimates accumulated writes, reapplies protection after driver updates, and can automatically remove itself once AMD releases a fix.
The fix is currently available only with a German-language interface and remains unofficial, so users should employ it at their own risk. The tool first checks whether a system is affected before applying any changes, allowing users to verify the bug's presence on their hardware before proceeding.
What happened
AMD's Radeon SSD write bug now has a community workaround that doesn't require disabling the External Events Utility. ComputerBase forum member Necandi (necanditool on GitHub) has released Radeon-atieclxx-SSD-Fix, a free, open-source tool that blocks the writes but leaves the service running. The developer found that atieclxx.exe keeps copying its own 660 KB executable out of the driver folder and into the Windows SYSTEM profile every second, or roughly 56 GB of writes per day. User reports put the write rate between 0.3 MB/s and 5 MB/s, and the top end works out to a massive 432 GB a day.
How this story arrived
Ordered by when each source was first observed, which is what the velocity figure is computed from. Publishers backdate; observed order does not.
- 01 Techpowerup first seen Radeon Users Get a Stopgap Open-Source Fix for AMD's SSD Write Bug
Overclock clusters coverage from independent sources and grades it automatically. The figures above are computed, not editorial. This page summarises and links to reporting by the outlets named — follow the links for the original work.