P3D V4.4 CTD
Posted: Sun Mar 10, 2019 11:26 am
Hello,
I have a serious issue since updating to V4.4.(complete installation several times) I never had any CTD in V4 but after installing V4.4 I cannot complete a flight anymore. The following crash occurs:
Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.4.16.27077, Zeitstempel: 0x5bfdbb35
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.17134.471, Zeitstempel: 0x7e614c22
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000f47fb
ID des fehlerhaften Prozesses: 0xb0c
Startzeit der fehlerhaften Anwendung: 0x01d4d72b6be5dbd7
Pfad der fehlerhaften Anwendung: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Well I know this is related to an overclocked system, which I have, but it was from day one with all V4 subversions and never was an issue. Not overclocking does simply not work, as P3D is to hungry related to prefomance and VR, which I use only. So there must something in V4.4 wich causing this, maybe you look into this for further versions, regarding this problem.
Kind regards
Sven
I have a serious issue since updating to V4.4.(complete installation several times) I never had any CTD in V4 but after installing V4.4 I cannot complete a flight anymore. The following crash occurs:
Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.4.16.27077, Zeitstempel: 0x5bfdbb35
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.17134.471, Zeitstempel: 0x7e614c22
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000f47fb
ID des fehlerhaften Prozesses: 0xb0c
Startzeit der fehlerhaften Anwendung: 0x01d4d72b6be5dbd7
Pfad der fehlerhaften Anwendung: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Well I know this is related to an overclocked system, which I have, but it was from day one with all V4 subversions and never was an issue. Not overclocking does simply not work, as P3D is to hungry related to prefomance and VR, which I use only. So there must something in V4.4 wich causing this, maybe you look into this for further versions, regarding this problem.
Kind regards
Sven