kaganerkan pixel logo

kaganerkan

News · Nov 21, 2026

NVIDIA GeForce Hotfix 621.35 Targets Excessive Background Disk Writes

NVIDIA says GeForce Hotfix Driver 621.35 fixes an issue that can cause excessive background writes to nvlog.nvlgstg. NVIDIA Customer Care announced the hotfix at 22:01 UTC on November 20, 2026 (01:01 on November 21 in Istanbul).

The filename matters if you are troubleshooting a busy drive. A spike in overall disk activity does not tell you which file is being written, and finding nvlog.nvlgstg on disk does not tell you how often it is being written. NVIDIA’s announcement does not give a write-rate threshold.

How to check which file Windows is writing

  1. Press Windows + R, type resmon, and press Enter to open Resource Monitor.
  2. Select the Disk tab and expand Disk Activity. With the computer otherwise idle, sort by Write (B/sec), highest first. Use the File column to look for a path ending in nvlog.nvlgstg.
  3. Watch over several refreshes. If another file accounts for the writes, the activity you are seeing is not the symptom NVIDIA describes. If nvlog.nvlgstg keeps appearing, note its write rate and your driver version. A single write is not enough to establish a pattern.

Why a log that stays small can still be busy

Consider two successful writes of 4,096 bytes to offset zero in the same file. The second overwrites the first: the two requests account for 8,192 bytes of write activity, but the file need not grow at all on the second write. Checking its size in Explorer misses that distinction. Conversely, a busy disk can be writing an entirely different file. Count operations and bytes for the named log, not changes in its size or the disk’s overall active time.

Our five-row example capture makes the distinction testable. It contains those two writes, a read of the same log, a larger write to another file, and a failed attempt to write the log. Run the local CSV counter with Python 3: python count-nvlog-writes.py nvlog-synthetic.csv. The result is 2 successful writes; 8,192 recorded bytes. The example is synthetic, not a GeForce trace. Even the right file’s recorded write lengths are not a measurement of physical SSD wear.

A before-and-after test you can repeat

  1. Record the installed driver version and the full log path from Resource Monitor. Open Microsoft Process Monitor, stop capture, clear existing events, enable file-system events and add an Include filter for that exact path. Don’t filter by process name: a different writer is worth noticing.
  2. Pick a repeatable condition. For an idle check, reboot, sign in, wait five minutes, and leave the same applications open. Capture exactly 60 seconds, stop, then save the displayed events as CSV with the English Path, Operation, Result and Detail columns. Clear events and repeat twice. Keep the three runs separate; a single periodic burst can dominate a short sample.
  3. Run the counter on each CSV. Record driver version, run length, successful writes and recorded bytes. Keep captures local; raw traces can contain usernames and unrelated file paths. If you choose to update, check applicability through NVIDIA’s support link, then repeat the same reboot, wait and three capture windows on 621.35. No need to downgrade a working driver just to create a baseline.

How to read the six runs: If each after-run records fewer bytes than even the quietest before-run, that supports a reduction on this PC under the tested conditions. If the ranges overlap, show the ranges rather than claiming a percentage fix; try longer matched windows. If writes were absent before the update, you didn’t reproduce the symptom. If the log quiets down but the disk stays busy, return to Resource Monitor and identify the new top path. Those are four different outcomes, not four versions of “fixed.”

Primary sources

Compiled with AI assistance from NVIDIA Customer Care’s announcement. The fix is NVIDIA’s claim; no independent driver testing or disk-write measurements are reported.