Tom’s Hardware reported 515 MB of process I/O and 270 MB of total C: drive writes during a five-minute test of GeForce driver 621.14. The figures describe different counters. Separate reports about driver 621.24 came from individual users, not the same test.
Check which process is writing, then compare that activity with the drive’s own write counter. They measure different things.
What the 621.14 test measured
Tom’s Hardware identified NVDisplay.Container.exe and the log file nvlog.nvlgstg in reports of repeated writes while a PC was idle. In its five-minute 621.14 test, the outlet recorded 515 MB of I/O attributed to the process and 270 MB of total writes to the C: drive. The process figure is not the amount written to the drive; those measurements should be kept separate.
Tom’s Hardware used Windows Resource Monitor, Windows performance counters and CrystalDiskInfo for its test. The SSD’s SMART “Data Units Written” counter matched Windows’ drive-level reporting in that measurement.
What users reported about driver 621.24
One user quoted by Tom’s Hardware estimated about 30 GB per hour on 621.24, and 70 GB or more in longer sessions. The same user also reported an additional 500 MB to 1 GB with each Alt+Tab. These were individual estimates, not standardized measurements.
How to check for the reported activity in Windows
Open Resource Monitor by running resmon, select Disk, and watch for NVDisplay.Container.exe and nvlog.nvlgstg while the PC is idle. Task Manager offers another process-level view: in its Details tab, add the I/O Write Bytes column and look for activity from the same process. To check writes recorded by the drive itself, compare its SMART “Data Units Written” counter in CrystalDiskInfo or the SSD maker’s utility.
Tom’s Hardware reported fewer than 2 MB of writes per five minutes for driver 621.01 in its comparison, and described rolling back to that version as a reported workaround. A Tech Based screencast also demonstrates checking Windows activity, rolling back a driver and setting nvlog.nvlgstg to read-only as a temporary workaround.
Tom’s Hardware reported that the NVIDIA Display Container LS service supports NVIDIA Control Panel and NVIDIA App, so stopping the service can affect those functions.