Consistent CTD 2-3 hrs into flight (P3D v3.3.5)

[Zach Barrington 0]

First off, thank you for taking the time to help me out! I saw another topic with someone who was having a similar issue 3 hours into his flights, but I don't think it was ever resolved. Here are the basics. I did four test flights this weekend with the T7, and all four CTDed within the first four hours. I realize I have a healthy list of addons, but before I nuke everything I wanted to get other opinions. My settings in P3D are mid to high-range, and I can provide those if you think it will help. It is not an OOM problem. Even when taking off from an FSDT airport, my remaining VAS stays steady around 850,000 according to FSUIPC. 

 

As a note, I deactivate my addon airports in the scenery library if I am not using them for a particular flight, and this weekend I suffered the CTDs both with and without using addon airports. Also, I flew a 3 hour flight in the NGX this weekend beginning at Flightbeam's KDEN with no problems. I have never had the NGX crash on longer flights either. Basics are below.

 

KORD-KSFO (CTD on descent into KSFO)

KMEM-OMDB (CTD over Newfoundland)

KIAD-ZBAA (CTD during climbout)

KSFO-KEWR (CTD somewhere over the midwest 3 hours in)

 

Addons:

 

- AS2016

- REX Texture Direct with clouds at 1024 and ground textures at 2096

- FTX Global Base

- FTX Global Vector

- FTX OpenLC NA and Europe

- FS Global Ultimate terrain mesh

- FSDT and Flightbeam airfields, including KSFO and KIAD

- FS2Crew

 

Below are the crash logs from each flight.

 

Source

Prepar3D exe

 

Summary

Stopped working

 

Date

‎9/‎3/‎2016 10:16 PM

 

Status

Report sent

 

Description

Faulting Application Path: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe

 

Problem signature

Problem Event Name: BEX

Application Name: Prepar3D.exe

Application Version: 3.3.5.17625

Application Timestamp: 5758bb31

Fault Module Name: MSVCR120.dll

Fault Module Version: 12.0.21005.1

Fault Module Timestamp: 524f7ce6

Exception Offset: 000a7666

Exception Code: c0000409

Exception Data: 00000007

OS Version: 10.0.14393.2.0.0.256.48

Locale ID: 1033

Additional Information 1: efe8

Additional Information 2: efe8c9c5005dfa6d706d3e48047b0ab8

Additional Information 3: e8ec

Additional Information 4: e8ec7861d9fd373141fc63bd2495b8f6

 

Extra information about the problem

Bucket ID: 892d93409f7dc141f4a01d11a734d7aa (116186514970)

 

Source

Prepar3D exe

 

Summary

Stopped working

 

Date

‎9/‎4/‎2016 7:04 PM

 

Status

Report sent

 

Description

Faulting Application Path: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe

 

Problem signature

Problem Event Name: APPCRASH

Application Name: Prepar3D.exe

Application Version: 3.3.5.17625

Application Timestamp: 5758bb31

Fault Module Name: StackHash_0cf7

Fault Module Version: 10.0.14393.103

Fault Module Timestamp: 57b7e09e

Exception Code: c0000374

Exception Offset: PCH_AD_FROM_ntdll+0x0006E1BC

OS Version: 10.0.14393.2.0.0.256.48

Locale ID: 1033

Additional Information 1: 0cf7

Additional Information 2: 0cf734f677db08f81319571a3a39226d

Additional Information 3: f09f

Additional Information 4: f09f7e84f50f70c120c89f611f6ced81

 

Extra information about the problem

Bucket ID: e620c1bf0d23d79cefad6287ec218b86 (108381159842)

 

 

Source

Prepar3D exe

 

Summary

Stopped working

 

Date

‎9/‎5/‎2016 1:45 AM

 

Status

Report sent

 

Description

Faulting Application Path: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe

 

Problem signature

Problem Event Name: APPCRASH

Application Name: Prepar3D.exe

Application Version: 3.3.5.17625

Application Timestamp: 5758bb31

Fault Module Name: StackHash_57b0

Fault Module Version: 10.0.14393.103

Fault Module Timestamp: 57b7e09e

Exception Code: c0000374

Exception Offset: PCH_9E_FROM_ntdll+0x0006E1BC

OS Version: 10.0.14393.2.0.0.256.48

Locale ID: 1033

Additional Information 1: 57b0

Additional Information 2: 57b06985cdc04b330d2f528eeca3d1bf

Additional Information 3: 4312

