Some Radeon owners have reported declining SSD health indicators and elevated write activity for over a year. The process behind it is atieclxx.exe, part of AMD’s External Events Utility installed alongside Adrenalin drivers. If you’re also dealing with other computer problems, that resource may help you work through them systematically.
What the Utility Is Actually Doing
Reported write rates on affected systems range from a trickle to a sustained flood, and the numbers add up fast.
Reported write rates from affected systems range from roughly 0.3 to 1.5 MB/s at idle, with one user describing a sustained rate of approximately 5 MB/s while the machine was doing nothing. At that upper rate, that amounts to over 400 GB of host writes per day.
A Reddit user identified as darklinkpower reported their SSD health indicator declined 1% per month across 16 months. Another user described 125 GB written during a single session. These are self-reported observations, not independently verified measurements of physical NAND degradation.
That distinction matters. The health percentage your SSD monitoring software shows is a vendor-calculated estimate built on proprietary endurance models. It is not a direct readout of remaining physical lifespan. Sustained host writes are worth taking seriously; they are not necessarily a guarantee of imminent drive failure.
AMD Acknowledged It. The Fix Has Not Shipped.
AMD identified the problem and pointed to a PCIe-related interaction as the likely cause, but affected users are still waiting for a corrected driver.
As reported, AMD said it was investigating on October 21 and attributed the behavior to an apparent loop or interaction between AMD External Events Utility and a PCIe-related component. That is the extent of what the company has confirmed publicly, based on available reporting.
Adrenalin 26.10.2 did not include a correction. Several sources anticipated a fix in 26.11.1, but no confirmed release date or verified universal resolution is established in the available material.
Check Your System Before You Do Anything Else
Persistent, sustained write activity from a specific AMD process is the signal to look for; a brief spike is not proof of anything.
Open Windows Resource Monitor by typing resmon into the Start menu. Navigate to the Disk tab and watch for persistent write activity from atieclxx.exe while your PC is otherwise idle. A short burst is not proof of the bug. The writes need to be sustained and clearly distinguishable from normal background workloads like antivirus scans, search indexing, or browser caching.
Log what you find before changing anything. Record the process name, write rate, duration, SSD model, Adrenalin driver version, and whether the activity persists after a reboot.
Workarounds Exist, With Real Trade-Offs
Both reported workarounds stop the symptom but carry costs that make them poor substitutes for a proper driver fix.
Some users report that stopping or disabling AMD External Events Utility halts the writes, but doing so can affect Radeon hotkeys, display detection, and FreeSync-related features. Disabling Resizable BAR has worked in some configurations but can reduce gaming performance and is not a universal solution.
No AMD-approved workaround has been identified in the available material. Unofficial file-replacement procedures circulating in forums carry their own risks and should not be treated as broadly safe , much like understanding how to stay safe from other hardware-level threats matters when managing system integrity.
AMD Owes Its Users a Faster Answer
A background utility that writes continuously to the drive holding your operating system is not behaving as intended, and the company responsible has yet to ship a correction.
A utility designed to run quietly in the background should not generate continuous, unexplained writing data to system drives continuously. In some configurations, AMD’s External Events Utility does exactly that. The company has acknowledged the problem and indicated a fix is coming, but has not shipped one as of the most recently available reporting.
Until it does, document the activity on your system, apply workarounds only after confirming the bug is present, and avoid unofficial forum patches. A proper fix needs to come from AMD.
