Adam_UK Posted March 9, 2019 Share Posted March 9, 2019 Hello All I have an issue with PAEN which causes a CTD in P3Dv4.4. The issue is reproducible and I have a saved flight scenario in the QW RJ100 which crashes at the same point every time. The issue is occurring when I am overflying PAEN at approximately FL200 on the route PANC TED J115 CDB PACD. If I uninstall PAEN through ORBX Central the issue goes away, even with the same saved scenario. There is no error message given when the CTD occurs. When I look at the event viewer, the crash report is always the same: Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35 Faulting module name: ntdll.dll, version: 10.0.17134.556, time stamp: 0x74bed8b0 Exception code: 0xc0000374 Fault offset: 0x00000000000f479b Faulting process ID: 0x31ec Faulting application start time: 0x01d4d66660fcf943 Faulting application path: F:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report ID: 568543cd-8abc-4fc2-ade5-d29ea2debb45 Faulting package full name: Faulting package-relative application ID: If I attempt a NEW flight, on the same route, the error occurs again... even without loading the saved scenario. If I fly around PAEN in a default aircraft I always manage to get an error after a few minutes which results in a crash of Couatl which gives the following error, but does NOT cause a CTD: couatl v3.2 (build 4061) panic log started on Sat Mar 9 11:08:30 2019 problem raised by addon <unknown> Traceback (most recent call last): File ".\common\modelCustomization.py", line 379, in setJetwayAirlineCode File ".\common\modelCustomization.py", line 443, in getModelForCouatlType File ".\common\modelCustomization.py", line 63, in _matches AttributeError: 'NoneType' object has no attribute 'startswith' {'Airport': 'PAEN', 'User Pos': (60.5381799651574, -151.23180464527556, 315.225 m, 315.225 m, 354.72865301482665)} Traceback (most recent call last): File "<string>", line 22, in OnIdle File ".\common\modelCustomization.py", line 379, in setJetwayAirlineCode File ".\common\modelCustomization.py", line 443, in getModelForCouatlType File ".\common\modelCustomization.py", line 63, in _matches AttributeError: 'NoneType' object has no attribute 'startswith' It should be noted that even when I uninstall ALL Couatl software (GSX / Addon Manager / Airports) the CTD STILL occurs in the QW RJ100 at the same point. This would indicate that the error is started by PAEN and causing Couatl to crash rather than vice versa, as the CTD is still present without Couatl. I only therefore included the Couatl log above as I thought somebody with a more in depth knowledge than me might be able to shed light on a cause/fix.... since it offers a little more information than the event viewer log which is somewhat generic. When in the QW RJ100 the CTD does not appear to raise a Couatl error. I also own all NA regions and all Global / Vector products for this area too. The season is set as 2nd March for my tests. Any help is appreciated. I have currently had to resort to uninstalling PAEN until I can find a fix in order to fly in the area! Cheers Adam Link to comment Share on other sites More sharing options...
canadagoose Posted November 19, 2020 Share Posted November 19, 2020 Was there any resolution to this or did it just go by the wayside. My P3Dv5.1 sim is crashing at waypoint ENA (N60 36.9'. W151 11.7'). It has happened 5 times straight where I cannot complete the flight. I do not think it is a coincidence that 2 users of the Orbx PAEN scenery are experiencing a CTD. Regards Tom Link to comment Share on other sites More sharing options...
KCPilot Posted January 12, 2021 Share Posted January 12, 2021 I have had the same issue using P3V4.5. Uninstalled it works fine. I have reinstalled it today and the issue is back. It has a CTD IVO N60 36 W151 15 when above 10,000'. I have been playing with it and trying it at different altitudes and above 10K seems to be an issue. Here are the events logs: 1/12/2021 at 10:02:52 Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93 Faulting module name: ntdll.dll, version: 10.0.18362.1171, time stamp: 0x103a4719 Exception code: 0xc0000374 Fault offset: 0x00000000000f9059 Faulting process id: 0xdec Faulting application start time: 0x01d6e90c54ec8cc3 Faulting application path: D:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 654a4d78-be11-4f79-beb7-70e2fdaaef5b Faulting package full name: Faulting package-relative application ID: 1/12/2021 at 10:02:51 Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00007FFB5441487E 1/12/2021 at 9:55:43 Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93 Faulting module name: ntdll.dll, version: 10.0.18362.1171, time stamp: 0x103a4719 Exception code: 0xc0000374 Fault offset: 0x00000000000f9059 Faulting process id: 0x32e0 Faulting application start time: 0x01d6e90ace84b411 Faulting application path: D:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: b0ecb61d-2ddf-43e5-83be-f2333aa81414 Faulting package full name: Faulting package-relative application ID: 1/04/2021 at 1:21:13 Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93 Faulting module name: clr.dll, version: 4.8.4300.0, time stamp: 0x5f7e616e Exception code: 0x80131506 Fault offset: 0x000000000048df56 Faulting process id: 0x2180 Faulting application start time: 0x01d6e2defed2d761 Faulting application path: D:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: 7919e754-ad8b-4498-82b5-2ca4dcf258fa Faulting package full name: Faulting package-relative application ID: 1/04/2021 at 1:21:11 Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF93D6BDF56 (00007FF93D230000) with exit code 80131506. Also had the attached file on the last crash. Thanks, Todd Link to comment Share on other sites More sharing options...
Heronjr Posted December 22, 2021 Share Posted December 22, 2021 +1 Link to comment Share on other sites More sharing options...
Recommended Posts