Daily Tech Now

Daily News on AI, Big Tech, Linux, Security & Gadgets

How to Check and Stop Nvidia Driver SSD Writes on 621.14 and 621.24

On one RTX 4090 running GeForce driver 621.24, an Nvidia background process wrote 2.0 to 2.7 GB to the system drive every minute while the PC sat idle. The owner, posting on Nvidia’s GeForce forums, put that at about 120 to 160 GB per hour. Other users report far lower numbers, and some see no…

Nvidia driver SSD writes: NVDisplay.Container.exe rewriting the nvlog.nvlgstg log file on a GeForce PC running driver 621.24

On one RTX 4090 running GeForce driver 621.24, an Nvidia background process wrote 2.0 to 2.7 GB to the system drive every minute while the PC sat idle. The owner, posting on Nvidia’s GeForce forums, put that at about 120 to 160 GB per hour. Other users report far lower numbers, and some see no problem at all.

Every report names the same process: NVDisplay.Container.exe, which runs the “NVIDIA Display Container LS” service. It keeps rewriting one binary log file instead of adding to it. The file lives at C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg.

The headline figure of 30 GB per hour has already spread widely. A post on X summarizing the user reports passed 1.1 million views within a day. This article focuses on what you can do: how to check your own PC, which workarounds users have tested, and where each one falls short.

Which Nvidia drivers are affected

The most detailed report comes from a user named Andergraude. It was filed in Nvidia’s official feedback thread for Game Ready driver 621.14, released on November 4. The report calls the bug a regression that is new in 621.14.

On a clean install of driver 621.01, the log file grew about 0.5 KB per minute. On 621.14, it grew about 325 KB per minute under the same conditions. Over five idle minutes, the container process wrote 515 MB on 621.14, compared with less than 2 MB on 621.01.

Andergraude also checked the SSD’s SMART “Data Units Written” counter. It matched the writes Windows reported, so on that system the data really reached the NVMe drive. The PC was idle at the desktop, with only a browser open and no game running.

Driver 621.24 arrived on November 12. In a separate forum thread about the nvtopps file, user AyzekUorren reports about 30 GB per hour on that version. Long sessions reached 70 GB or more. Telemetry was turned off in the NVIDIA App on that PC.

The same thread adds two useful details. One user sees the behavior on the 621.24 Studio driver as well. Another saw no problem on 610.88 before moving to 621.24.

Reported write volumes by driver

The figures below come from different machines and different tests. They are user reports, not lab results.

Driver Reported by What was measured
621.01 (clean install) Andergraude, RTX 4070 Super Under 2 MB in 5 idle minutes
621.14 Andergraude, RTX 4070 Super 515 MB in 5 idle minutes
621.24 AyzekUorren About 30 GB per hour
621.24 Tuong Dinh, RTX 4070 Ti 90 GB per day
621.24 Tarkara 184 GB since boot after 2 days
621.24 mertuygr, RTX 4090 2.0 to 2.7 GB per minute after about 43 hours of uptime
621.24 Navid A1, RTX 5080 502 MB over 2 days
621.14 and 621.24 Dankbomber1990, RTX 5070 Ti Not reproduced; log grew about 0.4 KB per minute

Wccftech ran its own spot check on an idle RTX 4090 system. It saw the process writing about 1.43 MB/s, or roughly 5.2 GB per hour if sustained.

Why the numbers vary so much

The reports point to one pattern. The service rewrites the whole log file every few seconds, so the write volume grows with the file. Andergraude watched the file go from 0 to 2.6 MB in about eight minutes. It later reached about 20 MB.

mertuygr saw the same thing on the RTX 4090. A fresh service restart started near 1 GB per minute and then climbed as the file grew. That explains why uptime matters so much in these figures.

Window switching seems to add bursts. AyzekUorren says each Alt+Tab adds roughly 500 MB to 1 GB of writes. Another user, chrisaverage, saw hundreds of megabytes written as soon as window focus changed. Andergraude found that video pages in a browser made it worse.

Not every PC is affected. Dankbomber1990 tested an RTX 5070 Ti at 4K with G-Sync on, and the log barely moved. That user listed GPU generation, resolution and G-Sync as possible differences, but called them leads, not conclusions.

How to check if your PC is affected

