P3D V4 Crashed to Desktop for me

[biloo 20]

Hi,

My P3D v4 crashed on me all of a sudden for no visible reason.

I was doing a long haul flight on my windows 10 desktop environment from OMAA to CYYZ and I was over the baltic sea when my sim suddenly crashed.

I checked the event logs and found interesting log that showed terrain.dll as the cause of error. The log details are at bottom of this post.

Not sure why this would happen. 

Addons I have installed are FTX Global, ASP4 and ASCA (both with latest beta build). ASCA applied Dynamic Weather theme. (Last Activated theme: Full Dynamics, Sky=Instinctive5, Cirrus=Nautical, Clouds=Multiple.

Other Addons connected:

PMDG 777-200LR, Navigraph beta desktop, FS Real time. I am not sure if these had any impact to the cause of crash.

If anyone have any ideas would be much appreciated.

LOG 1 from Application log:

Log Name:      Application
Source:        Application Error
Date:          6/24/2017 6:27:20 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Description:
Faulting application name: Prepar3D.exe, version: 4.0.23.21468, time stamp: 0x59279be2
Faulting module name: terrain.dll, version: 4.0.23.21468, time stamp: 0x59279b72
Exception code: 0xc0000005
Fault offset: 0x00000000000e0ddd
Faulting process id: 0x1164
Faulting application start time: 0x01d2ecf9d50abde1
Faulting application path: X:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: X:\Program Files\Lockheed Martin\Prepar3D v4\terrain.dll
Report Id: 3244b0fd-b95e-46e0-a0fc-aa80544330d2
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>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-06-24T22:27:20.571631500Z" />
    <EventRecordID>9227</EventRecordID>
    <Channel>Application</Channel>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.0.23.21468</Data>
    <Data>59279be2</Data>
    <Data>terrain.dll</Data>
    <Data>4.0.23.21468</Data>
    <Data>59279b72</Data>
    <Data>c0000005</Data>
    <Data>00000000000e0ddd</Data>
    <Data>1164</Data>
    <Data>01d2ecf9d50abde1</Data>
    <Data>X:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data>
    <Data>X:\Program Files\Lockheed Martin\Prepar3D v4\terrain.dll</Data>
    <Data>3244b0fd-b95e-46e0-a0fc-aa80544330d2</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Log 2 (.Net Source error)

 

Log Name:      Application
Source:        .NET Runtime
Date:          6/24/2017 6:27:20 PM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
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 00007FF85F9A0DDD

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-06-24T22:27:20.117926200Z" />
    <EventRecordID>9226</EventRecordID>
    <Channel>Application</Channel>
    <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 00007FF85F9A0DDD
</Data>
  </EventData>
</Event>

 

[downscc 1,327]

In the PMDG 777-200LR, did you use the left PFD 2D popup?  I don't think the terrain.dll caused the crash, it just happened to be doing something when the application was in the process of crashing and it got named by the OS for a memory access violation.  Stay away from the left PfD popup, using the right FO PFD popup works just fine.

[biloo 20]

Hi Dan,

I had the left CDU popup working. Wasn't using the left 2d popup.

Its a bummer though to redo the flight again.

I am wondering maybe to start adopting saving function at regular intervals during the flight.

Have you guys had any issue with FSUIPC5 autosave function when using with PMDG T7? such as FSUIPC crash or pauses ?

[racingmars 6]

Same thing just happened to me! I too was doing a long haul, KSFO to NZAA in the 777-200LR, and about 9 hours in P3Dv4 crashed. In my case the event log is saying the access violation was from ai_player.dll (I don't have any AI traffic turned on). AS16 and ASCA latest updates, ChasePlane, Navigraph Simlink... very similar setup to you.

The only popup window I used during the flight was left CDU; it was not open at time of crash. 

[uhntissbaby111 58]

I was doing my inaugural long haul in P3D v4 the other night. PMDG 77L, flightbeam KMSP to Justsim EDDL. ASCA + AS4 and Chaseplane. Along with ORBX Global and NA and EU LC. Took off, and when I woke up, the sim was closed from what I'm assuming was a crash. However, there was nothing in the event log. Did 2 long hauls since, going the other way, and no crashes. So I just chalked it up to FSX/P3D being themselves. Part of me wants to curse out the code for being so old and unstable etc etc. Saying that no other games I play crash like this. But then, in fairness, I think about how no other game has nearly as many addons and applications running with it. Think about all the stuff we modify our sims with. Terrain, scenery, airplanes, weather, traffic, cameras, and the list goes on. Do we blame the base sim? Or the fact that we are running so much stuff with it?

[biloo 20]

41 minutes ago, racingmars said:

Same thing just happened to me! I too was doing a long haul, KSFO to NZAA in the 777-200LR, and about 9 hours in P3Dv4 crashed. In my case the event log is saying the access violation was from ai_player.dll (I don't have any AI traffic turned on). AS16 and ASCA latest updates, ChasePlane, Navigraph Simlink... very similar setup to you.

The only popup window I used during the flight was left CDU; it was not open at time of crash. 

I am just redoing the flight. So far so good.

There is one common event occurring in both session is that my navigraph desktop beta again would lose connection to the simulator.

This happened in the first session and few minutes later my sim crashed.

I closed navigraph and restarted it and this time didn't connect it to simulator. I have also closed simlink.

Lets see if I get any errors. So far so good. Fingers crossed.

[Piotr007 167]

I just found out a "wrong" OC will also generate CTD's?

 

[fluffyflops 1,858]

Was this using the latest patch for the 777?

[sgreen91 182]

The crash with nothing in the event viewer for me ended up being the XMP settings in bios.  Disabled XMP and the CTD never returned.

 

 

[biloo 20]

3 hours ago, tooting said:

Was this using the latest patch for the 777?

Yep its using the latest patch from PMDG.

Its working right now.

There are two differences compared from the first time.

Before repeating the second attempt I restarted my PC, and during the flight I stopped the moving map function from navigraph desktop beta.

Btw the beta version installed is 6.0.0.0619

And also the ASP4 + ASCA are the latest version: 6583 and 6383 respectively.

I haven't touched anything from the overclocking or BIOS side. They are pretty much vanilla setup.