Two weeks ago I was poking fun at AMD for a driver that quietly chewed through SSDs. Well, it’s Nvidia’s turn. A fresh Nvidia driver SSD bug in GeForce 621.14, and still present in 621.24, has the display driver rewriting a log file over and over, on a PC that’s doing absolutely nothing.
The numbers go from annoying to ridiculous depending on who’s measuring. One user clocked about 3 GB an hour on an idle machine. Another, on the newer 621.24, reported around 30 GB an hour, with longer sessions pushing past 70 GB. Every Alt+Tab added another 500 MB to 1 GB, which is a fun party trick nobody asked for.
What the Nvidia driver SSD bug actually does
The culprit is NVDisplay.Container.exe, the “NVIDIA Display Container LS” service that the Nvidia App and Control Panel depend on. Since 621.14 (released on November 4) it keeps rewriting a binary log called nvlog.nvlgstg, and the bigger that file gets, the more it writes. Delete the log and it calms down for a while, then ramps back up.
And yes, these are real writes hitting the drive, not just a process counter looking scary. The person who spotted it cross-checked Windows Resource Monitor against the SMART “Data Units Written” value in CrystalDiskInfo, and the figures matched, as Tom’s Hardware details. The previous driver, 621.01, wrote less than 2 MB over the same five-minute window. Three clean reinstalls with DDU changed nothing; only a rollback did.
If this sounds familiar, it’s because the AMD Radeon driver was caught doing almost the same thing last month, copying its own executable once a second. AMD at least admitted it and shipped a fix on November 12. Nvidia’s release notes for 621.24 list “N/A” under open issues, which is a bold way of saying nothing.
Should you panic about SSD endurance?
No, but you should care. A typical 1 TB drive is rated for around 600 TB of writes. At the low end of this bug, a PC that never sleeps burns through roughly 28 TB a year, close to 5% of the drive’s endurance. At 30 GB an hour for eight hours a day, you’re looking at something like 15% a year, for nothing. Your drive won’t die next week, but you paid for that endurance and Nvidia is spending it on a log file.
It also isn’t just wear. Several people report hitching in games and video while the service is thrashing the disk, so the “it’s only background writes” defence doesn’t fully hold. And with SSD prices being what they are right now, nobody is in a hurry to replace a drive early. That’s exactly why people go to such lengths to rescue old ThinkPads with a ten-dollar chip rather than buy new hardware.
How to check if you’re affected
Open Resource Monitor (resmon in the Start menu), go to the Disk tab and sort by writes. If NVDisplay.Container.exe sits at the top, writing to a file ending in nvlog.nvlgstg, congratulations, you’re in the club. For a second opinion, note the “Total Host Writes” figure in CrystalDiskInfo, leave the PC idle for an hour, and compare. Not every system seems to be hit, so it’s worth the two minutes.
What I’d do: roll back to 621.01 and ignore the update nag until Nvidia publishes a fix in the release notes. If you can’t roll back, open services.msc, set NVIDIA Display Container LS to Manual and stop it. The writes stop instantly. The downside is that the Nvidia App and Control Panel won’t open until you start the service again, which, frankly, is a sacrifice most of us can live with.
What bugs me is that this isn’t new. Nvidia had a near-identical logging problem back in 2021, fixed in driver 471.96, and another one with 572.16. Same company that loses $11 million of GPUs between Oakland and Texas apparently also loses track of its own regression tests.
Your SSD has a finite number of writes. Don’t let a log file nobody reads eat them.
Discover more from TechPassion
Subscribe to get the latest posts sent to your email.





