Fix MSFS crashing when switching to VR with checks for OpenXR runtimes, overlays, add-ons, drivers, VRAM pressure and overclocks.
Microsoft Flight Simulator usually crashes when switching to VR because the active OpenXR runtime is wrong, an overlay or add-on conflicts, or the transition exhausts GPU memory. Start the correct headset runtime first, test Safe Mode, lower VR settings, disable optional OpenXR layers, and return CPU, GPU and RAM tuning to stock.
These checks apply to Microsoft Flight Simulator 2020 and 2024 on PC. If the simulator also crashes without VR, establish a stable flat-screen baseline using our general MSFS crash-isolation procedure before troubleshooting the headset transition.
What should I do first when MSFS crashes on Toggle VR?
Test the VR transition with the simplest possible software and graphics configuration.
- Restart the complete VR stack. Reboot the PC and headset, then start the headset software and confirm that tracking and the display work before opening MSFS.
- Select the correct OpenXR runtime. The active runtime must match the software carrying your headset connection. Do not start a second VR platform merely because another setup guide uses it.
- Disable optional OpenXR layers and overlays. Turn off performance overlays, recording hooks, post-processing injectors, foveated-rendering tools and third-party motion-reprojection layers. MSFS supports OpenXR directly and does not require an API translation layer.
- Run MSFS without add-ons. Choose Safe Mode if the simulator offers it after the crash. Otherwise, temporarily rename the
Communityfolder, disable third-party Marketplace content where practical, and use a default aircraft at a modest default airport. - Reduce the separate VR graphics settings. Lower VR render scaling, terrain and object level of detail, clouds and texture resolution. Close browsers, recording software and other GPU-heavy applications.
- Remove unstable hardware tuning. Test the CPU and GPU at stock clocks and voltages. If crashes continue, temporarily disable XMP or EXPO memory profiles as an isolation test.
- Load the flight in 2D, then enter VR. Once the cockpit is stable, use the bound Toggle VR command—commonly
Ctrl+Tabwith the default PC profile. Our correct VR setup and launch sequence covers the normal procedure in more detail.
Change one category at a time and retest. Re-enabling everything together hides which component caused the crash.
Why does MSFS crash only when entering VR?
Switching to VR creates a sudden workload and forces the simulator, graphics driver and OpenXR runtime to establish a new rendering session.
| Symptom | Likely area | Best first test |
|---|---|---|
| Immediate desktop crash after Toggle VR | OpenXR runtime, API layer or overlay | Select the intended runtime and disable every optional layer |
| VR image appears, freezes, then MSFS closes | VRAM pressure or display driver | Lower VR render scaling and texture resolution, then close GPU-heavy applications |
| VR works in Safe Mode | Aircraft, scenery, toolbar panel or other add-on | Restore add-ons in small groups until the crash returns |
| Headset is black but the desktop view still responds | Display routing or runtime handshake rather than a true crash | Follow the headset black-screen checks |
| The entire PC restarts or loses power | Hardware instability, temperature or power delivery | Restore stock settings and check hardware temperatures and power connections |
How do I check for an OpenXR runtime conflict?
Only one OpenXR runtime should be active, and it must recognise the headset before MSFS starts.
Open the software used for your headset connection and set its OpenXR runtime as active. Fully close MSFS and all VR software before changing runtimes, then restart the headset stack. If the problem began after installing a VR utility, remove or disable its OpenXR API layer rather than running several layers simultaneously.
A common mistake we see is changing the runtime but leaving an old overlay or injector loaded in the background. If VR still fails after the crash has been eliminated, use our broader OpenXR and headset troubleshooting checks.
Could the graphics driver or VRAM be causing the crash?
A display-driver fault is likely when the transition reaches the headset briefly and then closes the simulator.
- Install the appropriate graphics driver cleanly and reboot. If the crashes began immediately after a driver change, test the previous stable driver available for the GPU.
- Update the headset software and firmware through its normal platform tools.
- Lower VR render scaling first, followed by texture resolution, terrain level of detail and object level of detail. These changes reduce the allocation spike when the second eye views are created.
- Disable third-party frame counters, capture tools and GPU monitoring overlays while testing.
- Keep the Windows page file system-managed and ensure its drive has free space. VR can expose memory pressure that flat-screen mode does not.
How can I identify the component that crashed?
Windows Reliability Monitor and Event Viewer can distinguish a runtime or driver failure from a generic simulator crash.
Search Windows for View reliability history, open the failed MSFS event and record its faulting module and exception code. You can also check Event Viewer > Windows Logs > Application. A headset-runtime or overlay module points towards the VR stack; a display-driver module supports a clean driver reinstall; the main simulator executable by itself is usually inconclusive.
Should I reinstall Microsoft Flight Simulator?
Reinstallation should be the last step because VR-switching crashes are more often caused by the runtime, driver, add-on or hardware configuration.
First repair or reinstall the headset runtime, test Safe Mode, reset the VR graphics profile and use the launcher platform’s file-verification or repair function. Do not manually delete the Official folder or downloaded content packages as an early troubleshooting step; that can create a much larger download without fixing the conflicting OpenXR component.