← Tech
💻Tech

NVIDIA Hotfix 621.35: How to Check and Fix nvlog.nvlgstg SSD Writes

Optional GeForce Hotfix 621.35 (20 Nov 2026) fixes excessive background writes to nvlog.nvlgstg. How to check Resource Monitor, install the hotfix, clean the log, and roll back.

TL;DR: NVIDIA's optional GeForce Hotfix Display Driver 621.35, posted 20 November 2026, fixes one issue: excessive background writes to the file nvlog.nvlgstg (bug 7116722). The hotfix is based on Game Ready Driver 621.24. Community reports tie the heavy writes to NVDisplay.Container.exe (the NVIDIA Display Container LS service) on 621.14 and 621.24, with some idle PCs showing far higher write activity than on 621.01. To check, open Resource Monitor → Disk, look for sustained writes from that process, and check the size of nvlog.nvlgstg. Then install 621.35 from NVIDIA's Customer Care page — it is not a WHQL Game Ready drop, and NVIDIA says the safest option is to wait for the next certified driver. After installing, confirm the write rate drops, then you can clear a leftover oversized log. This is a different bug from Hotfix 621.12 (RTX 50 video freezes) and from the AMD Adrenalin idle-SSD-write fix.

Last checked: 22 November 2026 (KST).

Close-up of an NVIDIA GeForce RTX 4090 Founders Edition graphics card, used here only as a general GeForce hardware illustration. GeForce Hotfix 621.35 is a Windows 10/11 x64 driver fix and is not limited to this model.

Photo: NVIDIA RTX 4090 Founders Edition close-up by ZMASLO, via Wikimedia Commons, CC BY 3.0. No changes were made other than display sizing. The hotfix is not limited to the RTX 4090.

What 621.35 actually fixes

NVIDIA's Customer Care page for 621.35, updated 20 November 2026, lists a single fix:

Excessive writes to file nvlog.nvlgstg may occur in background [7116722]

The same page says the hotfix is "based on our latest GeForce Game Ready Driver." In the GeForce Forums announcement, NVIDIA staff specify that base version as 621.24, and offer a Windows 10 / Windows 11 64-bit DCH package.

A GeForce hotfix is not the same as a full Game Ready WHQL driver. NVIDIA's own wording is that these builds are beta, optional and provided as-is, go through "a much abbreviated QA process," are offered only through the Customer Care site, and will be taken down once the fixes land in the next official driver. NVIDIA also says the safest option is to wait for the next WHQL certified driver.

This is not a fix for the RTX 50 video-freeze and black-screen issue covered in our 621.12 install and rollback guide. That earlier hotfix was about playback after 621.01. Game Ready 621.14 already listed that video-playback fix in its official changelog. 621.35's published changelog adds only the nvlog.nvlgstg write fix.

How we got here

Driver Type Date What is confirmed about SSD writes
621.01 Game Ready WHQL 21 Oct 2026 Used as the clean comparison in later reporting. Idle tests cited by TechPowerUp and Notebookcheck show under about 2 MB in a 5-minute idle window. This release also introduced the separate RTX 50 video-freeze bug later fixed in 621.12 / 621.14.
621.12 Optional hotfix 27 Oct 2026 Fixes video freezes and black screens on some RTX 50 / RTX Spark systems after 621.01, plus a few unrelated issues. It is not an SSD-write patch. See our 621.12 guide.
621.14 Game Ready WHQL 4 Nov 2026 Official NVIDIA driver page: released 4 November 2026. Community reporting, including TroubleGrid and Notebookcheck, traces the heavier nvlog.nvlgstg writes to this release. Officially, this WHQL build also includes the 621.01 video-playback fix.
621.24 Game Ready WHQL 12 Nov 2026 Official driver details and release notes: 12 November 2026. Still reported affected. The highest widely cited user estimate is about 30 GB per hour on this build. 621.35 is based on this driver.
621.35 Optional hotfix 20 Nov 2026 Official fix for excessive background writes to nvlog.nvlgstg [7116722]. Windows 10 / 11 x64 only, as published.

NVIDIA has acknowledged the write issue as bug 7116722 and shipped 621.35. It has not published its own write-rate measurements, an affected-GPU list, or a date for the next WHQL package that will include the same fix.

Who should install it

  • You're on 621.14 or 621.24 and you can see sustained writes from NVDisplay.Container.exe: this is the official patch. Install 621.35.
  • You're on those drivers and haven't checked yet: run the check below first. XDA and other reports note that some people on the same driver versions saw no unusual activity, so it is not established that every PC is affected.
  • You already rolled back to 621.01 and it's stable: you can stay there for now and wait for the next official Game Ready driver. You do not have to move to a non-WHQL hotfix just to pick up this fix later.
  • You're on an older driver and happy with it: there's no reason to jump to 621.35 only for this.
  • You'd rather not run a shortened-QA hotfix: NVIDIA's own advice is to wait for the next WHQL driver.

How to check if you're affected

