Jump to content

Numerous CTD


Bernard Ducret

Recommended Posts

I  continue having several CTD with the A330 since I purchased it last April. My latest were one on a flight from VTSP to LSZH when lining up with the LOC 28 at LSZH, suddenly the plane became uncontrollable and crashed to CTD, yesterday on a flight from TFFF to LFPO, everything fine until my descent when I switched to the FMCG to enter my landing data, CTD...  Today, same flight, but this time CTD on the ground at TFFF. That airplane is special indeed, fortunately I have plenty of others (more complex) where my flights do end up at the gate!...

 

Jokes apart, I would not mind understanding what the problem is, as I mentioned tongue in cheek, several other complex airplanes reputed to me much more hungry on resources demonstrate no such problem, so I am at a loss to understand why this A330 can't reach its destinations. In most cases so far, my CTD would happen when switching to a different view, today it is when I called the flight computer view (not the first time this happens).

 

So any help will be welcome indeed.

 

Yesterday, CTD upon entering descent data into FMCG:

 

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:    C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe

Problem signature
Problem Event Name:    AppHangXProcB1
Application Name:    Prepar3D.exe
Application Version:    4.5.14.34698
Application Timestamp:    5e94b5c2
Hang Signature:    1c8b
Hang Type:    134250496
Waiting on Application Name:    dxdiag.exe
Waiting on Application Version:    10.0.18362.387
OS Version:    10.0.18363.2.0.0.768.101
Locale ID:    4108
Additional Hang Signature 1:    1c8be9cbb6b1410d402a17e1a1dca7da
Additional Hang Signature 2:    d887
Additional Hang Signature 3:    d8877434df3c4a8e07591cc978a38401
Additional Hang Signature 4:    1c8b
Additional Hang Signature 5:    1c8be9cbb6b1410d402a17e1a1dca7da
Additional Hang Signature 6:    d887
Additional Hang Signature 7:    d8877434df3c4a8e07591cc978a38401

Extra information about the problem
Bucket ID:    4c01f845cfe4ed1037fb82ec002f1808 (1728118832153696264)
 

This morning, same flight from TFFF, but this time, the CTD happened on the ground after I started the APU immediately before pushback:

 

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:    C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe

Problem signature
Problem Event Name:    AppHangB1
Application Name:    Prepar3D.exe
Application Version:    4.5.14.34698
Application Timestamp:    5e94b5c2
Hang Signature:    6bbc
Hang Type:    134217729
OS Version:    10.0.18363.2.0.0.768.101
Locale ID:    4108
Additional Hang Signature 1:    6bbc6ba8cdd50d5c60783929fd30f220
Additional Hang Signature 2:    1aba
Additional Hang Signature 3:    1abaf2ff6a516ff174e45303e3999d24
Additional Hang Signature 4:    b218
Additional Hang Signature 5:    b2183095f5ec05d744247b18b597f1c3
Additional Hang Signature 6:    d09a
Additional Hang Signature 7:    d09a55ff9f1cb25c0ec1f84aae1aef5c

Extra information about the problem
Bucket ID:    72dd8b7d37c7455066b27d16e240e41d (1635507151927567389)
 

As a reminder, my PC main specifications are as follows:

  • P3Dv4.5.3
  • Windows 10 Home 1909
  • Intel 8770K NO OC, NO HT
  • EVGA GeForce GTX 1070 8GB VRAM, Driver 446.14
  • 32 GB RAM

The A330 is installed in the Aerosoft folder on C drive along with my numerous other Aerosoft products.

 

I am using the plane in conjunction with the usual following software:

  • Active Sky P3Dv4.5
  • REX Environment Force
  • Aivlasoft EFB v2
  • MCE
  • GSX 2
  • Track IR

 

Thank you. 

Link to comment
Share on other sites

  • Deputy Sheriffs
1 hour ago, Jean-Claude said:

Waiting on Application Name:    dxdiag.exe

At least this message points to a problem with DirectX. Make sure that all your drivers are up to date.

Run the attached tool and post the output here.

Link to comment
Share on other sites

  • Aerosoft

