Skip to content
PC Platform News

NVIDIA issues out-of-band GeForce hotfix 621.35 to stop excessive SSD writes

User reports put affected drivers' SSD writes at as much as 30 gigabytes each hour.

https://quarterstack.online/pc-platform/nvidia-geforce-hotfix-621-35-ssd-writes/

Share

NVIDIA released GeForce Hotfix Driver 621.35 on November 20, 2026 as an out-of-band update, a fix issued outside the normal release schedule, for Windows 10 and Windows 11 to stop excessive background writes that can wear out solid-state drives.

The problem involved the NVIDIA Display Container service, which repeatedly rewrote the entire nvlog.nvlgstg log file in ProgramData instead of appending new entries to the existing file. A solid-state drive, or SSD, stores data on flash memory chips rather than on spinning disks.

User reports indicate affected drivers produced as much as 30 gigabytes of writes to an SSD each hour.

SSDs have finite write endurance, so excessive background writes can cut a drive’s lifespan significantly over several years, especially when a computer remains powered on around the clock. NVIDIA’s acknowledgment confirms the excessive logging issue was indeed a driver bug. NVIDIA’s release notes state: “Excessive writes to file nvlog.nvlgstg may occur in background.”

The company calls hotfix drivers optional betas with abbreviated testing, which lets it issue fixes faster using customer feedback. The hotfix builds on the latest Game Ready WHQL driver, version 621.24, and targets the issue under NVIDIA bug reference 7116722. Users may bypass the beta hotfix and wait for the upcoming Game Ready driver containing the same correction.

AMD released optional non-WHQL Adrenalin Edition 26.11.1 on November 12 to address excessive system drive writes, with its External Events Utility service writing up to 5 megabytes per second to SSDs continuously on affected machines. The two storage bugs have different root causes and are not correlated, although attention to AMD’s problem may have sped up discovery of NVIDIA’s issue. Users can check for the bug by opening Windows Resource Monitor and looking for NVDisplay.Container.exe producing noticeably high active writes in bytes per second.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *