Fix FS2004 crashes to desktop during flight by isolating memory limits, faulty scenery, aircraft, gauges, AI traffic and configuration errors.
FS2004 usually crashes to desktop during a flight because it exhausts its 32-bit address space or loads a faulty add-on—most often scenery, an aircraft gauge, AI traffic, weather textures or a module. Record where the crash occurs, repeat the flight with default content, then isolate the component instead of reinstalling FS2004 immediately.
Reading the FS2004 crash pattern
The location, aircraft and elapsed flight time usually reveal which part of FS2004 is failing.
| Crash pattern | Likely cause | Best first test |
|---|---|---|
| Always at the same location | Scenery, airport files, terrain or an AI aircraft loading nearby | Disable local add-on scenery and AI traffic |
| Only with one aircraft | Panel gauge, model, sound set or aircraft texture | Repeat the flight in a default aircraft |
| After a long flight or near dense scenery | 32-bit address-space exhaustion | Reduce scenery, clouds, AI and texture load |
| At a similar time on every flight | Scheduled AI traffic, weather update or a leaking gauge | Test with AI disabled and default weather |
| Randomly, including with default content | Damaged configuration, incompatible module, driver or Windows issue | Rebuild fs9.cfg and test without third-party modules |
Check Windows Event Viewer immediately after the CTD under Windows Logs > Application. A named third-party DLL or gauge is useful evidence. Entries naming only fs9.exe, ntdll.dll or another Windows component identify where the crash surfaced, not necessarily what caused it.
What should I test first?
Start with a controlled default flight and restore add-ons one category at a time.
- Record the trigger. Note the aircraft, airport, approximate position, weather, cockpit view and elapsed time. Try the same route again to determine whether the failure is repeatable.
- Create a new flight. Do not reload the original saved flight, because it can retain references to its aircraft, panel, weather and situation files. Use a default aircraft and default weather.
- Remove scenery and traffic from the test. Set airline and general-aviation traffic to zero, then disable suspect scenery through the Scenery Library and restart FS2004. Do not delete scenery folders during diagnosis.
- Undo recent add-ons. Examine anything installed shortly before the crashes began, including files copied into
Modules,Gauges,Effects, shared texture folders or an aircraft panel. Remove only files known to belong to that package. Our guide to correct FS2004 add-on folder placement explains where each component belongs. - Rebuild the configuration. Close FS2004, open
%APPDATA%\Microsoft\FS9, back upfs9.cfg, then rename it tofs9.cfg.old. FS2004 creates a clean file at the next launch. This also resets display and controller settings, so retain the backup. Review any previous edits against our advice on safe FS9.cfg graphics changes and recovery. - Confirm the simulator is patched. Install the official FS2004 9.1 update if the installation does not already have it, while checking that older modules and aircraft remain compatible with the patched executable.
- Test the Windows side. If a completely default flight still crashes, compare windowed and full-screen modes and temporarily disable software that injects overlays. Follow our modern-Windows FS2004 compatibility checks for permissions, configuration and display troubleshooting.
Restart FS2004 between tests. Returning to the flight-selection screen does not guarantee that every aircraft, gauge or scenery resource has been released.
Is an FS2004 out-of-memory error always shown?
No. FS2004 can close to the desktop after exhausting or fragmenting its limited 32-bit address space without displaying an explicit out-of-memory message.
A 64-bit edition of Windows does not turn FS2004 into a 64-bit application. Detailed aircraft, high-resolution textures, dense airport scenery, autogen, clouds and large AI fleets all compete for the simulator’s finite address space. A larger page file may help overall Windows memory pressure, but it does not remove the process limit.
- For crashes near dense cities or airports, reduce scenery complexity, autogen and AI traffic.
- For failures in heavy weather, reduce cloud detail or draw distance and remove replacement weather textures from the test.
- For crashes limited to a detailed aircraft, test its panel, gauges and texture set before reducing settings across the whole simulator.
A Large Address Aware modification can provide extra headroom on compatible 64-bit Windows installations, but it modifies fs9.exe and cannot repair a corrupt gauge or BGL file. Back up the executable and verify compatibility with the installed FS2004 patch and modules before considering it.
Why does FS2004 crash at the same place every flight?
A repeatable geographic crash usually means FS2004 is loading a bad scenery object, airport BGL, terrain file or AI model as the aircraft enters that area.
The offending airport can begin loading well before it becomes visible, so a CTD during descent may still be airport-related. Disable the airport package, its required object libraries and nearby terrain or landclass separately. If the crash disappears with default scenery, use our focused checklist for crashes near add-on airports.
Also test with AI traffic at zero. A damaged AI model or texture can crash FS2004 only when that aircraft is scheduled to appear. Conflicting or malformed airport facility files are another possibility, although duplicate files more commonly cause parking, runway or elevation problems than a direct CTD.
Disabling a scenery library does not remove gauges, effects or textures that its installer copied into shared FS2004 folders. If disabling the scenery solves only part of the problem, check the package documentation and remove its shared files carefully rather than deleting similarly named default files.
Should I reinstall FS2004 after a mid-flight crash?
Reinstall FS2004 only after default aircraft, weather, scenery and a rebuilt configuration still produce the crash.
If the default test works, the core simulator installation is probably sound and reinstalling it will not fix the faulty add-on. If a reinstall becomes necessary, test the patched base simulator first, then restore aircraft, scenery, gauges and modules in small groups. Copying the entire old installation back at once also restores the original fault.