A green-lit gaming PC setup displays system performance graphs and a completed driver update on its monitor.
NVIDIA moved fast this week. The question now is whether the fix fully works. The company shipped GeForce Hotfix 621.35 to stop its display driver from writing large amounts of data to a log file on SSDs. Less than two days later, a test from one Reddit user suggests the problem can return after the PC has been running for a while, though at a lower rate. Both things can be true. The hotfix appears to help, and it may not cure every case.

Here's what is confirmed, what is only reported, and what GeForce owners should actually do.

A green-lit gaming PC setup displays system performance graphs and a completed driver update on its monitor. The bug: a log file that kept rewriting itself​

The problem centers on a background NVIDIA service that runs on almost every GeForce system. As Notebookcheck put it, the NVDisplay.Container.exe process, which runs as the NVIDIA Display Container LS service, repeatedly rewrites a binary log file named nvlog.nvlgstg on the drive where Windows is installed. NTCompatible reports that the file lives at C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg.

The affected versions are recent ones:

  • 621.14: users trace the regression to driver 621.14, released on November 4.
  • 621.24: the Game Ready driver from November 12. NTCompatible says the problem got worse with this release, yet NVIDIA's own 621.24 release notes listed zero open issues.
  • 621.01: reported as unaffected. TechPowerUp noted that in some extreme cases, the idle writes were up to 30 GB per hour, while the older 621.01 driver only logged around 2 MB per 5-minute idle window.

Treat the 30 GB/hour figure as the worst reported case, not a typical rate. TalkEsport points out that not every system was hit by it. Neowin adds that an Nvidia staff member on the company's forums said that the bug doesn't affect GeForce RTX 50 series graphics cards. That's worth noting, because the follow-up test below was run on an RTX 40-series card.

Section summary: a regression in 621.14 and 621.24 caused NVIDIA's Display Container service to keep rewriting nvlog.nvlgstg on the system drive. On some PCs this happened even when the machine was idle.

The fix: Hotfix 621.35​

NVIDIA's support page lists GeForce Hotfix Display Driver 621.35 with a single change: excessive background writes to nvlog.nvlgstg, tracked as bug 7116722. Notebookcheck reports that Nvidia has since acknowledged the issue as bug 7116722 and, on November 20, released GeForce Hotfix Display Driver 621.35. Wisevoter's timeline dates the release November 21, but NVIDIA's own page shows November 20.

Key details:

ItemDetail
VersionGeForce Hotfix 621.35
Based onGame Ready 621.24
Single listed fixExcessive writes to nvlog.nvlgstg in background [7116722]
PlatformsWindows 10 and Windows 11, 64-bit
CertificationBeta, not WHQL
DistributionNVIDIA Customer Care site

The distribution point is easy to miss. Guru3D notes that users searching the app for an update may not see 621.35 offered there. If the NVIDIA App says you're up to date, that doesn't mean you have the hotfix. You have to download it manually.

NVIDIA's standard hotfix warnings apply too. The company calls these drivers beta, optional and provided as-is, says they go through a much shorter QA process, and says waiting for the next WHQL-certified driver is the safest choice. The fix is expected to be folded into a future official release. OC3D framed the choice for affected users as installing the hotfix or going back to an older Game Ready driver.

Section summary: 621.35 is NVIDIA's official, targeted fix for this bug. It's a manual-download beta, and the regular WHQL release with the same fix is still to come.

The follow-up: one user says the writes came back​

On November 22, Wccftech reported a test by Reddit user "robbiekhan". He compared three drivers on a Windows 11 26H2 PC with an RTX 4090 and a 2TB Samsung 990 PRO NVMe SSD:

  • Hotfix 621.35: in the first hour after installing, NVDisplay.Container.exe logged only 90.8 KB of writes. During a following nine-hour stretch of overnight idle with the display in standby, the process logged 40.85 GB of I/O writes, an average of 1.26 MB/s. The SSD's own S.M.A.R.T. host-write counter, read in HWiNFO64, went up by 36 GB.
  • Studio 621.24: 1.18 TB of process I/O writes over five days of uptime, with a peak of 9.15 MB/s during active browsing.
  • Game Ready 621.01: 12.55 MB over 55 minutes and 9.47 MB over a 93-minute window.

