CTD upon touchdown

[stefltt 11]

I just had a CTD a few minutes ago when beginning to taxi at my departure airport SBEG. FTX Vectors was not reinstalled yet, so it's not the cause. It may be related to P3D directly ? For the time being, all CTDs have occured with the PMDG DC6. I need to try with the 747, the 777, and the 737 to check if it's happening again.

Here below a copy of messages in win10 log (in french). Maybe a specialist can decode all this stuff better than me.

Stéphane LI-THIAOTE

Quote

Application : Prepar3D.exe
Version du Framework : v4.0.30319
Description : le processus a été arrêté en raison d'une exception non gérée.
Informations sur l'exception : code d'exception c0000005, adresse d'exception 00007FFC61025090
Pile :
 

Quote

Nom de l’application défaillante Prepar3D.exe, version : 4.0.28.21686, horodatage : 0x594a7255
Nom du module défaillant : api.dll, version : 4.0.28.21686, horodatage : 0x594a7300
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000025090
ID du processus défaillant : 0x2538
Heure de début de l’application défaillante : 0x01d3085381e7d6cc
Chemin d’accès de l’application défaillante : D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Chemin d’accès du module défaillant: D:\Lockheed Martin\Prepar3D v4\api.dll
ID de rapport : 4b60dbcb-31f6-4662-af27-dd88f7c5d926
Nom complet du package défaillant : 
ID de l’application relative au package défaillant : 

Quote

Récipient d’erreurs , type 0
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0

Signature du problème : 
P1 : Prepar3D.exe
P2 : 4.0.28.21686
P3 : 594a7255
P4 : api.dll
P5 : 4.0.28.21686
P6 : 594a7300
P7 : c0000005
P8 : 0000000000025090
P9 : 
P10 : 

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER86FE.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8867.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8866.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8876.tmp.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_f18d325bc37cca5b5c8a87ac4eb53ecea819d212_305ee810_14949873

Symbole d’analyse : 
Nouvelle recherche de la solution : 0
ID de rapport : 4b60dbcb-31f6-4662-af27-dd88f7c5d926
Statut du rapport : 97
Récipient avec hachage : 

Quote

Nom de l’application défaillante Prepar3D.exe, version : 4.0.28.21686, horodatage : 0x594a7255
Nom du module défaillant : api.dll, version : 4.0.28.21686, horodatage : 0x594a7300
Code d’exception : 0xc000041d
Décalage d’erreur : 0x0000000000025090
ID du processus défaillant : 0x2538
Heure de début de l’application défaillante : 0x01d3085381e7d6cc
Chemin d’accès de l’application défaillante : D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Chemin d’accès du module défaillant: D:\Lockheed Martin\Prepar3D v4\api.dll
ID de rapport : 7ed7eace-e1f6-4405-b1ea-3318696a0253
Nom complet du package défaillant : 
ID de l’application relative au package défaillant : 

Quote

Récipient d’erreurs , type 0
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0

Signature du problème : 
P1 : Prepar3D.exe
P2 : 4.0.28.21686
P3 : 594a7255
P4 : api.dll
P5 : 4.0.28.21686
P6 : 594a7300
P7 : c000041d
P8 : 0000000000025090
P9 : 
P10 : 

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9B03.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C1D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C1E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9C2F.tmp.txt

Ces fichiers sont peut-être disponibles ici :
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_53e1be6cf8e402fee9220df1b2a23883cdec98_305ee810_2298aaa3

Symbole d’analyse : 
Nouvelle recherche de la solution : 0
ID de rapport : 7ed7eace-e1f6-4405-b1ea-3318696a0253
Statut du rapport : 97
Récipient avec hachage : 

 

 

[Adamski_NZ 952]

4 hours ago, scandinavian13 said:

How are you mapping a tiller axis, then?

In P3D Options/Controls/Axis Assignments (with the Saitek stick selected): Axis Steering Set.

Adam.

