This is an important observation because the Redditor noted that disabling this service/process prevents the log from being updated, thereby ending the errant, seemingly wasteful file writing. Alternatively, piping the process output to nul: is a workaround advanced by the Redditor. They note that this has no discernible effect on their system, but warn others to only do the same at their own risk.
Note that Takia_Gecko doesn’t say whether their system uses FreeSync. Comments on this post don’t establish any relationship between FreeSync functionality and this log file writing workaround, either.
We’ve reached out to AMD to ascertain whether these seemingly meaningless log file updates are going to be addressed in upcoming updates to its chipset drivers.
Follow Tom's Hardware on Google News , or add us as a preferred source , to get our latest news, analysis, & reviews in your feeds.
Mark Tyson Social Links Navigation News Editor Mark Tyson is a news editor at Tom's Hardware. He enjoys covering the full breadth of PC tech; from business and semiconductor design to products approaching the edge of reason.
toffty I have two computers both with an AMD CPU+GPU and latest drivers. The log directory in question does not exist in either computer so not sure how much of a problem this is with current drivers 🤷♂️ Reply
chemistu toffty said: I have two computers both with an AMD CPU+GPU and latest drivers. The log directory in question does not exist in either computer so not sure how much of a problem this is with current drivers 🤷♂️ Same here. Reply
Takia_Gecko Hey, OP (Takia_Gecko) here. Thank you for covering this and reaching out to AMD — My goal with this was to get it fixed, and you covering this has considerably increased the chance that it will. I just wanted to clarify something and add some context. First, the most important thing. Takia_Gecko claims they confirmed with an AMD engineer that a Windows process … I did NOT confirm anything with an AMD engineer nor have I said that I did. I've linked another reddit post from 7 years, ago, where an AMD engineer responded and confirmed that this is the case (https://reddit.com/r/Amd/comments/8bvcfo/do_not_disable_amd_external_events_utility/) I agree that not every of these thousands of writes will go to the disk immediately. The writes are also not very big, so in terms of TBW it probably won't be much of an impact. Still I think this is erroneous behaviour and should be fixed. From my research, I know it has been going on for multiple years. This behavior was charted by a utility dubbed ReadDirectoryChangesW. Nitpick: That's the name of the Windows API I used in my tool, but not the utilities name. Note that Takia_Gecko doesn’t say whether their system uses FreeSync. I don't. I use G-Sync. Feel free to reach out to me per e-mail or here, if you want any additional information. Reply
mrdoc22 I can confirm it on "Windows 11 25H2" with "AMD Adrenalin 25.10.2" and "AMD Chipset driver 7.06.02.123" on my machine it's placed in "C:\Windows\System32\DriverStore\FileRepository\amdfendr.inf_amd64_a45773f484fe1fd0\AMD\EeuDumps", so I created a hardlink to my ramdrive until they fix it. The logfile gets updated when you just switch to another window. Reply
edzieba Even with writes being buffered (be it an on-drive cache or HMB) spamming write operations is still spamming ops that don't need to occur and that the OS then needs to deal with – either caching and then managing the cache writeout, or forwarding a steam of ops to the SSD to cache and writeout. Either way, that's a bunch of ops occurring that don't need to, adding pointless overhead. I'd bet the DPC and ISR impact would be nonzero, would be interesting to see how Latencymon reacts when this logging is occurring vs. the logging killed (and not just write-holed). Reply
Takia_Gecko edzieba said: Even with writes being buffered (be it an on-drive cache or HMB) spamming write operations is still spamming ops that don't need to occur and that the OS then needs to deal with – either caching and then managing the cache writeout, or forwarding a steam of ops to the SSD to cache and writeout. Either way, that's a bunch of ops occurring that don't need to, adding pointless overhead. I'd bet the DPC and ISR impact would be nonzero, would be interesting to see how Latencymon reacts when this logging is occurring vs. the logging killed (and not just write-holed). Agree, plus we just noticed that it also invokes Defender for every write. so MsMpEng CPU usage spikes every time you move or resize a window. Reply
thesyndrome I heard about this yesterday and checked my own system because I had heard that it affects AMD CPUs as well as GPUs (I have a 7800X3D paired with an Nvidia GPU), for me the EEUDumps folder does exist, but theres only 5 files in there and they are all from June or July last year, so it looks like mine isn't constantly writing there, but I spoke to someone else with the same CPU and they didn't have the folder at all, but I had the AMD Adrenalin software installed and they didn't so that might be why I had the folder but he didn't. Reply
mrdoc22 I just checked my 2 backupcomputers, for the driver "AMD Crash Defender" in "devicemanagement", which is causing this extremely logging. The one with Nvidia graphicscard dosen't have the driver or the directory "eeudumps". The one with AMD graphicscard have the driver and also have the directory "eeudumps", where "Adrenalin 25.6.1" is installed, and have also extremely logging. It's is coming from "Adreanlin installation" not Chipset installation, I have back to "Adreanlin 24.5.1 installationfiles" where I can find it. Reply
Flyfisherman No. On my system it does not exist: GPU: ASUS TUF GAMING Radeon™ RX 6900 XT CPU: AMD Ryzen 9 3950X Mobo: Asus ROG Crosshair VIII Hero (X570) BIOS ver. 5302 (2025-10-27) Memory: Corsair VENGEANCE® RGB RT 32GB (2 x 16GB) DDR4 DRAM 3200MHz C16 (1.2V) Extended monitor setup: first AORUS-FI27Q 2560×1440 (16:9), secondary Philips IPS 1920×1200 (16:10) Windows 11 Pro 24H2 AMD Radeon s/w: 25.11.1 AMD Chipset: 7.06.02.123 Best regards from Sweden Reply
mrdoc22 Flyfisherman said: No. On my system it does not exist: GPU: ASUS TUF GAMING Radeon™ RX 6900 XT CPU: AMD Ryzen 9 3950X Mobo: Asus ROG Crosshair VIII Hero (X570) BIOS ver. 5302 (2025-10-27) Memory: Corsair VENGEANCE® RGB RT 32GB (2 x 16GB) DDR4 DRAM 3200MHz C16 (1.2V) Extended monitor setup: first AORUS-FI27Q 2560×1440 (16:9), secondary Philips IPS 1920×1200 (16:10) Windows 11 Pro 24H2 AMD Radeon s/w: 25.11.1 AMD Chipset: 7.06.02.123 Best regards from Sweden Are you sure? Have you checked in "Devicemanagement" under "Systemdevices" for "AMD Crash Defender" Reply
Key considerations
- Investor positioning can change fast
- Volatility remains possible near catalysts
- Macro rates and liquidity can dominate flows
Reference reading
- https://www.tomshardware.com/software/windows/SPONSORED_LINK_URL
- https://www.tomshardware.com/software/windows/amd-users-flag-heavy-ssd-write-activity-tied-to-chipset-driver-incessant-log-file-writes-observed-every-time-a-window-is-moved-or-resized#main
- https://www.tomshardware.com
- Sony announces 240 Hz PlayStation gaming monitor — QHD monitor features built-in DualSense charging hook and VRR support for PS5
- Five convicted for helping North Korean IT workers pose as Americans and secure jobs at U.S. firms — over 240 companies were victimized by the scam
- Creality 3D printers see big discounts in 'Mega Sale' — up to 34% off
- AMD users flag heavy SSD write activity tied to chipset driver — incessant log file writes observed every time a window is moved or resized
- Call of Duty: Black Ops 7 campaign requires a constant online connection and has zero checkpoints — mission levels are designed for four, necessitating repetiti
Informational only. No financial advice. Do your own research.