Fix Microsoft Flight Simulator crashes after an NVIDIA app update by disabling overlays, repairing the driver and rebuilding shader caches.
Microsoft Flight Simulator crashes after an NVIDIA app update because the update may have changed the display driver, refreshed NVIDIA's overlay, invalidated shader caches or applied a new game profile. Disable the overlay first; if that fails, clean-install or roll back the driver, clear the DirectX shader cache, and retest at stock GPU settings.
This applies to Microsoft Flight Simulator 2020 and 2024 on Windows. The NVIDIA app and graphics driver are separate components: an app update may refresh the overlay without changing the driver, so establish which component changed before rolling anything back.
Why can an NVIDIA update make MSFS crash?
An NVIDIA update can disturb several parts of the graphics stack that Microsoft Flight Simulator relies on.
- Overlay injection: NVIDIA Overlay, Game Filters, recording and performance monitoring hook into the simulator's rendering process. An updated overlay can cause a crash even when the display driver is unchanged.
- Driver regression or incomplete installation: A newly installed driver may contain an MSFS-specific problem, or files from the previous installation may not have been replaced cleanly.
- Stale shader data: Shader caches created by the previous driver can become incompatible after a driver change.
- Changed graphics settings: NVIDIA's game optimisation or a refreshed per-game profile may raise resolution, enable a feature or alter a driver override, increasing VRAM use.
- Marginal GPU stability: A driver change can expose an overclock, undervolt or memory setting that appeared stable with the previous driver.
The timing can also be coincidental. A Community add-on, simulator update or damaged package may have changed in the same period, which is why Safe Mode remains a useful test.
Did the NVIDIA app or the graphics driver change?
The correct fix depends on whether the NVIDIA app, the display driver or both were updated. Check the driver version in the NVIDIA app's Drivers section or under the NVIDIA display adaptor's Driver properties in Windows Device Manager.
| Evidence | Likely cause | Best first test |
|---|---|---|
| Driver version is unchanged | Overlay, filters or app profile | Disable NVIDIA Overlay and revert app-applied settings |
| Driver version changed and other 3D software also fails | Driver installation or GPU stability | Clean-install the driver and use stock GPU settings |
| Crash occurs only with Frame Generation, DLSS or high GPU load | Feature-specific driver problem or VRAM pressure | Disable that feature temporarily and reduce GPU memory demand |
| MSFS opens in Safe Mode | Add-on or content conflict | Test with the Community folder empty |
Errors such as DXGI_ERROR_DEVICE_HUNG, DXGI_ERROR_DEVICE_REMOVED or an nvlddmkm event point towards the graphics path. Our focused graphics-device error diagnosis covers the additional checks for those messages. A generic fault naming only FlightSimulator.exe or ntdll.dll does not prove the NVIDIA driver caused it.
How do I fix MSFS after the NVIDIA update?
Work through these fixes in order and retest after each one. A mistake we see constantly is changing the driver, add-ons, graphics settings and caches together, which hides the actual cause.
- Restart Windows fully. Do not test while an NVIDIA installation is waiting for a restart. Reproduce the crash using the same aircraft, airport and graphics settings where possible.
- Disable NVIDIA Overlay. Turn the NVIDIA Overlay setting off inside the NVIDIA app, including Game Filters, recording and performance monitoring. Merely pressing
Alt+Zand closing the panel does not disable the rendering hook. Close the app and test MSFS again. - Undo NVIDIA graphics changes. Revert any recommended settings the app applied and restore the MSFS per-game driver profile to its defaults. If the simulator reaches its menus, temporarily disable Frame Generation and switch from DLSS to TAA. These are diagnostic changes, not permanent quality recommendations.
- Repair the display driver. If the driver version changed, reinstall that driver using the clean-installation option when offered. This resets NVIDIA profiles, so record any custom settings first. If the same crash began with that exact driver and a clean installation does not help, roll back to the previous known-good NVIDIA driver.
- Clear the DirectX shader cache. Close MSFS, then use Windows Settings under System, Storage and Temporary files to remove DirectX Shader Cache. Restart Windows afterwards. The next flight may stutter while shaders are rebuilt. The MSFS Rolling Cache stores scenery data and is not a substitute for clearing the shader cache.
- Return the GPU to stock settings. Remove overclocks, undervolts, custom power limits and automatic GPU tuning. Disable other recording, monitoring and overlay software for the same test.
- Isolate simulator content. Start MSFS in Safe Mode when offered, or temporarily move the contents of the Community folder elsewhere. Do not delete the add-ons. If Safe Mode works, restore them in small groups until the failing package is identified.
Should I clean-install, roll back or remove the NVIDIA app?
Clean-install the same driver after a failed or incomplete driver installation; roll back only when the driver version changed; remove the NVIDIA app only when its version changed but the display driver did not.
- Clean-install the current driver when other 3D applications also crash, installation was interrupted or driver files appear damaged.
- Roll back one known-good driver when MSFS worked immediately before that specific driver was installed and still fails after a clean reinstall. Use Device Manager's Roll Back Driver option if available, or install the previous NVIDIA-supplied package.
- Remove only the NVIDIA app through Windows Installed apps when disabling its overlay is insufficient and the driver itself never changed. Select the NVIDIA app entry, not the NVIDIA Graphics Driver. MSFS can run without the app.
What if MSFS crashes before the main menu?
A pre-menu crash should be tested with NVIDIA Overlay disabled and MSFS Safe Mode active. If Safe Mode is not offered, temporarily empty the Community folder and retry; our startup and loading checks for Microsoft Flight Simulator cover the remaining package, service and installation causes.
If the simulator opens only after removing the NVIDIA app, reinstalling the whole simulator will not help. The app or one of its overlay features is the relevant variable.
Should I reinstall Microsoft Flight Simulator?
No—reinstalling MSFS should be a last resort because it does not replace the NVIDIA driver, overlay or Windows shader cache. Consider a simulator repair only after testing a clean driver, disabled overlays, stock GPU settings and an empty Community folder.
If the crash has no NVIDIA or graphics-device indicators after those checks, use our broader crash checklist for MSFS 2020 and 2024 to examine memory stability, background software, corrupted content and simulator-specific settings.