Skip to content
TroubleGrid

AMD Radeon driver writes to the SSD constantly at idle (atieclxx.exe)

Last verified November 2026Tested against Fixed in AMD Software: Adrenalin Edition 26.11.1 (Optional, 12 November 2026), AMD scopes the fix to Radeon RX 7000 series and above, RX 500 / Polaris and Vega - confirmed still affected on the 26.5.2 Polaris branch, RX 6000 - not named in the fix; an RX 6950 XT on 26.11.1 still wrote ~966 KB/s, RX 5000 - not named in the fix and not yet tested, Adrenalin 26.10.2 and earlier - affected; 26.3.1 and older shipped the amdkmpfd files, Radeon display driver 32.0.32015.12012 affected; 32.0.32015.16001 ships with 26.11.1, Windows 10 and Windows 11Good evidence

AMD shipped the fix on 12 November 2026 in Adrenalin 26.11.1, an Optional driver: its Fixed Issues list names “excessive writes to the system drive … while the system is idle”. Read the scope carefully, because it is the whole story here — AMD names Radeon RX 7000 series and above only. Polaris and Vega cards are confirmed still affected and AMD says that branch will take a while; one RX 6950 XT was still writing roughly 966 KB/s after updating. So: update first if you are on RX 7000 or newer, and confirm with Resource Monitor afterwards. If your card is older, or still writing after the update, the workarounds further down are still what you have.

In early November 2026 Radeon owners noticed their system drive being written to continuously on an idle PC. AMD has now fixed it for the newer cards, and the detail that matters is which ones. This page covers how to tell whether your PC is affected, what AMD's fix does and does not cover, and what each remaining workaround costs you if it does not.

Symptoms

  • Constant disk write activity on the Windows drive while the PC is idle
  • atieclxx.exe shows a steady write rate of a few hundred KB/s in Resource Monitor
  • The I/O write bytes figure for atieclxx.exe in Task Manager climbs every second
  • SSD host writes (Total Host Writes / Data Units Written) growing by tens of GB a day with no explanation
  • Drive activity LED flickering continuously on an otherwise idle machine

Why this happens

A driver installation that can never finish

atieclxx.exe is trying to install amdkmpfd, AMD's PCI filter driver. The driver package's INF still records where that driver's files belong, and ten install sections still reference the file list for it, but the list is empty: current Adrenalin packages no longer ship the files, while 26.3.1 and older did. Every attempt therefore fails, and the utility starts over about a second later with no retry limit. One pass of that loop copies the utility's own 677,392-byte executable into C:\Windows\System32\config\systemprofile\AppData\Local\AMD\, and that copy is the write you can see. Because the driver being installed is the filter driver associated with Smart Access Memory, turning Resizable BAR off removes the trigger on some systems. Adrenalin 26.11.1 fixes this from the other end: the utility itself is almost unchanged, but after installing it the amdkmpfd folder and service are gone, so there is no longer an install for the utility to retry. That is consistent with AMD describing the change as having been made in the kernel-mode driver.

Install Adrenalin 26.11.1 or later (Radeon RX 7000 and above) · Stop and disable the AMD External Events Utility service · Turn off Resizable BAR / Smart Access Memory in the BIOS · Deny the SYSTEM account permission to overwrite the copied file

Why the reported numbers disagree so wildly

The headline figures come from host-level and cached write counters, not from writes measured at the drive. The utility's own counter showed about 70 GB after 31 hours while its write-operation count barely moved, because the program writes into the Windows file cache and the System process flushes it to disk. Measured with Process Monitor, the non-cached writes actually reaching the drive came to 14.3 MB over 30 seconds, about 0.48 MB/s. The user reports of 0.3 to 5 MB/s are host figures, and the widely quoted 400+ GB per day is an extrapolation from the single highest of them. How much of any of this reaches the flash depends on the drive's own write amplification as well.