Oops missed that.

 

CTD's on view changes have been an issue ever since P3d V3 and I have never found any reliable information on it. To make sure it does not have to do with resources, could you set the sim to minimal settings and try to force the error again?

 

Link to comment
Share on other sites

Hi Otto, here is the requested file.

 

Hardware
--------
CPU Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
GPU NVIDIA GeForce GTX 1070 (2560 x 1440 x 4294967296 colors)
GPU Driver 446.14
RAM 32GB @ 3200MHz

Microsoft Windows
-----------------
Windows 10 Post April 2020 (2004) Update 64-bit

User Profile and Document Folders
---------------------------------
User Profile Location:
Environment.GetFolderPath =        C:\Users\Simulateur
Volatile Environment\USERPROFILE = C:\Users\Simulateur

Documents Folder:
Environment.GetFolderPath = C:\Users\Simulateur\Documents
Shell Folders\Personal =    C:\Users\Simulateur\Documents


Microsoft .NET Framework 1.0 - 4.0
----------------------------------
.NET Framework DF
.NET Framework 2.0.50727 Service Pack 2
.NET Framework 3.0 Service Pack 2
.NET Framework 3.5 Service Pack 1
.NET Framework 4
.NET Framework 4.0

Microsoft .NET Framework 4.5+
-----------------------------
.NET Framework 4.7.2 or later (only latest version is shown)

Microsoft Flight Simulator X & Lockheed Martin Prepar3D
-------------------------------------------------------
Prepar3D v4.x (4.5.14.34698) found at: C:\Program Files\Lockheed Martin\Prepar3D v4\
Prepar3D v3.x not installed
FSX Steam Edition not installed
FSX SP2/Acceleration not installed

X-Plane 10 & 11
---------------
X-Plane 11 not installed

X-Plane 10 not installed

Microsoft XAudio2
-----------------
XAudio2_9.dll found: 10.0.18362.650 (WinBuild.160101.0800)
XAudio2_8.dll found: 10.0.18362.1 (WinBuild.160101.0800)
XAudio2_7.dll found: 9.29 (DXSDK_JUN10.100602-0421)
XAudio2_6.dll found: 9.28 (DXSDK_FEB10.100204-0932)
XAudio2_5.dll found: 9.27 (DXSDK_AUG09.090904-1620)
XAudio2_4.dll found: 9.26 (DXSDK_MAR09.090316-1354)
XAudio2_3.dll found: 9.25 (DXSDK_NOV08.081027-0939)
XAudio2_2.dll found: 9.24 (DXSDK_AUG08.080731-0600)
XAudio2_1.dll found: 9.23 (DXSDK_JUN08.080530-1349)
XAudio2_0.dll found: 9.22 (DXSDK_MAR08.080305-1539)


Simconnect, SDKs and Visual C++ Redistributables
------------------------------------------------
Microsoft ESP SimConnect Client v1.0.20.0 - (Version Data: 1.0.20.0)
Microsoft Flight Simulator SimConnect Client v10.0.60905.0 - (Version Data: 10.0.60905.0)
Microsoft Flight Simulator SimConnect Client v10.0.61242.0 - (Version Data: 10.0.61242.0)
Microsoft Flight Simulator SimConnect Client v10.0.61259.0 - (Version Data: 10.0.61259.0)
Microsoft Visual C++ 2005 Redistributable - (Version Data: 8.0.56336.0)
Microsoft Visual C++ 2005 Redistributable - (Version Data: 8.0.61001.0)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17 - (Version Data: 9.0.30729.0)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161 - (Version Data: 9.0.30729.0)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.21022 - (Version Data: 9.0.21022.0)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161 - (Version Data: 9.0.30729.0)
Microsoft Visual C++ 2010  x64 Redistributable - 10.0.40219 - (Version Data: 10.0.40219.0)
Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219 - (Version Data: 10.0.40219.0)
Microsoft Visual C++ 2012 x64 Additional Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2012 x64 Minimum Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2013 x64 Additional Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2019 X64 Additional Runtime - 14.25.28508 - (Version Data: 14.25.28508.0)
Microsoft Visual C++ 2019 X64 Minimum Runtime - 14.25.28508 - (Version Data: 14.25.28508.0)
Microsoft Visual C++ 2019 X86 Additional Runtime - 14.23.27820 - (Version Data: 14.23.27820.0)
Microsoft Visual C++ 2019 X86 Minimum Runtime - 14.23.27820 - (Version Data: 14.23.27820.0)
Prepar3D v4 Content - (Version Data: 4.5.14.0)
Prepar3D v4 Professional Client - (Version Data: 4.5.14.0)
Prepar3D v4 Scenery - (Version Data: 4.1.7.0)
 

