I hand fly a lot of circuits taking off and landing at the same airport and pretty much never get CTDs doing them. 

On long flights I am getting them about a third of the time, and it's becoming really old now. I've never looked at event manager before, and I don't really know what the info there means, but I have taken screenshots related to my most recent CTD so someone here can hopefully point me in the right direction for a solution.

It was happening in P3Dv5.1 and it is happening in 5.2 as well. Usually about half an hour or so into flights.Today I have flown 6 long flights, and had CTDs in 2 of them. I had Active Sky running, Chaseplane, LRM and TrackIR. I have quite a lot of Orbx scenery.

I had previously thought the culprit may be PACX as I use that on long flights and not on circuits, but todays 2 CTDs without PACX kind of rule out that theory. The first one today I was flying the PMDG 737 NGXu, and the second one was the PMDG 744.

Does everyone get CDTs in about a third of long flights? I hope not as it is sucking the enjoyment out them for me.

 

Edited July 2, 20214 yr by WestEnd

I've copied and pasted all the text from the images in my OP, which may be easier to see. I have also been using AIG AI.

Log Name:      Application

Source:        Application Error

Date:          02/07/2021 00:44:57

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Flight-Sim-PC

Description:

Faulting application name: Prepar3D.exe, version: 5.2.18.27565, time stamp: 0x60befcbd

Faulting module name: terrain.dll, version: 5.2.18.27565, time stamp: 0x60befc36

Exception code: 0xc0000005

Fault offset: 0x00000000000093e3

Faulting process ID: 0x1378

Faulting application start time: 0x01d76ecc7e2b1e36

Faulting application path: D:\Lockheed Martin\Prepar3D v5\Prepar3D.exe

Faulting module path: D:\Lockheed Martin\Prepar3D v5\terrain.dll

Report ID: 88e5a8d3-ff13-44aa-b160-a72344ffd5dc

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-01T23:44:57.0152990Z" />

    <EventRecordID>49449</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>Application</Channel>

    <Computer>Flight-Sim-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Prepar3D.exe</Data>

    <Data>5.2.18.27565</Data>

    <Data>60befcbd</Data>

    <Data>terrain.dll</Data>

    <Data>5.2.18.27565</Data>

    <Data>60befc36</Data>

    <Data>c0000005</Data>

    <Data>00000000000093e3</Data>

    <Data>1378</Data>

    <Data>01d76ecc7e2b1e36</Data>

    <Data>D:\Lockheed Martin\Prepar3D v5\Prepar3D.exe</Data>

    <Data>D:\Lockheed Martin\Prepar3D v5\terrain.dll</Data>

    <Data>88e5a8d3-ff13-44aa-b160-a72344ffd5dc</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

 

Prepar3D.exe

 

5.2.18.27565

 

60befcbd

 

terrain.dll

 

5.2.18.27565

 

60befc36

 

c0000005

 

00000000000093e3

 

1378

 

01d76ecc7e2b1e36

 

D:\Lockheed Martin\Prepar3D v5\Prepar3D.exe

 

D:\Lockheed Martin\Prepar3D v5\terrain.dll

 

88e5a8d3-ff13-44aa-b160-a72344ffd5dc

 

	Log Name:      Application Source:        .NET Runtime Date:          02/07/2021 00:44:54 Event ID:      1026 Task Category: None Level:         Error Keywords:      Classic User:          N/A Computer:      Flight-Sim-PC Description: 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 00007FFE4D2493E3 Stack:   Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">   <System>     <Provider Name=".NET Runtime" />     <EventID Qualifiers="0">1026</EventID>     <Version>0</Version>     <Level>2</Level>     <Task>0</Task>     <Opcode>0</Opcode>     <Keywords>0x80000000000000</Keywords>     <TimeCreated SystemTime="2021-07-01T23:44:54.9762457Z" />     <EventRecordID>49448</EventRecordID>     <Correlation />     <Execution ProcessID="0" ThreadID="0" />     <Channel>Application</Channel>     <Computer>Flight-Sim-PC</Computer>     <Security />   </System>   <EventData>     <Data>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 00007FFE4D2493E3 Stack: </Data>   </EventData> </Event>

 

 

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 00007FFE4D2493E3 Stack:

 

 

Most of the CTDs I have had I have been using time compression. 

