Reproducible CTD *resolved*

[espresso]

Hello everyone,

I am currently having a very annoying problem with Prepar3Dv5, newest hotfix.

I want to do a flight for my virtual airline, starting at LGKO in the FSLabs A321. I do all my preparations and shortly after takeoff I run into a CTD with the faulting module being clr.dll . One time it was ntdll.dll. But most of the time it is clr.dll .
Now I know that these can come from addons doing weird things, but after deactivating this and that I cannot nail it down. I can start at LGKO on the runway with engines running (FSLabs A321), takeoff and everything works fine.
But when I want to do the flight (starting from the gate, setting the payload, using ground services, etc.) it leads to this perfectly reproducible CTD.

The main addons I use are: Active Sky with Cloud Art, GSX, ChasePlane, lots of ORBX stuff, ENVshade and ENVtex, AIG Traffic.
What puzzles me the most is the fact that I can start with engines running from LGKO on the runway and everything works, when I start from gate or from scratch it -> CTD.

Any advice would be greatly appreciated! Many thanks in advance!

Event viewer error messages:

Log Name:      Application
Source:        Application Error
Date:          18.07.2021 19:31:02
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      CYCLOPS
Description:
Faulting application name: Prepar3D.exe, version: 5.2.22.27615, time stamp: 0x60db69bf
Faulting module name: clr.dll, version: 4.8.4390.0, time stamp: 0x609c45bd
Exception code: 0xc0000005
Fault offset: 0x00000000001bc88f
Faulting process id: 0x37f0
Faulting application start time: 0x01d77bf6857e51d0
Faulting application path: D:\Prepar3Dv5\Prepar3D.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 9f421653-7e62-4aa8-96d1-7881ee902c93
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-07-18T17:31:02.8167101Z" />
    <EventRecordID>7092</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>CYCLOPS</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>5.2.22.27615</Data>
    <Data>60db69bf</Data>
    <Data>clr.dll</Data>
    <Data>4.8.4390.0</Data>
    <Data>609c45bd</Data>
    <Data>c0000005</Data>
    <Data>00000000001bc88f</Data>
    <Data>37f0</Data>
    <Data>01d77bf6857e51d0</Data>
    <Data>D:\Prepar3Dv5\Prepar3D.exe</Data>
    <Data>C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll</Data>
    <Data>9f421653-7e62-4aa8-96d1-7881ee902c93</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Application Error
Date:          17.07.2021 21:21:19
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      CYCLOPS
Description:
Faulting application name: Prepar3D.exe, version: 5.2.22.27615, time stamp: 0x60db69bf
Faulting module name: ntdll.dll, version: 10.0.19041.1110, time stamp: 0xe7a22463
Exception code: 0xc0000005
Fault offset: 0x00000000000a2097
Faulting process id: 0x3bc8
Faulting application start time: 0x01d77b3d6aab72b9
Faulting application path: D:\Prepar3Dv5\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 2fbd6ef4-ffc4-476b-8dd6-4217563352d3
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-07-17T19:21:19.6603055Z" />
    <EventRecordID>6966</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>CYCLOPS</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>5.2.22.27615</Data>
    <Data>60db69bf</Data>
    <Data>ntdll.dll</Data>

[Captain Kevin]

First, what exact steps are you doing that it reaches this point. Second, what scenery are you using. Third, is it just one gate, or is it at multiple gates. Fourth, does this happen at just that airport or does it happen at other airports. Fifth, does this happen with any other aircraft. Lastly, what happens if you use just the plane, GSX, and the airport.

[virtuali]

Your error message clearly proves the crash doesn't have anything to do with GSX or FSDT. It's a crash in clr.dll, which is the .NET runtime ( Common Language Runtime ) and NONE of our software that runs in the sim uses .NET, it's all pure 100% C++ native 64 bit Windows API.

The only software that we use that is a .NET application, is the GSX Control Panel and the Live Updater, and since they never run together with the sim, they cannot possibly cause a crash when the sim is running.

[Steff Fabiano]

Thanks for your report.

I do have the exact same problem for about 2 weeks within P3D v 4.5. Everything worked fine before. I did not change anything, the problem came all of a sudden. The flight works fine with the P3D-default F22-Raptor at the Airbase. It worked, too with this aircraft at another airport, but if I change the aircraft to e.g. JeeHell A320 (what I use usually) I can only start from a RWY, not from the gate. As soon as I start pushback, after a few seconds the CTD happens. Or it happens when leaving the RWY after landing and taxiing to a gate. With or without add-ons (active sky, UTlive ... clearing shaders, delete p3d.cfg, clear scenery-indexes ... does not matter and has the same result. Very weird !

I did not find a solution yet. Thanks for any suggestion.

[espresso]

I've got some news:

I did some further testing. My suspect was and still is the FSLabs Airbus A321. With that airplane I could reproduce the CTD every time. With other airplanes it worked fine.
Now comes the puzzling part: I recently tested again with the A321 and it worked! Can't say though exactly what has changed.
I will definitely test again.

[Steff Fabiano]

Thanks espresso, I will do the same and please keep us informed !

[espresso]

Did the flight yesterday, without any problems.
I am glad that it works now, on the other hand I do not really know what has caused the issue or how it was resolved.
Maybe some update, somewhere...

Thanks to all who tried to help!

[espresso]

Thanks espresso, I will do the same and please keep us informed !

How are you doing with your problem?

[TheCaptain3618]

I've got some news:

I did some further testing. My suspect was and still is the FSLabs Airbus A321. With that airplane I could reproduce the CTD every time. With other airplanes it worked fine.
Now comes the puzzling part: I recently tested again with the A321 and it worked! Can't say though exactly what has changed.
I will definitely test again.

First, Load an Default aircraft, set the time & the starting point & then load the flight. When 100% Loaded, load the Airbus. It worked like a charm for me.
In this case:

1. VEHICLE: MUST be Default
2. LOCATION: Anywhere
3. WEATHER: Any Theme
4. TIME AND SEASON: Any date, anytime

Press ‘OK’ to load the simulation. When Loaded:

5. Shut down the engine (if Running)
6. Go to the P3D vehicle selection menu and choose an FSLabs Airbus (Be A320, A319, A321, CFM or IAE) [Only 1 Airbus at a time]

[Steff Fabiano]

Hi,

I deselected all add-ons and extra stuff and started from scretch - so with the default.

And the result was, that it came to an add-on as faulty program which created the CTD all the time. I deselected the "lua" and P3D worked fine again !