Fix FSX freezes during flights by isolating scenery, aircraft, AI and weather, resetting fsx.cfg, and finding memory or add-on faults.
FSX, including FSX: Steam Edition, usually freezes during flights because scenery, weather, AI traffic or an add-on overwhelms its main thread or 32-bit memory space. Test the same route with a default aircraft and traffic disabled, then isolate scenery and add-ons, reset fsx.cfg, and check Windows Reliability Monitor for the failing module.
Confirm whether FSX is frozen or overloaded
A short stall that recovers is usually workload; an indefinite hang is a fault. FSX may stop repainting its window while loading dense scenery, regenerating weather or processing a large amount of AI traffic, so allow one stalled session time to recover before ending the process.
If the simulator closes and returns to the desktop, it has crashed rather than frozen. Follow our separate FSX crash-diagnosis procedure, which covers faulting modules and crash reports. Also check that FSX is not simply paused and that the Pause on task switch option is not being triggered.
How do I isolate an FSX in-flight freeze?
The fastest diagnosis is a controlled flight using only default content, followed by restoring one category at a time.
- Create a clean baseline. Start a new flight with a default aircraft, default weather theme and no external weather, traffic or utility applications. Set airline, general aviation, road, ship and ferry traffic to zero.
- Repeat the problem route. If the freeze usually happens near a particular airport, fly through the same area. Use a new flight rather than relying only on the original saved flight, which may contain faulty aircraft or weather state.
- Reduce the expensive settings. Lower autogen density, scenery complexity, cloud detail and traffic first. Test a finite frame-rate target as well as Unlimited; do not use several frame limiters simultaneously. Our guide to the FSX settings with the largest performance impact explains which sliders matter most.
- Restore one category at a time. Add the original aircraft, then weather, AI traffic, scenery and external utilities. Fly the same test after each change.
- Record the exact trigger. Note the coordinates, aircraft action, weather update or elapsed flight time. A mistake we see constantly is changing several settings and removing multiple add-ons together, which hides the actual cause.
What does the freeze pattern reveal?
The point at which FSX freezes usually identifies the subsystem that should be tested next.
| Freeze pattern | Likely cause | Next test |
|---|---|---|
| Always at the same location | Airport, scenery, terrain or local AI traffic | Disable scenery covering that area and repeat with all traffic off |
| Only with one aircraft | Gauge, model, sound or aircraft module | Use a default aircraft on the same route |
| After changing a switch or opening a panel | Aircraft gauge or panel module | Load the aircraft without using that panel, then reinstall or remove the package |
| During a weather refresh | Weather utility, cloud load or network-fed data | Use a default static weather theme and close the external weather application |
| After several hours or near a detailed destination | 32-bit memory pressure or an add-on leak | Reduce textures, traffic and scenery, then compare with a default aircraft |
| Frame rate collapses and later recovers | CPU or scenery-loading overload | Reduce autogen, traffic and cloud settings |
Why does FSX freeze at the same place?
A repeatable freeze at the same coordinates usually points to scenery or an AI object being loaded in that area. Disable the relevant add-on entry in the Scenery Library rather than deleting its files, set every traffic slider to zero, and retry with a default aircraft.
Check for overlapping versions of the same airport, especially when an airport package, regional scenery and an AI airport file all modify it. If disabling local scenery fixes the flight, restore the entries individually until the faulty layer is identified. If default scenery also freezes with a clean configuration, repair or verify the simulator files.
Why does FSX freeze on long flights?
Long-flight freezes often result from FSX exhausting its finite 32-bit virtual address space as detailed aircraft, textures, weather, AI and destination scenery accumulate. Installing more physical RAM does not remove that architectural limit.
Use a lighter aircraft as a comparison, reduce high-resolution textures and traffic, and avoid combining the most demanding aircraft, weather and airport scenery in one test. Restarting FSX between flights may clear the symptom, but a freeze that returns after a similar elapsed time with one add-on suggests a leak or repeating update task. See our 32-bit memory diagnosis and practical FSX fixes for the settings and add-ons most likely to consume address space.
Reset fsx.cfg before reinstalling FSX
Resetting fsx.cfg is safer and faster than reinstalling the whole simulator, particularly after years of accumulated graphics tweaks.
- Close FSX and its helper applications.
- Open the configuration location. Enter
%APPDATA%\Microsoftin File Explorer and open the relevantFSXorFSX-SEfolder. If both exist, use the folder whosefsx.cfgtimestamp changes when the simulator runs. - Back up the file. Rename
fsx.cfgtofsx.cfg.old. - Launch FSX. It will generate a clean configuration. Test a default flight before restoring settings or tweaks.
This resets simulator options but does not uninstall aircraft or scenery. If the clean file works, rebuild settings manually instead of copying the old configuration back wholesale.
Use the Windows hang record
Windows Reliability Monitor can distinguish an application hang from a crash and may name the responsible module. Search Windows for reliability history, open the event at the time of the freeze and inspect its technical details; Event Viewer may also contain an Application Hang entry.
A named aircraft, gauge, weather or scenery DLL is useful evidence. Generic Windows modules such as ntdll.dll or KERNELBASE.dll do not, by themselves, prove that Windows caused the freeze. Manually terminated hard hangs may show only an AppHang record with no useful module.
Repair only after the clean test fails
Repair or reinstall FSX only if a default flight still freezes with a new configuration and all optional add-ons disabled. FSX: Steam Edition users can verify installed files, while boxed FSX users should repair the installation and apply the official service packs appropriate to their edition.
Back up deliberately modified default files before verification because they may be replaced. Reinstalling without removing or renaming the old configuration and testing add-ons separately often reproduces the same freeze immediately.
FSX: Steam Edition differences
The diagnostic method is the same in FSX: Steam Edition, but legacy installers may target a boxed FSX folder or register components against the wrong installation. Confirm that the package installer recognises FSX:SE and that its aircraft, gauges, scenery and required components entered the intended installation.
Files appearing under SimObjects do not guarantee that an older aircraft or gauge is fully compatible. Use our guidance on checking FSX: Steam Edition add-on compatibility and installation paths before treating the simulator itself as faulty.