Why does FS2004 restart my PC, and how do I fix it?

FS2004 should never restart the whole PC. An instant reboot usually points to a power-supply, overheating, RAM, graphics-driver or hidden blue-screen fault rather than FS2004 itself. Disable Windows’ automatic restart, record any stop code, then test a clean FS2004 setup at a capped frame rate before changing hardware.

Why FS2004 can expose a PC fault

A user-mode application such as FS2004 normally cannot force a healthy computer to lose power. It can, however, expose an existing fault by loading the processor, graphics card, memory, audio driver and USB controllers together.

Do not dismiss FS2004 because it is old. Running with the frame-rate target set to unlimited can keep a processor core or graphics card busy, while complex scenery, AI traffic and add-on gauges increase the load. A weak power supply, blocked cooling system or unstable overclock may therefore fail during a flight even when ordinary desktop work appears normal.

How can I tell a reboot from an FS2004 crash?

The screen behaviour and Windows records determine which fault you should investigate.

Event Viewer may show Kernel-Power event 41 after an abrupt reset. That entry confirms Windows was not shut down correctly; it does not identify the cause. A bug-check entry or file in C:\Windows\Minidump is more useful because it indicates that Windows encountered a blue-screen fault.

FS2004 PC restart troubleshooting order

Test one change at a time so that a temporary improvement does not conceal the real cause.

1. Protect your files first. Repeated hard resets can corrupt Windows, FS2004 configuration files and saved flights. Back up anything important before reproducing the fault.
2. Reveal hidden blue screens. Run sysdm.cpl, open the Advanced tab, select Startup and Recovery settings, and clear Automatically restart under System failure. If the next failure displays a stop code, photograph or write it down.
3. Check Windows records. Open Reliability Monitor and Event Viewer after the restart. Look for a bug check, hardware error or driver failure immediately before the shutdown, rather than treating event 41 itself as the diagnosis. Our power, temperature, RAM and blue-screen restart workflow explains how to interpret each branch.
4. Create a clean FS2004 baseline. Rename %APPDATA%\Microsoft\FS9\FS9.cfg to FS9.cfg.old, then start FS2004 so it creates a fresh configuration. Test a default aircraft at a default airport in daylight and fair weather. Temporarily deactivate third-party scenery and known add-on modules, but do not remove default files.
5. Reduce the rendering load. Set FS2004’s frame-rate target to about 25–30 FPS instead of unlimited, lower traffic and scenery detail for the test, and run in windowed mode. If that prevents the reset, restore settings gradually; the underlying issue may still be cooling, power or a graphics driver rather than insufficient PC performance.
6. Remove external variables. Disconnect non-essential USB devices, including extra controllers, hubs and audio hardware. Reconnect them one at a time if the simulator becomes stable.
7. Return hardware to stock settings. Disable CPU or GPU overclocks, undervolts and memory overclock profiles temporarily. A setting that passes light desktop use can fail under sustained simulation or graphics load.
8. Inspect cooling safely. Check that fans turn and vents are not obstructed. Power off and unplug a desktop before cleaning accessible dust; never open a power-supply unit. A laptop that becomes unusually hot or shuts down under other 3D applications needs its cooling or power adaptor checked.
9. Test the graphics driver. Remove overlays, recording hooks and third-party graphics wrappers, then install a known-stable driver using its clean-install option where available. A newer driver is not automatically better for FS2004’s older DirectX rendering path.
10. Check memory and power. Run Windows Memory Diagnostic. Any reported memory error must be resolved before further FS2004 testing. If the PC loses power without creating a dump, especially in other 3D applications too, have the power supply, adaptor and motherboard checked rather than repeatedly reinstalling the simulator.

What if one aircraft or airport triggers the restart?

A repeatable restart tied to one aircraft or location should be isolated with a simple comparison matrix.

• Same aircraft, different default airports: suspect that aircraft’s gauges, panel, sound package or model.
• Different default aircraft, same airport: suspect local scenery, mesh, AI traffic or an airport add-on.
• Every aircraft and location: concentrate on the graphics driver, FS9 configuration, peripherals and PC hardware.
• Only after a predictable amount of flying time: temperature, memory exhaustion or power delivery becomes more likely.

Remove or disable the implicated add-on rather than copying replacement DLL files from an unknown source. Even when an add-on is the trigger, a complete PC reset still suggests that a driver or hardware component handled the error badly.

Match the evidence to the fix

The lasting fix should follow the evidence rather than the last FS2004 setting changed.

• Named graphics driver or graphics-related blue screen: clean-install or roll back to a stable driver, remove overlays and test without graphics wrappers.
• Rising temperatures, throttling or stopped fans: clean the cooling path, restore stock settings and repair defective cooling hardware.
• Memory diagnostic errors: return memory to standard settings, then have faulty or incompatible RAM corrected.
• Instant black-screen reset with no dump: investigate the power supply, laptop adaptor, motherboard and electrical connections.
• Stable with default content but not one add-on: remove, reinstall or replace that add-on and any gauge modules it requires.

Should I reinstall FS2004 or use compatibility mode?

No—reinstallation and compatibility mode are not first-line fixes for an abrupt whole-PC restart. They can solve permissions, configuration and display-mode problems, but they cannot repair overheating, unstable RAM or failing power delivery.

If the trouble started after moving FS2004 to a newer Windows installation and the computer does not actually lose power, follow our FS2004 checks for Windows 10 and 11. Reinstall only after the PC is stable, the fresh FS9.cfg test has failed and add-ons have been excluded.

When should I stop testing?

Stop reproducing the restart if you notice a burning smell, electrical noise, a stationary cooling fan, extreme heat or resets outside FS2004. Those signs require hardware inspection; repeated flights risk file corruption and may worsen a failing power or cooling component.