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

FS2004 should never restart the whole PC. If Windows reboots, the likely cause is a hidden blue screen, overheating, unstable RAM, a graphics driver or failing power delivery—not FS2004 alone. Disable automatic restart, record any stop code, then test stock FS2004 at a capped frame rate before replacing or reinstalling anything.

Is it a crash to desktop or a full PC restart?

A crash to desktop leaves Windows running; a full restart takes Windows down and points first to a system-level fault.

After an abrupt reset, Event Viewer commonly records Kernel-Power, event ID 41. This confirms that Windows did not shut down correctly; it does not prove that the power supply failed or identify any other cause.

A BugCheck entry or a dump file in C:\Windows\Minidump is more useful because it shows that Windows encountered a blue-screen fault. The absence of a dump is not conclusive: sudden loss of power and incorrect dump settings can both prevent one being written.

Why can FS2004 restart the computer?

Microsoft Flight Simulator 2004 (FS9) can expose an unstable PC, but it should not be able to reboot a healthy one.

FS2004 can keep a processor core busy while simultaneously loading the graphics, sound, memory, scenery, AI traffic and USB input systems. The unlimited frame-rate setting is especially good at creating sustained load. A marginal power supply, blocked cooling path or unstable overclock may therefore fail in FS2004 even when web browsing and ordinary desktop work appear normal.

• Hidden blue screen: Windows restarts so quickly that the stop screen is never seen. Graphics, audio, storage and USB drivers can all be involved.
• Overheating: the reset appears after a fairly consistent period of flying, during dense scenery or in demanding weather.
• Power delivery: the display goes black instantly and the PC starts its boot sequence without creating a dump.
• Unstable RAM or tuning: an overclock, undervolt or memory performance profile works during light use but fails under mixed CPU and graphics load.
• Add-on or peripheral trigger: a particular gauge, scenery package, controller or audio device reaches a faulty driver path. The add-on can be the trigger without being the underlying reason Windows restarts.

How do I fix FS2004 restarting my PC?

The safest fix is to identify whether the reset comes from a blue screen, software trigger, heat, memory or power, changing only one variable at a time.

1. Protect files and record the pattern. Repeated hard resets can corrupt Windows, FS9.cfg and saved flights. Back up important files, then note the aircraft, airport, weather, view, elapsed flight time and connected controllers involved in the failure.
2. Reveal hidden blue screens. Run sysdm.cpl, open the Advanced tab, select Startup and Recovery settings, and clear Automatically restart under System failure. Photograph the next stop code and any named file. This setting cannot prevent an actual loss of power.
3. Check Windows records. Open Reliability Monitor by searching for View reliability history, then examine Event Viewer around the same time. Look for a bug check, hardware error or driver failure immediately before the shutdown. Treat event 41 as a timestamp, not a diagnosis.
4. Create a clean FS2004 baseline. Close FS2004 and rename %APPDATA%\Microsoft\FS9\FS9.cfg to FS9.cfg.old. Start the simulator so it creates a fresh file, then use a default aircraft, default airport, daylight, fair weather and a new flight rather than a saved one. If FS2004 fails before reaching the menu but Windows stays running, use our startup fault checks for configuration files, gauges and modules.
5. Exclude third-party content. Disable recently added scenery through the Scenery Library where possible and test with a default aircraft. Temporarily disable only positively identified third-party modules or graphics wrappers, using backups and their normal removal method. Do not delete default files or download random replacement DLLs.
6. Cap the frame rate. Set FS2004's target to roughly 25–30 FPS instead of unlimited. Lower AI traffic and scenery detail for the test, and compare full-screen with windowed mode. If this stops the reset, the problem is load-dependent; it does not by itself prove that the PC merely needs lower settings.
7. Return hardware to standard settings. Temporarily remove user-applied CPU and GPU overclocks, undervolts and memory performance profiles. Record existing settings before changing them. Stability at stock settings means the previous tuning was not reliable under FS2004's workload.
8. Remove peripheral variables. Disconnect non-essential USB hubs, flight controls, external audio devices and other accessories, leaving the basic keyboard and mouse connected. Reconnect devices one at a time after a stable test.
9. Check the graphics path. Disable overlays, recording hooks and third-party graphics wrappers. If the resets began directly after a display-driver change, roll back to the previous stable driver; otherwise use the driver's clean-install option where available. The newest driver is not automatically the best match for FS2004's older DirectX rendering path.
10. Inspect cooling safely. Check that fans turn and vents are unobstructed. Power off and unplug a desktop before removing accessible dust, and never open a power-supply unit. A laptop that becomes excessively hot or also shuts down during other demanding software needs its cooling system and power adaptor inspected.
11. Test memory and power. Run Windows Memory Diagnostic. A single reported memory error is enough to stop FS2004 testing and investigate the RAM or its settings, although a clean result cannot rule out every intermittent fault. Instant resets without dumps, especially outside FS2004 as well, warrant professional checks of the power supply, adaptor, motherboard and electrical connections.

