AMD Radeon Driver Bug Is Quietly Writing to Your SSD Around the Clock, and a Fix Is on the Way
Your graphics card driver is supposed to sit quietly in the background until you launch a game. For some AMD Radeon owners, it is doing the exact opposite. A driver component called atieclxx.exe has been caught writing to the system SSD non-stop, even when the PC is completely idle, and AMD has now confirmed the problem is real.
The bug is not a one-off glitch. According to Wccftech, reports of the constant writes have surfaced across multiple Adrenalin driver releases, on both Windows 10 and Windows 11, and across different Radeon GPUs. The good news is that AMD says a fix is already in progress. The bad news is that it may not arrive with the next driver release.
What the Bug Does
The culprit is the AMD External Events Utility, a background component of AMD’s graphics driver software. Its client process, atieclxx.exe (the AMD External Events Client Module), is supposed to handle tasks like detecting display changes and managing hotkeys. On affected systems, it instead generates a steady stream of writes to the system drive around the clock.
The issue gained fresh attention after a Reddit PSA by user darklinkpower on r/pcmasterrace, which collected reports from Radeon owners seeing the same behavior. One user measured roughly 5 MB/s of sustained write activity from the process. Other reports put the figure between 0.3 and 1.5 MB/s. The numbers vary from system to system, but the pattern is the same: writes that never stop, even when nothing is running.
That matters because SSDs wear out with every write. A drive that is being written to all day, every day, for no reason is burning through its endurance for nothing. How much that actually shortens a drive’s life is still an open question, and Wccftech is careful to note that there is currently insufficient evidence to say how much the bug reduces SSD endurance, if at all. Still, no one wants a background process hammering their storage for no benefit.
AMD Has Confirmed the Problem
This is not a rumor or an unconfirmed complaint thread. An AMD representative known as AMD_Matt acknowledged the issue on the AMD community forums in October, describing it as a genuine problem the company was investigating. Another AMD representative, AMD_Vik, later indicated on Reddit that a fix had likely already been committed, although it might have missed the cutoff for the next driver release.
AMD’s latest driver, Adrenalin Edition 26.10.2, released on October 30, does not mention the issue in its official release notes. That driver did address several crashes and driver timeouts affecting Radeon RX 7000 and RX 9000 GPUs, but the SSD write bug is not listed among its fixes. If the fix missed the cutoff as AMD_Vik suggested, Radeon owners may need to wait one more driver cycle.
It is also worth noting that not every Radeon system is affected. Some users report no unusual disk activity at all, even on Adrenalin 26.10.2. The bug appears to hit only some configurations, which may explain why it took a while to get AMD’s attention.
How Much Writing Are We Talking About
Wccftech calculated that a sustained 5 MB/s of writes adds up fast. At that rate, the affected process could theoretically generate around 432 GB of host writes per day, or nearly 13 TB per month. Those figures assume the activity never stops, and they describe host writes, which do not necessarily equal the amount physically written to the NAND flash inside the drive. Even so, the scale of the numbers explains why Radeon owners are taking the issue seriously.
| Reported write rate | Host writes per day* | Host writes per month* |
|---|---|---|
~5 MB/s | ~432 GB | ~13 TB |
~1.5 MB/s | ~130 GB | ~3.9 TB |
~0.3 MB/s | ~26 GB | ~0.8 TB |
*Theoretical totals assuming uninterrupted activity at the reported rate, using the same calculation Wccftech published for the 5 MB/s case. Actual NAND wear depends on the drive and cannot be inferred from host writes alone.
How to Check If Your PC Is Affected
Checking takes less than a minute, and it uses a tool already built into Windows. Here is how to do it:
- Press Win + R, type
resmon, and press Enter to open Resource Monitor. - Go to the Disk tab and sort the processes by write activity.
- Look for
atieclxx.exe, listed as the AMD External Events Client Module. - Watch it for a minute or two. If it shows sustained write activity while your system is idle, your PC is likely affected.
If you see no unusual activity from the process, your system is probably fine. There is no need to change anything. The bug does not hit every Radeon setup, so a clean check means you can simply wait for the driver fix like everyone else.
Workarounds, and Why You Should Think Twice
Some users have found ways to stop the writes, but both known workarounds come with trade-offs:
- Stop the AMD External Events Utility. You can stop the service through
services.msc, and users report this eliminates the excessive writes. The catch is that disabling it can interfere with Radeon features, including FreeSync behavior and Adrenalin hotkeys. - Disable Resizable BAR. Some users have identified this as another possible workaround. The catch is that turning off Resizable BAR can negatively affect gaming performance, which defeats the purpose of owning a gaming GPU.
Neither workaround is a real fix. Both trade one problem for another, and Wccftech advises users not to modify these settings unless they have confirmed the problem on their own systems. With AMD already investigating and a fix reportedly submitted, waiting for a proper driver update is the safer play for most people. If you do decide to try a workaround, remember how to undo it, and consider doing a clean install of your GPU drivers with DDU when the fixed driver arrives, so no leftover settings carry over.
How to Read Your SSD’s Health While You Wait
If your system is affected, the next question is how much damage the writes are actually doing. The honest answer is that nobody knows yet, but you can check your own drive instead of guessing.
Every SSD tracks its total host writes, and most drive makers ship a free utility that shows the number plainly: Samsung Magician, WD Dashboard, and Crucial Storage Executive are the common ones. Open yours and look for total host writes or TBW, then compare it against the drive’s rated endurance, which is printed in the spec sheet. A drive rated for hundreds of terabytes will absorb weeks of extra writes without complaint. A smaller or older drive with less headroom is the one to watch.
A free tool like CrystalDiskInfo shows the same health data, including the drive’s remaining life percentage, for any brand. Check it once now so you have a baseline, then check again when the fixed driver lands. If the number barely moved, the bug cost you nothing. If it jumped, you will know exactly how much, and you can decide whether the drive needs replacing sooner than planned.
What to Do Now
The practical steps are simple. First, check Resource Monitor to see whether your system is affected. If it is, decide whether the write rate is worth the trade-offs of a workaround, or whether you would rather wait for AMD’s fix. If it is not, do nothing and keep an eye on the next Adrenalin release notes.
It is also a good moment to remember that SSDs are not free. With SSD prices still high amid the ongoing memory shortage, wearing out a drive early is an expensive problem. That is exactly why a background bug like this one deserves attention, even if the real-world endurance impact is still unclear.
AMD has owned the problem and a fix is reportedly on the way. Until it lands, the best move is to check your own system, and if you are affected, weigh the workarounds carefully instead of rushing to disable features you actually use. For Radeon owners who have battled driver crashes and timeouts in the past, this is one more reason to keep driver updates on your radar.
News Source: Wccftech
