Your gaming PC can look completely idle while something in the background keeps writing data to its SSD. An AMD Radeon driver bug may be responsible on some Windows 10 and Windows 11 systems, although not every Radeon user is affected. Before disabling services or worrying about drive health, there is a simple way to check whether your own computer has the problem.
AMD has acknowledged the reports and is investigating. However, the important distinction is between an unusual background process and proven hardware damage. So far, there is no evidence that these writes are actually shortening SSD lifespan.
How to check the AMD Radeon driver bug in one minute
You do not need to install monitoring software or change any graphics settings. Windows already includes a tool that can show which processes are writing data to your storage drive.
Press Win + R, type resmon and press Enter. In Resource Monitor, open the Disk tab and find the processes showing write activity. Sort them by their write rate, then look for atieclxx.exe. Leave the PC idle for a short period and watch whether the process continues writing rather than briefly appearing during normal activity.
This executable belongs to the AMD External Events Client Module, associated with the AMD External Events Utility included in Adrenalin software. Its presence alone is not a problem. What matters is whether it produces sustained disk writes while the computer has no obvious workload. If it does not, there is no reason to assume your installation is affected.
AMD Radeon driver bug: how much SSD data is being written?
The numbers explain why the issue attracted attention, but they also need context. In AMD’s official community discussion, a Windows 11 user with a Radeon RX 9070 XT reported approximately 0.3 MB/s of continuous writes while using Adrenalin 26.10.1. Other reports describe rates between 0.3 and 1.5 MB/s, with one case reaching 5 MB/s.
At a constant 5 MB/s, a process would write approximately 432 GB in 24 hours. That calculation assumes the highest reported rate continues without interruption throughout the entire day. It is not a measured daily total for affected PCs, nor evidence that their drives are failing.
Modern SSDs are designed to handle substantial write workloads, and their endurance varies by model and capacity. Consequently, a write-rate reading cannot establish how much useful life a particular drive has lost. The reasonable concern is unnecessary background activity, not a confirmed wave of damaged SSDs.
Why disabling AMD External Events Utility is not the first move
Some affected users have tried stopping AMD External Events Utility through Windows Services, which can be opened by pressing Win + R and entering services.msc. However, this is a workaround with possible side effects, not an official permanent repair.
The service is connected to Radeon software functionality. Disabling it can interfere with features such as FreeSync and Adrenalin hotkeys. That trade-off matters if you depend on variable refresh rate gaming or frequently use AMD’s shortcuts.
Therefore, the safer approach is to confirm persistent writes before considering any changes. If your system behaves normally, leave the service alone. Even when the issue is visible, waiting for AMD’s fix may be preferable to sacrificing useful graphics features. This is a different kind of PC storage problem from the recent NieR:Automata Steam installation bug, where an official temporary workaround addresses excessive storage requirements.
AMD Radeon driver bug fix: what has AMD confirmed?
On October 21, AMD representative AMD_Matt responded in the company’s official Adrenalin 26.10.1 community discussion. The representative acknowledged that the reports appeared to describe a genuine issue and indicated that AMD was investigating with the intention of addressing it in a future driver release.
However, AMD has not announced when that correction will arrive. Its Adrenalin 26.10.2 release notes, dated October 30, do not identify this continuous SSD-writing problem as fixed. Moreover, some users running 26.10.2 report no unusual activity, so the driver version alone cannot establish whether a PC is affected.
For Radeon owners, this also raises a broader question about software reliability alongside hardware performance. As Battle4Play recently explored in its coverage of AMD’s changing PC gaming outlook, the company’s future involves more than graphics cards alone. For people already using Radeon hardware, dependable driver behavior remains an essential part of the experience.
For now, the AMD Radeon driver bug deserves attention rather than panic. Check atieclxx.exe in Resource Monitor, avoid unnecessary service changes and watch AMD’s future driver notes for an explicit fix. A confirmed background write issue is worth correcting, but it should not be confused with confirmed SSD damage.
Creator of the website, Pokemon trainer by nature. Trying to report on everything related to the world of video games, series and movies. Yu-Gi-Oh is my weakness, collecting cards since the dawn of time.
