Why does FSX crash at 100% loading, and how do I fix it?

FSX usually crashes at 100% because the progress bar has finished loading scenery but the simulator fails while creating the aircraft, gauges, weather, AI traffic or 3D view. Test a stock aircraft at a default airport, then isolate add-ons; if every flight fails, rebuild FSX.cfg and repair the installation.

What does 100% loading mean in FSX?

In both Microsoft Flight Simulator X and FSX: Steam Edition, 100% means the loading counter has finished, not that the flight has successfully started. FSX still has to initialise the cockpit, gauges, traffic, weather and rendered world before displaying the flight.

The percentage therefore does not identify the faulty component. The pattern of the crashes is more useful:

How do I isolate an FSX crash at 100%?

The fastest diagnosis is to establish one clean flight and then change one variable at a time.

1. Test a clean baseline: create a new Free Flight using a stock aircraft, an uncomplicated default airport, daytime, clear weather and no AI, road or boat traffic. If it loads, the core simulator is working and one of the removed variables is responsible.
2. Stop loading the saved situation: do not reuse the last flight or a custom default flight. A saved .FLT can reference an aircraft, airport or weather file that has been removed. If FSX automatically launches the broken flight before showing its opening screen, rebuild FSX.cfg as described below.
3. Change one item per test: try the problem aircraft at the clean airport, then the stock aircraft at the problem airport. This separates an aircraft fault from a scenery fault without guessing.
4. Inspect the aircraft: if only one add-on aircraft crashes, temporarily remove its folder from SimObjects\Airplanes and reinstall it. Missing or incompatible gauges, a damaged panel configuration and installation into the wrong nested folder are common causes. Our guide to checking FSX aircraft folders and required gauges covers the expected structure.
5. Disable local scenery: untick the most recently added airport, scenery or mesh area in the Scenery Library, restart FSX and repeat the flight. Disable rather than delete it so that the test is reversible.
6. Remove traffic and live tools: set traffic sliders to zero and close third-party traffic or weather programs. If this fixes the crash, re-enable each package separately; a faulty traffic database or an add-on injecting data as the flight opens can fail at the end of loading.
7. Test for memory pressure: use a less complex aircraft and reduce texture resolution, autogen, scenery complexity and traffic. FSX remains a 32-bit application even on 64-bit Windows, so a demanding aircraft-airport combination can exhaust its address space at 100%. Use our FSX memory-limit fixes if the crash follows scenery density rather than one particular file.

What if every stock flight crashes at 100%?

If every stock aircraft and default airport fails, reset the simulator's configuration and remove third-party startup modules before reinstalling anything.

1. Back up and rebuild FSX.cfg: close FSX, open %APPDATA%\Microsoft and find the active FSX configuration folder. Boxed FSX normally uses FSX; Steam Edition may use FSX-SE or FSX, depending on the installation history. Rename fsx.cfg to fsx.cfg.old, then launch FSX so it creates a clean file. Do not copy the entire old configuration back, or the fault may return.
2. Disable launch modules: in the same configuration folder, back up and temporarily rename dll.xml and exe.xml if they exist. If FSX then loads, restore the files one at a time and disable individual third-party entries until the failing module is found.
3. Check Steam Edition paths: old installers may write to the boxed-FSX folder even when Steam Edition is installed elsewhere. They can also install gauges or modules that are unsuitable for FSX:SE. Check our explanation of Steam Edition add-on paths and compatibility problems before reinstalling the add-on.
4. Repair core files: for FSX: Steam Edition, use Steam's installed-files verification. For boxed FSX, use the repair option from the matching installation media and repair or reinstall Acceleration afterwards if it was installed. Verification restores altered stock files but does not remove extra third-party files, so disable suspected add-ons first.
5. Reset the display configuration: an FSX.cfg rebuild resets most graphics options. If the crash returns after restoring settings, leave DirectX 10 Preview disabled and test without overlays, injectors or post-processing tools.

A full reinstall should be the last step. FSX uninstallers can leave configuration files, saved flights and third-party add-ons behind, so reinstalling over those files often reproduces the same 100% crash.

How can I identify the exact file causing the crash?

Windows Event Viewer can reveal which module was active when fsx.exe stopped. Open Windows Logs, select Application and inspect the relevant Application Error for its faulting module name.

• A named third-party gauge or module strongly implicates that add-on.
• terrain.dll or g3d.dll often points towards scenery, terrain data, graphics or memory pressure rather than a damaged copy of that DLL.
• ai_player.dll makes traffic files and AI packages the first things to test.
• ntdll.dll is a generic crash location and does not prove that the Windows DLL itself is corrupt. Do not download a replacement DLL.

If FSX also crashes before the menu or during otherwise normal flights, use our broader FSX crash-isolation checklist to check drivers, permissions, configuration files and system-wide causes.