Confirm atieclxx.exe is the process writing to your drive

Why older Radeon cards are still affected after the fix

AMD's Fixed Issues entry names Radeon RX 7000 series and above, and nothing else. Polaris and Vega cards run a separate driver branch, and AMD has said the filter driver has different responsibilities there, so the change cannot simply be carried across and “may take us a while to work in” — an RX 560 and an RX 580 on the 26.5.2 Polaris driver both still loop. RX 6000 is the awkward middle case: it is not named in the release notes either, and an RX 6950 XT updated to 26.11.1 was still writing about 966 KB/s until the permission workaround was applied. RX 5000 has not been tested. If your card is in any of those groups, treat the update as worth doing but not as the fix, and re-measure afterwards.

Confirm atieclxx.exe is the process writing to your drive · Stop and disable the AMD External Events Utility service · Turn off Resizable BAR / Smart Access Memory in the BIOS · Deny the SYSTEM account permission to overwrite the copied file

Fixes

Confirm atieclxx.exe is the process writing to your drive

about 3 min

Not every Radeon PC is affected, even on the same card and driver, and plenty of other things write constantly in the background. This takes a minute and decides whether any of the rest of this page applies to you.

Applies to: Windows 10, Windows 11

  1. Leave the PC idle: close games, launchers and browsers, and do not start a download.
  2. Press Win+R, type resmon and press Enter to open Resource Monitor.
    resmon
  3. Open the Disk tab and expand "Processes with Disk Activity", then sort by Write (B/sec).
  4. Look for atieclxx.exe. On an idle PC it should be writing essentially nothing. A steady few hundred KB/s is the fault described here.
  5. As an alternative, open Task Manager, go to the Details view, right-click a column header, choose Select columns and tick "I/O write bytes". If that number for atieclxx.exe climbs every second, you are affected.
  6. Judge this by the write rate, not by the file. The utility clears the copy's attributes and overwrites it in place, so neither a read-only flag nor the file's appearance on disk tells you whether the loop is running.
  7. Re-run this same check after any driver change, including after installing 26.11.1. It is the only way to know the loop has actually stopped on your PC.

Reported to work by 3 users; not confirmed by the vendor.

Source: ComputerBase, candygoogy (independent analysis), necanditool (independent analysis), candygoogy (independent analysis)

Install Adrenalin 26.11.1 or later (Radeon RX 7000 and above)

about 25 min

This is the only change that removes the cause rather than blocking a symptom. AMD lists it under Fixed Issues in 26.11.1 — but only for RX 7000 series and above, so check your card against that scope before expecting it to work.

Applies to: AMD Software: Adrenalin Edition 26.11.1 and later, Radeon RX 7000 series and above for the documented fix

  1. Check which card you have. If it is RX 7000, RX 9000 or newer, AMD's fix covers you. If it is RX 6000, RX 5000, Vega or Polaris (RX 400/500), it is not named in the fix — you can still update, but measure afterwards rather than assuming.
  2. Download AMD Software: Adrenalin Edition 26.11.1 or later from AMD's driver page. Note that 26.11.1 is an Optional release, not a Recommended one.
    https://www.amd.com/en/support/download/drivers.html
  3. Read that release's Known Issues before installing. 26.11.1 ships with open issues of its own, including a driver timeout in War Thunder on RX 5000 for which AMD recommends staying on 26.9.1, and an intermittent crash in Assassin's Creed Black Flag Resynced on RX 7000.
  4. Install it and restart.
  5. If you applied the permission workaround or disabled the service, undo that now — otherwise you cannot tell whether the driver fixed anything.
  6. Repeat the check in the first fix. On a card the fix covers, atieclxx.exe should write essentially nothing at idle. If it is still writing, your card is not covered and the workarounds below are still what you need.

Confirmed by the vendor, though some users report it does not help.

Source: AMD, candygoogy (independent analysis), ComputerBase

