NVIDIA Driver SSD Write Bug: Is Hotfix 621.35 Enough?
As an Amazon Associate we earn from qualifying purchases. Prices are as of the time shown and may change; the price on Amazon at checkout applies. Details
NVIDIA drivers 621.14 and 621.24 can write up to 30GB an hour to your SSD at idle. Hotfix 621.35 targets it, but one test says it isn't fully fixed.
By Zoltan LukacsiIT and SEO professional, 20 years
NVIDIA's GeForce drivers 621.14 and 621.24 have a bug that makes the NVDisplay.Container.exe process rewrite a log file on your system SSD over and over, even while the PC is idle. NVIDIA released Hotfix Driver 621.35 on November 20, 2026 to fix it, so install that (or roll back to 621.01) and then check that the writes have stopped, because one early test says they can come back.
What is the NVIDIA SSD write bug?
The NVIDIA Display Container LS service keeps rewriting a binary log file called nvlog.nvlgstg on the Windows drive. Notebookcheck collected the user reports: 515MB of writes after five minutes idle on 621.14, over 3GB in ten minutes for another user, and roughly 30GB an hour on 621.24 for a third. The same idle test on 621.01 wrote less than 2MB. Wccftech measured about 1.43 MB/s on an idle RTX 4090 with ShadowPlay and the overlay switched off. NVIDIA tracks it as bug 7116722.
Does hotfix 621.35 fix it?
NVIDIA says so, but one early test disagrees. The hotfix's single listed fix reads "Excessive writes to file nvlog.nvlgstg may occur in background", as quoted by Notebookcheck. On November 22, Wccftech reported a Reddit user's test on an RTX 4090 with a Samsung 990 Pro 2TB: only 90.8KB written in the first hour after installing 621.35, then 36GB of host writes during a 9-hour overnight idle. That is lower than 621.24, where the process wrote 1.18TB over five days on the same PC, but not zero. It is one user's result, and Wccftech calls it isolated.
The hotfix is an optional beta without WHQL certification. Download it from NVIDIA's hotfix support page if you're on 621.14 or 621.24, or wait for the next Game Ready driver. Rolling back to 621.01 also avoids the bug, but Windows Latest notes it can bring back the black screens some RTX 50 cards had on that driver.
How to check if your PC is affected
- Press Win + R, type resmon and press Enter.
- Open the Disk tab and sort by Write (B/sec).
- Leave the PC idle for a few minutes. If NVDisplay.Container.exe keeps writing to nvlog.nvlgstg, you're affected.
Do the check again the morning after installing 621.35, since the Reddit test only saw the writes return after hours of uptime. CrystalDiskInfo's "Total Host Writes" figure, noted before and after a night idle, shows what actually reached the drive.
How much SSD life does the bug use?
At Wccftech's measured 1.43 MB/s around the clock, the bug writes about 45TB a year; at the worst reported 30GB an hour, about 263TB. The table compares that with each maker's TBW rating, the amount of data the drive is warranted to handle. On 8 hours a day, divide by three.
| SSD | TBW (maker spec) | Rating used per year at 1.43 MB/s | At 30GB an hour |
|---|---|---|---|
| Crucial P310 1TB | 220TB | 21% | 119% |
| Kingston NV3 1TB | 320TB | 14% | 82% |
| Samsung 990 Pro 1TB | 600TB | 8% | 44% |
| Samsung 990 Pro 2TB | 1,200TB | 4% | 22% |
| WD_Black SN7100 2TB | 1,200TB | 4% | 22% |
Process counters don't always match what reaches the flash: Notebookcheck notes that in one five-minute test the whole C: drive logged 270MB while the process showed 515MB. A TBW rating is a warranty limit, not a failure point, as our SSD lifespan and TBW guide explains. AMD had the same kind of bug in November; see how AMD fixed it in Adrenalin 26.11.1.
What should you do?
If you're on 621.14 or 621.24, I'd install hotfix 621.35 today and run the resmon check the next morning. If the writes are back, roll back to 621.01 until NVIDIA ships a WHQL driver with the fix. Owners of a small, low-endurance drive like the 220TBW Crucial P310 1TB have the most to lose, so check CrystalDiskInfo's health figure too.
Compare NVMe SSDs →
Every NVMe drive ranked by speed, endurance and price per terabyte.
Frequently Asked Questions
Which NVIDIA drivers have the SSD write bug?
GeForce drivers 621.14 (released November 4, 2026) and 621.24 (November 12), according to Notebookcheck and TweakTown. The earlier 621.01 driver wrote less than 2MB in the same idle test.
Does hotfix 621.35 fix the NVIDIA SSD write bug?
It is meant to. NVIDIA lists one fix: excessive writes to the file nvlog.nvlgstg in the background. One Reddit tester reported by Wccftech still logged 36GB of host writes over a 9-hour overnight idle on 621.35, so check your own PC after installing it.
How do I check if the NVIDIA driver is writing to my SSD?
Press Win + R, type resmon, open the Disk tab and sort by Write (B/sec). If NVDisplay.Container.exe keeps writing to nvlog.nvlgstg while the PC sits idle, your system is affected.
Will the NVIDIA driver bug kill my SSD?
Not on a decent drive at typical rates. At the 1.43 MB/s Wccftech measured, a PC on 24 hours a day writes about 45TB a year, under 4% of a 2TB Samsung 990 Pro's 1,200TBW rating. At the worst reported 30GB an hour, a 220TBW Crucial P310 1TB would pass its rating in about 10 months.




