A gaming PC and monitor display a driver hotfix dashboard tracking disk writes, with green accents throughout.
NVIDIA has released an optional hotfix for a GeForce driver bug that kept some Windows PCs writing to their SSDs while they were sitting idle. NVIDIA released GeForce Hotfix Display Driver 621.35, dated November 20, 2026. It contains a single fix for excessive background writes to the nvlog.nvlgstg file and is distributed only through NVIDIA's Customer Care support site.

SSBCrack and POPTOPIC both covered this release. They describe the same driver, not two separate fixes. SSBCrack covered the fix and the workarounds people were using. POPTOPIC focused on the trade-off of getting the fix through a beta driver. Both points matter if you're deciding whether to install it.

A gaming PC and monitor display a driver hotfix dashboard tracking disk writes, with green accents throughout. What NVIDIA actually fixed​

The release notes list one item. NVIDIA acknowledges that excessive writes to the file nvlog.nvlgstg may occur in the background, and tracks the issue under bug ID 7116722.

  • Affected drivers: users on versions 621.14 and 621.24, where the NVDisplayContainer.exe process could repeatedly write to the nvlog.nvlgstg log file while the system was idle
  • Timeline: NTCompatible reports that the problem first appeared in Game Ready 621.14 on November 4 and got worse with 621.24 on November 12, yet NVIDIA's own 621.24 release notes listed zero open issues
  • Where the file lives: C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg
  • What the hotfix is built on: NVIDIA's latest Game Ready driver, currently 621.24, released November 12

NVIDIA's release note doesn't explain what changed in the code, and it doesn't say how much writing to expect after you install it. The fairest description is that 621.35 targets the problem. Nobody has published independent tests showing how well it works.

Section summary: If you're on 621.14 or 621.24, the background service that supports the NVIDIA Control Panel and NVIDIA App may be rewriting a log file over and over. Hotfix 621.35 is NVIDIA's targeted fix for that.

How bad was it? The numbers need context​

The headline figure is alarming. In some extreme cases, idle writes reached 30 GB per hour, while the older 621.01 driver logged only about 2 MB per five-minute idle window. Before you panic about your NVMe drive, keep three things in mind:

  • 30 GB/hour is the worst reported case, not the typical one. Tom's Hardware's November 18 report described one measurement of about 270 MB of total C: drive writes in five minutes, which works out to roughly 3 GB per hour. A separate user estimated around 30 GB per hour.
  • Not every PC was affected. TalkEsport says plainly that not every system was hit by it, and Tom's Hardware made the same point.
  • Lots of activity doesn't mean lots of used space. POPTOPIC points out that background writes are repeated activity. A log that keeps rewriting itself can wear an SSD without filling it up.

Tom's Hardware also did some endurance math, which shows why people were worried and also why it isn't a crisis. It used a typical 1 TB SSD rated for 600 TB written over a five-year warranty. At 270 MB every five minutes, a PC that never sleeps would write about 28 TB a year. In the 30 GB/hour scenario, eight hours a day would use roughly 15% of that rated endurance each year. Tom's Hardware said these are illustrative numbers: real PCs aren't on all the time, and the measured writes include everything else the system was doing. So this kind of waste shortens an SSD's rated life. It doesn't destroy the drive overnight.

One more claim is worth mentioning with caution. Neowin reports that an Nvidia staff member on the company's forums said the bug doesn't affect GeForce RTX 50 series graphics cards. We couldn't confirm that in NVIDIA's release notes, so don't use it as a reason to skip checking your own system.

Section summary: The writes were real and sometimes heavy. How bad they were depended a lot on the individual PC.

How to check whether your PC is affected​

You can check in a couple of minutes with tools built into Windows. PC Gamer described this method:

  • Open Task Manager (Ctrl+Shift+Esc).
  • Go to the Details tab.
  • Right-click any column header and choose Select columns.
  • Turn on I/O write bytes.
  • Find NVDisplay.Container.exe and watch the number while the PC is idle.

If that number climbs quickly while you aren't doing anything, that's a strong clue. It isn't proof. Task Manager shows how much the process asked to write, not how much the SSD actually stored. In Tom's Hardware's example, 515 MB of process I/O lined up with only 270 MB of total C: drive writes over the same five minutes. To check the drive itself:

  • Use Resource Monitor or Windows performance counters to see total disk writes.
  • Compare the SSD's SMART Data Units Written value before and after an idle period, using CrystalDiskInfo or your drive maker's SSD utility.

