Skip to content

NewsSSD

NVIDIA GeForce Drivers 621.14 and 621.24 Reportedly Hammer SSDs With Idle Writes: How to Check Your PC

Users report that GeForce drivers 621.14 and 621.24 make NVDisplay.Container.exe keep rewriting a log file on the system SSD while the PC is idle, with claims of up to 30GB an hour. NVIDIA hasn't acknowledged it. Check Resource Monitor's Disk tab; rolling back to 621.01 is the reported workaround, but RTX 50 owners should note its video playback bug.

By , Editorial team

4 min read

NVIDIA GeForce Drivers 621.14 and 621.24 Reportedly Hammer SSDs With Idle Writes: How to Check Your PC

Days after AMD fixed a Radeon driver utility that kept writing to people's SSDs, NVIDIA owners are reporting a similar problem. According to posts on NVIDIA's own driver feedback threads, picked up by Tom's Hardware on 18 November 2026 and since covered by Windows Latest and Guru3D, GeForce drivers 621.14 and 621.24 can make a background service rewrite a log file on the system drive over and over while the PC sits idle. This article is based on those reports and NVIDIA's release notes; Forge PC hasn't reproduced the problem on its own systems, and NVIDIA had not commented at the time of writing.

What's being reported

The writes come from NVDisplay.Container.exe, the process behind the NVIDIA Display Container LS service, which the NVIDIA Control Panel and NVIDIA App need to work. Users say it repeatedly rewrites a binary log file at:

C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg

The figures shared so far vary a lot from PC to PC:

Driver

Reported idle writes

Source of the figure

621.01

Under 2MB in five minutes

Forum user, via Tom's Hardware and Guru3D

621.14

515MB of process writes in five minutes, 270MB actually reaching the C: drive

Forum user, via Tom's Hardware

621.24 (12 November 2026)

"About 30gb per 1h", and 70GB or more in long sessions

Forum user, via Tom's Hardware and Windows Latest

Tom's Hardware notes that the first user checked the drive's SMART "Data Units Written" counter, which matched what Windows reported, so these are real writes rather than just a busy process counter. The same reports say the write volume grows as the log file grows, and the user on 621.24 said this happened with telemetry turned off in the NVIDIA App. Not every PC seems to be affected: Windows Latest says several Reddit users on these drivers see nothing unusual.

Guru3D stresses that these are user reports, not an NVIDIA-confirmed defect, and that host writes aren't the same as NAND wear, because SSD controllers merge and cache small writes. That's a fair caution.

How much does it matter for your SSD?

It's unlikely to kill a drive overnight, but it's wear you get nothing for. Tom's Hardware worked out that the lower 270MB-per-five-minutes figure comes to roughly 28TB a year on a PC that never sleeps, close to 5% of the 600TB endurance rating typical of a 1TB SSD. Windows Latest adds that the higher reported rate of 30GB an hour, for eight hours a day, works out to about 15% of that rating a year.

Guru3D notes that this matters most for drives with low endurance ratings, particularly QLC models. Our TLC vs QLC SSD guide explains the difference, and with UK SSD prices as high as they are, nobody wants to burn through endurance for nothing.

How to check if your PC is affected

Both Tom's Hardware and Windows Latest suggest the same checks:

  1. Press Win + R, type resmon and press Enter to open Resource Monitor.

  2. Open the Disk tab and sort Disk Activity by Write (B/sec).

  3. Leave the PC idle for a few minutes and look for NVDisplay.Container.exe writing to nvlog.nvlgstg again and again.

  4. For writes that actually reach the drive, note the Host Writes or Data Units Written value in CrystalDiskInfo or your SSD maker's app, leave the PC idle for an hour and compare. Our guide to checking SSD health shows where to find these numbers.

What you can do now

There's no official fix yet. NVIDIA's release notes for 621.24 don't list the problem as an open issue, and no hotfix had been announced at the time of writing. The options users have reported are:

  • Roll back to 621.01. This is the workaround most often suggested, and a second user in NVIDIA's forum thread said it helped. Guru3D says it's not guaranteed to work. See how to roll back a graphics driver.

  • Know the RTX 50 catch. Windows Latest points out that 621.01 is the driver NVIDIA had to patch for video freezes and black screens on RTX 50 GPUs, quoting NVIDIA's release notes as saying video playback "may freeze or black screen" after 621.01. So RTX 50 owners who roll back may swap one bug for another.

  • Clean reinstalls don't seem to help. One user tried three clean reinstalls with DDU on 621.24 without success. Our DDU guide is still the right method if you do roll back.

  • Deleting the log file is only temporary. Stopping the service, deleting nvlog.nvlgstg and restarting the service cut the writes by about 91% for one user, according to Windows Latest, but the file then grew again.

  • Disabling the service stops the writes, but you lose the NVIDIA Control Panel and NVIDIA App while it's off, so we wouldn't recommend that for most people.

