One reported test suggests excessive background writes persisted on a PC running Nvidia’s GeForce 621.35 hotfix: the idle system recorded about 36GB of SSD host writes over nine hours. Not the overnight shift anyone ordered from a graphics driver. Source Source
The update was released to address excessive writes, according to Neowin and Wccftech. Both outlets cover the same underlying test, not independent replications. Neowin identifies the tester as its reviewer Robbie Khan, whose setup included Windows 11 26H2, an RTX 4090 and a Samsung 990 PRO 2TB SSD. Source Source
A quiet first hour, then gigabytes overnight
After installing 621.35, Khan reportedly recorded just 90.8KB of additional writes from the Nvidia process NVDisplay.Container.exe during the first hour. Source Source
Over a subsequent nine-hour idle period, with the monitor entering standby, Khan reportedly recorded:
- 40.85GB of additional process I/O writes attributed to NVDisplay.Container.exe.
- About 36GB more SSD host writes, recorded through the drive’s SMART counters in HWiNFO64. Source Source
The first counter measures the process’s software write activity, which doesn’t translate directly into bytes written to the SSD. The second measures writes sent to the SSD from across the system, so it doesn’t show that NVDisplay.Container.exe caused all 36GB of the increase. Neither figure demonstrates data loss or SSD damage. Source Source
Both outlets interpret the results as reduced excessive-write activity compared with driver 621.24, rather than its elimination on this system. Extended uptime and display standby were part of the test conditions; that doesn’t establish either as the trigger. Source Source
Nvidia reportedly wants the logs
Japanese site NichePCGamer reports that some users describe the issue as resolved after updating, while others say it persists. According to the site’s account of Nvidia’s forum response, continued writes to the nvlog.nvlgstg file could reflect repeated errors caused by another factor on the PC. Source
The site also reports that Nvidia is asking affected users to share that log file and send its link, along with their graphics-card model, to driverfeedback@nvidia.com. Source
Khan reportedly saw much lower process-write activity after returning to driver 621.01: 12.55MB over 55 minutes, followed by mostly inactive behavior during further desktop and media use. That’s a reported workaround on his machine, not evidence that everyone should roll back or that the older driver is universally trouble-free. Source
For GeForce owners checking their own systems, NichePCGamer points to Windows Resource Monitor’s Disk tab to inspect NVDisplay.Container.exe’s writes to nvlog.nvlgstg. The useful check is what the process actually does over time—not whether the installer successfully delivered a version number with “hotfix” attached. Source
Comments