Do this while the PC is idle, before you update, so you have a baseline. Repeat the same steps after installing 621.35.

1. Confirm your driver version

In NVIDIA Control Panel, open Help → System Information (or System Information from the main window) and read the driver version. You can also run nvidia-smi in a terminal and look at Driver Version. You want to know whether you are on 621.14, 621.24, 621.35, 621.01, or something else.

2. Watch the process in Resource Monitor

  1. Close games, browsers and anything else that would reasonably be writing to disk. Let the machine sit idle for a couple of minutes.
  2. Press Win + R, type resmon, and press Enter.
  3. Open the Disk tab.
  4. In Processes with Disk Activity, sort by Write (B/sec).
  5. Look for NVDisplay.Container.exe. On an affected PC, reports describe a steady stream of writes that does not die down at idle, rather than occasional small spikes.
  6. In the Disk Activity pane, check the File column. Community write-ups from TroubleGrid, Guru3D, and XDA identify the target as:
C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg

NVIDIA's changelog names the file, nvlog.nvlgstg, but not this full path. The path above is what those reports and Resource Monitor traces show. C:\ProgramData is a hidden folder; if Explorer doesn't show it, paste the path into the address bar, or use the PowerShell check below.

You can also use Task Manager → Details, right-click the column headers, enable I/O write bytes, and watch NVDisplay.Container.exe for several minutes. That counter is cumulative since the process started, so a large total after many hours is less useful than the change between two readings on an idle PC.

3. Check the log file size

In PowerShell:

Get-Item "$env:ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg" |
  Select-Object FullName, Length, LastWriteTime

A file that already exists is not, by itself, proof of the bug — the service is supposed to keep a log. What matters is sustained rewrite activity in Resource Monitor, and a file whose size and timestamp keep changing while the PC is idle. Several reports describe the file being truncated and rewritten, rather than simply appended to, which is why the write volume can grow as the log itself grows. That mechanism comes from community reporting (TroubleGrid, Guru3D, XDA), not from NVIDIA's one-line changelog.

User-reported write rates — and what they don't prove

NVIDIA has not published official rates. The figures below are individual user measurements relayed by tech outlets. They are not averages, and they are not a claim that every 621.14 or 621.24 install writes at these speeds.

User-reported idle write rates for NVIDIA drivers 621.01, 621.14 and 621.24 Log-scale bar chart of user-reported idle write rates, not official NVIDIA measurements. 621.01 is under 2 MB per 5 minutes, about 0.024 GB per hour. One 621.14 report is 515 MB per 5 minutes, about 6.18 GB per hour. Another 621.14 report is over 3 GB in 10 minutes, about 18 GB per hour. One 621.24 estimate is about 30 GB per hour. User-reported idle write rates (not NVIDIA official measurements) Approximate GB/hour, converted from the original reported windows. Log scale. 0.01 0.1 1 10 40 Approximate GB written per idle hour (log scale) 621.01 <2 MB / 5 min 621.14 A 515 MB / 5 min 621.14 B >3 GB / 10 min 621.24 ~30 GB / hour Sources: Notebookcheck, TechPowerUp, TroubleGrid, Guru3D. Process write counters may not equal physical NAND writes.
Driver Original reported figure Approx. GB/hour (converted) Source
621.01 (clean-install comparison) Under ~2 MB in 5 minutes idle ~0.024 TechPowerUp, Notebookcheck, TroubleGrid
621.14 (one report) 515 MB in 5 minutes idle ~6.2 Notebookcheck, TroubleGrid
621.14 (another report) Over 3 GB in 10 minutes ~18 Notebookcheck
621.24 (one estimate) About 30 GB per hour ~30 TechPowerUp, Notebookcheck, Guru3D

Treat those conversions as a way to put different time windows on one chart, not as laboratory results. Notebookcheck and Guru3D both warn that Windows process write counters may not equal bytes physically written to NAND, because of caching, the file system, and the SSD controller. Guru3D also notes that the reports have not established measurable drive wear, or how commonly the issue occurs. One XDA account said SMART totals on that author's drive lined up with what Windows showed; that is still one user's observation, not an official finding.

In short: check your own PC, install the official hotfix if you are affected, and don't treat the highest 30 GB/hour figure as a guaranteed rate.

How to install 621.35

NVIDIA says it only provides hotfix drivers through the Customer Care support site. Do not expect this build to show up as a normal NVIDIA App or Windows Update Game Ready drop.

  1. Download GeForce Hotfix Display Driver 621.35 for Windows 10 / Windows 11 (x64) from NVIDIA's 621.35 Customer Care page. The forums announcement also points to NVIDIA's official international.download.nvidia.com package for the same 64-bit DCH build.
  2. Close games, browsers, overlay software and anything else using the GPU.
  3. Run the installer and accept the license.
  4. Choose Custom (Advanced). If you want a clean slate, tick Perform a clean installation — this resets NVIDIA Control Panel and NVIDIA App settings to defaults, so note any per-game profiles first. A standard custom install is enough if you only want the hotfix applied on top of your current settings.
  5. Finish the install, let the screen flicker, and reboot when asked.
  6. Confirm the version is 621.35 in NVIDIA Control Panel or nvidia-smi.

