Boeingfreak777F

Well I just found the issue, I just deactivated everything from FSDT and reactivated one after another. Everything works fine, when I'm activating KLAX v2, it comes to the CTD with the ntdll.dll.

Well I'll give it a try to unload the Sceneries and reactivate one after another, but in my opinion it doesn't come from the scenerys, I tried to load an PMDG Aircraft on an Default Scenery and it crashed too. I will reply, when I finished testing...

After the P3D Hotfix 1, I've got the same problems with the ntdll.dll, everything works fine, my scenerys are all 100% P3D V4 compatible. It only crashes when I try to load the 747 or 777, all other ACFT working fine, scenerys working fine, but on PMDG Planes it crashes... My Local Settings are German, before the Hotfix it worked fine, I didn't change anything, only the hotfix. But before the HOTFIX I've got an p3d crash because of the Local Settings that can be found here: http://www.prepar3d.com/forum/viewtopic.php?t=124836 Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.0.28.21686, Zeitstempel: 0x594a7255 Name des fehlerhaften Moduls: ntdll.dll, Version: 6.1.7601.23807, Zeitstempel: 0x5915fdce Ausnahmecode: 0xc0000005 Fehleroffset: 0x0000000000023de5 ID des fehlerhaften Prozesses: 0x161c Startzeit der fehlerhaften Anwendung: 0x01d2ef441fbb4c1c Pfad der fehlerhaften Anwendung: I:\Prepar3D v4\Prepar3D.exe Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll Berichtskennung: 7080ca9a-5b37-11e7-be0c-d43d7e19413f Fehlerbucket , Typ 0 Ereignisname: APPCRASH Antwort: Nicht verfügbar CAB-Datei-ID: 0 Problemsignatur: P1: Prepar3D.exe P2: 4.0.28.21686 P3: 594a7255 P4: ntdll.dll P5: 6.1.7601.23807 P6: 5915fdce P7: c0000005 P8: 0000000000023de5 P9: P10: Angefügte Dateien: C:\Users\MY PC\AppData\Local\Temp\WERB78B.tmp.WERInternalMetadata.xml Diese Dateien befinden sich möglicherweise hier: C:\Users\MY PC\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_b36f736f748b40ed2ad987414f1d7312039685b_2325bc3d Analysesymbol: Es wird erneut nach einer Lösung gesucht: 0 Berichts-ID: 7080ca9a-5b37-11e7-be0c-d43d7e19413f Berichtstatus: 65