NVIDIA fixes the driver's massive SSD writes with hotfix 621.35

Graphic composition of NVIDIA with the GeForce RTX logos and the text Hotfix Driver on a green background

NVIDIA released hotfix 621.35 for its GeForce drivers on November 21, a package with a single fix in the release notes: “excessive writes may occur to the nvlog.nvlgstg file in the background.” It is the response to a problem that had stopped being an isolated complaint, because the driver was writing up to 30 GB per hour to the system SSD on machines that were doing nothing at all.

The fault was documented in versions 621.14 and 621.24, according to the reports collected by PC Gamer and confirmed by other outlets. The NVDisplay.Container.exe process kept rewriting a binary log continuously, even with the machine idle, and that traffic ended up in users’ sights starting November 15, three days after 621.24 reached the Game Ready channel.

Where the writes came from: nvlog.nvlgstg

The file involved is nvlog.nvlgstg, which on Windows lives in C:\ProgramData\NVIDIA Corporation\nvtopps\nct\. According to the analysis reported by PC Gamer, the problem was not the volume of the log itself but the way it was written: the file was rewritten in full on every pass instead of appending lines at the end, so the cost grew as the file got bigger. At a sustained rate of 1 or 2 MB per second, the figure comes out to 5 or 7 GB per hour; the most aggressive cases reached 30 GB per hour.

The comparison with the previous version helps size the error. In driver 621.01, the same process wrote around 2 MB for every five-minute window while idle, roughly 24 MB per hour; PC Gamer measured 63 MB in one hour of activity on its own machine with that version. Against those 24 MB, the 30 GB of 621.24 amounts to a factor of about 1,280 times more writes, all of them useless to the user.

Samsung 990 PRO 1 TB SSD in M.2 format on a turquoise background

What it means for SSD lifespan

The wear on a solid-state drive is not measured in speed but in terabytes written: every gigabyte the driver writes without need consumes NAND cycles and brings the drive closer to its declared TBW limit. At 30 GB per hour, a machine left on 24 hours a day would accumulate around 720 GB per day of writes that produce nothing. The math is not catastrophic for a consumer drive in a short session, but it becomes relevant on a laptop that stays on for weeks and, above all, on machines with small drives.

In a month in which NVIDIA has already raised the price of the RTX 50 by up to 500 dollars, SSD wear is an added cost that appears on no invoice. Nor is it a problem exclusive to NVIDIA: AMD acknowledged similar excessive writes in its Radeon drivers and fixed them with the optional Adrenalin 26.11.1 a few days earlier.

How to check whether your machine is affected

PC Gamer publishes a method that requires installing nothing: open Task Manager, go to the Details tab, right-click the column header, choose “Select columns” and enable “I/O write bytes.” The value shown next to NVDisplay.Container.exe is in bytes, so it is worth dividing it by one billion to read it in gigabytes. If that figure runs into the billions within a few hours of use, the machine is affected.

Who should install 621.35 and who can wait

The hotfix builds on 621.24, the Game Ready driver from November 12, and NVIDIA distributes it only through its customer support page, not the usual channel. The company warns that these packages are beta, optional and offered as is, with an abbreviated quality process that does not go through full WHQL certification. Anyone running 621.14 or 621.24 who has confirmed anomalous writes should update; anyone who has not seen the problem can wait for the next certified Game Ready release.

The alternatives that circulated before the hotfix remain valid as an emergency measure: reverting to 621.01 with a clean install, stopping the NVIDIA Display Container LS service while working, or applying the Registry tweak that blocks the writes without giving up the rest of the driver’s features. None of the three replaces a fixed driver, and NVIDIA itself already assumes the definitive fix will arrive with the next WHQL release.

Related news

Other news