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
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
- Save £200 on this MSI QD-OLED gaming monitor — just £399 for a vibrant 1440p display with a 240Hz refresh rate
- For just $10-per-terabyte, you can grab a 24TB Seagate BarraCuda HDD before shortages hit — solve all your storage needs for just $249
- [Daily Due Diligence] NVDA NVDA
- Hands-on with Valve's new Steam Frame headset — Arm-powered, mixed-mode device uses Fex translation layer for traditional x86 games
- Google strikes massive deal to buy 1.5 terawatt hours of Ohio solar capacity — 15-year deal will see most of 50 megawatt solar farm's capacity diverted to data
Informational only. No financial advice. Do your own research.