Your SSD Might Be Dying Because of AMD Drivers — Here’s How to Stop It Now

File this under: Tech weirdness I wish was fiction. AMD drivers are quietly hammering your drive with log writes every time you move or resize a window. Not a couple writes. We’re talking hundreds of hits per wiggle. A Reddit user, Takia_Gecko, caught it on video, and the rabbit hole is surprisingly deep.

What’s actually going on

If you’re running AMD chipset drivers or Radeon software, you may be affected. The culprit appears to be a background service called External Events Utility. When it’s running, simply dragging a window around your desktop can trigger a flood of log writes. Stop the service, and the flood stops instantly.

The logs typically land in this folder: C:\Windows\System32\AMD\EEUDumps. Depending on your driver version, they can also show up here: C:\Windows\System32\DriverStore\FileRepository\amdfendr.inf_amd64_***\AMD\EeuDumps. People have been reporting similar behavior since at least 2022, but the scale of the writes wasn’t obvious until someone watched it in real time.

How to see it on your own system

Grab Microsoft’s Process Monitor, filter for file paths containing EEUDumps, and then move a browser window around. If your setup is affected, you’ll see a parade of write operations scroll by. Results vary between machines, but for many users it’s hundreds of tiny updates just from normal desktop behavior. If nothing shows up in the System32 path, check the DriverStore location.

The DIY band-aid (only if you know what you’re doing)

Takia_Gecko shared a workaround that diverts those writes into a black hole instead of your SSD. It’s clever, but not thoroughly tested, and messing with system folders always carries risk. Proceed only if you’re comfortable with potential side effects and can undo changes if something breaks.

• Open Command Prompt as Administrator.
• If your logs are in C:\Windows\System32\AMD\EEUDumps, run: "rmdir /s /q C:\Windows\System32\AMD\EEUDumps"
• Then create a directory link to the null device so writes vanish: "mklink /d C:\Windows\System32\AMD\EEUDumps nul:"
• If your EEUDumps folder lives under DriverStore instead, adjust the path to: "C:\Windows\System32\DriverStore\FileRepository\amdfendr.inf_amd64_***\AMD\EeuDumps"

Important: Redirecting or disabling the External Events Utility might break stuff you actually want, like FreeSync behavior or how certain peripherals are detected. That trade-off might sting more than theoretical SSD wear.

Is this actually damaging your SSD?

Some users say the panic is overblown. Modern SSDs are built to soak up small, frequent writes using controller caches before anything hits the NAND. The files themselves look tiny, which suggests the total written data could be minimal in practice. Still, SSD prices have ticked up lately, so the idea of wasting lifespan on hyperactive logs is understandably annoying.

The part that really grates

This is a perfect example of how dependent we are on opaque driver software. When something goes sideways, there’s rarely clear documentation, and we end up waiting for an official note that may never come while Reddit sleuths do the legwork. Right now, we don’t have numbers from AMD on how much data is actually being written, so users are choosing between two bad options: potential wear or potentially broken features. Neither should be necessary if the logging were tuned properly or had an easy off switch.

If you check your EEUDumps folder, what do you see? Are you riding it out or trying the workaround? I’m curious how widespread this is in the wild.