A new unofficial tool called Radeon-atieclxx-SSD-Fix has been released to address the continuous SSD writing issue affecting some AMD Radeon systems. Developed by GitHub user Necandi, the utility attempts to stop unnecessary background disk writes without disabling AMD External Events Utility, potentially avoiding the display and gaming functionality problems associated with earlier workarounds.
The open-source project, published on GitHub, provides tools to detect the issue, estimate unnecessary SSD writes and apply a targeted workaround. Unlike disabling the entire AMD service, its primary method changes file permissions to prevent repeated writes while allowing the service to continue running.
The release follows reports of an AMD Radeon driver bug causing continuous SSD writes, which AMD has acknowledged and is preparing to address through a driver update.
The problem involves atieclxx.exe, a process associated with AMD External Events Utility. On affected Windows systems, the process can repeatedly copy itself to a location within the system profile, generating disk activity even when the PC is otherwise idle.
According to Necandi’s technical documentation, Windows Event Tracing showed the process repeatedly copying an approximately 660 KB executable file, potentially generating around 56 GB of writes over 24 hours of continuous operation.
That figure represents the developer’s observed behavior rather than a universal write rate. Actual activity varies between affected configurations, and not every PC running AMD Radeon drivers experiences the problem.
Although SSDs are designed to withstand substantial amounts of writing, sustained unnecessary activity can consume part of their rated write endurance. The amount of additional wear depends on the affected drive, its endurance rating and how long the problem persists.
The new utility attempts to address the underlying file-copy behavior rather than stopping the service responsible for it.
Its targeted protection method uses Windows file access permissions to deny the SYSTEM account permission to overwrite or delete the specific copy of atieclxx.exe involved in the repeated writes. When the process attempts another copy operation, Windows rejects the modification.
Because AMD External Events Utility remains active, Necandi claims the workaround preserves FreeSync functionality, frame pacing and Radeon hotkeys.
However, those compatibility claims come from the developer. Independent testing has not established that the workaround preserves every affected feature across different Radeon graphics cards, driver versions and Windows configurations.
Previous user-discovered workarounds involved disabling AMD External Events Utility through Windows Services or turning off Resizable BAR in the motherboard BIOS. Both approaches have potential drawbacks, including possible display-feature disruptions or reduced gaming performance.
The new tool is intended to provide a narrower intervention without requiring either change.
Radeon-atieclxx-SSD-Fix also includes diagnostic functionality to help determine whether a system is affected before applying the workaround.
The utility can measure write activity associated with atieclxx.exe and distinguish between repeated copies to the known destination, writes to another location and systems where the behavior is not detected.
It also estimates how much unnecessary data may have been written and compares that amount with an SSD’s typical rated write endurance.
These calculations are approximate rather than measurements of actual physical SSD wear. The tool estimates accumulated writes using the observed write rate and estimated operating time since the AMD graphics hardware was installed. Where SSD operating-hour information is unavailable, it assumes eight hours of operation per day.
Consequently, its estimates cannot establish when the bug first appeared, how much additional physical wear occurred or how much useful life a particular SSD has lost.
Another feature is an optional maintenance mechanism designed to keep the targeted protection in place after driver updates.
According to the GitHub documentation, applying the targeted workaround creates a Windows scheduled task that runs under SYSTEM three minutes after startup and every 30 minutes thereafter.
The task can restore the file-permission restriction if an AMD driver update replaces the affected file. The developer also says it checks whether a newly installed driver has resolved the problem and removes the restriction when the behavior is no longer detected.
The utility includes options to disable AMD External Events Utility entirely or reverse the modifications it makes.
Necandi states that the software does not download additional components, communicate over the internet or modify the AMD driver itself. Its source code is publicly available under the MIT license, and the current interface is in German.
Despite those features, the software remains an unofficial third-party workaround and is neither developed nor endorsed by AMD.
Applying the targeted fix requires administrator privileges and modifies permissions on a file within the Windows system profile. Its scheduled task also operates with SYSTEM privileges. These changes introduce potential compatibility and security considerations, particularly when future driver updates alter the affected process or its file-handling behavior.
Users should review the source code and understand the modifications before executing the software with elevated privileges. Disabling Windows security warnings simply to launch an unfamiliar utility is not advisable.
For Radeon owners concerned about the issue, checking Windows Resource Monitor for sustained writes associated with atieclxx.exe is a reasonable first step that does not require installing third-party software.
AMD has acknowledged the underlying driver problem, with a corrective update expected in the Adrenalin 26.11.1 release. The company has not announced a specific release date.
Until an official fix becomes available, Radeon-atieclxx-SSD-Fix offers an alternative mitigation approach for affected systems, but its effectiveness and compatibility remain dependent on individual configurations. Users who do not observe abnormal disk activity have little reason to modify their driver environment.