If you previously stopped or disabled NVIDIA Display Container LS as a workaround, set that service back to Automatic and start it after the hotfix is in place. Disabling it for good can prevent the NVIDIA Control Panel and NVIDIA App from opening, which is why outlets treated that only as a temporary workaround, not a lasting fix.

Confirm the writes stopped, then clean leftover logs

  1. Let the PC sit idle for several minutes.
  2. Repeat the Resource Monitor check. After a successful fix, NVDisplay.Container.exe should no longer show a sustained write stream to nvlog.nvlgstg. Occasional small writes can still be normal logging. Independent before-and-after measurements on 621.35 were still limited as of 22 November 2026, so this check is worth doing rather than assuming the installer finished the job.
  3. Recheck the log file's size and LastWriteTime.

If a large leftover nvlog.nvlgstg is still sitting on the drive and Resource Monitor is now quiet, you can delete that leftover file:

  1. Press Win + R, type services.msc, and press Enter.
  2. Find NVIDIA Display Container LS.
  3. Right-click → Stop.
  4. Delete nvlog.nvlgstg from C:\ProgramData\NVIDIA Corporation\nvtopps\nct\ (or the path Resource Monitor showed on your PC).
  5. Start the service again, and leave its startup type set to Automatic.

Do not use deletion as a substitute for the hotfix. Before 621.35, stopping the service and deleting the log only helped temporarily; reports said the file and the writes came back. And if writes continue after 621.35, don't just keep deleting the file. On 21 November 2026, NVIDIA staff on the hotfix forum thread said that leftover writes may mean something else on the PC is triggering a repeated error. They asked users to zip nvlog.nvlgstg, upload it to a file-sharing service, and send the download URL to driverfeedback@nvidia.com, along with the graphics card model.

Rollback notes

  • Waiting is still a valid path. If 621.35 feels too early, stay on a driver that is not writing heavily — or on 621.01 if that is already stable — and wait for the next official Game Ready driver. NVIDIA says the hotfix will be pulled once those fixes ship in the official release.
  • If 621.35 causes a new problem, roll back. In Device Manager, under Display adapters, open your NVIDIA GPU → Properties → Driver → Roll Back Driver if that button is available. If it isn't, download the previous WHQL package you want (for example 621.24, 621.14, or 621.01) from NVIDIA and install it, or use Display Driver Uninstaller (DDU) in Windows Safe Mode for a cleaner revert. The same DDU caution from our 621.12 guide applies: use the official DDU build, and don't mix this with unpaid or unofficial driver packages.
  • Rolling back to 621.01 to avoid the writes is the old workaround, not the first choice now. TechPowerUp and Notebookcheck both described 621.01 as the reliable pre-hotfix escape. The catch is that 621.01 is also the driver that caused video playback freezes and black screens on some RTX 50 Series GPUs and RTX Spark systems. That is the bug Hotfix 621.12 and later 621.14 were meant to close. Going back to 621.01 can reopen that risk on those systems. 621.35 is the path that keeps you on the 621.24 line and adds the log-write fix.
  • Don't leave NVIDIA Display Container LS disabled as a long-term workaround. It is only a stopgap, and it can break the Control Panel and NVIDIA App.

Related Terapep guides

FAQ

Is 621.35 a WHQL Game Ready driver?

No. It is an optional beta hotfix with a shortened QA pass, based on WHQL Game Ready 621.24. NVIDIA says the safest option is to wait for the next certified driver, which should include this fix.

Will the NVIDIA App offer this update?

NVIDIA says hotfix drivers are provided only through the Customer Care site. Use the official 621.35 page.

Does this also fix the RTX 50 video freeze from 621.01?

That video issue is not listed in the 621.35 changelog. It was already listed as fixed in Game Ready 621.14, and 621.35 is based on the later 621.24 WHQL build. If your only problem is the log-file writes, 621.35 is the patch for that. If you are still on 621.01 because of some other reason, read the 621.12 guide before rolling forward or back.

Is this the same bug AMD just patched?

No. AMD's optional Adrenalin 26.11.1 driver fixed excessive system-drive writes at idle on some Radeon systems, typically traced to atieclxx.exe. NVIDIA's issue is NVDisplay.Container.exe writing nvlog.nvlgstg. They showed up around the same time, but they are separate vendor bugs. See our AMD 26.11.1 check-and-update guide.

Should I worry that my SSD is already worn out?

Not from the published evidence. The high write figures are user reports, and process-level write totals are not automatically the same as NAND wear. If you want a reality check, compare your drive's SMART total bytes written (or TBW used) in the manufacturer's tool with the drive's rated endurance — but don't assume the worst-case 30 GB/hour story happened on your PC unless your own logs show it.

Sources

#nvidia#geforce#hotfix-driver#621-35#ssd#nvdisplay#nvlog#how-to#2026

← Back to all posts