A gaming PC with a transparent, green-lit case sits beside a Windows desktop monitor on a dimly lit desk.
Two weeks ago, an SSD wearing out on its own looked like an AMD problem. Now NVIDIA users are reporting the same kind of thing. On some Windows PCs, a background process from NVIDIA's display driver is reportedly rewriting a log file over and over while the machine sits idle. The highest figures come from individual user measurements, and those measurements can overstate what actually reaches the drive. Still, the pattern has been reported often enough, over a long enough period, that it's worth spending five minutes checking your own system.

A gaming PC with a transparent, green-lit case sits beside a Windows desktop monitor on a dimly lit desk. What's being reported​

The process in question is NVDisplay.Container.exe. A detailed bug report in NVIDIA's own GeForce 621.14 feedback thread says the process, which runs as the service "NVIDIA Display Container LS", continuously rewrites the binary log file C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg, causing heavy SSD writes while the PC is idle.

The cause appears to be how the file is written, not how big it is. Troubleshooting site TroubleGrid summarizes the user reports this way: reports consistently describe the file being truncated and rewritten rather than appended to, which is why the write volume scales with how big the file has already grown and why deleting it drops the write rate sharply. In plain terms, the service appears to rewrite the whole log every time it adds an entry. That's like reprinting an entire book every time you add a sentence. As the log grows, each rewrite costs more.

The numbers, and why to treat them carefully​

The most careful measurement comes from the NVIDIA forum report. The reporter says driver 621.01 (clean install) is NOT affected: nvlog.nvlgstg grows ~0.5 KB/min and NVDisplay.Container.exe writes < 2 MB per 5 min, vs ~325 KB/min growth and 515 MB per 5 min on 621.14 under the same conditions. The same user estimated that this causes unnecessary SSD wear (about 3 GB/hour from this process alone at idle).

The more alarming figures also come from individuals. According to TroubleGrid, a second user in the thread recorded more than 3 GB in ten minutes with Process Monitor, and a third, on the newer 621.24 driver, reported about 30 GB an hour. TroubleGrid also points out that whether 621.24 is as bad as 621.14 is not settled. The 30 GB/hour number is one report, measured a different way on different hardware.

Wccftech ran its own check on a Windows 11 PC with an RTX 4090. It reports a screenshot of the Windows Resource Monitor shows 'NVDisplay.Container.exe' with a process ID of 3504, actively writing at a rate of 1,433,500 B/sec. That's about 5.2 GB per hour if the rate held steady, which a single snapshot can't show. Wccftech saw this even with NVIDIA's capture features (Highlights, ShadowPlay, Replay, Desktop Capture) and the NVIDIA App overlay turned off.

The key caveat: Windows' per-process write counters include writes to the file cache, and not all of those reach the SSD's flash memory. In the forum reporter's five-minute test, 515 MB of process writes appeared alongside 270 MB of total writes to drive C:. The same reporter said the SSD's own SMART "Data Units Written" counter matched what Windows reported, which suggests real writes were reaching the drive on that machine. If you want to know whether your SSD is actually being worn down, that SMART counter is the number to watch.

Summary: Multiple users report heavy idle writes from a single NVIDIA process to a single log file. The worst figures are individual measurements, not a controlled survey.

Is 621.01 actually clean? The reports disagree​

Most coverage treats 621.14 (released November 4) as the release where things got worse and 621.01 as a safe place to roll back to. The 621.14 feedback thread is less tidy than that. Another poster there writes that the problem occurred with driver 617.42 and has continued with 621.14, and lists it as also seen on 610.88 and 621.01.

So the 621.01 rollback has worked for some people, but it isn't guaranteed. It's quite possible that 621.14 made an existing logging behavior much heavier rather than creating it. The older history supports that reading.

This isn't new​

The same log file has been causing complaints for a long time. In an older NVIDIA forum thread titled "Driver excessively writing to nvlog.nvlgstg", a Dell XPS owner wrote that the file grows in megabytes during the day, and every day (reboot) it gets overridden. A Process Monitor trace in that thread shows NVDisplay.Container.exe opening the file with an "OverwriteIf" disposition and making a single write 10,272,768 bytes long. In the same thread, a GeForce 4060 owner on Windows 10 checked the same way and no such disk activity at all appeared. Another user fell back to the official driver from Dell (528.79), which apparently doesn't have this feature that is responsible for writing to nct\nvlog.nvlgstg at all.

NVIDIA has fixed something like this before. The 621.14 report notes that a similar issue with nvtopps.db3 was fixed in driver 471.96 in 2021. That was a different file, so it doesn't prove the current problem has the same cause or will get the same fix. It does show NVIDIA has treated this kind of logging bug as a driver issue in the past.

NVIDIA has not publicly acknowledged the current reports. TroubleGrid says the 621.24 release notes from November 12 list no open issues, and none of the forum threads it reviewed has an NVIDIA reply.

How to check your own PC​