You do not need extra software for a first check. These steps come from the forum reports.

  1. Open Task Manager and go to the Details tab. Right-click a column title, choose Select columns, and turn on “I/O write bytes”. Then look at the total for NVDisplay.Container.exe since boot.
  2. For a live view, press Win+R, type resmon and press Enter. On the Disk tab, sort by Write (B/s) and look for NVDisplay.Container.exe.
  3. Open C:\ProgramData\NVIDIA Corporation\nvtopps\nct and watch nvlog.nvlgstg. If its modified time changes every few seconds, the loop is running.
  4. For a firmer answer, note your SSD’s SMART “Data Units Written” value in the drive maker’s tool or CrystalDiskInfo. Check it again after an idle hour.

A few hundred megabytes over several days matches the unaffected systems in the thread. Tens of gigabytes per day match the affected ones. Keep in mind that Windows I/O counters do not always equal the data written to flash, a point Wccftech also makes.

Workarounds users have tested

None of these fixes come from Nvidia. Each one has a cost, and some do not survive a reboot.

Roll back to driver 621.01

Several users say the writes stopped after going back to 621.01. Tarkara, who had logged 184 GB in two days, is one of them. The trade-off is losing later fixes. For example, Nvidia’s 621.14 notes list a fix for video playback freezing or going black on some RTX 50 Series GPUs and RTX Spark after updating to 621.01.

Stop the service and delete the log

Stop “NVIDIA Display Container LS”, delete nvlog.nvlgstg, then start the service again. Andergraude measured a 91% drop in the process’s writes after doing this. The relief is short, though, because the file grows back and the writes climb with it.

Set the service to Manual

User j-11 stopped the service and set its startup type to Manual. That ends the writes. However, Wccftech warns that disabling the service for good can break the NVIDIA Control Panel and the NVIDIA App.

Make the log file read-only

Marking nvlog.nvlgstg as read-only stops the writes for the current session. After a reboot, the container renames the locked file to nvlog_0.nvlog and creates a fresh nvlog.nvlgstg. Three users describe this behavior.

Stop the trace session

AyzekUorren found that the command logman stop NVIDIA-NVTOPPS-FILTER -ets halts the writes. It resets after a reboot. AyzekUorren also warned that it may disable something useful.

Technical details: the plugin behind the log

This section is for readers comfortable with the Windows registry. mertuygr read the container’s own log and found that only one plugin writes the file. It is _nvtopps.dll, listed as “NvTopps_Plugin”, and the container loads it as an optional plugin.

The container supports a per-plugin DisableLoad value. mertuygr ran this command in an administrator PowerShell window:

New-Item 'HKLM:\SYSTEM\CurrentControlSet\Services\NVDisplay.ContainerLocalSystem\Parameters\LocalSystem\_nvtopps' -Force | New-ItemProperty -Name DisableLoad -PropertyType DWord -Value 1 -Force

After a service restart or reboot, %ProgramData%\NVIDIA\NVDisplay.ContainerLocalSystem.log should show a line about disabling the plugin. On mertuygr’s PC, writes fell to 0 MB per minute and the log file was no longer created. The service stayed on Automatic, and the NVIDIA App still worked in a refresh-rate test.

To undo it, delete the _nvtopps key. A driver reinstall may also reset it. This tweak comes from one user’s testing. Nvidia has not documented what the plugin does, so other features could depend on it.

The log has caused trouble before. Andergraude notes that a similar issue with a file called nvtopps.db3 was fixed in driver 471.96 in 2021.

What Nvidia has said, and what to watch

So far, nothing in public. The official 621.24 feedback thread lists two general fixes and does not mention the log. We found no reply from Nvidia staff in the threads we reviewed. Wccftech also reports that Nvidia has not acknowledged the problem.

AMD faced a similar report this month. According to Wccftech, AMD admitted its bug and shipped a fix in Adrenalin 26.11.1.

Three questions remain open. Nvidia has not said which hardware or settings trigger the loop. It has not said whether turning off the nvtopps plugin is safe. And it has not said when a fixed driver will ship. Until it does, a quick check in Task Manager is the simplest way to know whether your SSD is paying the price.

About the Author

Trang Nguyen Avatar

Leave a Reply

Your email address will not be published. Required fields are marked *