Having been mulling things over, and Googling for ages trying to look for solutions I came across this post from Jim Young 3 years ago on a CTD thread 

"Save your p3d.cfg as p3d.cfg.off.  Restart P3D and let the config rebuild.  Try again w/o touching any of the P3D settings.  The majority of terrain.dll crashes are caused by high settings, especially Autogen.  Your system cannot render things fast enough.  If that does not work, then bring back the old one and you will have to go to page 10 of the AVSIM CTD Guide (link in my signature) and begin the investigating process but I'm almost 100% sure reducing your p3d.cfg settings will resolve this issue."

I wonder if my PC specs are fine to run things at normal speed, hence the sim is stable on hand flown circuits, but I would need to reduce my settings to avoid frequent CTDs if I speed things up in cruise on long flights. perhaps the scenery and terrain is having to be loaded a lot faster and therefore it struggles to keep up.

That maybe seems more likely than a dodgy add on, as all the add ons I use are extremely popular with P3D users who don't all seem to be having issues.

 

 

4 hours ago, Rob_Ainscough said:

I recommend you install HF1 for V5.2 ... us the following sequence if you plan to go the individual MSI route:

Uninstall V5.2 Client

Uninstall V5.2 Content

Uninstall V5.2 Scenery

Install V5.2 HF1 Content

Install V5.2 HF1 Client

Install V5.2 HF1 Scenery

Suggest you delete VolumetricClouds.cfg and your Prepar3D.cfg before starting V5.2 HF1 for the first time.

Cheers, Rob.

Thabks Rob,

I'm planning to do that today now the FSL update is out.

4 hours ago, WestEnd said:

Thabks Rob,

I'm planning to do that today now the FSL update is out.

I've done four flights of 12 hours plus with 5.2 and haven't had any issues.  I don't use time compression.  Any time I've had an issue I pretty much follow the recommendations made by Rob above. 

You said you were seeing this in v5.1 as well--I have not updated to 5.2, but I do not have a problem with long flights in 5.1

A duplicate airport file (AFCAD/ADE) in a scenery you are flying near, or a corrupt texture file in a scenery or AI acft livery can all cause this.  If you have non-Orbx add-on airports in Orbx scenery areas, you usually need to deconflict the Orbx airport file and the add-on airport file.

If the problem doesn't occur in other locations, it suggests a scenery conflict.

If it doesn't occur with AI disabled or occurs at certain times of day but not others, it suggests a problem with an AI livery being spawned nearby at that day/time.

7 hours ago, w6kd said:

You said you were seeing this in v5.1 as well--I have not updated to 5.2, but I do not have a problem with long flights in 5.1

A duplicate airport file (AFCAD/ADE) in a scenery you are flying near, or a corrupt texture file in a scenery or AI acft livery can all cause this.  If you have non-Orbx add-on airports in Orbx scenery areas, you usually need to deconflict the Orbx airport file and the add-on airport file.

If the problem doesn't occur in other locations, it suggests a scenery conflict.

If it doesn't occur with AI disabled or occurs at certain times of day but not others, it suggests a problem with an AI livery being spawned nearby at that day/time.

Hopefully reducing my graphics settings if I use time compression will sort it.

I do have non Orbx add on airports now, but at the time of 5.1, Orbx was the only add on scenery I had. For me 5.1 was just generally very unstable. If I went into settings during a flight I was asking for a CTD. If I navigated to another airport it often crashed.  I did keep reducing settings until it became reasonable stable in actual flights. 

5.2 has been much more stable for me. I could fly circuits all day moving my aircraft to a different airport each time with no issues. Changing setting during flights is no problem. I did bump my settings up a bit from where they were in 5.1, so maybe / hopefully that's what the issue has been if scenery and terrain has been needing to be generated at 4 or 8 times normal speed. 

I wouldn't know where to start with trying to resolve any possible conflicts between different scenery products. I just make sure I have airports at the top of my scenery library, regions below that, and global stuff below that. I have the Orbx insertion point below all airports from other developers, and use Lorby organiser if these things change for any reason. 

I did 3 long flights yesterday with no problems, without using time compression, and I am on my fourth today with no problems so far. 

I have my settings right on the balance of what looks good to me, and where my sim has acceptable performance in terms of smoothness etc. It looks like time compression pushes my set up beyond what it can do at my current settings, but normal speed is fine.