Before you change anything, confirm that this specific problem is happening on your machine.

  1. Press Win + R, type resmon, and press Enter to open Resource Monitor.
  2. Open the Disk tab.
  3. Under "Processes with Disk Activity," sort by Write (B/sec). TroubleGrid suggests you leave it for ten minutes and watch the figure for NVDisplay.Container.exe.
  4. In the Disk Activity pane, check whether the writes go to C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg.
  5. If you want a running total, open Task Manager's Details tab and add the I/O write bytes column. Remember that this is a process counter, not a measure of SSD wear.
  6. Check your drive's SMART "Data Units Written" (or host writes) value with the SSD maker's tool, wait a few hours, and check again.

What a positive result looks like: NVDisplay.Container.exe writes to nvlog.nvlgstg every few seconds and keeps doing it while the PC is idle.

If you see a different process, this problem doesn't apply to you. TroubleGrid lists other common causes of idle writes, including Windows Search indexing, SysMain, antivirus scans, Windows Update, browser caches, Steam shader pre-caching, and cloud-sync clients. If the process is atieclxx.exe, you're looking at the separate AMD issue. That can happen even on a PC with an NVIDIA graphics card if it has an AMD processor.

Reported workarounds and their trade-offs​

None of these comes from NVIDIA. They're things users say have helped.

Option 1: Clear the log (temporary)

  1. Press Win + R, type services.msc, and press Enter.
  2. Right-click NVIDIA Display Container LS and choose Stop. Your screen may flicker once.
  3. Delete nvlog.nvlgstg from the folder listed above.
  4. Right-click the service and choose Start.
  5. Run the Resource Monitor check again.

In the forum test, after stopping the service, deleting nvlog.nvlgstg and restarting the service, it dropped to 48 MB (-91%), and total writes to the C: drive dropped from 270 MB to 145 MB. That is one user's result. The file grows back over time, and TroubleGrid notes that another 621.24 user saw no improvement after restarting the service and rebooting.

Option 2: Roll back to 621.01. Some users report this fixed the problem. As noted above, at least one forum post says 621.01 was affected too. You'd also be giving up whatever changes came in the newer drivers.

Option 3: Disable the service. Some users suggest setting the service to Manual startup. Be aware of the cost. While the service isn't running, NVIDIA Control Panel and the NVIDIA App won't open, and that's where G-SYNC, color, scaling, and per-game 3D settings are changed. TroubleGrid also says turning off telemetry in the NVIDIA App doesn't help. The 30 GB/hour user had telemetry off already, and the Dell reporter didn't have the NVIDIA App installed at all.

Does it actually matter for your SSD?​

That depends on how fast your own system is writing. TroubleGrid's estimate is that 3 GB an hour on a PC running nonstop comes to about 26 TB a year. Consumer 1 TB NVMe drives are usually rated for a few hundred terabytes of writes, so that's a noticeable share of the drive's endurance spent on a log nobody reads. Taking the 30 GB/hour report at face value, a machine left on around the clock would write about 720 GB a day (my own arithmetic, not a measurement). The low rates seen with older drivers are much less of a concern.

For most people this isn't an emergency. It's worth checking, and acting on if your system turns out to be affected.

The AMD comparison​

The timing invites comparison with AMD. AMD's Adrenalin 26.11.1 Optional release notes list excessive writes to the system drive at idle on Radeon RX 7000-series cards and newer as a fixed issue. PC Perspective summed it up: It's not just an AMD thing (which was patched, by the way). The two problems are separate, though. According to TroubleGrid, the AMD one involves atieclxx.exe copying its own executable, while the NVIDIA one involves a display service rewriting a log file. They look the same in Task Manager, but the causes and fixes are different.

Bottom line​

  • What's reported: NVDisplay.Container.exe repeatedly rewrites nvlog.nvlgstg on some GeForce systems. Users say 621.14 made it much worse, and it has also been reported on 621.24.
  • What isn't known: how many systems are affected, the root cause, and whether 621.01 is reliably unaffected. The forum reports conflict on that last point.
  • NVIDIA's position: no public acknowledgment, and nothing in the 621.24 known-issues list.
  • What to do: check with Resource Monitor first. If you're affected, clearing the log gives temporary relief, and a rollback has helped some users. Avoid disabling the service unless you can live without NVIDIA Control Panel.

If you've measured this on your own machine, especially with SMART host-write figures from before and after, post your numbers, driver version, and GPU in the forum thread. Comparable measurements across different systems are the clearest way to show how common this is.

 

References

  1. NVIDIA GPU Drivers Reportedly Writing Up To 30GB Per Hour To SSDs, Echoing AMD’s Recent Driver Bug - Wccftech Wccftech 2026-11-18T13:44:00+00:00
  2. NVIDIA Driver Constantly Writing to SSD: Fix | TroubleGrid troublegrid.com
  3. Topic: GeForce GRD 621.14 Feedback on NVIDIA #GeForce Forums nvidia.com