How to fix NVIDIA LocalSystem Container stopped working in Windows?

NVIDIA LocalSystem Container (NvContainerLocalSystem) is a background service of the NVIDIA app, and when it crashes, Reliability Monitor says it stopped working. Windows restarts it on its own, so one entry needs no fix. Open Services first and check that it runs again.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What NVIDIA LocalSystem Container is and what "stopped working" means

NVIDIA LocalSystem Container is the display name of a Windows service whose short name is NvContainerLocalSystem. In the Services window its description reads "Container service for NVIDIA root features", and its startup type is normally Automatic. It runs in the background under the LocalSystem account and serves the NVIDIA app or GeForce Experience, not the graphics driver itself.

"Stopped working" is the wording of Reliability Monitor. It means the service's program closed without a clean stop. The matching entry in Event Viewer says that the service "terminated unexpectedly" and which recovery action Windows takes. The full text of that entry looks like this:

Event Viewer, Windows Logs > System, source Service Control Manager

The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service.

Why NVIDIA LocalSystem Container stops or will not start

Most often the service crashed once, for example during an NVIDIA app or driver update, and Windows restarted it. Less often the service is stopped or disabled and stays down. Rarely the NVIDIA software is damaged or half removed, so the service is missing or fails to start with Error 14109.

NVIDIA has published no article that explains crashes of this service, and we found no known-issue entry for it. NVIDIA does describe failures of its installer as often caused by "an incorrect system state", and its reset for that state is the base of Fix 3.

Windows could not start the NVIDIA LocalSystem Container service: Error 14109

This message appears when you press Start on the service in Services, or after Windows tried to recover it. Microsoft's list of system error codes gives 14109 (0x371D) the name ERROR_GENERIC_COMMAND_FAILED and the text "A generic command executable returned a result that indicates failure."

The message in Services

Windows could not start the NVIDIA LocalSystem Container service on Local Computer.
Error 14109: A generic command executable returned a result that indicates failure.

So Windows did not fail by itself: a helper program reported a failure back. A 2021 security write-up found that NVIDIA's services had a recovery setting that runs C:\Windows\NvContainerRecovery.bat after the service crashes more than 2 times. That fits a command that returns failure, but we could not confirm that current NVIDIA software still uses this file.

How to fix NVIDIA LocalSystem Container stopped working

Fixes 1 and 2 take a few minutes and solve most cases. Fixes 3 and 4 reinstall NVIDIA's software when the service is missing or keeps crashing. Fixes 5 to 7 are general checks for the rare cases that remain.

Fix 1. Check whether Windows already restarted the service

2 minutesNo riskYou found one or a few "stopped working" entries in Reliability Monitor and the PC works normally.

The event text itself says Windows restarts this service 6 seconds after a crash. Before you change anything, confirm that the restart worked and how often the crash happens.

1. Press Win + R, type perfmon /rel and press Enter. Reliability Monitor opens.
2. Select the day with the red mark and find NVIDIA LocalSystem Container in the list below the chart. Note how many days show it.
3. Press Win + R, type services.msc and press Enter.
4. Find NVIDIA LocalSystem Container under the letter N.
5. Read the Status and Startup Type columns. Running and Automatic are the normal values.

For the exact count, open Event Viewer, go to Windows Logs > System, select Filter Current Log and type 7031 in the event ID box. Each entry is one crash.

Fix 2. Restart the NVIDIA container services and set them to Automatic

3 minutesNo riskThe service is stopped, set to Manual or Disabled, or the NVIDIA app or its overlay will not open.

A stopped or disabled service does not come back by itself, and tweak tools or guides on "disabling NVIDIA telemetry" often switch it off. Starting it and restoring Automatic gives the NVIDIA app its background part again.

1. Press Win + R, type services.msc and press Enter.
2. Double-click NVIDIA LocalSystem Container.
3. Set Startup type to Automatic and select Apply.
4. Select Start under Service status and wait until it shows Running, then select OK.
5. Right-click NVIDIA Display Container LS and select Restart.
6. Restart the PC and check both services again.

Step by step with both Windows versions: Check and restart Windows services

Fix 3. Uninstall the NVIDIA app, reset NVIDIA's state and install it again

20 minutesLow riskThe service is missing, fails with Error 14109, or crashes every day.

The service is installed by the NVIDIA app or GeForce Experience. NVIDIA's own reset for a broken install is: uninstall, restart, stop NVIDIA services and processes, delete two Logging keys and install again. A fresh install also writes the service and its recovery settings anew.

