Some AMD Radeon PCs may be quietly writing data to their SSDs around the clock, even when Windows is sitting idle. The suspected culprit is a bug in AMD’s Radeon driver software involving the External Events Utility, a background component installed with Adrenalin.
Users have traced the activity to atieclxx.exe, the AMD External Events Client Module. Reports describe anything from roughly 0.3 MB/s to 1.5 MB/s in sustained writes, with one particularly severe case reaching about 5 MB/s while the computer was doing nothing. At that rate, the system drive could receive approximately 18GB of host writes per hour, although host-write totals do not translate directly into the same amount of physical NAND wear. Independent testing and user reports have likewise identified the External Events Utility as the process behind the activity.
The concern became more serious after one Radeon owner claimed their SSD’s reported health had fallen by about one percentage point every month for 16 months. That figure has not been independently confirmed, and SSD health readings vary by manufacturer, controller, NAND type, and monitoring software. Nevertheless, uninterrupted writes can inflate a drive’s total host-written data and potentially accelerate wear, particularly on systems left powered on for long periods.
AMD has acknowledged the problem. In an October 21 response on its community forum, an AMD representative said the company was investigating with the goal of addressing it in a future driver release. A later update from AMD representative AMD_Vik reportedly linked the behavior to an interaction between the External Events Utility and Microsoft’s PCIe filter driver, with a fix submitted for validation. Current coverage points to Adrenalin 26.11.1 as the expected release containing the repair. AMD’s planned driver update has not yet made the issue harmless for users running affected configurations.
The bug does not appear to affect every Radeon system or map neatly to one driver version. Reports span multiple Adrenalin releases, while the October 30 Adrenalin 26.10.2 notes did not call out the problem. That makes the combination of GPU, Windows installation, PCIe configuration, and driver history potentially as important as the driver package itself.
Until the fix arrives, users can check for the problem by opening Windows Resource Monitor with resmon, selecting the Disk tab, and watching for persistent writes from atieclxx.exe while the PC is idle. Stopping or disabling AMD External Events Utility through services.msc has reportedly reduced the activity, but may affect Radeon features such as hotkeys, display detection, or FreeSync. Disabling Resizable BAR is another reported workaround, though it can reduce performance in some games. The safest long-term move is to monitor the drive, keep backups current, and install the next Adrenalin release once AMD publishes a confirmed fix.
