Your idle Radeon PC may be busier than you think.
A subtle yet persistent bug within AMD Radeon drivers is causing undue strain on Solid State Drives (SSDs), even when a PC is seemingly inactive. This issue, stemming from an infinite loop within a specific driver utility, is leading to constant, low-level write operations to SSDs, potentially impacting their long-term health and endurance. While the write volumes may appear negligible on a per-second basis, their cumulative effect over days, weeks, and months could significantly shorten the lifespan of these critical storage components. AMD has acknowledged the problem and indicated that a fix is in development, but affected users are currently left with limited and potentially performance-impacting workarounds.
The Unseen Activity: A Driver’s Unceasing Task
At the heart of this issue lies the AMD External Events Utility (atieclxx.exe), a component responsible for managing hotkey functions and AMD’s FreeSync technology. Reports from users on various online forums, including Reddit, have detailed how this utility engages in continuous data writing to SSDs. The observed write speeds vary, ranging from a low of approximately 0.3 megabytes per second (MB/s) on many systems to as high as 5 MB/s in more severe cases. These operations primarily involve the logging of internal driver diagnostics, status checks, and system event data.
While individual write operations might seem insignificant, their persistent nature presents a concerning cumulative effect. A write rate of 0.3 MB/s, for instance, translates to roughly 26 gigabytes (GB) of data written to the SSD each day. Escalating to 5 MB/s, the daily write volume jumps to an astonishing 432 GB, accumulating to nearly 13 terabytes (TB) of data per month. This level of sustained activity is highly unusual for a PC that is not actively engaged in demanding tasks like large file transfers, intensive gaming, or video editing.
Quantifying the Impact: SSD Endurance Under Threat
The implications of this constant writing on SSD lifespan are significant. Modern SSDs are rated for a specific amount of data they can withstand being written to them over their operational life, measured in Terabytes Written (TBW). For example, a typical 500GB SSD might have a TBW rating of around 300 TB.

If a user’s PC is subjected to the lower end of the bug’s write activity (0.3 MB/s), it equates to approximately 9.5 TB of data written annually (26 GB/day * 365 days). This represents about 3.16% of the total rated write endurance of a 300 TBW SSD in a single year.
However, in more extreme cases where the write speed reaches 5 MB/s, the annual data written skyrockets to approximately 173 TB (432 GB/day * 365 days). This scenario would consume an alarming 57.6% of a 300 TBW SSD’s rated lifespan in just one year. At these rates, even a robust SSD could see its operational life dramatically reduced, potentially failing years ahead of its expected service life. It is important to note that these figures represent the data the operating system reports as being written. The actual number of write cycles to the flash memory chips can be influenced by the SSD controller’s wear-leveling algorithms and other internal processes, meaning the direct impact on physical flash endurance is not always a one-to-one correlation, but the increased activity is undeniable and a cause for concern.
Chronology of the Discovery and Acknowledgment
The issue began to surface in user discussions around late October 2024. Initially, PC enthusiasts and tech-savvy users noticed unusual storage activity on their systems equipped with AMD Radeon graphics cards. Through diligent monitoring and troubleshooting, they identified the atieclxx.exe process as the source of the persistent write operations.
- Late October 2024: Users begin reporting high SSD write activity attributed to AMD Radeon drivers.
- October 26, 2024: A representative from AMD, identified as AMD_Matt, publicly acknowledges the existence of the bug on Reddit, confirming that the company is aware of the issue.
- October 30, 2024: AMD releases Adrenalin driver version 23.10.2. While this update addresses various performance and stability improvements, it does not explicitly mention a fix for the SSD write bug.
- Early November 2024: Another AMD representative, AMD_Vik, communicates that a "low-risk fix" has been submitted by a colleague and expresses optimism for its inclusion in an upcoming driver release. However, no specific release date is provided.
This timeline highlights that while AMD has acknowledged the problem and is working on a solution, an official fix has not yet been deployed to the public. Users are therefore left in a state of uncertainty regarding the immediate availability of a permanent resolution.

Official Response and User Workarounds
AMD has been relatively transparent about the ongoing situation, with representatives engaging with the user community to provide updates. Following the initial acknowledgment, the company has indicated that a software patch is in the works.
"We are aware of reports regarding the AMD External Events Utility (atieclxx.exe) causing higher than expected write activity to SSDs on some systems," an AMD spokesperson might have stated in a hypothetical official release. "Our engineering team has identified the root cause and is actively working on a fix. We anticipate this resolution will be included in an upcoming driver release. In the meantime, we recommend users consult community forums for potential temporary workarounds, while advising caution regarding any modifications that could impact system stability or functionality."
In the interim, users experiencing this issue have a couple of potential workarounds, though each comes with its own set of compromises:
-
Disabling the Service: Users can manually disable the AMD External Events Utility service through the Windows Services console (services.msc). While this effectively halts the problematic write operations, it also carries the risk of disabling FreeSync functionality and disrupting custom hotkey assignments within AMD Adrenalin software. This can lead to a degraded user experience for those who rely on these features.

-
Disabling Resizable BAR: Another reported workaround involves disabling the Resizable BAR (Base Address Register) feature in the system’s UEFI/BIOS settings. Resizable BAR is a performance-enhancing technology that allows the CPU to access the entire GPU memory at once, potentially improving frame rates in certain games. Disabling it to resolve the SSD write bug could lead to a noticeable reduction in gaming performance, making it an undesirable solution for many gamers.
The cautious approach, as suggested by some tech analysts, is to first verify if the issue is indeed affecting your system. This can be done by opening the Resource Monitor in Windows (accessible by pressing Win + R, typing resmon, and navigating to the Disk tab) and observing the processes that are actively writing to the disk. If atieclxx.exe is shown to be consistently writing data, then the user is likely impacted.
Broader Implications and Analysis
The discovery of this bug raises several pertinent questions about driver development and quality assurance in the PC hardware industry. While bugs are an inevitable part of complex software, an issue that silently degrades the lifespan of a critical hardware component like an SSD, especially when the system is idle, is particularly concerning.
- Impact on SSD Market: For consumers who invest in high-end SSDs for their speed and durability, such a bug could erode confidence in AMD hardware and potentially influence future purchasing decisions. The longevity of storage is a key selling point for SSDs, and any perceived threat to that longevity, however small, can have an impact.
- Consumer Trust: The transparency and speed with which AMD addresses this issue will be crucial in maintaining consumer trust. While acknowledging the problem is a positive step, the delay in delivering a definitive fix and the reliance on user-implemented workarounds that compromise functionality are not ideal.
- Driver Development Standards: This incident underscores the importance of rigorous testing and validation of driver software, particularly concerning background processes that can have long-term hardware implications. The "infinite loop" description suggests a flaw in error handling or state management within the driver.
As the technology landscape evolves, with increasingly complex hardware and software integrations, such issues serve as a reminder of the intricate balance required to deliver a seamless and reliable user experience. The eventual resolution of this AMD Radeon driver bug will be closely watched by consumers and industry professionals alike, serving as a case study in how hardware manufacturers manage and communicate software-related hardware impacts. Until a stable and official fix is rolled out, affected users must weigh the potential risks to their SSDs against the compromises offered by the current workarounds.