Additional Information 4: 4312d2dca96d826794ede4ff73aa06f9

 

Extra information about the problem

Bucket ID: d19efb7435254f93c64219cf6d8a5956 (108380476707)

 

 

Source

Prepar3D exe

 

Summary

Stopped working

 

Date

‎9/‎5/‎2016 4:07 PM

 

Status

Report sent

 

Description

Faulting Application Path: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe

 

Problem signature

Problem Event Name: APPCRASH

Application Name: Prepar3D.exe

Application Version: 3.3.5.17625

Application Timestamp: 5758bb31

Fault Module Name: StackHash_a6f4

Fault Module Version: 10.0.14393.103

Fault Module Timestamp: 57b7e09e

Exception Code: c0000374

Exception Offset: PCH_54_FROM_ntdll+0x0006E1BC

OS Version: 10.0.14393.2.0.0.256.48

Locale ID: 1033

Additional Information 1: a6f4

Additional Information 2: a6f466e090001d971f84192b40ee9ab2

Additional Information 3: 63cd

Additional Information 4: 63cd6de33d5b001d383760c00eebd604

 

Extra information about the problem

Bucket ID: 4801078e17df6b3301d0c2474262c346 (108381381003)

 

-Zach Barrington

[scandinavian13 5,192]

 

 

Below are the crash logs from each flight.

 

All of these are errors specific to P3D. Please forward them the information.

[downscc 1,327]

 

 

Below are the crash logs from each flight.

 

All but one are the dreaded stackhash errors, the other being a runtime module with a stack overflow.  These are difficult to isolate, but it has to do with something not right in your system.  It's not P3D and it's not PMDG... all I can suggest is that you google the keyword stackhash to try to get some clues.  For example one clue is that this error occurs when DEP is invoked which means something running in windows is trying to access memory not authorized to it.

 

One technique is to eliminate things until the problem stops, the other is to go back to a clean install and get it working then add things.

[Zach Barrington 0]

Thanks for the leads! It will be a slow process trying to isolate the issue, as it takes a few hours for the crash to occur.

[downscc 1,327]

Thanks for the leads! It will be a slow process trying to isolate the issue, as it takes a few hours for the crash to occur.

Yeah, I've spent weeks on a problem that occurred between 4 and 10 hours.  Even if it doesn't happen you don't know if that is significant unless the error happens 100% of the time within that time span.

 

My preferred method is to start with a vanilla P3D and 777 without other addons.  Make sure it runs without error. Add/change something and test. Repeat.

[fluffyflops 1,858]

Ive had the issues from day 1 of the piece of crap  thats the 777 in p3d...

 

tonights loss of 8 hours of my life was from going from windowed screen to full screen.  I get the hour glass then bang ctd...

 

But no doubt Kyle will be along in a minute to cut and paste his normal line of "its not us its p3d, id love to help but we are too busy making the 747 to make some more money instead of fixing the buggy 777 in p3d"

 

ill even drop a screen shot look of all the flights I have succesfully done in other addons, but they will just blame p3d again and plam me off again... I absolutly zero respect for these bunch of conmen,

 

no other addons gives this much ###### apart from the 777 in p3d,,, 

Yeah, I've spent weeks on a problem that occurred between 4 and 10 hours.  Even if it doesn't happen you don't know if that is significant unless the error happens 100% of the time within that time span.

 

My preferred method is to start with a vanilla P3D and 777 without other addons.  Make sure it runs without error. Add/change something and test. Repeat.

 

 

you shouldnt have to Dan, I sick of PMDG blaming other people for their short comings.  its been happening ever since they released the triple for p3d

First off, thank you for taking the time to help me out! I saw another topic with someone who was having a similar issue 3 hours into his flights, but I don't think it was ever resolved.

 

 

 

 

There many many people with the issues of CTDs using the 777 in p3d,,, just look at the threads on here and the p3d forumn, I swaer no other addon has as many bug threads as the 777 in p3d

[downscc 1,327]

 

 

you shouldnt have to Dan, I sick of PMDG blaming other people for their short comings. its been happening ever since they released the triple for p3d

 

Your choice, you can stop using the product and move on or you can try to figure out the solution.  The only error that is repeatable that occurs over a period of time happens when you use the left PFD 2D popup, that is not your problem. Therefore, the problem you are having is unique and might have something to do with your computer. There are 100s of people that do not have any problem for every one that does...i don't care who you trash talk but if you are serious about trying to figure it out then we can have a dialog.