1. Right-click Start, open Settings and go to Apps > Installed apps.
2. Find NVIDIA App, select the three dots next to it and select Uninstall. Do the same for GeForce Experience if it is listed.
3. Restart the PC.
4. Run services.msc and stop every service whose name starts with NVIDIA that is still running.
5. Open Task Manager and end the processes whose names start with nv or NVIDIA.
6. Delete the two Logging keys shown below, if they exist (back up the registry first).
7. Open NVIDIA's app page, select Download Now and run the file.

The two keys from NVIDIA's article on installer issues

HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Logging
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NVIDIA Corporation\Logging

If the NVIDIA installer itself stops with error 0xE6000000, your card needs a different app version: How to fix NVIDIA Installer cannot continue error code 0xE6000000.

Fix 4. Reinstall the NVIDIA graphics driver

20 minutesLow riskNVIDIA Display Container LS crashes too, the problem began after a driver update, or Fix 3 did not help.

The display container belongs to the driver package, and the app's service talks to the driver. A driver that was updated only in part leaves the two out of step, and a full driver reinstall puts matching files back.

1. Right-click Start and select Device Manager.
2. Expand Display adapters, right-click your NVIDIA card and select Uninstall device.
3. Tick Attempt to remove the driver for this device and select Uninstall.
4. Restart the PC. The screen runs with a basic Windows driver for now.
5. Run the driver file you downloaded and choose the option with the NVIDIA app.

Updating, rolling back and reinstalling drivers on Windows 11 and Windows 10: Update, roll back or reinstall a driver

Fix 5. Find a program that clashes with NVIDIA's software with a clean boot

30 minutesLow riskThe crash happens at the same moment every time, for example when one game, overlay or monitoring tool starts.

A clean boot starts Windows with only Microsoft's services and no startup apps. If NVIDIA LocalSystem Container stops crashing then, a background program causes it, and you find it by turning items back on in halves.

Leave the NVIDIA services on during the test: in the Services tab of System Configuration, tick the NVIDIA entries again after Disable all. Do not tick Safe boot on the Boot tab, because Safe Mode loads no NVIDIA driver at all.

1. Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
2. Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.

   

3. Disable the remaining services. Select Disable all, then select Apply.
4. Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.

   

5. Disable the startup apps. On the Startup apps tab in Task Manager, select each item whose status is Enabled and select Disable. Write down or take a screenshot of the items you disable: you need the list to turn them back on.

   

6. Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
7. Restart and test. Restart the PC. Windows now starts in a clean boot environment: try again the thing that failed (run the app, install the update, uninstall the program).

These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to perform a clean boot in Windows

Fix 6. Install pending Windows updates

15 minutesNo riskWindows Update shows waiting updates, or several services crash besides the NVIDIA one.

A half-installed update can leave system parts that services rely on in a mixed state. Installing what is waiting and restarting finishes it.

1. Right-click Start, open Settings and select Windows Update.
2. Select Check for updates, or Install all if updates are waiting.
3. Restart the PC when asked, then check the NVIDIA service again.

Windows 10 left support on 14 October 2025, so keep it updated as far as Windows Update still offers. If Windows Update is stuck: Run the Windows Update troubleshooter

Fix 7. Repair Windows system files with DISM and SFC

20 minutesNo riskOther services crash too, or the fixes above did not stop the crashes.

NVIDIA does not name this step for its service. It makes sense when several services crash, because then the shared Windows parts, not NVIDIA's files, are the likely cause.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

   

2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

   

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

   

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

   

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

If NVIDIA LocalSystem Container still crashes

Look at what happens at the same second as the crash. Reliability Monitor and the Application log often name the program file that failed, which tells you whether it is NVIDIA's own file or something that hooked into it.

1. In Reliability Monitor, double-click the NVIDIA entry and read Faulting Module Name or the technical details, if they are shown.
2. In Event Viewer, open Windows Logs > Application and look for an Application Error entry at the same time.
3. Open the service's Properties > Recovery tab and note what is set for each failure.
4. Note your NVIDIA app and driver version and your Windows version (run winver).

• What to send to NVIDIA support: the 7031 entries, the Application Error entry, the recovery settings and the versions above. NVIDIA's support page offers a chat and a question form.
• When the faulting module is not NVIDIA's: the named program is the cause. Update or remove it, then test again.
• When it is hardware: if the PC also freezes, the screen goes black or Reliability Monitor shows hardware errors, the service is a victim. Test the memory with How to test your RAM with Windows Memory Diagnostic and check the card's power and seating.

How to keep NVIDIA LocalSystem Container from crashing again

Frequently asked questions

What is NVIDIA LocalSystem Container?

