How do I fix the MSFS graphics device error?
To fix the “Your graphics device has encountered a problem” error in Microsoft Flight Simulator, return the GPU to stock settings, install or roll back to a stable graphics driver, disable overlays, and reduce VRAM-heavy settings. In MSFS 2020, also test DirectX 11; MSFS 2024 has no DX11 fallback.
What does the graphics device error actually mean?
The message means the simulator’s DirectX session lost usable access to the graphics device, usually because the driver stopped responding or was reset by Windows. It does not automatically mean that the graphics card is defective.
Common triggers include an unstable overclock or undervolt, a faulty driver installation, an overlay hooking into the renderer, excessive VRAM use, corrupt shader or rolling-cache data, and instability elsewhere in the PC. RAM, CPU and power faults can all present as a graphics-device crash.
| When the error appears | First suspect | Best initial test |
|---|---|---|
| Immediately after a graphics-driver update | Driver regression or damaged shader cache | Clean-install or roll back the driver, then rebuild the shader cache |
| Only with one aircraft or airport | Add-on conflict or unusually high VRAM use | Run in Safe Mode and repeat the flight with default content |
| After several minutes under heavy load | Temperature, clock, power or VRAM pressure | Restore stock settings, cap the frame rate and lower GPU-heavy options |
| Only in VR, with frame generation or under DX12 | Renderer-specific instability | Disable the feature and test the same flight again |
| Before reaching the main menu | Driver, overlay or damaged configuration | Use our startup-specific driver and black-screen checks |
If Microsoft Flight Simulator closes without this exact message, follow the wider checks for random MSFS crashes and device-lost faults instead.
Fix the MSFS graphics device error in this order
Most cases can be resolved without reinstalling Microsoft Flight Simulator or Windows if each change is tested separately.
Establish a clean test: Restart Windows, launch the simulator in Safe Mode if offered, and temporarily remove everything from the
Communityfolder. Use a default aircraft, a standard airport, clear weather and a short daytime flight. Do not delete add-ons; move or rename them temporarily. If the crash occurs while loading a flight, follow our clean-flight isolation process for aircraft, airports and add-ons.Return hardware to stock: Reset GPU core, memory, voltage and power-limit adjustments in any tuning utility, then close that utility. Temporarily remove CPU and RAM overclocks as well, including memory profiles if the system remains unstable. Do not raise GPU voltage or flash its firmware to cure this error.
On a laptop, connect mains power and assign Microsoft Flight Simulator to the high-performance discrete GPU in Windows graphics settings. Do not disable the integrated GPU blindly, as some laptops route their display through it.
Reinstall or roll back the graphics driver: Use the graphics-card manufacturer’s installer and select its clean-install option when available. If the error began immediately after a driver update, roll back to the previous stable release rather than repeatedly reinstalling the same package. Restart Windows after the change.
Disable software that hooks into the renderer: Turn off recording overlays, performance overlays, GPU monitoring displays, ReShade, external frame-generation modifications and similar injectors. Close them fully rather than merely hiding their on-screen panels. Re-enable one item at a time after the simulator is stable.
Test the other rendering path in MSFS 2020: Select DirectX 11 in the simulator’s graphics options, restart it and repeat the same flight. Microsoft Flight Simulator 2024 does not provide the DX11 selector, so driver, add-on and load testing take priority there.
Reduce GPU and VRAM demand: Lower render scaling, texture resolution, clouds, terrain level of detail and object level of detail. Disable frame generation for the test and cap the frame rate below the GPU’s usual maximum so it has some headroom. Our graphics-setting priorities for reducing GPU load explain which options to cut first.
Rebuild caches and repair the installation: Delete and recreate Rolling Cache from the simulator’s data settings, then clear the Windows DirectX shader cache. Make sure the Windows page file remains system-managed and that both the Windows and simulator drives have free space. Use the platform’s repair or file-verification function before attempting a full reinstall; choose Repair before Reset where both are offered.
Check for wider system instability: Monitor GPU temperature, hotspot temperature where reported, fan operation and clock behaviour during a test flight. With the PC switched off, check that the graphics card and its power connectors are secure. If other demanding 3D applications also reset the driver, produce artefacts or black-screen, the fault is no longer specific to MSFS.
This exact dialogue is principally a Windows PC error. If a console edition instead closes to its dashboard, PC driver, DirectX and registry fixes do not apply; fully restart the console, install simulator and system updates, and test without the most recently added content.
Should I use DirectX 11 or DirectX 12?
Use DirectX 11 as a diagnostic and stability fallback in MSFS 2020 when the error occurs under DirectX 12. If the same flight repeatedly works under DX11, the likely cause is the DX12 driver path, frame generation, shader data or the additional load created by the chosen settings.
Changing renderer can rebuild shaders, so some temporary stutter on the first flight is normal. MSFS 2024 uses DX12 without an equivalent DX11 fallback; repeatedly searching for a hidden DX11 switch or copying configuration changes intended for MSFS 2020 will not solve the problem.
Will increasing TdrDelay fix the error?
Increasing the Windows TdrDelay value is not a proper first-line fix because it merely gives a stalled graphics task longer before Windows resets the driver. It can replace a quick crash with a much longer freeze while leaving the underlying driver, hardware or workload problem untouched.
Avoid downloadable registry fixes and arbitrary timeout values. Change graphics timeout settings only when a hardware vendor or Microsoft support procedure requires a specific value for a diagnosed issue.
How do I know whether the graphics card is failing?
Suspect hardware when graphics resets continue at stock clocks across MSFS and other demanding 3D applications, especially if they are accompanied by artefacts, black screens, abnormal temperatures or repeated display-driver resets.
Windows Reliability Monitor may record events such as LiveKernelEvent 141 or 117, but those codes do not identify the defective component by themselves. A weak power supply, unstable RAM, GPU fault or driver problem can generate similar evidence.
If a small GPU underclock appears to stop the crashes, treat that as a diagnostic clue rather than a permanent repair. Once the system is stable, restore add-ons and graphics options one at a time; the first change that brings the error back usually identifies the actual trigger.