Stop and disable the AMD External Events Utility service

Check before applyingabout 5 min

The workaround that circulated first, and still the one to reach for if AMD's fix does not cover your card. It stops the writes reliably, because this service is the thing doing the writing — but it also switches off the features the service provides.

Applies to: Windows 10, Windows 11

Before you do this

Disabling this service has been reported to affect FreeSync and other variable-refresh behaviour, frame pacing and Adrenalin hotkeys, and more generally to cause display quirks. If you rely on any of those, prefer the permission workaround below, or accept the trade until AMD ships a driver fix. Re-enable the service before reporting any display problem to AMD.

  1. Press Win+R, type services.msc and press Enter.
    services.msc
  2. Find "AMD External Events Utility" in the list, right-click it and choose Stop.
  3. Right-click it again, choose Properties, and set Startup type to Disabled, so that stopping it now is not undone the next time Windows starts.
  4. Click Apply, then restart the PC and repeat the check in the first fix.
  5. To undo this, set Startup type back to Automatic and start the service again.
  6. If you later install a driver that fixes this for your card, set Startup type back to Automatic, start the service, and re-check.

Reported to work by 3 users; not confirmed by the vendor.

Source: ComputerBase, necanditool (independent analysis), candygoogy (independent analysis), KitGuru

Turn off Resizable BAR / Smart Access Memory in the BIOS

Check before applyingabout 10 min

The loop is a failing attempt to install amdkmpfd, AMD's PCI filter driver, and that driver is the piece tied to Smart Access Memory. That is why switching Resizable BAR off stops it on some systems — and why it changes nothing on others. On an RX 7000 or newer card, update to 26.11.1 before giving up performance for this.

Applies to: Systems with Resizable BAR / Smart Access Memory available in the BIOS

Before you do this

Turning off Resizable BAR costs performance in some games, and Smart Access Memory depends on it. BIOS layouts differ between boards, so note the setting's original value before you change it. This has been reported to help only some affected systems, so check the write rate afterwards and put it back if nothing changed.

  1. Restart and enter BIOS/UEFI setup — usually by holding Del or F2 during startup; your board's splash screen names the key.
  2. Find "Re-Size BAR Support" or "Resizable BAR", often under a PCI Subsystem Settings or Advanced menu, and set it to Disabled.
  3. Save and exit, let Windows start, then repeat the check in the first fix.
  4. If atieclxx.exe is still writing, set Resizable BAR back to Enabled — it is not the trigger on your system, and you would be giving up performance for nothing.

Reported to work by 2 users; not confirmed by the vendor. 1 report it did not help.

Source: necanditool (independent analysis), ComputerBase, KitGuru, candygoogy (independent analysis)

Deny the SYSTEM account permission to overwrite the copied file

Advancedabout 5 min

The least disruptive of the workarounds: the service keeps running and keeps doing its job, and only the one write it repeats is blocked. Worth preferring over disabling the service if your card is not covered by AMD's fix. Undo it after any driver update that might have fixed the loop.

Applies to: Windows 10, Windows 11

Before you do this

This changes permissions on a file inside a protected system directory and is not supported by AMD. A driver update replaces the file, so the change is lost and must be reapplied — re-check after every driver update. Undo it before reporting a driver problem to AMD. Do not use the circulating one-line commands that download a remote script and execute it in the same breath; the whole change is the single command below, which you can read before you run it.

  1. Confirm first, with the check in the first fix, that atieclxx.exe really is writing. If it is not, this changes nothing and should be skipped.
  2. Open Terminal or Command Prompt as administrator (right-click Start, then "Terminal (Admin)").
  3. Run this. It denies only the SYSTEM account, and only write and delete, on that one file — nothing else on the system is touched. If it reports that the file cannot be found, the copy does not exist on your PC and this workaround does not apply.
    icacls "C:\Windows\System32\config\systemprofile\AppData\Local\AMD\atieclxx.exe" /deny *S-1-5-18:(W,D)
  4. Repeat the check in the first fix. The write rate should fall to zero within a few seconds while the service stays running.
  5. To undo it, run this and re-check.
    icacls "C:\Windows\System32\config\systemprofile\AppData\Local\AMD\atieclxx.exe" /remove:d *S-1-5-18
  6. Do not use the read-only attribute instead. The utility clears file attributes before it copies, so read-only is simply removed and the write still happens.

