Why does Microsoft Flight Simulator 2020 keep crashing?

Microsoft Flight Simulator 2020 usually keeps crashing because of an incompatible Community add-on, corrupted cache or package data, unstable graphics drivers or overclocks, exhausted memory, or software hooking into the simulator. Start in Safe Mode, empty the Community folder, remove overclocks, update Windows and the GPU driver, then test one change at a time.

What usually causes MSFS 2020 to crash?

The timing and location of the crash provide the strongest clues. A crash to desktop, frozen application or Xbox dashboard exit is different from an aircraft collision or overstress event where the simulator remains open; for the latter, use our guide to diagnosing an aircraft crash while autopilot is controlling it.

An error such as 0xc0000005 is only a memory-access exception; it does not prove that the physical RAM is faulty. Likewise, seeing FlightSimulator.exe or a Windows system module in Reliability Monitor rarely identifies the real cause by itself.

How should I troubleshoot repeated MSFS 2020 crashes?

The quickest method is to establish a clean, repeatable baseline and reintroduce variables gradually. Changing drivers, add-ons and graphics settings together may stop the crash, but it leaves you unable to identify what fixed it.

1. Record the trigger. Note the aircraft, livery, airport, flight phase and approximate time before the crash. Repeat the test using a default aircraft, default livery, clear weather and an undemanding airport.
2. Use Safe Mode. After an abnormal shutdown, Microsoft Flight Simulator may offer Safe Mode at the next launch. This is the simulator's own Safe Mode, not Windows Safe Mode, and it disables third-party content for the session. If the flight works there, add-on content is the leading suspect.
3. Empty the Community folder. Move every package somewhere outside Community, then start MSFS normally. Do not place disabled add-ons inside a subfolder of Community, because the simulator may still scan them. Our Community add-on installation and folder guide explains the package structure and common nesting mistakes.
4. Clear the rolling cache. Delete the rolling cache through the simulator's Data settings, restart MSFS and let it create a fresh cache if you use that feature. Test temporarily with online functionality disabled if the crash occurs while new scenery is loading.
5. Return the PC to stock settings. Remove CPU and GPU overclocks, undervolts and aggressive memory profiles. A machine can appear stable in other games yet fail under MSFS because its workload stresses the CPU, GPU and memory together for long periods.
6. Stabilise the graphics driver. Install a stable driver appropriate to the GPU. If crashes began immediately after a driver update, roll back instead. Disable recording, monitoring and performance overlays while testing.
7. Reduce memory pressure. Use a system-managed Windows page file, keep free space on the system drive and lower texture resolution, terrain detail, traffic or render resolution for a test. If DirectX 12 is selected, test DirectX 11; DX11 is a useful fallback when the error mentions the graphics device or the problem appears under heavy GPU load.
8. Repair files last. Use the game platform's verify or repair function before considering a full reinstall. Also complete pending Windows, platform-service and simulator content updates, then reboot rather than relaunching straight away.

If MSFS cannot reach the menu at all, follow the separate startup and launcher troubleshooting sequence; launch failures involve a different set of checks from crashes during a flight.

How do I find the add-on causing the crash?

Restore Community packages in groups until the crash returns, then divide the suspect group in half. This binary-search method is far quicker than testing a large library one package at a time.

1. Confirm the same flight works with an empty Community folder.
2. Restore approximately half the packages and repeat the test.
3. If it crashes, remove half of that group; if it does not, test the other half.
4. Continue until one aircraft, livery, scenery package or shared library remains.
5. Check that package's simulator compatibility and required dependencies before restoring it.

A mistake we see constantly is testing only the main aircraft package while leaving an old livery, sound replacement or shared avionics library installed. Third-party aircraft also fail when a package is nested incorrectly or intended for another simulator version; our add-on aircraft installation checks cover those faults without duplicating them here.

Do not move arbitrary files out of the Official folder as though it were another Community folder. Remove or reinstall Marketplace packages through Content Manager so the simulator can track them correctly.

What if MSFS crashes only at one airport or in one aircraft?

A repeatable crash tied to one location or aircraft nearly always points to content rather than general PC performance. Disable overlapping scenery for that airport, nearby regional enhancements, airport-object libraries, the selected livery and any aircraft-specific modifications.

Test a default aircraft at the suspect airport, then the suspect aircraft at a simple default airport. If only the location fails, investigate scenery; if only the aircraft fails everywhere, investigate the aircraft, livery and its dependencies. If each works alone but not together, memory pressure or an interaction between packages is more likely.

How can I fix MSFS 2020 crashes on Xbox?

Xbox troubleshooting centres on installed content and console state because Xbox does not use the PC Community folder. Fully quit Microsoft Flight Simulator rather than leaving it suspended, restart the console, and test a default aircraft at a simple airport.

• Ensure the simulator and installed content have finished updating.
• Remove the most recently installed Marketplace aircraft, livery or scenery through Content Manager.
• Temporarily disable live traffic, multiplayer and online scenery to isolate streaming-related failures.
• Keep adequate internal storage free for updates and temporary data.
• Reinstall a suspect content package before reinstalling the entire simulator.

Should I reinstall Microsoft Flight Simulator 2020?

A full reinstall should be the final step, not the first. It will not fix an unstable overclock, faulty driver or incompatible add-on that is restored immediately afterwards, and MSFS separates the launcher from its much larger package installation.

Before uninstalling, test with no third-party content, clear the rolling cache, repair platform files and reinstall only the package associated with a repeatable crash. If you do reinstall, preserve the Community folder separately and test the clean simulator before copying any add-ons back.