Link to comment
Share on other sites

52 minutes ago, Mathijs Kok said:

To make sure it does not have to do with resources, could you set the sim to minimal settings and try to force the error again?

Thanks Mathijs, I understand your suggestion. But since my settings are perfectly working with all my other complex add-ons with no such CTDs, I am reluctant to consider that I would need to reduce my settings simply to use the A330. As a compromise, until we get to the bottom of that, I will make my A330 flights without changing views and see if I run into this problem again for any other reason (because the problem reports dont all point to that only direction). The views that I am mostly using are: Outside spot view (during cruise flight to avoid ghost imaging on my screen), VC left side and MCDU 1. I use the MCDU 3 to load the plane and prepare for the flight, then I ignore it.

 

Something I have been wondering: Is it safer to "call" the MCDU 1 with Shift+1 or cycle through the views to it (I dont remember which P3D key is used for that as I am using a switch on my yoke), is one solution better than the other to avoid this kind of problem?

 

Thank you.

Link to comment
Share on other sites

  • Aerosoft

I see your point but at the same time we have thousands of people who do NOT have the issue you face. So it simply has to be something local on your system. As you will have seen there were around 18 people on the forum reporting the same thing that you see. Some of them fixed issues with .net runtimes, others with DirectX, and three could only fix the issue by a clean install of the os and the sim.  That other add-ons work does not give any solid information because all complex add-ons contains different codes, often made with different tools and often compiled for the sim with different versions of the SDK. I got one system where none of the PMDG aircraft wort and I simply know that is not because the add-on has an issue but because something is wrong with the system. 

 

In no way intended to speak bad of the PMDG products (we are proud distributors of their products and they are good friends) but they know the issues regarding view changes. Just google 'pmdg view change crash" and you will find this is an issue going on for years. You will find the same for every complex aircraft. And often people will write that other complex add-ons work fine, lol. The issue you have can be solved, we know that a correct OS and a correct P3D will not show the issue. Exactly what causes it on your system is near impossible to know. Personally I would completely re-install all runtimes first and if that does not solve it do a re-install of the sim.

 

I do not think that calling up the views differently will matter a lot. What I do know is that you are more likely to run into the issues when you are low on GPU memory and that is why I asked you to test with a lower load.

Link to comment
Share on other sites

  • Deputy Sheriffs

Another suggestion:
Looking at your first error message, P3D called the dxdiag.exe, which is IMHO very unusual.

So please run the dxdiag.exe directly and check if it reports any problems.

Another  thing: you installed P3D under c:\Program Files. This is not the best place for such kind of software, although the installer offers this folder. So in case you consider a reinstall, install it elsewhere outside this folder.

Link to comment
Share on other sites

Thanks a lot to all for your help. I shall try your suggestions next Thursday morning and will report back if I have any issue, otherwise, I will fly the A330 and be watchful of your information in any upcoming problem and will provide feedback on this thread.

Only thing I wish to avoid at this time is a full re-install, within the next six months, either I'll move on to MSFS 2020 or P3Dv5, so I'll keep using the aircraft that leave me in peace during that period if the A330 does not want to cooperate nicely, but I like the A330 and would prefer very much to resolve this issue if realistically doable and without too much hassle.

And, by the way, great and friendly support gentlemen!

Link to comment
Share on other sites

  • Deputy Sheriffs

Yes, a fresh install of everything nobody wants, but as Mathijs already said, in some cases it was the only solution.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use