How do I fix random FS2004 crashes on a modern PC?

FS2004 usually crashes randomly on a modern PC because of a corrupt FS9.cfg, an incompatible add-on, an unwritable installation folder, a full-screen or graphics conflict, or 32-bit memory exhaustion. The reliable fix is to establish a clean baseline, then restore the configuration and add-ons one change at a time.

What usually causes random FS2004 crashes?

A crash that feels random is normally tied to a repeatable trigger such as a particular aircraft, airport, display action or level of memory use.

How should I troubleshoot random FS2004 crashes?

The fastest method is to change one variable at a time and retest the same flight or action after every change.

1. Record the trigger before changing anything. Note the aircraft, airport, weather, view and approximate flight time. Check Windows Reliability Monitor for the faulting module: a named third-party DLL is a strong lead, while ntdll.dll or fs9.exe alone does not identify the root cause.

2. Rebuild FS9.cfg. Close FS2004, open %APPDATA%\Microsoft\FS9, and rename fs9.cfg to fs9.cfg.old. FS2004 creates a clean file when it starts again. This resets graphics, sound and control settings, so keep the old file rather than deleting it.

3. Create a clean test flight. Use a default aircraft, a default airport, simple weather and no saved flight inherited from an add-on. Set AI traffic low or off. If this remains stable, the base simulator is probably sound and an add-on or high setting is responsible.

4. Verify the FS9.1 update. FS9.1 is the final official update and should be applied before diagnosing an otherwise clean installation. Modified executables or overwritten core files can stop the update applying correctly, so follow our safe FS9.1 patching and version-check procedure rather than repeatedly running the updater.

5. Disable third-party content in reverse installation order. Start with the most recently installed aircraft, scenery, traffic package, gauge or module. Move only known third-party aircraft and modules out of their folders; do not empty the entire Gauges, Modules or Effects directories because FS2004 itself needs files there.

   Untick suspect scenery in the Scenery Library and restart the simulator. A common mistake we see is an archive extracted one directory too high, or an old installer overwriting shared gauges. Our FS2004 add-on folder and dependency guide explains the correct structure.

6. Test windowed mode and remove graphics hooks. Press Alt+Enter to switch modes, turn off recording overlays and disable any frame limiter, shader injector or graphics wrapper you added. If you installed a local d3d9.dll wrapper in the FS2004 folder, back it up and test without it; never remove the Windows system copy.

7. Check the installation folder. Old add-ons often expect to write inside the FS2004 directory. An installation under Program Files can therefore produce permission and VirtualStore conflicts. A dedicated folder such as C:\FS2004 is usually cleaner; if moving an established installation would break registry paths, use our clean Windows 11 installation procedure instead.

Why does FS2004 crash only at one airport or with one aircraft?

A location-specific or aircraft-specific crash almost always points to add-on content rather than Windows itself.

For an aircraft crash, test its components separately where possible: panel and gauges, model, sound, effects and flight-dynamics files. A missing gauge usually leaves a blank instrument, but a badly compiled or incompatible gauge can close the simulator during aircraft selection or panel loading.

For a crash near one airport, disable that scenery layer and any overlapping regional scenery, mesh or AI traffic package. Duplicate airport files may place conflicting facilities in the same area, while a malformed scenery or traffic BGL can fail only when FS2004 reaches its loading radius. Reinstalling the entire simulator will not repair a defective add-on.

Can FS2004 run out of memory on a modern PC?

FS2004 remains a 32-bit application even on a 64-bit computer with abundant RAM, so dense add-on combinations can exhaust its finite virtual address space.

Memory pressure is likely when a flight is stable with default scenery but crashes after several hours, during approach to a detailed hub, or after switching between several complex aircraft. Reduce the heaviest contributors first:

• AI aircraft and traffic density
• Autogen and scenery complexity
• Large cloud, ground and aircraft textures
• Overlapping regional scenery packages
• Complex panels containing many third-party gauges

Unofficial large-address-aware modifications alter the executable and are not a first-line fix. They can conflict with patching or modified executables, and they cannot repair a faulty gauge or BGL. Establish a stable clean simulator before considering any executable modification, and keep an untouched backup.

Does compatibility mode stop FS2004 crashing?

Compatibility settings sometimes help, but applying several at once makes the real fault harder to identify.

Test windowed mode first, followed separately by Disable fullscreen optimisations and then an older Windows compatibility mode. Running as administrator is useful as a permissions test, but a writable installation folder is a better permanent solution. Return CPU, GPU and memory overclocks or undervolts to stock while testing.

Do not copy random UIAutomationCore.dll, d3d9.dll or other DLL files from an FSX troubleshooting guide. FSX fixes are not automatically valid for FS2004, and an unknown DLL can create another crash or security risk. If the simulator never reaches the menu rather than crashing during flight, use our modern-Windows startup, disc-check and configuration fixes.

When should I reinstall FS2004?

Reinstall only when FS2004 still crashes with a rebuilt FS9.cfg, default aircraft and scenery, no third-party modules, and conservative graphics settings.

Back up add-ons and saved material first. An uninstall may leave the old configuration and third-party folders behind, so rename those leftovers before installing a genuinely clean copy outside Program Files. Run the base simulator once, apply FS9.1, test again, and then restore aircraft, scenery and modules in small groups until the faulty component reveals itself.