Learn why FSX add-ons cause crashes and isolate faulty aircraft, gauges, scenery or modules without reinstalling the whole simulator.
Add-ons make FSX crash when they load incompatible code, missing gauges or effects, malformed configuration files, conflicting scenery, or more memory than FSX’s 32-bit process can address. Fix the problem by reproducing the crash, disabling the most recently added component, checking the faulting module, then restoring add-ons one at a time.
In FSX and FSX: Steam Edition, the add-on may only be the trigger. A damaged shared gauge, an old startup module or an already crowded memory space can affect several aircraft and airports, so deleting the last aircraft installed is not always the complete fix.
What causes FSX add-ons to crash?
The usual causes are incompatible modules, incomplete installations, damaged files, scenery problems and exhaustion of FSX’s limited 32-bit address space.
- Incompatible gauges or DLL modules: compiled
.gauand.dllfiles run inside the FSX process, so obsolete or incompatible code can close the simulator rather than merely disable the add-on. - Missing or misplaced files: an incorrectly nested aircraft folder, missing dependency or absent shared gauge can break a panel. Missing textures and effects normally produce visual faults rather than a crash, but a compiled gauge with a missing dependency can be fatal.
- Broken startup entries: malformed
dll.xmlorexe.xmlfiles, duplicate module entries and two versions of the same utility can make FSX fail before reaching the main menu. - Faulty scenery or AI content: a malformed BGL, object library or AI model may crash FSX only when the relevant airport or aircraft comes into range. Ordinary scenery overlap is more likely to cause visual or performance problems, so do not assume every duplicate airport is the culprit.
- Memory pressure: complex aircraft, large textures, dense scenery, detailed weather and heavy AI traffic all consume the same finite virtual address space. The crash may occur late in a flight even though every individual add-on works by itself.
- Wrong simulator path or edition: older installers may write files or configuration entries to a boxed FSX installation while Steam Edition is installed elsewhere. Antivirus quarantine and restricted folders can also leave an apparently completed installation missing key files.
How can I find which FSX add-on is crashing?
The fastest method is to create a stock-aircraft baseline, change one variable at a time and use the point of failure to identify the add-on category.
| When FSX crashes | Most likely area to check |
|---|---|
| Before the main menu | Startup DLLs, external utilities, dll.xml, exe.xml or the active fsx.cfg |
| After selecting an aircraft | Aircraft model, panel, compiled gauge, shared dependency or saved default flight |
| During flight loading | Selected aircraft, airport scenery, AI package or weather-related add-on; loading percentages are not universal diagnostic codes |
| Near one airport | Airport scenery, local object library, terrain file or AI aircraft entering range |
| After a long flight | 32-bit address-space exhaustion or an add-on that steadily consumes memory |
- Back up the working files first. Preserve your configuration and add-on records before editing XML files or resetting FSX. Our guide to backing up FSX settings and add-ons safely covers the files worth keeping.
- Build a clean test flight. Use a default FSX aircraft at a default airport with simple weather and low AI traffic. If this works, test the suspect aircraft at that same airport, then a stock aircraft at the suspect airport. This separates aircraft faults from scenery faults quickly.
- Disable the newest add-on. Move an aircraft’s complete folder outside every scanned
SimObjectslocation; merely renaming it insideSimObjects\Airplanesmay not stop FSX scanning it. Disable suspect scenery through the Scenery Library rather than deleting files, and never remove default scenery areas as a test. - Test startup modules separately. With FSX closed, find the configuration directory containing the active
fsx.cfg, back updll.xmlandexe.xml, then temporarily rename those XML files. Their location or parent folder name can differ when boxed FSX and Steam Edition have both existed on the same PC, so identify the active folder by its modification time rather than assuming a path. - Read the Windows crash record. Reliability Monitor or Event Viewer may name a faulting gauge, module or DLL. A named third-party file is useful evidence; generic entries such as
KERNELBASE.dll,ntdll.dllorfsx.exeidentify where Windows recorded the failure, not necessarily the add-on that caused it. - Restore components one at a time. Relaunch FSX after each aircraft, scenery area or startup module is enabled. Restoring several items together destroys the evidence and can hide a conflict between two individually functional add-ons.
- Reset the FSX configuration if needed. Rename the active
fsx.cfgand let FSX create a fresh one. This resets simulator settings and trusted-module records, which is why the backup matters. Do not copy the entire old file back immediately; reapply only the settings you need.
Why does FSX crash only at one airport or with one aircraft?
A repeatable crash tied to one aircraft or location usually means FSX is loading a specific model, gauge, scenery object or AI asset at that point.
For an aircraft-only crash, temporarily select a panel variant without third-party gauges if one is supplied, check that aliases point to an installed aircraft, and confirm that the package is not buried one folder too deep. For an airport-only crash, disable the airport package and its separate object libraries, then retest with AI traffic reduced; a faulty AI model may appear only near busy airports.
What if the crash happens after a long flight?
A late crash in a complex area is more likely to be memory pressure than a single corrupt file. Reduce large texture sets, autogen, AI traffic and overlapping detailed scenery, then repeat the same route. Adding physical RAM does not remove the address-space limit inside the 32-bit FSX process, although it can help Windows avoid paging.
Can older add-ons crash FSX: Steam Edition?
Yes. Some older aircraft and scenery work, but FS2004-era compiled gauges, legacy copy protection and installers that assume a boxed FSX path can fail on newer Windows installations.
Check our guide to FS2004 add-on compatibility with FSX before loading legacy gauges or models. For Steam installations, our Steam Edition compatibility and path guidance explains how missing dependencies and installation paths can resemble genuine incompatibility.
Do not solve an old gauge error by copying random system DLLs into the FSX directory. Use the prerequisites supplied by the add-on, and remove duplicate versions of the same module before testing again.
Should I reinstall FSX to fix an add-on crash?
No—if FSX runs with a stock aircraft, stock airport and third-party startup modules disabled, reinstalling the simulator is unlikely to fix the offending add-on.
Use Steam’s file-verification function or the boxed edition’s repair option only after establishing that default files are damaged. Verification does not remove most third-party files and may restore modified default files, so back up deliberate changes first. If a clean configuration and stock test still crash, work through our broader FSX crash-diagnosis checklist before reinstalling Windows or the simulator.