NVIDIA driver writes to the SSD constantly (NVDisplay.Container.exe, nvlog.nvlgstg)
Confirm the writer first: in Resource Monitor's Disk tab, look for NVDisplay.Container.exe writing to C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg every few seconds. If that is what you see, the quickest relief is to stop the "NVIDIA Display Container LS" service, delete that log file and start the service again — one measured test on 621.14 cut the process's writes by 91%, though the file grows back. For a lasting fix, go back to 621.01, which is reported clean. Do not disable the service permanently unless you accept losing the NVIDIA Control Panel and NVIDIA App, and note NVIDIA has not acknowledged any of this: its 621.24 release notes list no open issues at all.
This is a different problem from the widely reported AMD one. The AMD bug is atieclxx.exe copying its own executable; this is NVIDIA's display service rewriting a binary log. The symptom looks identical in Task Manager, the cause and the fix are not, and almost all of the press coverage you will find is about AMD.
Symptoms
- Constant disk write activity on the Windows drive while the PC sits idle
- NVDisplay.Container.exe shows a steady or large write figure in Resource Monitor's Disk tab
- The I/O write bytes column for NVDisplay.Container.exe in Task Manager's Details tab climbs continuously
- SSD host writes (Data Units Written / Total Host Writes) growing by tens of GB a day with nothing obvious running
- A file at C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg whose timestamp changes every few seconds
- In the worst reports, games and video stutter and the mouse pointer hitches while the logging runs
- Each Alt+Tab between programs produces a burst of several hundred MB of writes
Why this happens
The display service rewrites its whole log instead of appending to it
NVDisplay.Container.exe, run by the service "NVIDIA Display Container LS", keeps a binary log at C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg. 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. One user measured a single WriteFile call of 10,272,768 bytes; another reported the file holding steady around 20 MB precisely because it is rewritten each time. This also explains why the problem gets worse the longer a session runs.
Stop the service, delete the log file, start the service again · Go back to driver 621.01, the last version reported clean
The 621.14 driver made the logging far more aggressive
The underlying logging has been reported on and off since at least driver 471.41, usually at a tolerable rate. A detailed report against 621.14 measured a step change: the log grew about 325 KB/min and the process wrote 515 MB per five minutes at idle, against roughly 0.5 KB/min and under 2 MB per five minutes on a clean install of 621.01 under the same conditions. A second user in the same thread measured over 3 GB in ten minutes and a third, on 621.24, reports about 30 GB an hour. That is the difference between a background annoyance and something worth acting on.
It is not the telemetry setting, and not the NVIDIA App
The most repeated advice on this is to turn off telemetry, or to assume NVDisplay.Container.exe exists only for telemetry and can be killed. Two independent reports rule that out: the user on 621.24 had telemetry already disabled in the NVIDIA App and still saw about 30 GB an hour, and the Dell XPS reporter did not have the NVIDIA App installed at all. A Microsoft Q&A poster also noted that modern drivers no longer expose telemetry as a separate service or scheduled task, so guidance written for older drivers no longer maps onto anything you can switch off.
Confirm NVDisplay.Container.exe is the process writing · Set the NVIDIA Display Container LS service to Manual
Fixes
Confirm NVDisplay.Container.exe is the process writing
about 10 minPlenty of things write to an idle disk. Naming the process and the file first is what stops you applying a GPU-driver fix to a Windows Search or antivirus problem.
Applies to: Windows 10, Windows 11, Any GeForce or Studio driver
- Open Resource Monitor (press Start, type Resource Monitor) and go to the Disk tab. Sort the "Processes with Disk Activity" list by Write (B/sec) and look for NVDisplay.Container.exe.
- In the "Disk Activity" pane underneath, look at the File column for the path the writes are going to. On an affected PC it reads nvlog.nvlgstg.
C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg - For a longer view, open Task Manager, go to the Details tab, right-click the column headers, choose "Select columns", and tick "I/O write bytes". Leave it for ten minutes and watch the figure for NVDisplay.Container.exe.
- Open that nvtopps\nct folder in File Explorer and press F5 a few times over a minute. On an affected PC the Date modified on nvlog.nvlgstg changes every few seconds.
- Optional, for a figure that reflects the drive rather than Windows' counters: check your SSD's Data Units Written or Total Host Writes in the manufacturer's tool, note it, and compare a few hours later.
Reported to work by 12 users; not confirmed by the vendor.
Source: NVIDIA GeForce Forums, Dell Community, Microsoft Q&A, Super User
Stop the service, delete the log file, start the service again
Check before applyingabout 5 minBecause the service rewrites the whole log rather than appending, shrinking the file back to nothing cuts the write rate immediately. It is relief, not a cure — the file grows back.
Applies to: Windows 10, Windows 11
Before you do this
This is a temporary measure: every report describes the file growing back, so the writes return over hours or days. Only one user has published a measurement of this procedure, and a separate user on 621.24 reports that restarting the service and rebooting did not help them, so treat the 91% figure as one result rather than a reliable expectation.
- Press Windows + R, type services.msc and press Enter. Find "NVIDIA Display Container LS", right-click it and choose Stop. Your screen may flicker once; the NVIDIA Control Panel and NVIDIA App will not open while it is stopped.
- Open File Explorer, paste the folder path below into the address bar and press Enter.
C:\ProgramData\NVIDIA Corporation\nvtopps\nct - Delete nvlog.nvlgstg. If Windows says the file is in use, the service has not fully stopped yet — wait a few seconds and try again.
- Back in services.msc, right-click "NVIDIA Display Container LS" and choose Start.
- Re-run the Resource Monitor check from the previous fix to see what the write rate is now. In the one measured test of this, the process's writes over five minutes fell from 515 MB to 48 MB.
Reported to work by one user; not confirmed by the vendor.
Source: NVIDIA GeForce Forums, NVIDIA GeForce Forums, NVIDIA GeForce Forums
Go back to driver 621.01, the last version reported clean
Check before applyingabout 25 minTwo users independently report the heavy writing starting with 621.14 and stopping when they went back a version. This is the only reported change that holds rather than wearing off.
Applies to: GeForce Game Ready 621.14 and 621.24, Windows 10, Windows 11
Before you do this
An older driver means no Game Ready support for titles released after it, and you give up the fixes 621.14 and 621.24 shipped. Note too that three users report clean reinstalls with DDU making no difference, so a reinstall of the same version is not what helps here — the version change is.
First:
- Download the 621.01 installer before uninstalling the current driver
- Download the 621.01 installer for your GPU from NVIDIA's driver download page first, before removing anything, so you are not left without a driver. Note your current version from the NVIDIA App or by running the command below.
nvidia-smi --query-gpu=driver_version --format=csv - Do not use Device Manager's "Roll Back Driver" or the Windows rollback feature for this. NVIDIA's own release notes state that Windows rollback will not reliably restore all the previous driver files, and that uninstalling through Device Manager may leave files and applications behind — Microsoft has confirmed that is by design.
- Instead, open Settings > Apps > Installed apps, find the NVIDIA Graphics Driver entry and uninstall it. That is the Add and Remove Programs route NVIDIA tells you to use.
- Restart the PC, then run the 621.01 setup.exe you downloaded. Choose a Custom install and tick "Perform a clean installation" if offered.
- After it finishes, re-run the Resource Monitor check. One user measured 260 KB of log writes over a full hour after going back a version, against gigabytes before.
- To stop Windows Update pushing the newer driver back on, leave "Get the latest updates as soon as they're available" off and decline optional driver updates.
Reported to work by 2 users; not confirmed by the vendor.
Source: NVIDIA GeForce Forums, NVIDIA, Dell Community
Set the NVIDIA Display Container LS service to Manual
Advancedabout 5 minThis reliably stops the writes, and it is the fix most often recommended on forums. It is listed last because of what it costs you, which those forum posts rarely mention.
Applies to: Windows 10, Windows 11
Before you do this
With this service stopped the NVIDIA Control Panel and NVIDIA App will not open, and those are where G-SYNC, colour settings, display scaling, resolution overrides and per-game 3D settings live. The claim you will see on forums that this process "is only telemetry, so you do not need it" is wrong: the Microsoft Q&A reporter who disabled it recorded that the disk activity stopped but the Control Panel became unusable. Settings you have already applied stay applied, but you cannot change them until you start the service again. Do not disable the service outright if you use G-SYNC or a custom colour profile.
- Press Windows + R, type services.msc and press Enter. Find "NVIDIA Display Container LS" and double-click it.
- Change "Startup type" from Automatic to Manual, click Stop, then click OK. Do not choose Disabled — Manual leaves you able to start it again when you need the Control Panel.
- When you next need the NVIDIA Control Panel or the NVIDIA App, come back to services.msc and Start the service first, then close it and stop the service again afterwards.
- Re-check with Resource Monitor to confirm the writes have stopped.
Reported to work by 2 users; not confirmed by the vendor.
Source: Microsoft Q&A, NVIDIA GeForce Forums
Known issues
NVIDIA has not documented this. The 621.24 release notes (RN-08399-621.24_v01, 12 November 2026) list Open Issues as "N/A" — no open issues at all — and the document does not mention disk writes, log files, nvlog, nvtopps or the Display Container service anywhere. There is no reply from NVIDIA on any of the forum threads behind this page, including one running about two years on NVIDIA's own site.
Affects GeForce Game Ready 621.24, GeForce Game Ready 621.14 · Status: open
NVIDIA has fixed this class of bug before. A closely related problem — constant rewriting of nvtopps.db3 by the same service — was fixed in driver 471.96 in 2021, reported independently in the 621.14 thread and in a Microsoft Q&A answer whose author confirmed 472.12 was clean. That is the precedent for expecting a driver-level fix rather than a permanent workaround.
Affects Driver 471.68 and earlier (nvtopps.db3 variant), Fixed in 471.96 · Status: fixed
Whether 621.24 is as bad as 621.14 is not settled. The measured comparison in the 621.14 thread is the only careful one, and it predates 621.24. One user reports about 30 GB an hour on 621.24, which is worse than the 3 GB an hour measured on 621.14, but that is a single report using a different method on different hardware. Treat the two as the same problem and the rates as indicative only.
Affects GeForce Game Ready 621.24 · Status: unknown
Process-level write figures overstate what reaches the NAND. Windows counts writes into the file cache, so a per-process total of 515 MB in five minutes sat alongside 270 MB of total writes to the C: drive in the same test. The reporter checked the SSD's own SMART Data Units Written counter and found it matched Windows' numbers, which is the check worth repeating before concluding your drive is being worn out.
Affects All reported versions · Status: workaround only
If none of this worked
If Resource Monitor does not show NVDisplay.Container.exe writing to nvlog.nvlgstg, none of this applies. Constant background writes on an idle PC also come from Windows Search indexing, SysMain, antivirus scanning, Windows Update, browser caches, Steam shader pre-caching, cloud-sync clients and game launcher logging — Resource Monitor's Disk tab names the process in every one of those cases. If the writer is atieclxx.exe rather than an NVIDIA process, that is the AMD External Events Utility bug, which has its own separate cause and fix, and which can be running on a PC with an AMD processor even if the graphics card is NVIDIA. And if your drive reports falling health with no process writing to it, check its SMART data with the manufacturer's tool before blaming a driver.
Common questions
- Is this actually damaging my SSD?
- It is using up write endurance you paid for, with no benefit to you, but the scale matters and the honest answer depends on the rate you measure. A consumer 1 TB NVMe drive is typically rated for a few hundred TB of writes. At the 3 GB an hour measured on 621.14 — about 26 TB a year if the PC ran constantly — you are consuming a noticeable fraction of that rating for nothing, which is worth fixing. At the much lower rates reported on older drivers it is closer to an annoyance. Measure your own drive's Data Units Written over a few hours before deciding how urgent this is, and bear in mind that Windows' per-process write counters include cached writes and read higher than what actually reaches the drive.
- Can I just delete the nvtopps folder, or block the file?
- Deleting the whole folder is not reported to help, because the service recreates what it needs and you lose nothing it was keeping. Making the file read-only is not reported to work either. The approaches that are actually reported to work are the three above: clear the file and let it regrow, change driver version, or stop the service. If you have seen a permissions-based trick for the AMD equivalent, note that it depends on specifics of that bug and nobody has published an equivalent analysis for this NVIDIA one.
- Does the NVIDIA App's telemetry setting stop it?
- No. The user reporting about 30 GB an hour on 621.24 already had telemetry turned off in the NVIDIA App, and the Dell XPS reporter did not have the NVIDIA App installed at all. Older guidance about disabling NVIDIA telemetry services and scheduled tasks was written for drivers that exposed them separately; current drivers do not, so there is nothing there to switch off.
- Should I use DDU and reinstall the same driver?
- Three users report doing exactly that, one of them three times, with no improvement. A clean reinstall of the same version does not help because the behaviour is in that version. What is reported to help is changing which version is installed — and NVIDIA's release notes say to do that through Add and Remove Programs followed by the older setup.exe, not through Device Manager or Windows rollback.
Did this fix work?
If a step is wrong, outdated, or did not help, telling us is the fastest way to get it corrected. Reports are reviewed before new articles.
Report a problem with this pageRelated problems
- AMD Radeon driver writes to the SSD constantly at idle (atieclxx.exe)
- Video stutters or the screen goes black in Chrome after the NVIDIA 621.01 driver
- Monitor won't wake from sleep on DisplayPort after an NVIDIA driver update
- PowerToys Mouse Without Borders: "Pairing could not be loaded or updated" after the 0.102 update
- No Sound Over HDMI or DisplayPort on an AMD Graphics Card After a Windows 11 Update
- KB5132061 Won't Install: 0x800f0993, 0x800f0989 and 0x80070306
Sources
NVIDIA · Release notes · checked Nov 15, 2026
- Document RN-08399-621.24_v01, dated November 12, 2026, covers driver version 621.24 WHQL
- Section 3.2 Open Issues in Version 621.24 WHQL lists its issue entry as "N/A" — NVIDIA records no open issues for this driver
- Section 3.1 Fixed Issues lists only Chaos Vantage OptiX Denoiser [6953474] and Windows Photos/Media Player DJI D-Log H.265 colours [6996250], with Fixed Gaming Bugs as N/A
- The document contains no mention of disk writes, SSD writes, log files, nvlog, nvtopps, telemetry or the NVIDIA Display Container service anywhere in its 1431 lines of extracted text
- Section 5.12 states: to reinstall a previous or older NVIDIA graphics driver, do not use the Windows rollback feature, as it will not reliably restore all the previous driver files; instead use Add and Remove Programs to remove the current driver, then install the older driver using setup.exe
- Section 5.13 states that uninstalling the NVIDIA driver using Windows Device Manager may not remove associated files or applications, that Microsoft has confirmed this behaviour is by design, and recommends Add and Remove Programs
- GeForce GRD 621.14 Feedback Thread (Released 11/4/26)Community report
NVIDIA GeForce Forums · Forum · checked Nov 15, 2026
- A detailed bug report in this thread names NVDisplay.Container.exe, service "NVIDIA Display Container LS", continuously rewriting C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg while the PC is idle
- The same report calls it a regression new in 621.14 and states that a clean install of 621.01 is not affected: nvlog.nvlgstg grows about 0.5 KB/min and the process writes under 2 MB per 5 minutes on 621.01, against about 325 KB/min and 515 MB per 5 minutes on 621.14 under the same conditions
- Over a 5-minute idle measurement the process accounted for 515 MB of write I/O; after stopping the service, deleting nvlog.nvlgstg and restarting the service it dropped to 48 MB, a 91% reduction, and total C: drive writes fell from 270 MB to 145 MB
- The reporter states the SSD's SMART "Data Units Written" counter matches the writes Windows reports, and estimates about 3 GB per hour from this process alone at idle
- The same report notes that a similar issue affecting nvtopps.db3 was fixed in driver 471.96 in 2021
- A second, independent user in the thread (RTX 3090, Ryzen 5900X) reports the same file being written continuously, measured over 3 GB of log writes in 10 minutes with Process Monitor, and says writes rise with activity such as video on a second monitor while gaming
- That second user reports the log writes becoming heavy enough that games and video stutter and mouse movement is affected, that the file stays around 20 MB because it is truncated and rewritten, that three clean reinstalls with DDU did not help, and that reverting to the previous driver in the branch reduced writes to 260 KB over a 1-hour test
- Continuous writing of gigabytes to SSD to nvtopps file, 621.24Community report
NVIDIA GeForce Forums · Forum · checked Nov 15, 2026
- A user reports the behaviour still present on driver 621.24, writing about 30 GB per hour and 70 GB or more over a long session
- The same user reports that each press of Alt+Tab to switch program adds roughly 500 MB to 1 GB of disk writes
- The user states telemetry is disabled in the NVIDIA App settings and the writes continue regardless
- The user reports that restarting the service and then restarting the system did not stop the writes
- Driver excessively writing to nvlog.nvlgstgCommunity report
NVIDIA GeForce Forums · Forum · checked Nov 15, 2026
- Eight or more distinct users report the same driver log being written excessively, on an ASUS ROG Zephyrus M16, a Samsung Galaxy Book4, a Razer laptop, an MSI Creator, and an ASUS TUF with an RTX 4070
- One user names the path C:\ProgramData\NVIDIA Corporation\nvtopps\nvtopps.log and reports that installing the driver from Windows Update instead of the NVIDIA website avoided it
- One user reports roughly 1 TB written over 10 days
- One user reports disk usage pegged at 100% from boot until the NVIDIA containers are shut down, which fixes it instantly
- One user suggests restarting the "NVIDIA Display Container LS" service or setting it to start manually
- One user asserts that NVDisplay.Container.exe is used for telemetry and so is not needed, which is the claim this article corrects
- The thread runs for about two years with no reply from NVIDIA
- Constant disk writes by NVIDIA processCommunity report
Microsoft Q&A · Forum · checked Nov 15, 2026
- The original poster reports constant disk writing from NVDisplay.Container.exe after updating to driver 471.68, and states the process is started by the service "NVIDIA Display Container LS", which defaults to starting automatically
- The original poster states that after disabling the service the disk activity stops but the NVIDIA Control Panel is unusable — the trade-off this article warns about
- One reply reports 4 TB written to an SSD in 40 days, roughly 100 GB per day
- The accepted answer reports constant rewriting of nvtopps.db3, that NVIDIA fixed that issue in driver 471.96, and confirms 472.12 is clean — a second source for the 2021 precedent
- The original poster notes the driver no longer exposes telemetry as a separate service or scheduled task, so older telemetry-disabling guidance no longer applies
- Excessive NVIDIA log or dump nvlog.nvlgstgCommunity report
Dell Community · Forum · checked Nov 15, 2026
- Two further independent users, on a Dell XPS 15 9570 with a GeForce GTX 1050 Ti Max-Q, report the same path C:\ProgramData\NVIDIA Corporation\nvtopps\nct\nvlog.nvlgstg being written continuously, in January 2025
- A trace in the thread identifies NVDisplay.Container.exe as the writing process, including a single WriteFile call of 10,272,768 bytes
- The original poster reports the file growing past 7 MB within a couple of hours and resetting on restart; a reply reports it reaching 17 MB after about 8 hours
- The original poster reports that a clean install with DDU did not help and that the NVIDIA App was not installed at all, so the behaviour is not caused by the NVIDIA App
- A reply reports that falling back to the older Dell-supplied driver 528.79 avoided the writes, and the thread remains marked unsolved
- NVDisplay.Container.exe is doing many disk writes (about 100GB/day): why, and is there any way to reduce it?Community report
Super User · Forum · checked Nov 15, 2026
- An independent report of about 100 GB per day of writes from NVDisplay.Container.exe on Studio driver 572.16, Windows 11 24H2, with an RTX 3080 laptop GPU
- The same user reports having seen the behaviour on driver 471.41 as well, so it is not confined to one release
- The user notes that the only advice found online was to upgrade the driver, and the question has stood unanswered since February 2025