What if one aircraft, airport or flight condition triggers the restart?

A repeatable trigger is valuable evidence: compare one variable at a time rather than reinstalling everything.

• One aircraft at several default airports: suspect its panel, gauges, sound set, model or a module it loads. Confirm by using a default aircraft under otherwise identical conditions.
• Several aircraft at one airport: suspect airport scenery, mesh, AI traffic or an overlapping scenery area. If the problem followed an installation, use our scenery-specific checks for corrupt BGL files and duplicate airports.
• Only at dusk, night or in heavy cloud: test the graphics driver, effects, replacement textures and wrappers before blaming the aircraft.
• After a similar amount of flying time: heat, gradual memory consumption or weakening power delivery becomes more likely.
• Only with a particular controller or audio device: disconnect it and remove associated background software from the test.
• Every aircraft and airport: concentrate on the graphics driver, fresh FS9.cfg, peripherals, RAM, cooling and power.

Even when removing one add-on stops the failure, a complete PC restart still means Windows, a driver or the hardware handled the trigger badly. A normal add-on fault should produce an error or crash to desktop, not reboot the machine.

Match the evidence to the repair

The lasting repair should follow the strongest evidence, not whichever FS2004 setting happened to be changed last.

• A stop code names a graphics, audio or USB driver: treat that file as a lead rather than absolute proof. Reinstall or roll back the associated driver and repeat the clean baseline test.
• Temperatures rise sharply or a fan stops: repair the cooling problem and restore standard clock settings before running FS2004 again.
• The memory test reports errors: return memory to standard settings and have faulty or incompatible RAM corrected. Do not try to work around real memory errors with simulator settings.
• The PC instantly loses power and produces no dump: investigate the power supply, laptop adaptor, motherboard and thermal protection. Reinstalling FS2004 will not help.
• The PC is stable at stock settings only: the overclock, undervolt or memory profile was unstable, even if it appeared reliable elsewhere.
• Default FS2004 is stable but one add-on always triggers a CTD: remove or reinstall that add-on and any required gauge modules. This is a simulator-content problem if Windows remains running.

Should I reinstall FS2004 or use compatibility mode?

No—neither is a first-line fix for an abrupt whole-PC restart. Reinstallation and compatibility settings can correct damaged simulator files, permission trouble and some display problems, but they cannot repair overheating, unstable RAM or failing power delivery.

Consider reinstalling only after Windows is stable, hardware checks are clean, a fresh FS9.cfg has made no difference and third-party content has been excluded. Back up personal aircraft, scenery and configuration files first, then test the base simulator before returning add-ons in small groups.

Compatibility mode is reasonable when FS2004 will not launch or cannot save settings on a newer Windows installation. Apply one compatibility change at a time. If selecting a mode merely changes how quickly the whole PC restarts, return to the driver and hardware investigation.

Stop testing when hardware warning signs appear

Stop reproducing the restart if you notice a burning smell, electrical crackling, extreme heat, a stationary fan, a swollen component or resets during other software. Power the machine down and arrange hardware inspection; repeated test flights risk file corruption and can worsen a failing cooling or power component.