Nvidia GeForce Drivers Accused of Hammering SSDs at Idle
Users on Nvidia's own GeForce forums report the 621.14 and 621.24 Game Ready drivers writing continuously to SSDs while idle. Nvidia hasn't acknowledged it; here's the reported fix.
Nvidia's two most recent GeForce Game Ready drivers, version 621.14 (released November 4) and version 621.24 (released November 12), are being flagged by users on Nvidia's own GeForce forums for writing unusually large, continuous amounts of data to SSDs even while a PC is sitting completely idle. The reports center on the NVIDIA Display Container LS service rewriting a log file inside C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg, with some posters citing figures as high as 30GB an hour. Nvidia has not listed the behavior as a known issue in either driver's official release notes, and as of this writing has made no public acknowledgment of it. The workaround most users are trying is rolling back to driver 621.01, the WHQL release that immediately preceded 621.14.
- What's reported: Continuous, high-volume writes to a driver log file while the PC is idle, traced by forum posters to the NVIDIA Display Container process.
- Drivers named: GeForce Game Ready 621.14 (Nov. 4) and 621.24 (Nov. 12). Users say 621.01, the prior WHQL release, does not show the behavior.
- Has Nvidia confirmed it? No. It is not listed in the "Open Issues" section of either driver's official release notes, and Nvidia has not issued a public statement on it.
- Is there an official fix? Not yet. The workaround circulating among affected users is rolling back to driver 621.01.
- Similar to anything before? Yes — a near-identical bug hit AMD's Radeon Adrenalin drivers, which AMD did acknowledge and fixed in Adrenalin 26.11.1.
What users are reporting
The reports are showing up in multiple threads on Nvidia's own GeForce community forums, including one titled "Continuous writing of gigabytes to SSD to nvtopps" and the general 621.24 feedback thread. Posters describe opening Windows' Resource Monitor or Task Manager's disk tab, sorting by write activity, and finding the NVIDIA Display Container process (commonly shown as nvcontainer.exe or NVDisplay.Container.exe) steadily writing to disk with no games running, no recording software active, and the system otherwise sitting untouched.
Pandromeda has not independently measured this behavior on test hardware, and these figures should be read as community-reported, not vendor-confirmed or lab-verified. What is consistent across the reports is the symptom: a GeForce system that should show near-zero background disk activity at idle instead shows a steady stream of writes that only stops when the affected service is halted or the driver is rolled back.
The reports aren't confined to a single GPU tier or system type. Forum posters describing the behavior mention a mix of desktop and laptop GeForce systems, which suggests — though again, without independent confirmation — that the trigger is more likely tied to the driver's background service itself than to any one specific card or chassis. That's a meaningfully different situation from a narrow, hardware-specific glitch, and it's part of why the thread has drawn enough attention to prompt direct comparisons to the AMD Radeon case covered below.
The process and file involved
Forum posters trace the writes to a single file: nvlog.nvlgstg, a binary log stored under C:\ProgramData\NVIDIA Corporation\nvtopps\nct\. The file is maintained by the NVIDIA Display Container LS service, a background component that has shipped with GeForce drivers for years and normally logs lightweight diagnostic data. Users report that on 621.14 and 621.24, that file is rewritten or appended to on a loop rather than only logging discrete events, which is what produces the sustained write activity rather than occasional small writes.
Some posters say that manually stopping the NVIDIA Display Container LS service and deleting the log file temporarily halts the writes, only for the behavior to resume once the service recreates the file. Others say simply marking the file read-only slowed, but did not fully stop, the growth. None of these are vendor-sanctioned fixes — they are workarounds users are testing on their own systems, with mixed and unverified results.
The NVIDIA Display Container LS service itself isn't new or inherently suspicious — it's a long-running background component that helps coordinate display settings, GeForce Experience or the NVIDIA app, and related driver features, and some amount of occasional disk I/O from it is normal and expected. The complaint specific to 621.14 and 621.24 isn't that the service writes to disk at all, but that the volume and frequency of those writes has reportedly jumped well past what users saw on 621.01 and earlier drivers, turning routine background logging into a sustained, idle-time write load.
How much data is being written (reportedly)
The volume estimates vary widely between individual reports, which is itself worth flagging: this is a collection of separate user measurements on different hardware and configurations, not a single controlled test. On the forums, posters have described write rates ranging from roughly 6GB an hour up to as much as 30GB an hour at idle, with at least one user in an extended-uptime scenario describing multiple gigabytes written per minute after the system had been running for over 40 hours. Other users elsewhere have reported smaller but still abnormal figures.
Pandromeda is labeling all of these numbers as user-reported and unverified. Nvidia has not published its own measurement of how much data the affected process writes, has not characterized the scope of affected configurations, and has not said whether the volume depends on uptime, GPU model, or specific system settings. Until Nvidia or an independent, methodologically transparent test confirms a number, treat any specific GB-per-hour figure as an anecdote rather than an established fact.
Which driver versions are implicated
Forum reports consistently name two GeForce Game Ready WHQL releases:
| Driver version | Release date (per Nvidia) | User-reported idle SSD writes? |
|---|---|---|
| 621.01 | Prior WHQL release | Reported clean by users rolling back to it |
| 621.14 | November 4, 2026 | Yes — cited in forum reports |
| 621.24 | November 12, 2026 | Yes — cited in forum reports, including after the 621.14-to-621.24 update |
In other words, users say the behavior did not go away between the two most recent Game Ready releases — it was reported on 621.14 at the start of November, when that driver launched alongside Game Ready support for World of Warcraft: Forever, and is still being reported on 621.24 after the November 12 update. That is a meaningful detail for anyone hoping the newer driver quietly resolved the issue: based on current forum reports, it has not.
What Nvidia's release notes actually say
Pandromeda reviewed Nvidia's own official release notes for both drivers directly. The 621.14 WHQL release notes list two fixed issues — a Call of Duty: Modern Warfare 4 color bug and a video-playback freeze affecting some RTX 50-series and RTX Spark systems — and its "Open Issues in Version 621.14 WHQL" section reads simply "N/A." The 621.24 WHQL release notes likewise list a Chaos Vantage OptiX Denoiser fix and a Windows Photos color-playback fix, and its own "Open Issues" section also reads "N/A." Neither document mentions SSD writes, disk activity, NvContainer, or the NVIDIA Display Container service anywhere in the text.
That absence is itself a documented fact, not a guess: as of the publication of both release notes, Nvidia had not flagged this behavior as a known issue in its own documentation. That is different from confirming the bug doesn't exist — an unlisted issue can still be real, just not yet acknowledged, tracked, or triaged publicly by Nvidia.
The workaround: rolling back to 621.01
With no official fix available, the remedy circulating among affected users in the forum threads is a manual driver rollback to version 621.01, the WHQL release that predates 621.14. Users doing this report a return to normal, low idle disk activity, though Pandromeda has not independently verified that every rollback report is consistent or that 621.01 is free of the issue under every configuration.
Rolling back a driver means giving up whatever was fixed or added in 621.14 and 621.24 — including the Call of Duty: Modern Warfare 4 and video-playback fixes in 621.14, and the Chaos Vantage and Windows Photos fixes plus day-one support for titles like Warhammer 40,000: Dawn of War IV and Where Winds Meet in 621.24. That kind of trade-off isn't unique to this bug — it's the same calculation GeForce users on Windows 10 have had to make around Nvidia's last Windows 10 driver branch, where newer features and older stability pull in opposite directions. Anyone considering a rollback should weigh that trade-off, and should first confirm for themselves — via Windows Resource Monitor or Task Manager's disk-activity tab — whether their own system is actually showing the abnormal write pattern, rather than rolling back on the assumption that it must be affected.
How this compares to the AMD Radeon bug
The timing invites an obvious comparison. Pandromeda reported yesterday on a nearly identical symptom in AMD's Radeon Adrenalin drivers — a background process writing abnormal, continuous amounts of data to SSDs at idle. The crucial difference is how each vendor has handled it so far.
| AMD Radeon (Adrenalin) | Nvidia GeForce (621.14 / 621.24) | |
|---|---|---|
| Vendor acknowledgment | Yes, acknowledged by AMD | No public acknowledgment as of this writing |
| Official fix shipped | Yes — Adrenalin 26.11.1 | No official fix; community rollback only |
| Current user workaround | Update to the fixed driver | Roll back to driver 621.01 |
These are two separate bugs in two separate vendors' driver stacks, not the same underlying defect. Nothing in Nvidia's forums or release notes ties the GeForce behavior to the cause AMD identified in its own drivers. The comparison is useful context — it shows this class of bug (a GPU driver background service hammering an SSD at idle) isn't unique to one vendor — but it should not be read as evidence that Nvidia's issue has the same cause, the same scope, or will be resolved the same way.
Is this really new?
Not entirely. Older Nvidia GeForce forum threads, including one from several years ago titled "Nvidia Container constantly writing to C-drive SSD," show that complaints about the NVIDIA Display Container process and disk activity are not brand new to the 621.xx driver branch. Background services that write diagnostic or telemetry data to disk are common across GPU drivers generally, and some baseline write activity from any such service is normal — the concern specific to 621.14 and 621.24 is the reported scale and persistence of the writes, well beyond what older complaints described. Repeated writes to the same storage cells, even in small amounts, can matter over time because consumer SSDs have a finite write-endurance rating (often expressed in total bytes written, or TBW) before their reliability starts to degrade, per general background on solid-state drive design on Wikipedia. That's why a background process writing tens of gigabytes an hour, continuously, is a bigger concern than a few megabytes of occasional logging.
What's next
As of now, there is no confirmed timeline for an Nvidia statement or fix. Nvidia's release notes for 621.14 and 621.24 don't mention the issue, and no public comment from the company has surfaced alongside the forum reports. The two most useful things affected users can do in the meantime are to verify the behavior on their own system using Windows' built-in disk-activity tools rather than assuming they're affected, and to watch Nvidia's GeForce forums and future driver release notes — a fix, if one comes, would most plausibly show up as a listed fixed issue in a future WHQL release.
It's also worth keeping an eye on whether the next Game Ready release, whenever Nvidia ships it, quietly resolves the behavior without ever naming it — something that has happened with other driver-side bugs in the past, where a fix arrives folded into general "stability improvements" language rather than a specific named entry. Until that happens, or until Nvidia adds an explicit line to a future release notes document, the safest assumption for affected users is that the behavior reported on 621.14 and 621.24 is still present. Pandromeda will update this story if Nvidia acknowledges the issue or ships a fix.
Frequently asked questions
What's causing Nvidia GeForce drivers to write so much data to SSDs?
Users on Nvidia's own GeForce forums report that the NVIDIA Display Container LS service is continuously rewriting a log file (nvlog.nvlgstg) on drivers 621.14 and 621.24, even while the PC is idle. Nvidia has not confirmed a cause.
Which Nvidia driver versions are affected?
Forum reports name GeForce Game Ready driver 621.14 (released November 4) and 621.24 (released November 12). Users say the prior release, 621.01, does not show the behavior.
Has Nvidia acknowledged this SSD-writing bug?
No. As of this writing, it is not listed in the Open Issues section of either driver's official release notes, and Nvidia has not made a public statement about it.
How much data is actually being written?
Estimates vary by user report, ranging from roughly 6GB an hour to as much as 30GB an hour at idle in some posts. These are community-reported figures, not numbers Nvidia or Pandromeda has independently verified.
Is there a fix or workaround?
There is no official Nvidia fix yet. The workaround circulating among affected users is manually rolling back to driver 621.01, which users say stops the abnormal write activity.
Is this the same bug that hit AMD Radeon drivers?
No. It's a separate bug affecting a different vendor's driver stack. AMD acknowledged a similar idle SSD-write issue in its Radeon Adrenalin drivers and shipped a fix in Adrenalin 26.11.1; Nvidia has not acknowledged or fixed its GeForce-side reports.
Sources
- NVIDIA GeForce 621.14 WHQL Release Notes (official PDF)us.download.nvidia.com
- NVIDIA GeForce 621.24 WHQL Release Notes (official PDF)us.download.nvidia.com
- NVIDIA GeForce Forums: "Continuous writing of gigabytes to SSD to nvtopps"nvidia.com
- NVIDIA GeForce Forums: GeForce GRD 621.24 Feedback Threadnvidia.com
- NVIDIA GeForce Forums: "Nvidia Container constantly writing to C-drive SSD" (background)nvidia.com
- Wikipedia: Solid-state drive (write endurance background)en.wikipedia.org
Mara Lindqvist edits the hardware desk. She covers graphics cards, processors, memory and storage, the foundries and chip designers behind them, and what the numbers on a spec sheet mean for people choosing a PC. Specifications in her stories come from manufacturer spec pages and datasheets.

