FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Headi on May 22, 2020, 02:45:04 pm
-
I have got a mistake with my P3Dv5.
Active Addons/Programs:
- Aerosoft A330 Pro
- Simwings, LEPA/LEMD
- GSX Level 2
- Pro ATC X
- ASP3D5 Beta
- projectFly
After asking for Pushback the Sim crah to Desktop 2 times.....
Windows Crashreport:
Name der fehlerhaften Anwendung: Couatl.exe, Version: 3.2.0.4336, Zeitstempel: 0x5eb5643c
Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.18362.815, Zeitstempel: 0xbea5fce0
Ausnahmecode: 0xc0000409
Fehleroffset: 0x0009e6eb
ID des fehlerhaften Prozesses: 0xb38
Startzeit der fehlerhaften Anwendung: 0x01d630314ccba61f
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Addon Manager\Couatl\Couatl.exe
Pfad des fehlerhaften Moduls: C:\Windows\System32\ucrtbase.dll
Berichtskennung: 84178a10-d6f4-47cc-a6d9-9ea6eaf252e6
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
-
Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 5.0.24.34874, Zeitstempel: 0x5eab3677
Name des fehlerhaften Moduls: VCRUNTIME140.dll, Version: 14.25.28508.3, Zeitstempel: 0x5e155520
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000000137b
ID des fehlerhaften Prozesses: 0x3470
Startzeit der fehlerhaften Anwendung: 0x01d6303149d552ba
Pfad der fehlerhaften Anwendung: F:\Program Files\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\VCRUNTIME140.dll
Berichtskennung: 99287378-ff08-4c2f-8baf-4aacb4570fad
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
-
I just had a crash at the same point. Using P3D v5 with hotfix 1 in the old PMDG NGX. When I asked for pushback the tug pulled up, then after a few seconds when I usually get "Hello captain. We are ready for pushback", instead I heard the sound stutter a few times and then P3D crashed to desktop. In my windows error log it's listed as a P3D.exe crash but it's in the same vcruntime140.dll and since it was at that point in the GSX cycle I'm suspecting it was actually GSX that caused it.
-
For information, installing the x64 redistributable from Microsoft solves this issue:
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads