Fix ReShade crashes in MSFS 2024 by removing bad injectors, presets and overlay conflicts, then checking drivers, DirectX 12 and GPU stability.
ReShade usually crashes Microsoft Flight Simulator 2024 because its graphics hook conflicts with another overlay, an outdated ReShade build or shader fails, the wrong executable/API was targeted, or the GPU driver is already unstable. Remove the hook, prove MSFS launches cleanly, then reinstall ReShade alone and restore presets one component at a time.
How do I stop ReShade crashing MSFS 2024?
The quickest reliable fix is a clean removal followed by a minimal installation with no preset or third-party shaders.
- Uninstall ReShade cleanly. Run the ReShade installer, select the same MSFS 2024 executable and use its uninstall option. If that is impossible, remove only files you have positively identified as ReShade components, such as
ReShade.ini,ReShade.log, thereshade-shadersfolder and its proxy DLL, commonlydxgi.dll. Do not delete every DirectX-named DLL indiscriminately. - Establish a clean MSFS baseline. Restart the PC, disable external overlays and launch a stock aircraft at a default airport. Temporarily moving third-party packages out of the Community folder removes another variable. MSFS Safe Mode disables Community content, but it does not disable ReShade because ReShade loads outside the package system.
- Check that MSFS works without injection. If it still crashes, ReShade is not the only cause. Return any GPU overclock or undervolt to stock and follow our graphics-device crash isolation checklist before reinstalling it.
- Install one stable ReShade copy. Target the executable that runs the simulator’s renderer, not a launcher or shortcut, and choose the installer’s
Microsoft DirectX 10/11/12option rather than OpenGL or Vulkan. Avoid manually changing permissions on protected application folders. Our clean ReShade installation procedure for MSFS 2024 covers the correct target selection in more detail. - Test without a downloaded preset. Launch MSFS with only the basic ReShade installation. If that works, ReShade’s core hook is functioning and the fault is probably in a preset, shader package or add-on component.
- Restore effects gradually. Add the preset first, then enable effects individually. If there are many effects, enable half at a time to identify the failing shader quickly.
A mistake we see constantly is installing ReShade against more than one executable or leaving an old proxy DLL behind after an update. Two hooks, or mismatched files from different ReShade builds, can make MSFS exit before the main menu appears.
What does the crash timing tell you?
The point at which MSFS 2024 exits usually identifies which part of the graphics chain needs attention.
| When it crashes | Likely cause | Best first test |
|---|---|---|
| Immediately after launch | Old or duplicate ReShade DLL, wrong executable, security software blocking injection, or another overlay | Remove ReShade completely and disable every overlay |
| When a flight finishes loading | Preset effect, depth-buffer shader, high VRAM use or unstable GPU settings | Load without the preset and return the GPU to stock settings |
| When one effect is enabled | Incompatible or damaged shader package | Disable that effect and reinstall only its required shader files |
| Only in VR, HDR or with frame generation | An incompatible rendering combination rather than a general MSFS fault | Test in ordinary 2D SDR with frame generation off, then restore features individually |
| After a graphics-driver or overlay update | Changed injection order, damaged driver installation or stale shader cache | Disable the updated overlay and reinstall or roll back the driver |
Can overlays conflict with ReShade?
Yes; multiple programs trying to hook the same DirectX presentation chain are a common cause of ReShade startup crashes.
Temporarily disable the NVIDIA overlay, Xbox Game Bar, Steam or Discord overlays, RTSS/MSI Afterburner display hooks, capture software and VR performance overlays. Test them one at a time rather than disabling several permanently, because the aim is to identify the specific combination that fails.
If the problem began after an NVIDIA software change, use our NVIDIA overlay, driver and shader-cache checks after an app update. Equivalent symptoms on AMD or Intel hardware still justify a clean driver reinstall, especially when MSFS also crashes without ReShade.
Can a ReShade preset crash MSFS 2024?
A preset file normally stores settings rather than executable code, but the shader or ReShade add-on it activates can crash or destabilise MSFS 2024.
- Remove duplicate versions of the same shader from different packages.
- Use only the effects required by the preset instead of installing every available shader collection.
- Avoid add-on-enabled components unless the effect genuinely needs them and the files are trusted; ReShade add-ons can execute code, unlike an ordinary preset.
- Test depth-based effects separately in VR, HDR and frame-generation modes. These combinations may produce missing depth, flickering or a black image even when they do not crash.
A shader compilation error in the ReShade overlay usually disables that effect rather than crashing the simulator. It still identifies the first shader to remove when the crash occurs as a flight loads or a preset becomes active.
Could GPU settings be the real cause?
ReShade can expose an existing GPU or VRAM stability problem because post-processing adds work at the end of every rendered frame.
Return overclocks and undervolts to stock, lower render scaling or texture demand temporarily, cap the frame rate and test without frame generation. If that stabilises MSFS, restore one setting at a time; keeping ReShade while the GPU remains on the edge of stability will only hide the underlying fault.
Clearing the Windows DirectX shader cache and the graphics driver’s shader cache can help after a driver or ReShade change, although the next flight may stutter while shaders are rebuilt. If the simulator remains unstable after ReShade has been removed, you can also regenerate the MSFS 2024 graphics profile rather than reinstalling the whole simulator.
How can I identify the exact ReShade crash?
The ReShade log and Windows crash record usually distinguish a failed effect from a driver-level device loss.
Check ReShade.log, normally stored with the installed ReShade files, and inspect the final operations before the crash. Messages about permissions or failure to load point towards a bad installation; repeated shader errors identify an effect to remove. A DEVICE_REMOVED or DEVICE_HUNG result points more strongly towards the driver, GPU stability or excessive graphics load.
Windows Reliability Monitor or Event Viewer can also show the faulting module. A ReShade proxy or add-on module makes the injection chain the prime suspect, while a graphics-driver module calls for driver and hardware checks. Neither result is absolute: overlays and ReShade share the same rendering process, so one component can cause another to be named in the crash record.
Does ReShade work with MSFS 2024 on Xbox or PS5?
No. ReShade requires PC access to the simulator executable and DirectX injection, so it cannot be installed on Xbox Series X|S, PlayStation 5 or PS5 Pro.
On PC, keep ReShade only if a bare installation remains stable and the crash returns when a specific shader, preset or overlay is restored. If the minimal hook alone repeatedly crashes an otherwise stable MSFS installation, remove it and wait for a compatible ReShade, driver or simulator update rather than repeatedly reinstalling MSFS.