Reported to work by 2 users; not confirmed by the vendor.

Source: candygoogy (independent analysis), necanditool (independent analysis), candygoogy (independent analysis)

Known issues

  • Fixed for RX 7000 and above. AMD Software: Adrenalin Edition 26.11.1, an Optional release dated 12 November 2026, lists “Excessive writes to the system drive may be observed while the system is idle on Radeon RX 7000 series graphics products and above” under Fixed Issues, along with a second entry for excessive writes while moving or resizing application windows. On a test PC, installing it over 26.10.2 removed the amdkmpfd folder and service entirely and took atieclxx.exe to 0 B/s.

    Affects AMD Software: Adrenalin Edition 26.11.1, Radeon display driver 32.0.32015.16001, Radeon RX 7000 series and above · Status: fixed

  • Still open on older cards. AMD's fix entry names RX 7000 and above and nothing else. Polaris and Vega are confirmed still affected — an RX 560 and an RX 580 on the 26.5.2 Polaris driver both still loop — and AMD says that branch “may take us a while to work in”. RX 6000 is not named either, and one RX 6950 XT on 26.11.1 still wrote about 966 KB/s. RX 5000 is untested. On these cards the workarounds on this page are still the answer.

    Affects Radeon RX 400 and RX 500 (Polaris), Radeon Vega, Radeon RX 6000 series, Radeon RX 5000 series (untested) · Status: open

  • 26.11.1 is an Optional driver and carries its own open issues: a War Thunder driver timeout on RX 5000, for which AMD recommends staying on Adrenalin 26.9.1; an intermittent crash in Assassin's Creed Black Flag Resynced on RX 7000; a Cyberpunk 2077 crash on some RX 9000 cards using FSR, Anti-Lag and frame generation during video playback on a second display; and Smart Access Memory switching off after installation on Windows 10. Check that list against the games you play before updating.

    Affects AMD Software: Adrenalin Edition 26.11.1 · Status: open

If none of this worked

If atieclxx.exe is not the process writing, none of this applies to you. Constant background writes on an idle PC also come from Windows Search indexing, SysMain, antivirus scanning, browser caches, Steam's shader pre-caching, cloud-sync clients and game or launcher logging — Resource Monitor's Disk tab names the responsible process in every one of those cases. Note too that the AMD External Events Utility is installed by AMD chipset drivers as well as Radeon drivers, so a PC with an AMD processor and an NVIDIA or Intel graphics card can be running it. And if your drive reports falling health with no process writing to it, that is a different problem: check its SMART data with the manufacturer's own tool before assuming a driver is at fault.

Common questions