Your options, ranked​

OptionWho it suitsTrade-off
Install Hotfix 621.35You're on 621.14 or 621.24 and see heavy writesBeta driver with less testing
Roll back to 621.01You want a WHQL-certified driver nowYou lose any changes made after 621.01
Wait for the next WHQL driverYou don't see the problemNone, if you're not affected
Temporarily stop NVIDIA Display Container LSEmergency stopgap onlyMay break Control Panel/NVIDIA App features

Coverage of the fix generally agreed: anyone affected should get the hotfix as soon as possible, while others can wait for the next WHQL release. Before the hotfix came out, workarounds included rolling back to 621.01 or temporarily stopping the NVIDIA Display Container LS service. NVIDIA lists 621.01 as a WHQL-certified driver released October 21, 2026, for 64-bit Windows 10 and Windows 11.

Treat the service workaround as a temporary measure. That service supports the NVIDIA Control Panel and NVIDIA App, so leaving it disabled may break features you use. One guide puts it this way: with Hotfix 621.35 available, it is better to install the hotfix and leave the service set to Automatic. PC Gamer also mentioned a registry workaround. It isn't NVIDIA's fix, and it shouldn't be needed now that a real fix is out.

The hotfix trade-off​

POPTOPIC's main point holds: a newer driver isn't automatically the safer one. NVIDIA describes hotfix drivers as beta, optional and provided as-is. Their fixes are rolled into the next official driver, and the hotfix is taken down when that driver ships. NVIDIA's own advice is that the safest option is to wait for the next WHQL-certified driver.

Some practical points:

  • It won't show up as an automatic update. Guru3D warns that users searching the NVIDIA App for an update may not see 621.35 offered there. Neowin adds that only manual installation is supported on hotfix drivers.
  • Downloads cover 64-bit Windows 10 and 11. POPTOPIC reports that NVIDIA's announcement includes a direct download for both. Get it from NVIDIA's Customer Care page, not a mirror you don't recognize.
  • There's no date for the next official driver. NVIDIA will include this fix in the next WHQL driver, but it hasn't said when that driver will ship.

The bigger picture: AMD had the same problem​

NVIDIA wasn't alone this month. Earlier this month, AMD released Adrenalin Edition 26.11.1, which, among other things, fixed the exact same bug. Both major GPU makers shipped drivers that wrote unnecessary data in the background, and in both cases users caught it before the companies did. That raises a fair question: why don't driver test suites check for unusual disk writes at idle?

NTCompatible noted that NVIDIA's 621.24 release notes listed no open issues. For anyone managing a fleet of PCs, the lesson is simple: test new GPU drivers on a few machines before rolling them out everywhere, and watch idle disk writes along with frame rates.

Bottom line​

If you're on GeForce 621.14 or 621.24, spend two minutes in Task Manager. If NVDisplay.Container.exe is writing heavily while the PC is idle, install Hotfix 621.35 from NVIDIA's support site, or roll back to 621.01 if you'd rather stay on a WHQL-certified driver. If the counter stays quiet, you can wait for the next WHQL release. Either way, a graphics driver's log file shouldn't be the busiest thing on your SSD.


Update: User reports writes returning after hotfix (November 22, 2026)​

According to Wccftech’s November 22 report, one Reddit user observed excessive writes returning after installing Hotfix 621.35. On a Windows 11 PC with an RTX 4090, the user reported just 90.8 KB of process writes in the first hour, followed by 40.85 GB over nine hours of overnight idle.

The SSD’s SMART counter rose by 36 GB during that period, though that drive-wide figure cannot be attributed entirely to NVIDIA’s process. The report concerns one configuration, not a controlled test, so it does not establish how widely the hotfix might be affected.

For users who experienced the original issue, the report is a reason to monitor writes over a longer idle period after installing the hotfix. If heavy writes persist, rolling back to 621.01 remains an option.

 

References

  1. NVIDIA’s SSD Write Fix Takes the Hotfix Route - POPTOPIC POPTOPIC 2026-11-21T22:15:13+00:00
  2. NVIDIA GeForce Hotfix 621.35 Targets Excessive SSD Writes, but One User Reports Recurrence wisevoter.com
  3. NVIDIA GeForce Hotfix 621.35 Fixes SSD Writes » TalkEsport talkesport.com