AMD has acknowledged a longstanding Radeon graphics driver bug that can cause continuous background writes to Windows system SSDs, even when a PC is idle. Affected users have reported write speeds reaching approximately 5 MB/s, potentially generating hundreds of gigabytes of unnecessary storage activity every day. AMD is working on a driver fix, although the issue remains unresolved in affected configurations.
The problem has received renewed attention following user reports shared on Reddit and coverage published by ComputerBase on November 9, 2026. It involves AMD External Events Utility, a background service associated with Radeon graphics drivers that handles display-related functionality. The issue is not a newly introduced regression, with similar behavior documented in earlier driver releases.
The processes associated with the reported activity include atieclxx.exe, identified as AMD External Events Client Module, and atiesrxx.exe. On affected systems, users have observed persistent disk activity associated with these components without corresponding workloads that would explain the writes.
Reported write rates vary considerably between systems. Some users have measured approximately 0.3 MB/s to 1.5 MB/s, while others have reported sustained activity approaching 5 MB/s.
At those rates, the potential cumulative writes are substantial. A continuous 1 MB/s represents approximately 86.4 GB over 24 hours, while 5 MB/s translates to roughly 432 GB daily or nearly 13 TB over 30 days. These figures assume uninterrupted activity and represent calculated write volumes rather than verified measurements of physical NAND flash wear.
The distinction matters because Windows-reported disk writes do not necessarily translate directly into equivalent physical writes to SSD flash memory. Although unnecessary sustained writes could contribute to storage wear, the precise effect on SSD lifespan has not been established through controlled endurance testing. One Reddit user reported losing approximately one percentage point of SSD health each month for 16 months, but that observation does not independently establish the driver’s contribution.
AMD representatives have addressed the issue in public Reddit discussions. An AMD representative using the name AMD_Matt acknowledged the problem in October, while AMD_Vik subsequently indicated that a potential fix had been submitted for validation. AMD_Vik also suggested that the correction could arrive in the next driver release, although a confirmed deployment date has not been announced.
The behavior appears to involve an interaction between AMD External Events Utility and a PCIe-related driver component. However, the specific conditions that trigger the continuous writes remain unclear.
Reports span multiple Radeon GPU generations, Windows versions and Adrenalin releases. Importantly, not every Radeon system is affected. Some owners running Adrenalin 26.10.2 have reported no unusual activity from either process, making it difficult to identify a single problematic driver version or hardware configuration.
Users can check their own systems through Windows Resource Monitor without modifying any driver settings. Press Windows + R, enter resmon, and open the Disk tab. The Disk Activity and Processes with Disk Activity sections can then be used to examine sustained write activity associated with atieclxx.exe.
Persistent writes should be observed over time rather than judged from a brief spike. Normal background activity is not sufficient evidence of this particular defect.
Until an official correction becomes available, affected users have identified two potential workarounds. The first involves stopping AMD External Events Utility through the Windows Services console. This can be accessed by pressing Windows + R, entering services.msc, and locating the service.
Disabling the service has stopped the excessive disk writes for some users, but it can also interfere with Radeon display functionality. Reported side effects include problems with Adrenalin hotkeys and frame pacing. One RX 6700 XT owner described less consistent frame rates when using Lossless Scaling frame generation after disabling the service, while other configurations may experience FreeSync-related issues.
Those tradeoffs are particularly relevant to Radeon gaming systems, where display synchronization and consistent frame delivery can affect perceived smoothness. AMD’s recent FSR 4 frame-pacing improvements also illustrate the importance of driver behavior to gaming performance, although they are separate from the SSD write defect.
The second reported workaround involves disabling Resizable BAR through the motherboard BIOS. Some users have found that this stops the background writes, while others report that it makes no difference.
Resizable BAR allows the processor to access larger portions of GPU memory and can improve performance in supported games. Disabling it may therefore reduce gaming performance depending on the hardware and workload. Neither workaround is guaranteed to resolve the issue across all affected configurations.
Users should also avoid manually replacing AMD system driver files with components from older releases, a workaround suggested in some community discussions. Such modifications carry additional stability risks and are not an established official solution.
AMD Software: Adrenalin Edition 26.10.2, released on October 30, does not list a correction for the persistent SSD write problem. With a potential fix undergoing validation, affected Radeon owners can monitor the relevant processes and check subsequent driver release notes for confirmation that the issue has been resolved.