AMD says this is fixed. Does that include my card?
Only if it is RX 7000 series or newer — that is the exact scope AMD wrote into the 26.11.1 Fixed Issues entry, and nothing else is named. Polaris (RX 400/500) and Vega are confirmed still affected, and AMD has said that branch will take a while. RX 6000 is not named and one RX 6950 XT was still writing after updating. RX 5000 is untested. Whatever card you have, update and then measure: the check in the first fix takes a minute and is the only thing that settles it for your PC.
26.11.1 is an Optional driver. Should I install it anyway?
If you are affected and on RX 7000 or newer, yes — an Optional release is a normal AMD channel, not a beta. But read its Known Issues first, because it ships with several: a War Thunder driver timeout on RX 5000 where AMD tells you to stay on 26.9.1, an Assassin's Creed Black Flag Resynced crash on RX 7000, a Cyberpunk 2077 crash on some RX 9000 setups, and Smart Access Memory switching itself off on Windows 10. If one of those is a game you actually play, the permission workaround on this page may be the better trade until a Recommended driver carries the fix.
Is this actually damaging my SSD?
Probably not much on a typical drive, which is not the same as saying it is fine. At the measured rate of roughly 0.5 MB/s it works out to something like 15 to 20 TB of host writes a year. A 1 TB consumer TLC drive is commonly rated for around 600 TB of writes, so this alone would consume a few percent of that rating per year. On a small or budget drive rated far lower, the proportion is worse. The figures circulating of 400+ GB a day and roughly one percentage point of drive health per month come from individual user reports and from cached write counters, and have not been independently verified.
Why does turning off Resizable BAR help some people and not others?
Because the loop is an attempt to install amdkmpfd, AMD's PCI filter driver, and that driver is the component tied to Smart Access Memory. Disabling Resizable BAR removes the trigger on systems where that install path is what runs. It is not a general cure, and it costs performance in some games, so check the write rate afterwards and put the setting back if nothing changed.
Can I just set the copied file to read-only?
No. The traces show the utility clearing the file's attributes immediately before it copies, so a read-only flag is removed and the write goes ahead. Denying the SYSTEM account write and delete permission on the file does hold, because the copy then fails with an access-denied error instead.
Does this affect PCs without a Radeon graphics card?
It can. The AMD External Events Utility also ships with AMD chipset drivers, so a system with an AMD processor and an NVIDIA or Intel graphics card may have the service installed and can show the same behaviour. Check for the process the same way.
Is it safe to leave the service disabled permanently?
It works, but you give up what the service does. FreeSync and other variable-refresh behaviour, frame pacing and Adrenalin hotkeys have all been reported to be affected, and more generally display quirks. If you rely on those, the permission workaround leaves the service running. On an RX 7000 or newer card you no longer need either: update to Adrenalin 26.11.1, re-enable the service, and check the write rate. On older cards, leaving it disabled is still a real trade-off rather than a free win.

Did this fix work?

If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.

Report a problem with this page

Related problems