There are two different measurements here. The 40.85 GB is what Windows counted as I/O writes by the process. The 36 GB in the headline is what the drive itself recorded as written. In the Reddit thread, the user said he checked SMART totals because Task Manager's process write counter can include writes that never reach the disk. That explains why the two numbers don't match.

What does the test actually show? On this one PC, 621.35 seemed to fix the loop at first, then the writes came back after long uptime at a lower rate than on 621.24. That points to a fix that reduced the problem without fully eliminating it, at least on this setup.

What doesn't it show? It isn't a controlled benchmark. The observation windows differ in length and workload, and it's one configuration. Nobody has independently reproduced it yet, and NVIDIA hasn't responded publicly to it. Wccftech's headline says the hotfix "still writes excessively", and its article goes as far as suggesting a rollback is the only fix. Yet the same piece calls it an isolated incident. The second statement is the one the evidence supports.

Section summary: one detailed user report says 621.35 cuts the writes but doesn't fully stop them during long idle periods. It's a useful warning, not proof that the hotfix fails.

Should you worry about your SSD?​

Probably not much, though it's fair to keep an eye on it. Notebookcheck notes that SSD endurance is rated in terabytes written (TBW), typically around 600 TBW for a 1 TB drive. The reported 36 GB overnight is a small fraction of that. The 1.18 TB over five days on 621.24 is more serious if it continues for months.

To put it in perspective: 36 GB a night adds up to about 13 TB a year, which a healthy modern NVMe drive can handle. At 30 GB an hour, around the clock, you'd be into a drive's rated endurance much faster. These are rough calculations on reported numbers, not NVIDIA measurements, and none of the reports show actual SSD damage.

What GeForce owners should do​

  1. Check your driver version. Open the NVIDIA App or NVIDIA Control Panel (System Information) and confirm which driver you're running.
  2. On 621.14 or 621.24? Those are the affected versions. Installing 621.35 is NVIDIA's official route. Anyone who was affected by this issue is advised to grab the hotfix as soon as possible, while others can wait for the next WHQL release.
  3. Look for sustained writes, not one big total. In Task Manager, open the Details tab and add the "I/O writes" column to watch NVDisplay.Container.exe. Remember this counter can overstate what actually reaches the disk. For the real picture, compare your drive's SMART host-write total (shown in tools such as HWiNFO64) before and after a long idle period. This mirrors the Reddit user's method.
  4. Be careful with workarounds. TechPowerUp reports that previous fixes for the SSD write bug included rolling back to 621.01 and a temporary fix that included stopping the NVIDIA Display Container LS service. Stopping that service can affect Control Panel and App features. With the hotfix available, one guide recommends that it is better to install the hotfix and leave the service set to Automatic. Rolling back is reasonable if your own monitoring still shows heavy writes on 621.35, but it shouldn't be the default for everyone.
  5. Managed fleets: IT teams that ship only WHQL drivers have a decision to make. They can stage the beta hotfix on affected machines or hold the last unaffected certified driver until NVIDIA's next WHQL release.

The bigger picture​

NVIDIA isn't alone here. Wccftech notes that the problem mirrored... more precisely, Wccftech reports that AMD had a similar idle-write issue earlier in November and released the optional Adrenalin Edition 26.11.1 driver for it. Two GPU vendors shipping background services that wrote far more than needed within the same month suggests a quality-control gap. Driver telemetry and logging grow with every release, and testing for idle disk behavior hasn't kept up.

The good news is that NVIDIA confirmed the bug and shipped a targeted fix within days. The open question is whether the coming WHQL driver fully resolves the long-uptime behavior one user reported. Until then, check your version, measure over a long idle period, and decide based on what your own drive shows.

 

References

  1. NVIDIA’s 621.35 Hotfix Driver Still Writes Excessively To The SSD; One User Claims 36GB Was Already Recorded When His PC Was Running Idle Overnight - Wccftech Wccftech 2026-11-22T07:26:54+00:00
  2. NVIDIA Hotfix Stops Excessive SSD Writes at Idle - Wisevoter Wisevoter 2026-11-21T04:54:05+00:00
  3. NVIDIA Releases GPU Hotfix Driver Version 621.35 That Addresses Excessive And Unnecessary Writes To SSDs wccftech.com