[Jack_Sawyer 4,600]

Same thing.  First real flight in it.

SKBO to SVMI - Orbx's new SA L/C - Chase Plane - Weather off - No FUSIPC - It crashed exactly on touchdown.

I will also submit a ticket.  I'm glad I searched first before stating a new post.

Here's all I got from the event viewer:

Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000316d3980
Faulting process id: 0xe34
Faulting application start time: 0x01d3094826f40ce4
Faulting application path: Z:\P3DV4\Prepar3D.exe
Faulting module path: unknown
Report Id: 81c61a90-7553-11e7-9853-d05099350c0e

 

 

[downscc 1,327]

It is going to be significant when somebody can come up with a specific set of conditions and configuration and steps take to reproduce because unless I've missed it no one can reproduce the events.  I know the beta team is trying but none of us can trigger the CTD on landing.

It would be helpful if information were passed among those that suffer this problem to see what can be ruled out and not... , and then start working on the possible causes.

[Viking01 183]

I passed all information I have on with my ticket and the questions to it. 

I can reproduce the CTD upon landing to about 80% of the flights as described in the ticket and the starting post. Same upon taxiing out: Full fuel load, no wx, no addons, KIAD, Flightplan KIAD-KORD, AFE on "maintaining". 5 tries, 4 CTD.

I can taxi out and complete the flight when I abort the AFE after he has completed the flow. 4 tries, 4 successful flights. No FSUIPC.

[downscc 1,327]

8 hours ago, Viking01 said:

I passed all information I have on with my ticket and the questions to it. 

I can reproduce the CTD upon landing to about 80% of the flights as described in the ticket and the starting post. Same upon taxiing out: Full fuel load, no wx, no addons, KIAD, Flightplan KIAD-KORD, AFE on "maintaining". 5 tries, 4 CTD.

I can taxi out and complete the flight when I abort the AFE after he has completed the flow. 4 tries, 4 successful flights. No FSUIPC.

That's good information Gunter.  As I never use the AFE that might be why I've never had this problem.  However, many others that do use the AFE don't have this problem so I hope the guys in support get enough feedback from those with the event to find the key to the solution.

[Meekg 86]

CTD on touchdown every flight.

[downscc 1,327]

39 minutes ago, Meekg said:

CTD on touchdown every flight.

That is exactly the kind of information that is useless... Mike, describe your configuration.  Using AFE? Using FSUIPC? Using any wx addon? Sound device? Using Orbx? Using Vector? etc...etc... this would be most helpful to the developers.

[Jack_Sawyer 4,600]

Hi Dan, I'll describe what happened to me.

Just got this plane and installed it.  Made one quick flight around an airport flight but didn't land, just quit the sim as I was in a rush.

Then I decided to fly from Bogota SKBO to Caracas SVMI.

The flight was perfect, I used the AFE for the before take off set up.  I didn't use him for the approach or landing.  But one thing I DID do was in the very beginning of the flight I changed GPS's which maybe wasn't a good idea.  When I did the window was flickering with about a zillion Windows chimes till I clicked on it that I acknowledged that it would reset the plane.  So it reset the plane and I continued with my flight.

Set up the autopilot to fly it along the way, made minor corrections with the knob for lateral guidance. All was well.

No AS4 & ASCA on this flight.

Chase Plane is installed.

Orbx South America LC, Orbx Global, Orbx Trees, Orbx Vector.

Was on a perfect ILS approach and landed, the second I went to spot view and started to taxi to the gate CTD.

Hope this helps.

Jack

[Meekg 86]

56 minutes ago, downscc said:

That is exactly the kind of information that is useless... Mike, describe your configuration.  Using AFE? Using FSUIPC? Using any wx addon? Sound device? Using Orbx? Using Vector? etc...etc... this would be most helpful to the developers.

AFE YES, FSUIPC YES, ORBX GLOBAL, TREES (no vector), sound device? My motherboard inbuilt one (realtek chipset I believe).

