Nvidia Hotfix 621.35 Fixes the SSD Write Bug: Should You Install It or Wait?

Technogater news card: Nvidia hotfix driver 621.35 targets the GeForce SSD write bug

By Robert Shakir, AI & Digital Marketing Consultant · Published November 21, 2026 · Facts checked against NVIDIA’s support page and press coverage on November 21, 2026

NVIDIA has finally owned up to the bug that had GeForce drivers rewriting a log file on loop and piling gigabytes of extra writes onto people’s SSDs. On November 20 the company posted GeForce Hotfix Display Driver 621.35 on its Customer Care site. It lists exactly one change: “Excessive writes to file nvlog.nvlgstg may occur in background”, logged internally as bug 7116722. That’s the same file users had flagged on drivers 621.14 and 621.24, which I covered yesterday in how to check whether the NVIDIA driver is hammering your SSD.

This is a news analysis based on NVIDIA’s hotfix notes and coverage from Notebookcheck and Neowin. I haven’t installed 621.35 on my own PC for this piece.

What NVIDIA actually released

The hotfix is built on top of the current Game Ready driver, 621.24, with that single targeted fix added. It’s for Windows 10 and Windows 11 (64-bit) and is only offered as a manual download from NVIDIA’s support portal, so the NVIDIA App won’t push it to you automatically. NVIDIA is upfront about the trade-off. In its own words, hotfix drivers are beta, optional and provided as-is, they go through a much shorter QA process, and the safest option is to wait for the next WHQL-certified driver. Once the fix is folded into the next official release, the hotfix gets taken down.

There’s one loose end. Neowin reports that an NVIDIA staff member said on the company forums that RTX 50-series cards aren’t affected, while several users replied that their RTX 50 machines did show the heavy writes. Until NVIDIA clears that up, I’d treat every GeForce PC on 621.14 or 621.24 as possibly affected and check it rather than trust the card model.

Your driver options right now

DriverStatusIdle SSD writesMain catch
621.01Older WHQL releaseNormal, per user testsLoses newer game updates; Notebookcheck notes video playback freezes and black screens on some RTX 50 cards
621.14 (Nov 4)WHQLHeavy writes reportedWhere the bug started
621.24 (Nov 12)Current WHQLHeavy writes reportedStill the default download for most people
621.35 hotfix (Nov 20)Beta, optionalFix targets the log fileShorter QA; manual install only
Next Game Ready driverNot out yet, no date givenExpected to include the fixYou wait, and the writes continue meanwhile

NVIDIA hasn’t published a release date for the next certified driver, so I can’t tell you how long the wait is.

Who should install the hotfix, and who should wait

  • You checked and you’re affected, and the PC stays on most of the day: install 621.35. Every day on 621.24 adds avoidable wear, and the hotfix is the same driver with one change, which keeps the risk low.
  • You’re affected but only game a few hours a week: either works. If you’d rather stay on certified drivers, stopping the “NVIDIA Display Container LS” service between sessions limits the damage until the next WHQL release, though Notebookcheck notes that’s only temporary relief.
  • You rolled back to 621.01 and it’s stable: stay put unless you hit the RTX 50 playback problems or need a newer game profile. There’s no rush to go back to beta.
  • Small offices with several GeForce workstations: try the hotfix on one machine, measure for a day, then decide. Don’t push beta drivers across a whole office in one go.
  • Not sure if you’re affected: check first. The Task Manager steps in yesterday’s guide take about ten minutes, and if the NVDisplay.Container.exe write counter barely moves, you don’t need to do anything.

How to install it cleanly

Download the hotfix from NVIDIA’s support page, run the installer, choose Custom and tick “Perform a clean installation”. Then repeat the check: note the write counter for NVDisplay.Container.exe, leave the PC idle for ten minutes, and look again. If it’s climbed by hundreds of megabytes, the fix hasn’t taken, and rolling back to 621.01 is still the reliable fallback. Deleting the log file on its own doesn’t solve anything, since it grows back.

How this compares with AMD

AMD hit a very similar bug this month, with its External Events Utility writing to the system drive at idle. According to Notebookcheck, AMD shipped a fix for RX 7000-series cards and newer in Adrenalin 26.11.1 on November 12, then extended it to older Radeon cards on Windows 10 on November 18. NVIDIA’s hotfix arrived 16 days after 621.14 shipped, and it’s still a beta. So AMD moved faster this time, but both companies let a driver ship that quietly wore down drives. Shopping for a gaming or creator laptop? I wouldn’t pick a GPU brand over this. Both are fixable in software, and the things that last longer, like RAM, screen and battery, matter more. My guides to the best laptops under $1,000 and gaming laptops under $2,000 cover what to weigh instead.

What it means for your SSD

A week or two of this is no reason to panic. A typical 1 TB SSD is rated for around 600 TB written. Even the worst user figure, about 30 GB an hour, adds up to roughly 10 TB over two weeks of running nonstop, under 2% of that rating. You can see your own drive’s total in its maker’s tool, such as Samsung Magician or Crucial Storage Executive, or in CrystalDiskInfo. A high health reading means you’ve lost a little lifespan, not the drive.

Robert’s take

“I’m glad NVIDIA named the file and the bug number instead of staying vague, but shipping the fix as a beta that most people will never see isn’t enough. Most GeForce owners don’t read support pages. They let the NVIDIA App update them, and the hotfix isn’t offered there. For a business, my advice hasn’t changed: test one machine first, then roll out. If you’ve been checking your PCs since this broke, the hotfix is worth it today.” Robert Shakir, AI & Digital Marketing Consultant

Sources

Related Posts