If you're not affected when you check, there's no need to change anything. Keep an eye on NVIDIA's next driver release notes; our guide to updating graphics drivers covers the usual ways to install it.

How this compares with AMD's bug

AMD's problem, covered in our Radeon driver SSD writes story, came from its External Events Utility (atieclxx.exe). Windows Latest says AMD fixed it in the optional Adrenalin 26.11.1 driver on 12 November, covering Radeon RX 7000 cards and newer, and Guru3D reports that Adrenalin 26.11.2 fixes more Radeon SSD writes. Tom's Hardware notes that NVIDIA had a similar Display Container logging bug in 2021, which it fixed in driver 471.96 and documented in its release notes.

Our verdict

If you run GeForce driver 621.14 or 621.24, spend five minutes in Resource Monitor while the PC is idle. If NVDisplay.Container.exe is constantly writing to nvlog.nvlgstg, rolling back to 621.01 is the workaround users report, but RTX 50 owners should weigh that against the video playback bug 621.01 had. If you're not seeing the writes, stay put and wait for NVIDIA's next driver, which will hopefully acknowledge and fix the issue.

The bottom line

If you run GeForce driver 621.14 or 621.24, spend five minutes in Resource Monitor while the PC is idle. If NVDisplay.Container.exe is constantly writing to nvlog.nvlgstg, rolling back to 621.01 is the workaround users report, but RTX 50 owners should weigh that against the video playback bug 621.01 had. If you're not seeing the writes, stay put and wait for NVIDIA's next driver, which will hopefully acknowledge and fix the issue.

Sources

  1. 01Tom's Hardware, Nvidia GeForce driver bug reportedly hammers SSDs with up to 30GB of writes per hour (18 November 2026)
  2. 02Windows Latest, First AMD, now Nvidia: your GPU driver could be quietly wearing out your Windows 11 PC's SSD (20 November 2026)
  3. 03Guru3D, Reports indicate recent NVIDIA GeForce drivers may generate heavy SSD writes

About the author

Forge PC Staff

Editorial team

The shared byline for articles researched, written and edited by the Forge PC editorial team. How we source, check and correct our work is set out in our editorial policy.

More from Forge PC Staff

Read next

Lemonade vs Ollama: Which Local AI Server Should You Use on an AMD or NVIDIA PC?

Versus

Lemonade vs Ollama: Which Local AI Server Should You Use on an AMD or NVIDIA PC?

Ollama is the safest default for local LLMs, with a big model library and support for NVIDIA, AMD and Apple hardware. Lemonade, an open-source server with AMD-backed optimisations, is the better choice on Ryzen AI and Radeon PCs if you want NPU support or speech and image models alongside LLMs. It also speaks the Ollama and OpenAI APIs.

Forge PC Staff5 min

Sleep vs Hibernate vs Shut Down in Windows 11: Which Should You Use on a Gaming PC?

Versus

Sleep vs Hibernate vs Shut Down in Windows 11: Which Should You Use on a Gaming PC?

Sleep keeps your session in RAM for the fastest resume but loses unsaved work in a power cut. Hibernate writes it to hiberfil.sys on your SSD and uses no power, but resumes more slowly. Shut down or restart for a clean start. On a gaming desktop, sleep for short breaks and hibernate for long ones; on a laptop, hibernate or shut down before travelling.

Forge PC Staff5 min

RTX 5090 vs RTX 4090 for Local AI: Is 32GB and 1.8TB/s Worth the Upgrade?

Versus

RTX 5090 vs RTX 4090 for Local AI: Is 32GB and 1.8TB/s Worth the Upgrade?

For local AI, the RTX 5090's 32GB of GDDR7 and 1,792GB/s of bandwidth beat the RTX 4090's 24GB and 1,008GB/s, so bigger models and longer contexts fit and token generation should be faster, with FP4 support too. It needs more power and NVIDIA recommends a 1,000W PSU. If your models fit in 24GB, a good-value RTX 4090 is still very capable.

Forge PC Staff5 min

How to Add Web Search to Your Local AI Chatbot in Open WebUI

How-To

How to Add Web Search to Your Local AI Chatbot in Open WebUI

Open WebUI can give a local model live web search. Start with the built-in DDGS engine, which needs no API key, move to a self-hosted SearXNG instance (with JSON output enabled) for more control, or use a hosted search API. Raise the model's context length to at least 16K tokens and use a model with good tool calling for useful answers.

Forge PC Staff5 min