Why do Microsoft Flight Simulator 2024 and 2020 crash?

Microsoft Flight Simulator 2024 and 2020 usually crash because of incompatible add-ons, damaged cache or package data, graphics-driver faults, unstable CPU, GPU or RAM tuning, exhausted memory or VRAM, or conflicting software. Test a default flight with third-party content removed and stock hardware settings, then restore one variable at a time.

Is this a simulator crash, freeze or aircraft failure?

A software crash closes Microsoft Flight Simulator, leaves it permanently unresponsive or returns a console to its home screen. A collision, overstress event or other in-simulator aircraft failure is different: MSFS remains open and displays the result.

A brief stutter while scenery loads is not necessarily a crash. If the application eventually recovers, investigate performance, memory and streaming load; our checks for MSFS 2020 freezing during a flight help separate a recoverable hang from a crash to desktop.

If the whole PC blue-screens, freezes hard or restarts, suspect a low-level driver, RAM instability, temperature or power-delivery problem before blaming the simulator.

Why do MSFS 2024 and 2020 crash at random?

Most apparently random crashes have a repeatable trigger, such as one aircraft, airport, weather state, online service or level of system load.

• Incompatible third-party content: aircraft, liveries, airports, scenery, utilities and shared libraries can break after a simulator update. Do not copy MSFS 2020 packages into MSFS 2024 unless their compatibility has been confirmed.
• Graphics-driver trouble: a damaged installation, problematic driver update or failure under sudden GPU load can close MSFS without a useful error.
• Marginal hardware stability: CPU or GPU overclocks, undervolts and borderline XMP or EXPO memory profiles may work elsewhere but fail during a long, demanding MSFS flight.
• Damaged data: interrupted updates, incomplete packages and a corrupted rolling cache can produce loading or location-specific crashes.
• Memory and VRAM pressure: complex aircraft, dense airports, high-resolution textures, traffic, VR and long sessions can consume the remaining headroom.
• Software conflicts: overlays, capture tools, controller remappers, RGB suites, monitoring tools and companion applications can hook into the simulator.
• Online or simulator faults: live weather, traffic, multiplayer, photogrammetry or a service-side problem may be responsible when default content is otherwise stable. Reinstalling cannot correct a remote service failure.

What does the timing of the crash tell you?

The stage at which Microsoft Flight Simulator crashes is one of the strongest clues to its cause.

How do I fix Microsoft Flight Simulator crashes?

The fastest reliable method is to establish one clean, repeatable test flight and change only one variable between runs.

1. Record the exact trigger and complete updates. Note the aircraft, livery, airport, weather, online features, flight phase and approximate point of failure. Fully restart the PC or console, then allow simulator, installed-content, operating-system and installation-platform updates to finish.

   If MSFS 2024 is not updating cleanly, follow our steps for checking and applying MSFS 2024 updates before diagnosing old package files.

2. Use the simulator’s Safe Mode. After an abnormal shutdown, MSFS may offer Safe Mode at the next launch. This is not Windows Safe Mode; it is a diagnostic session that disables most third-party simulator content.

   On PC, close MSFS and move every package outside the active Community folder as an additional check. Do not place disabled packages in a subfolder inside Community, because the simulator may still scan them. Its location varies with the installation platform and any custom packages path.

   Safe Mode is not a permanent repair. External utilities, overlays and hardware software may still run, while Marketplace and other optional packages may need to be disabled separately through the simulator’s content controls.

3. Create a simple baseline flight. Use a default aircraft and livery, a small default airport, clear preset weather and no live traffic, multiplayer or photogrammetry. If this works, restore online services, aircraft and scenery separately rather than all at once.

4. Return the PC to stock settings. Remove CPU and GPU overclocks or undervolts and temporarily disable XMP or EXPO. MSFS stresses the processor, graphics card and memory together, so tuning that survives other games can still be unstable here.

   Check temperatures and storage space as well. If stock settings stop the crashes, treat the tuning, cooling or hardware stability as the fault rather than concealing it by lowering an unrelated simulator option.

5. Stabilise the graphics driver. Install pending Windows updates and an appropriate GPU driver. If crashes began immediately after a driver update, return to the previous stable release; otherwise use the driver’s clean-install option instead of repeatedly installing over the existing package.

   After changing drivers, clearing the PC shader cache can help if stale compiled data is involved. Expect temporary stuttering while shaders rebuild.

   In MSFS 2020, test DirectX 11 if DirectX 12 is selected, especially when an error says the graphics device was removed or hung, or the failure appears under heavy GPU load. MSFS 2024 does not provide the same DirectX 11 fallback.

6. Close overlays and external utilities. Shut down recording overlays, frame counters, monitoring tools, frame-generation injectors, RGB and motherboard suites, camera tools, controller remappers and companion applications. Disconnect non-essential USB devices while retaining the controls needed for the test.

7. Reset cached and online data. Delete the rolling cache through the simulator’s data settings, restart MSFS and leave the cache disabled for a short test. A stale cache can keep reproducing a location-specific crash even after suspect scenery has been removed.

   Test preset weather, offline traffic, no multiplayer and no photogrammetry. Restore each service in a fresh session so a transient online problem is not confused with damaged local files.

8. Preserve memory and VRAM headroom. Lower texture resolution when VRAM is tight, terrain and object detail when dense scenery is the trigger, and traffic or cockpit-display demand in CPU-heavy situations. Reducing render scaling can ease GPU load, while a frame-rate cap may help when the graphics card remains at maximum utilisation.

   Keep adequate free space on the Windows and simulator drives. Do not disable the Windows page file while diagnosing crashes; a system-managed page file is the safest baseline.

