Find why the PMDG 737NGX crashes FSX Steam Edition on load and fix installer, SimConnect, runtime, panel-state and memory faults.
The PMDG 737NGX usually crashes FSX: Steam Edition while loading because the wrong NGX build was installed, its gauge files or legacy SimConnect prerequisites are missing, or a saved panel state is corrupt. A clean FSX:SE-compatible installation, repaired runtimes and a test from a fresh default flight fix most cases.
What causes the PMDG 737NGX loading crash?
The crash point usually separates a PMDG installation fault from an FSX-wide problem. FSX:SE runs many boxed-FSX products, but compatibility is not automatic for old gauge modules and installers; our guide to older FSX add-on compatibility in Steam Edition explains the main differences.
| Symptom | Most likely cause | First check |
|---|---|---|
| Every NGX model crashes | Wrong installer, missing gauge files or runtime dependency | Confirm the product version and reinstall its prerequisites |
| Only one model or livery crashes | Broken livery entry, missing expansion or damaged textures | Test a base-package aircraft with its standard livery |
| Only saved flights crash | Corrupt or obsolete panel state | Create a fresh Free Flight session |
| It crashes only at detailed airports | FSX virtual-address-space exhaustion or scenery conflict | Test at a default airport after restarting FSX |
| Default aircraft also crash | Core FSX configuration, scenery or another module | Troubleshoot FSX rather than the NGX first |
Use the legacy PMDG 737NGX for FSX, installed with a build explicitly supporting FSX or FSX:SE. The 737NGXu is a separate Prepar3D product, while newer PMDG 737 packages are not FSX add-ons. Our comparison of realistic 737 add-ons for FSX clarifies these product generations.
How do I stop the PMDG 737NGX crashing on load?
Start with an aircraft-only test, then repair the installation in a controlled order.
- Aircraft-only test: Restart FSX:SE and load a default aircraft at a default airport with clear weather. Close the session, then start a fresh flight with a standard NGX variant. Do not switch into the NGX from another complex aircraft or use an old saved flight.
- Correct product: Confirm that the installer is for the legacy FSX 737NGX. If using the 600/700 expansion, the base 800/900 package must be installed first, and both components must belong to the same simulator generation.
- Correct destination: Ensure the installer targets the active FSX:SE root folder containing
fsx.exe, not an old boxed-FSX directory or theSimObjectsfolder. Remnants of a boxed installation can make older installers choose the wrong location. - Clean reinstall: Back up custom liveries and panel states, uninstall the NGX expansion before the base package where applicable, and remove only confirmed leftover NGX files. Use Steam’s file verification to repair core FSX files, run FSX once with a default aircraft, close it, then reinstall the base NGX before any expansion or liveries.
- Legacy dependencies: Repair the legacy SimConnect packages and Microsoft x86 runtime components supplied with FSX or the add-on. FSX is a 32-bit application, so it can require x86 components even on 64-bit Windows. Do not download individual replacement DLL files or copy them into the FSX directory.
- Security and trust: Run the legitimate installer with administrative permission, check whether security software quarantined a PMDG gauge or module, and accept FSX’s trusted-software prompt for recognised PMDG components. Use narrowly targeted exclusions rather than disabling protection permanently.
- Fresh state: Rename the PMDG-generated 737NGX settings and panel-state folder so the aircraft can create clean data. Test a base aircraft with its standard livery before restoring custom liveries, saved states, weather engines or other modules.
Copying only the aircraft folder into SimObjects\Airplanes is not a valid NGX installation. The aircraft also requires gauges, data files and supporting components placed elsewhere by its installer.
Why does the NGX crash at 100% loading?
A crash at 100% often occurs while the aircraft’s gauges and saved state are initialising, so the final loading percentage does not prove that scenery caused it. If the cockpit never appears, prioritise the installer, SimConnect and runtime checks above; our dedicated checks for FSX crashes at 100% loading cover the wider causes.
- Crash before the cockpit appears: suspect an incompatible gauge module, missing dependency or installation in the wrong FSX folder.
- Cockpit appears briefly and then closes: suspect a damaged panel state, blocked module or configuration file.
- Only one livery fails: remove that livery and test the same aircraft model with its standard texture set.
- Only a saved
.FLTfile fails: build a new flight because the save may reference an obsolete livery or panel state.
Can FSX run out of memory while loading the 737NGX?
Yes. FSX:SE is a 32-bit simulator, and the NGX can push its virtual address space over the limit when combined with detailed scenery, large textures, dense AI traffic and complex weather.
Start a new FSX session, choose a default airport, use the standard NGX livery and reduce scenery complexity, texture resolution and AI traffic for the test. Avoid loading another complex aircraft first because FSX does not always release all of its gauges and textures when aircraft are changed.
If the NGX loads reliably at a default airport but crashes at one detailed airport, reinstalling the aircraft is unlikely to be the answer. Isolate that scenery and reduce memory-heavy settings instead. A crash everywhere, including a fresh default location, points back towards the NGX installation or its dependencies.
What should I check if a clean reinstall still crashes?
Back up and rename configuration files one at a time rather than deleting them together. A fresh FSX.cfg resets display settings and trusted-module records; temporarily isolating dll.xml or exe.xml can expose a conflict with another add-on, but those files may also contain entries required by legitimate modules.
FSX:SE configuration folders can differ between a Steam-only installation and a computer that also had boxed FSX installed, so confirm which roaming application-data folder changes when the simulator closes. If a regenerated configuration works, reapply settings manually instead of restoring the entire faulty file.
Finally, inspect Windows Reliability Monitor or Event Viewer for the faulting module. A PMDG gauge points towards the aircraft installation, a SimConnect component towards its legacy runtime, while ntdll.dll or KERNELBASE.dll is usually only where the failure surfaced. If default aircraft or unrelated flights also crash, follow our systematic FSX crash-isolation procedure before changing the NGX again.