Why does Prepar3D v5 freeze, and how do I fix it?

Prepar3D v5 usually freezes because an incompatible add-on, damaged configuration or shader cache, faulty scenery, a graphics-driver problem, or exhausted GPU memory stalls the simulator. Test a default aircraft and airport first, then disable add-ons, rebuild generated files, reduce GPU load, and repair the installation only if the base simulator still locks up.

What usually causes Prepar3D v5 lock-ups?

The point at which Prepar3D v5 freezes is often the best clue to the cause. A lock-up tied to one aircraft or location is usually an add-on problem, while freezing after a long flight more often indicates resource pressure, a driver fault or an add-on that leaks memory.

How do I fix Prepar3D v5 freezing?

The quickest reliable method is to establish a clean baseline and add components back until the lock-up returns. Changing several unrelated settings at once may hide the symptom without identifying what caused it.

1. Confirm that it is genuinely frozen. Give Prepar3D several minutes once and inspect its CPU and disk activity in Task Manager. A first launch after rebuilding shaders or loading dense scenery can appear unresponsive; a repeatable stop at the same point is more significant.
2. Start a fresh default flight. Use a default aircraft, a simple default airport, fair weather and no saved flight. If this works, the core simulator is probably sound and the original aircraft, scenery, weather or saved scenario becomes the main suspect.
3. Check the Windows record. Reliability Monitor and Event Viewer may classify the incident as an application hang or reveal that the process actually crashed. A generic module such as ntdll.dll does not identify the culprit by itself. If Prepar3D closes rather than remaining stuck, follow our full workflow for diagnosing Prepar3D crashes.
4. Disable external utilities and add-ons. Stop weather engines, traffic programs, camera tools and other SimConnect clients, then disable third-party aircraft and scenery. With a large library, disable half the packages, test, and continue halving the failing group. Our guide to organising and safely disabling Prepar3D add-ons explains the cleaner package-based approach.
5. Rebuild the configuration and shader cache. Close Prepar3D and rename %APPDATA%\Lockheed Martin\Prepar3D v5\Prepar3D.cfg to a backup name. Test before also renaming the Shaders folder under %LOCALAPPDATA%\Lockheed Martin\Prepar3D v5. Prepar3D creates replacements when it starts. Reapply settings manually rather than copying the entire old configuration back.
6. Test location-specific scenery. If the freeze occurs near the same coordinates, disable the airport plus any regional mesh, vector or landclass package covering it. Airport scenery alone may not be responsible. For hangs associated with a Terrain.dll report, use these terrain and scenery fault checks.
7. Reduce GPU load. Prepar3D v5's DirectX 12 renderer relies heavily on dedicated GPU memory. Lower texture resolution, anti-aliasing, shadows, dynamic reflections, autogen, cloud distance and traffic until the same flight remains stable. Close recording software and overlays during the test. These Prepar3D graphics and performance adjustments cover the settings that have the largest impact.
8. Repair only after the clean test fails. If a fresh default flight still freezes with add-ons disabled, use the Prepar3D v5 installer's repair option and ensure the installed Client, Content and Scenery components have not been mixed with files from another build. Also test a clean graphics-driver installation; if the problem began directly after a driver change, returning to the previously stable driver is a sensible comparison.

How can I identify the add-on causing the freeze?

A repeatable comparison is more useful than guessing from the last package installed. Keep the aircraft, airport, weather, time and route unchanged, then enable one add-on category at a time.

• If the default aircraft works, enable the original aircraft without its optional utilities first.
• If the default airport works, restore scenery by region rather than enabling the whole library.
• If the freeze takes time to appear, test external utilities individually for at least as long as the original flight lasted.
• If removing an add-on appears ineffective, check that its package is actually disabled and that no older copy remains inside Prepar3D's core folders.

A mistake we see constantly is copying old FSX-era files directly into the simulator and later assuming that disabling an add-on package removes them. Files placed in core aircraft, scenery, effects or gauge folders can remain active until they are removed or the installation is repaired.

Does “Not responding” mean Prepar3D has crashed?

“Not responding” means Windows is not receiving timely messages from Prepar3D's main process; it does not automatically mean the process has failed. Active CPU or disk use during a one-off scenery or shader load justifies waiting, but repeated hangs at the same aircraft, airport or menu action point to a fault that needs isolating.

If audio continues while the picture remains fixed, concentrate on the graphics driver, GPU memory, overlays and display mode. If audio loops and all simulator input stops, an in-process add-on or scenery operation is a stronger suspect.

Should I reinstall Prepar3D v5 to fix freezing?

A full reinstall should be the last step because it may leave the same user configuration and add-on packages in place. Renaming the configuration, rebuilding shaders and proving that a default flight fails will tell you whether repairing or reinstalling the base simulator is justified.

Back up only files you know you changed. Restoring the complete old configuration or every add-on immediately after reinstalling can restore the lock-up before the clean simulator has been tested.

What if the entire PC freezes?

A system-wide lock-up is more likely to involve the graphics driver, unstable hardware, heat or an overclock than Prepar3D alone. Return CPU, GPU and memory settings to their defaults, remove unnecessary overlays, check temperatures and inspect Windows logs after restarting.

Do not use one successful desktop session as proof that an overclock is stable. Prepar3D can maintain a sustained CPU and GPU load that exposes instability not seen during lighter applications.