Days after AMD fixed a Radeon driver utility that kept writing to people's SSDs, NVIDIA owners are reporting a similar problem. According to posts on NVIDIA's own driver feedback threads, picked up by Tom's Hardware on 18 November 2026 and since covered by Windows Latest and Guru3D, GeForce drivers 621.14 and 621.24 can make a background service rewrite a log file on the system drive over and over while the PC sits idle. This article is based on those reports and NVIDIA's release notes; Forge PC hasn't reproduced the problem on its own systems, and NVIDIA had not commented at the time of writing.
What's being reported
The writes come from NVDisplay.Container.exe, the process behind the NVIDIA Display Container LS service, which the NVIDIA Control Panel and NVIDIA App need to work. Users say it repeatedly rewrites a binary log file at:
C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg
The figures shared so far vary a lot from PC to PC:
Driver | Reported idle writes | Source of the figure |
|---|
621.01 | Under 2MB in five minutes | Forum user, via Tom's Hardware and Guru3D |
621.14 | 515MB of process writes in five minutes, 270MB actually reaching the C: drive | Forum user, via Tom's Hardware |
621.24 (12 November 2026) | "About 30gb per 1h", and 70GB or more in long sessions | Forum user, via Tom's Hardware and Windows Latest |
Tom's Hardware notes that the first user checked the drive's SMART "Data Units Written" counter, which matched what Windows reported, so these are real writes rather than just a busy process counter. The same reports say the write volume grows as the log file grows, and the user on 621.24 said this happened with telemetry turned off in the NVIDIA App. Not every PC seems to be affected: Windows Latest says several Reddit users on these drivers see nothing unusual.
Guru3D stresses that these are user reports, not an NVIDIA-confirmed defect, and that host writes aren't the same as NAND wear, because SSD controllers merge and cache small writes. That's a fair caution.
How much does it matter for your SSD?
It's unlikely to kill a drive overnight, but it's wear you get nothing for. Tom's Hardware worked out that the lower 270MB-per-five-minutes figure comes to roughly 28TB a year on a PC that never sleeps, close to 5% of the 600TB endurance rating typical of a 1TB SSD. Windows Latest adds that the higher reported rate of 30GB an hour, for eight hours a day, works out to about 15% of that rating a year.
Guru3D notes that this matters most for drives with low endurance ratings, particularly QLC models. Our TLC vs QLC SSD guide explains the difference, and with UK SSD prices as high as they are, nobody wants to burn through endurance for nothing.
How to check if your PC is affected
Both Tom's Hardware and Windows Latest suggest the same checks:
Press Win + R, type resmon and press Enter to open Resource Monitor.
Open the Disk tab and sort Disk Activity by Write (B/sec).
Leave the PC idle for a few minutes and look for NVDisplay.Container.exe writing to nvlog.nvlgstg again and again.
For writes that actually reach the drive, note the Host Writes or Data Units Written value in CrystalDiskInfo or your SSD maker's app, leave the PC idle for an hour and compare. Our guide to checking SSD health shows where to find these numbers.
What you can do now
There's no official fix yet. NVIDIA's release notes for 621.24 don't list the problem as an open issue, and no hotfix had been announced at the time of writing. The options users have reported are:
Roll back to 621.01. This is the workaround most often suggested, and a second user in NVIDIA's forum thread said it helped. Guru3D says it's not guaranteed to work. See how to roll back a graphics driver.
Know the RTX 50 catch. Windows Latest points out that 621.01 is the driver NVIDIA had to patch for video freezes and black screens on RTX 50 GPUs, quoting NVIDIA's release notes as saying video playback "may freeze or black screen" after 621.01. So RTX 50 owners who roll back may swap one bug for another.
Clean reinstalls don't seem to help. One user tried three clean reinstalls with DDU on 621.24 without success. Our DDU guide is still the right method if you do roll back.
Deleting the log file is only temporary. Stopping the service, deleting nvlog.nvlgstg and restarting the service cut the writes by about 91% for one user, according to Windows Latest, but the file then grew again.
Disabling the service stops the writes, but you lose the NVIDIA Control Panel and NVIDIA App while it's off, so we wouldn't recommend that for most people.
If you're not affected when you check, there's no need to change anything. Keep an eye on NVIDIA's next driver release notes; our guide to updating graphics drivers covers the usual ways to install it.
How this compares with AMD's bug
AMD's problem, covered in our Radeon driver SSD writes story, came from its External Events Utility (atieclxx.exe). Windows Latest says AMD fixed it in the optional Adrenalin 26.11.1 driver on 12 November, covering Radeon RX 7000 cards and newer, and Guru3D reports that Adrenalin 26.11.2 fixes more Radeon SSD writes. Tom's Hardware notes that NVIDIA had a similar Display Container logging bug in 2021, which it fixed in driver 471.96 and documented in its release notes.
Our verdict
If you run GeForce driver 621.14 or 621.24, spend five minutes in Resource Monitor while the PC is idle. If NVDisplay.Container.exe is constantly writing to nvlog.nvlgstg, rolling back to 621.01 is the workaround users report, but RTX 50 owners should weigh that against the video playback bug 621.01 had. If you're not seeing the writes, stay put and wait for NVIDIA's next driver, which will hopefully acknowledge and fix the issue.