Useful information: I completed a couple of successful landings after adding the AlwaysFullLoad=1 in Prepar3d.cfg file main section.

Consequently I've had another CTD when trying to select the prop reversers back to normal, after normal application of reverse power.

The latter, as opposed to the CTD on touchdown generated an event, I therefore believe the two events are unrelated.
Here's the latest CTD log:

Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: menus.dll, version: 4.0.28.21686, time stamp: 0x594a71cc
Exception code: 0xc0000005
Fault offset: 0x0000000000005100
Faulting process ID: 0x43c0
Faulting application start time: 0x01d30a347726a402
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v4\menus.dll
Report ID: 94febc1e-4a65-4136-90b1-12e762f21768
Faulting package full name:
Faulting package-relative application ID:

 

[kityatyi 78]

CTD after commencing taxi. I thought it has to do with GSX but GSX was not involved at all this time. Quite a few of my flights on the DC-6 ended up with crashes-to-desktop for reasons yet unknown to me.

Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.0.28.21686
P3: 594a7255
P4: 0000
P5: 134217984
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DD1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DD1.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1DE2.tmp.txt
\\?\C:\Users\kityatyi\AppData\Local\Temp\WER115A.tmp.appcompat.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppHang_Prepar3D.exe_4025e111e034876a5e22fffa87f52b6d1447861_305ee810_6df61968

Analysis symbol: 
Rechecking for solution: 0
Report Id: bf88e662-aae9-499c-9bd3-dd92f5f4bea8
Report Status: 97
Hashed bucket: 

[Meekg 86]

14 hours ago, Meekg said:

Useful information: I completed a couple of successful landings after adding the AlwaysFullLoad=1 in Prepar3d.cfg file main section.

Disregard, the problem presented itself again.

[kityatyi 78]

...aaaand it happened again, just as I touched down, as soon as the landing gears touched the runway, screen froze, sound keeps playing and in 3 seconds simulator shuts down without a single error message. Ar least 25% of my flights in the DC-6 end up with a crash-to-desktop. Something is definitely not right with this bird. :-(

[RichieFly 729]

I had the crash at touchdown again after many flights without problems.

The new factor, I believe, was clearing out the cache files. I cleared them out since I installed a new nVidia driver. New driver...doubt it is the problem. I flew an entire flight in the 747 without issue. (man, what a flight it was too!)

 

It happened again. Quick turn around the airfield and upon nosewheel touching down, it crashed.

Here's the event viewer info:

Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: api.dll, version: 4.0.28.21686, time stamp: 0x594a7300
Exception code: 0xc000041d
Fault offset: 0x0000000000025090
Faulting process id: 0x3158
Faulting application start time: 0x01d30b0898c8273f
Faulting application path: D:\P3dInstall\Prepar3D v4\Prepar3D.exe
Faulting module path: D:\P3dInstall\Prepar3D v4\api.dll
Report Id: ca62bb66-9752-4a1b-9abd-0cf42f46561f
Faulting package full name: 
Faulting package-relative application ID: 

Some info about add ons:

ASP4, ASCA, Orbix Vector, Orbix Global. Otherwise, that's it.

Very strange. Could it be the new nVidia driver?

My hardware is in my signature.

Edited August 1, 2017 by RichieFly
More info

[Adamski_NZ 952]

Wow - this must be one of the most annoying bugs to track down. After struggling with it happening almost every flight (under various circumstances), I can't seem to reproduce it at all now!

I tried all the usual voodoo to *make it happen*, but no go. As regards the clearing of [shaders] cache (mentioned above) - I don't think that's the problem. I clear mine quite often (as I'm often testing new PTA preset settings) ... and it wasn't making any difference to when I *did* have the problem.

My current theory is that maybe some values/paths aren't being correctly initialised - so CTDs happen more often after a fresh install. With repeated use, maybe these values get stored (or cached) somewhere.

Adam.