It is a background service that NVIDIA's software installs on PCs with an NVIDIA graphics card. Its short name is NvContainerLocalSystem, and in the Services window its description reads "Container service for NVIDIA root features". It runs under the LocalSystem account and serves the NVIDIA app or GeForce Experience, for example the overlay and updates. It is not the graphics driver itself: the driver has its own service, NVIDIA Display Container LS. If you never installed the NVIDIA app or GeForce Experience, you may not have this service at all.

Do I need NVIDIA LocalSystem Container running?

You need it if you use the NVIDIA app or GeForce Experience. Without it the app's background features do not work. Your games and the screen keep working without it, because the graphics driver runs on its own. We could not find an NVIDIA list of exactly which features stop, so the safe advice is to leave it on Automatic. If you never open the NVIDIA app, uninstalling the app is a cleaner choice than disabling its service.

Is it okay to disable NVIDIA LocalSystem Container?

It is possible, and Windows will not break, but it is not a fix for a crash. Users on NVIDIA's forum report that some NVIDIA app hotkeys stop working when it is disabled, and one user on Microsoft's forum reports that disabling it brought back Discord notification banners. Those are user reports, not NVIDIA statements. If you disable it, set it back to Automatic before you update the NVIDIA app, because a stopped service can make the update fail. To turn it on again, use Fix 2.

The NVIDIA LocalSystem Container service terminated unexpectedly. Should I worry?

Not if it happened once or twice. This is event 7031 in the System log, and its text tells you that Windows restarts the service after 6000 milliseconds. Check in Services that it shows Running again (Fix 1). Worry only when the entries appear every day, when the service stays stopped, or when the NVIDIA app stops working. Then go through Fix 2 and Fix 3. The same event exists for NVIDIA Display Container LS, the driver's own service.

What does Error 14109 mean for NVIDIA LocalSystem Container?

Microsoft's list of system error codes names 14109 (0x371D) ERROR_GENERIC_COMMAND_FAILED: "A generic command executable returned a result that indicates failure." So a helper program that Windows ran for the service reported a failure. On NVIDIA's services this is most likely the recovery command set in the service's Recovery tab, but we could not confirm that for current versions. The fix is the same either way: uninstall the NVIDIA app, reset NVIDIA's state and install it again (Fix 3).

NVIDIA LocalSystem Container is missing from Services. What now?

The service is installed by the NVIDIA app or GeForce Experience, so a missing service means that software is not installed, or was removed only in part. Check Settings > Apps > Installed apps for NVIDIA App. If it is not there and you want its features, install it from NVIDIA's app page. If it is there, uninstall it, restart, and install it again as in Fix 3. If you do not use the app, a missing service is not a problem: the driver still works.

Is nvcontainer.exe a virus?

The real nvcontainer.exe is NVIDIA's program behind the NVIDIA container services. To check yours, open the service's Properties and read Path to executable: it should point into an NVIDIA folder under Program Files. We did not confirm the exact folder for every version. A file of that name in a user folder or in Temp is suspicious, and then you should run a full scan with Microsoft Defender: How to scan for malware with Microsoft Defender. NVIDIA patched a 2021 security flaw in GeForce Experience version 3.22 that involved this service, so keep NVIDIA's software up to date.

What is the difference between NVIDIA LocalSystem Container and NVIDIA Display Container LS?

NVIDIA Display Container LS belongs to the graphics driver package. NVIDIA LocalSystem Container belongs to the NVIDIA app or GeForce Experience. In the Services window they sit next to each other, both start automatically and both can show up as stopped working in Reliability Monitor. When only the LocalSystem Container crashes, start with the app (Fix 3). When the Display Container crashes too, the driver is the more likely cause, so reinstall the driver (Fix 4).

What about the NVIDIA NetworkService Container?

This page is about the LocalSystem Container. Older GeForce Experience versions also installed NVIDIA NetworkService Container, a separate service. If you still have it and it will not start, the most likely cause is the same as here: an old or damaged GeForce Experience install. Uninstall GeForce Experience and install the current NVIDIA app instead, as described in Fix 3. If the old service is gone after that, nothing else is needed, because the current app does not depend on it as far as we could confirm.

How do I stop the NVIDIA container?

To stop it for this session, open Services with services.msc, right-click NVIDIA LocalSystem Container and select Stop. It starts again after the next restart because its startup type is Automatic. To stop it for good, set the startup type to Manual or Disabled, which also stops the NVIDIA app's background features. Stopping it does not affect your games or the picture on the screen. If the container uses a lot of processor time, update the NVIDIA app first rather than turning it off.