Why does Microsoft Flight Simulator keep crashing?
Microsoft Flight Simulator usually crashes because of an incompatible add-on, corrupted cache or package, GPU driver trouble, excessive memory use, or unstable hardware. Fix it by testing a clean simulator, updating software, clearing caches, reducing demanding settings, and checking system stability before reinstalling.
What usually causes Microsoft Flight Simulator crashes?
Most crashes to desktop are caused by add-on conflicts or PC stability problems rather than a single universal simulator bug. The point at which MSFS fails is the most useful clue.
| Crash pattern | Areas to check first | Best first test |
|---|---|---|
| Crash during launch or the loading bar | Incompatible package, damaged cache or incomplete update | Start with no third-party content and clear the rolling cache |
| Crash with one aircraft or airport | Aircraft, livery, scenery conflict or memory pressure | Use a default aircraft at a default airport |
| Random crash after several minutes | GPU driver, RAM, overclock, heat, VRAM or background software | Use stock clock speeds and lower graphics demand |
| Crash after a simulator or add-on update | Outdated package or newly introduced driver conflict | Remove recent add-ons and review recent system changes |
| Return to the Xbox dashboard or PlayStation home screen | Optional content, storage pressure or console cache | Remove recent content and perform a full shutdown |
Error codes are clues, not diagnoses. For example, 0xc0000005 is a general access-violation error; it can result from a bad add-on, driver problem, unstable memory or overclock. A graphics-device removed or hung message points more directly towards the GPU driver, graphics API, overclock or VRAM usage.
How do I fix Microsoft Flight Simulator crashing?
Work through these checks in order and retest after each change. Altering everything at once can hide the cause and make a temporary improvement impossible to explain.
Platform matters. MSFS 2020 runs on PC and Xbox, while MSFS 2024 runs on PC, Xbox Series X|S, PS5 and PS5 Pro. Community-folder and GPU-driver fixes apply only to PC; PlayStation troubleshooting applies only to MSFS 2024. We have a separate set of version-specific MSFS 2024 crash checks for that release.
- Record where the crash happens. Note the aircraft, airport, weather, flight phase and whether it fails at the same point. On Windows, Reliability Monitor can show the faulting application or module, although the named module is not always the root cause.
- Restart and update the complete software chain. Fully restart the computer or console rather than resuming from sleep. Install pending simulator, operating-system and installation-platform updates. On PC, update the GPU driver—or roll it back if the crashes began immediately after a driver change.
- Test without add-ons. Use Safe Mode if the simulator offers it after an abnormal exit. Otherwise, move everything out of the active
Communityfolder; our guide to finding the correct Community folder helps when multiple package locations exist. A clean Community folder does not disable Marketplace or other optional packages, so remove or disable recently installed content there as well. - Restore packages in batches. If the clean simulator works, return half the add-ons, retest, and continue dividing the suspect group. Check libraries and dependencies alongside the aircraft or scenery that requires them. Carrying unsupported content between releases is a common problem, so confirm which MSFS 2020 add-ons can be used in MSFS 2024.
- Build a controlled test flight. Select a default aircraft, default airport, clear preset weather and daytime conditions. Temporarily disable live traffic, multiplayer and other streamed features. If this works, add one variable at a time until the failure returns.
- Clear and recreate caches. If MSFS reaches its settings, delete the rolling cache using the simulator's own control and recreate it. A stale cache can reproduce a crash at one location even after the offending scenery has been removed. Clearing the PC shader cache can also help after a graphics-driver change, although the first flight may stutter while shaders rebuild.
- Reduce memory and graphics pressure. Lower render scaling, terrain and object detail, texture resolution and traffic. Cap the frame rate if the GPU remains at maximum load. On PC, try the other DirectX mode where the installed MSFS version provides that choice. Our settings for reducing CPU, GPU and VRAM pressure cover the demanding options in more detail.
- Disable software that hooks into the simulator. Temporarily close overlays, recording tools, hardware monitoring utilities, frame-generation injectors and peripheral-management software. Disconnect non-essential USB devices, especially if the crash began after adding a controller or updating its driver.
- Return the PC to stock stability settings. Remove CPU and GPU overclocks and test without memory overclocking profiles. Check temperatures, available storage and RAM stability. Leave the Windows paging file system-managed; disabling it can cause MSFS to close when committed memory exceeds physical RAM.
- Repair the installation. Use the repair or file-verification function supplied by the installation platform. Back up third-party content first, and test the repaired simulator before restoring it.
Why does MSFS crash only at one airport or with one aircraft?
A repeatable crash tied to one airport or aircraft normally indicates a content conflict, damaged package or local memory spike. Duplicate airport sceneries, an incompatible livery, a missing aircraft dependency and cached terrain from a removed package are frequent causes.
Remove every package affecting that location or aircraft, not just the most obvious one. Clear the rolling cache, restart MSFS and repeat the flight using default content. If the crash occurs only at a large hub with complex weather and traffic, reduce terrain detail, traffic and texture demand before blaming the scenery itself.
Should I reinstall Microsoft Flight Simulator?
Reinstall only after the clean simulator still crashes with default content and stock hardware settings. Reinstallation is slow and often fails to solve add-on, driver, cache or RAM problems.
On PC, remember that uninstalling the launcher may leave downloaded packages or the Community folder elsewhere on the drive. Back up third-party files, follow the platform's removal process, and make sure the new installation is tested before restoring them. Do not casually delete cloud-synchronised profile data, as that can remove control mappings and progress.
On Xbox or PS5, remove recently installed optional content, perform a complete shutdown, confirm adequate free storage and test again before reinstalling. Consoles do not expose a Community folder, so PC-specific package and driver instructions do not apply.