Tech News After AMD, Nvidia users confirm Windows driver bug quietly degrades your SSD over time

Gandalf_The_Grey

Level 86
Verified
Honorary Member
Top Poster
Content Creator
Well-known
Forum Veteran
Earlier this month, we reported on a bug on Radeon's Windows GPU driver that makes the AMD External Events Client Module / AMD External Events Utility (atieclxx.exe) component write massive amounts on data to SSDs and other installation drive, continuously, which means over a day it could end up writing over 430 GB of data. This is dangerous especially to low-capacity SSDs as it quickly wears out the storage and the drive health. After the widespread reporting of the bug, the Radeon team published a fix via driver version 26.11.1.

Following that, GeForce users now confirm that a similar bug affects them too, with Nvidia's Windows GPU drivers apparently generating excessive disk writes through a logging component. Interestingly, this is not entirely new thing as reports of the same behavior have been around for quite some time, though that was resolved with a future update.

The issue was brought up again recently in Nvidia's official GeForce Game Ready Driver 621.14 feedback thread on the official GeForce forum. Users have reported excessive writes involving the nvlog.nvlgstg file, which is associated with Nvidia's logging and telemetry activity. The file is located under C:\ProgramData\NVIDIA Corporation\nvtopps\nct\ and appears to be repeatedly overwritten by the Nvidia Display Container process.

A report in the thread provides some rather concerning numbers as the user says that on Game Ready Driver 621.14, NVDisplay.Container.exe was responsible for approximately 515 MB of disk writes in just five minutes while the system was idle. The same test on the previous 621.01 driver resulted in less than 2 MB of writes over the same period.

The user also checked the SSD's SMART data for units written counter and found that it reflected the additional writes. As such, this is not a misleading figure in Windows' process-level disk activity reporting. By summing up the figures, the user estimated that the Nvidia process could account for roughly 3 GB of writes per hour, even when the PC is doing basically nothing.

Aside from long term SSD wear, this constant logging in the short term could become severe enough to cause games and videos to stutter, with even mouse movement being affected. Cleanly reinstalling the new driver using Display Driver Uninstaller (DDU) did not resolve the problem, and rolling back to the previous driver brought the writes down to just 260 KB over an hour.
 
Hi Gandalf. This is worth checking, but the headline runs slightly ahead of the evidence.

AMD has officially confirmed and fixed its excessive-write problem in Adrenalin 26.11.1. On the NVIDIA side, there is a credible and unusually detailed user report on NVIDIA’s forum showing a large regression with 621.14:

  • NVDisplay.Container.exe repeatedly writes nvlog.nvlgstg.
  • Reported process I/O was 515 MB in five minutes on 621.14, versus under 2 MB on 621.01.
  • The reporter also checked the SSD’s SMART “Data Units Written,” supporting that at least some of this reached the drive rather than existing only as cached process I/O.

That establishes a real problem on at least the reported system. It does not yet establish that all—or even most—621.14 installations are affected, and NVIDIA’s 621.14 information does not currently acknowledge this as a known issue.

There is also a numerical wrinkle: 515 MB per five minutes extrapolates to about 6.2 GB/hour, not 3 GB/hour. The lower figure appears to come from the reported drive-level writes, whereas 515 MB is the process I/O counter. Process bytes, filesystem writes and SMART host writes are related but not interchangeable. SMART is the more useful confirmation, although it measures data sent to the drive, not the exact amount eventually written to NAND after the controller’s internal handling.

At 3 GB/hour continuously, the excess would be about 26 TB per year. That is wasteful and significant—particularly for small or low-endurance SSDs—but “quickly destroys your SSD” would still be tabloid seasoning. Short-term latency or stuttering is arguably the more immediate concern.

Anyone using 621.14 can check without changing anything:

  1. Open Resource Monitor → Disk.
  2. Sort by Write (B/sec) and watch NVDisplay.Container.exe for 5–10 idle minutes.
  3. Check whether the activity targets
    C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg.
  4. If possible, compare the SSD’s SMART “Data Units Written” before and after a controlled idle period.

If affected, rolling back to 621.01 is the cleaner temporary workaround. Reinstalling the same affected driver with DDU would not be expected to cure a driver regression. Stopping NVIDIA Display Container and deleting the log may confirm the source, but it is temporary and can disable NVIDIA Control Panel or related functions. Unaffected systems do not need a panic rollback merely because the driver number matches.

Sources
 

MalwareTips community

Join the discussion

Create a free account to reply to this thread, ask your own questions and get help from the community.

  • Reply and ask questions
  • Get alerts when someone answers
  • Free malware removal help

Join 75,667 members who help each other for free, since 2010.

Create free account
or continue with

Recently browsing

Members and guests who viewed this thread in the last 5 minutes

Back
Top