9. Repair or verify the installation. Use the repair or verification function supplied by the platform through which MSFS was installed. Verification may not inspect every separately downloaded or streamed package, so one damaged aircraft or airport can remain afterwards.

   Do not move arbitrary files out of the Official folder as if it were another Community folder. Remove or reinstall optional and Marketplace packages through the simulator’s content controls so their installation state remains tracked.

10. Restore add-ons in controlled batches. Add aircraft, scenery, utilities and liveries in small groups, repeating the exact test after every change. A mistake we see constantly is copying an entire MSFS 2020 Community folder into MSFS 2024 and assuming every package remains compatible.

How can I identify which add-on is crashing MSFS?

A half-split test isolates a faulty add-on much faster than restoring packages individually.

1. Move every package outside Community while MSFS is closed and confirm that the exact crash no longer occurs.
2. Restore approximately half the packages and repeat the same aircraft, airport and conditions.
3. If it crashes, divide the restored group again. If it remains stable, test the other half.
4. Continue until one aircraft, livery, scenery package, utility or shared library remains.
5. Check the isolated package’s simulator compatibility, folder structure and required dependencies before restoring it.

Use the known trigger for every run. A short flight elsewhere proves little when the original failure occurred while loading a particular airport or operating one aircraft system.

Do not test only the main aircraft while leaving an old livery, sound replacement, panel modification or shared avionics library installed. If an aircraft crashes while loading or immediately after selection, use our aircraft-selection crash checks for MSFS 2024 to isolate liveries, shared avionics, streamed content and damaged models.

Why does MSFS crash with one aircraft or airport?

A failure tied to one aircraft or location usually indicates damaged content, a dependency problem or a package conflict rather than a general installation fault.

For an aircraft-specific crash, remove its liveries, sound and panel modifications plus any utility that connects specifically to it. Update the aircraft and all required dependencies together, then test it at a simple default airport. A crash triggered when avionics or another aircraft system starts can involve WebAssembly content; our WASM add-on troubleshooting steps cover that narrower failure.

For an airport-specific crash, disable every package covering the airport and surrounding area, including duplicate airport versions, regional enhancements, object libraries, old aerial imagery and overlapping scenery. Clear the rolling cache, restart MSFS and test the default airport before restoring the suspect package without other local scenery.

Cross-testing separates the causes: fly a default aircraft at the suspect airport, then the suspect aircraft at a small default airport. If only the location fails, investigate scenery; if the aircraft fails everywhere, investigate its package and dependencies. If each works alone but not together, suspect package interaction or insufficient memory and VRAM headroom.

Why does MSFS crash only with live weather or online data?

A crash that disappears with preset weather and online services disabled usually involves cached data, a transient service problem, network software or an add-on conflict.

Test live weather, live traffic, multiplayer and photogrammetry one at a time across fresh sessions. If MSFS remains stable offline, the core installation is less likely to be damaged. Leave the failing service disabled and retest later before changing unrelated drivers or reinstalling the simulator.

What do “Your last session ended unexpectedly” and 0xc0000005 mean?

Neither message identifies the root cause of a Microsoft Flight Simulator crash.

“Your last session ended unexpectedly” means only that the previous simulator process did not close normally. Choose Safe Mode after an unexplained crash to desktop; Normal Mode is reasonable if you deliberately ended the process or know the interruption came from a power cut or system restart.

The error 0xc0000005 is a general memory-access violation, not proof that physical RAM is faulty. It can result from an add-on, driver, unstable overclock or memory problem. Likewise, seeing FlightSimulator.exe or a Windows system module in Reliability Monitor rarely identifies the real culprit by itself.

A graphics-device removed or hung message points more directly towards the GPU driver, graphics API, GPU tuning or VRAM usage. Use the timestamp and crash pattern to correlate any report with the aircraft, airport and system load at the time.

How do I stop MSFS crashing on Xbox or PlayStation?

Console troubleshooting follows the same clean-content principle but omits PC-only driver, Community folder, overclock and page-file steps.

MSFS 2024 is available on Xbox Series X|S, PlayStation 5 and PS5 Pro. MSFS 2020 remains a PC and Xbox title and was never released on PlayStation.

• Fully close the simulator instead of resuming a suspended session, then perform a complete console restart.
• Complete console, simulator and installed-content updates before testing.
• Clear the simulator’s rolling cache and test without live weather, multiplayer, traffic and photogrammetry.
• Disable or remove the most recently installed optional aircraft, livery or scenery through the simulator’s content controls.
• Use a default aircraft at a small default airport to establish a baseline.
• Keep adequate storage free for updates and temporary data.
• Reinstall a suspect content package before reinstalling the entire simulator.

Should I reinstall Microsoft Flight Simulator?

A full reinstall is justified only when MSFS still crashes in a clean state after repair, driver, cache and hardware-stability checks have failed.

Consider reinstalling when:

• platform repair or verification repeatedly reports or fails to correct damaged files;
• an interrupted update leaves packages that cannot be repaired or removed normally;
• the simulator crashes with default content, stock hardware settings and no external utilities;
• the package location or its permissions appear damaged.

A platform uninstall may leave downloaded packages, the Community folder or synchronised settings behind. MSFS 2020 also separates its launcher from the much larger package installation, so removing the launcher alone may not create a clean baseline.

Move third-party content aside and note any custom package location before uninstalling. Do not casually delete cloud-synchronised profile data, because doing so may remove control mappings or progress.

Test the new installation before restoring any add-ons. If the clean simulator is stable and the crash returns only after old content is restored, another reinstall will waste time; the fault is in the restored package, dependency or utility.