Sources

  • AMD · Release notes · checked Nov 13, 2026

    • Fixed Issues lists "Excessive writes to the system drive may be observed while the system is idle on Radeon RX 7000 series graphics products and above."
    • Fixed Issues also lists "Excessive writes to the system drive may be observed while moving or resizing application windows."
    • The release is an Optional driver, article number RN-RAD-WIN-26-11-1, last updated 12 November 2026
    • The fix entry names Radeon RX 7000 series graphics products and above, and no entry names RX 6000, RX 5000, Vega or Polaris cards
    • Known Issues include an intermittent crash or driver timeout in Assassin’s Creed Black Flag Resynced on RX 7000 series
    • Known Issues include an intermittent driver timeout in War Thunder on RX 5000 series, with AMD recommending Adrenalin 26.9.1 for affected users
    • Known Issues include AMD Smart Access Memory becoming disabled after driver installation on Windows 10 systems
    • AMD recommends using the AMD Cleanup Utility when downgrading to a previous version of Adrenalin Edition
    • The driver supports Radeon RX 9070/9060/9050, RX 7000, RX 6000 and RX 5000 series products
  • AMD · Release notes · checked Nov 12, 2026

    • AMD Software: Adrenalin Edition 26.10.2 (last updated 30 October 2026) is the current Adrenalin release and its Known Issues list does not mention excessive SSD writes, the AMD External Events Utility or atieclxx.exe
    • AMD's release notes document Smart Access Memory and other driver defects by name, so the absence of this one indicates AMD has not documented it in its release notes
  • KitGuru · News · checked Nov 13, 2026

    • AMD has not published a formal statement about the issue; an unnamed AMD employee replied in a Reddit thread indicating the problem was being looked at
    • Typical user-reported write rates range from 0.3 MB/s to 1.5 MB/s, with one report of sustained activity around 5 MB/s
    • The 400+ GB per 24 hours figure is an extrapolation from the 5 MB/s report rather than a measurement
    • The workarounds reported are disabling the AMD External Events Utility service, which can cause display quirks, and turning off Resizable BAR in the BIOS, which risks reducing gaming performance
  • ComputerBase · News · checked Nov 13, 2026

    • The AMD External Events Utility service, running as atieclxx.exe or atiesrxx.exe, writes continuously to the Windows boot volume on affected systems
    • The problem does not affect all users and reportedly predates the current drivers by around 18 months, so a single triggering driver version cannot be identified
    • Resource Monitor can be used to confirm which process is writing by searching for atieclxx.exe
    • Disabling the service via services.msc may impair FreeSync and frame pacing, and disabling Resizable BAR in the BIOS may reduce performance; both have helped some users but not in every case
    • The AMD External Events Utility can also be present on systems with an AMD chipset but no Radeon GPU
  • candygoogy (independent analysis) · Reference · checked Nov 13, 2026

    • A Process Monitor capture on Windows 11 with an RX 9070 XT and display driver 32.0.32015.12012 shows atieclxx.exe repeating the same sequence about once a second and copying its own 677,392-byte executable to C:\Windows\System32\config\systemprofile\AppData\Local\AMD\atieclxx.exe
    • The utility's own cached write counter (Win32_Process.WriteTransferCount) showed about 70 GB after 31 hours while the write-operation count barely moved, because the writes go into the Windows file cache and are flushed by the System process
    • Measured non-cached paging writes actually reaching the drive were 14.3 MB over 30 seconds, about 0.48 MB/s
    • The loop is a failing installation of amdkmpfd, AMD's PCI filter driver: the driver INF still records the target path and ten install sections reference its file list, but the list is empty and current packages no longer ship the files, while Adrenalin 26.3.1 and older did
    • Setting the read-only attribute on the copied file does not stop the writes because the utility clears file attributes before copying
    • Denying the SYSTEM account write and delete permission on the copied file with icacls stops the writes, the copy attempts end in ACCESS DENIED, and the service keeps running without a faster retry loop
  • candygoogy (independent analysis) · Reference · checked Nov 12, 2026

    • On the test PC the writes amounted to 662 KB/s, about 55 GB a day, roughly 20 TB a year, against a typical 1 TB SSD endurance rating of around 600 TB of writes
    • The behaviour has been confirmed by users on Radeon RX 580, RX 6700 XT, RX 7900 XTX, RX 9060 XT, RX 9070 and RX 9070 XT, on Windows 10 and Windows 11
    • Not every PC is affected, even with the same card and driver
    • The repository states that AMD confirmed the bug and said the fix will come in Adrenalin 26.11.1
    • Affected systems can be identified by adding the I/O write bytes column in Task Manager's Details view and watching atieclxx.exe
  • necanditool (independent analysis) · Reference · checked Nov 12, 2026

    • An independent measurement using Windows Event Tracing (ETW) found that on affected drivers atieclxx.exe copies itself once a second from the driver folder to C:\Windows\System32\config\systemprofile\AppData\Local\AMD\atieclxx.exe, a file of roughly 660 KB, about 56 GB per day
    • After the copy the service looks for installation files for the amdkmpfd filter driver, which is associated with Smart Access Memory, which explains why turning off Resizable BAR helps some users
    • A deny entry for the SYSTEM account on that single file stops the writes while leaving the service, FreeSync, frame pacing and hotkeys untouched
    • Disabling the AMD External Events Utility service always stops the writes but can impair FreeSync and frame pacing
    • File timestamps cannot be used to detect the rewriting because CopyFile carries the timestamps over from the source
    • A driver update replaces the file, so a permission-based workaround has to be reapplied afterwards