Open Hardware & RISC-V

Open-source tool Radeon-atieclxx-SSD-Fix blocks AMD driver SSD write bug without breaking features

Key Takeaway

A community-developed open-source Windows tool blocks excessive SSD writes from AMD's Radeon driver by restricting file permissions rather than disabling the External Events Utility, preserving FreeSync and frame pacing functionality.

Summary

A German developer known as Necandi has released Radeon-atieclxx-SSD-Fix, an open-source utility that addresses a confirmed AMD Radeon driver bug causing excessive SSD writes without requiring users to disable the External Events Utility. The tool works by using Windows file permissions to deny the SYSTEM account write access to a specific file that atieclxx.exe repeatedly copies, which has been measured at rates between 0.3 MB/s and 5 MB/s—potentially writing over 400 GB per day in the worst cases.

The workaround preserves Radeon features like FreeSync, frame pacing, and hotkeys that would be lost if the service were disabled entirely. The tool includes detection for affected systems, estimates of prior write damage, a scheduled task to reapply protection after driver updates, and an automatic removal mechanism for when AMD eventually patches the issue in a future Adrenalin release. The interface is currently German-only, and the tool is unofficial and user-supported.

How the permission-based workaround functions

  • File permission blocking: The tool denies SYSTEM account write access to the destination file path in the Windows SYSTEM profile, causing each copy attempt by atieclxx.exe to fail silently without writing new data to the SSD.
  • Service preservation: Unlike disabling the External Events Utility entirely, this approach leaves atieclxx.exe running so dependent features including FreeSync, frame pacing, and Radeon hotkeys remain operational.
  • Write volume measurement: User reports document the bug producing between 0.3 MB/s and 5 MB/s of sustained writes, with the 660 KB executable being copied roughly every second—translating to 56 GB daily at typical rates and up to 432 GB at peak.
  • Persistence mechanism: The utility installs a scheduled task that automatically reapplies the permission block after AMD driver updates, which would otherwise reset the file ACLs and restore the buggy behavior.
  • Planned obsolescence: The tool includes functionality to detect when AMD has fixed the underlying driver issue and can self-remove the protection once the official Adrenalin 26.11.1 or later patch arrives.

Why it matters

While this targets Windows rather than Linux directly, the open-source release on GitHub demonstrates how community tooling can mitigate vendor driver defects while preserving functionality, a pattern relevant to cross-platform graphics driver quality discussions. For dual-boot users and the broader PC hardware ecosystem that FOSSWire covers, this preserves SSD health on systems running AMD Radeon hardware until AMD ships their official fix, reducing hardware replacement costs and e-waste from prematurely worn NAND flash.

Original reference: www.techpowerup.com →