CTD upon touchdown

[PMDG777 231]

12 minutes ago, kityatyi said:

However, I also had several crashes when I did not use GSX at all, like last night, when I ended up with a CTD upon the moment I touched down - even though I did not even open GSX during the entire session. In fact since I figured out that the above scenario goes well only if I do not use GSX, I completely avoid using GSX with the DC-6.

Can you disable GSX altogether from the sim (don't even let it run, uninstall if you have to), and see if it still crashes.

[kityatyi 78]

1 minute ago, PMDG777 said:

Can you disable GSX altogether from the sim (don't even let it run, uninstall if you have to), and see if it still crashes.

I will certainly give this one a try and see. Oh, and by the way, at some of the crashes that occured during the previously described scenario, sometimes, I did get a footprint in the Event Viewer that pointed out menus.dll as the cause of the crash. I actually do have one such report saved, this crash happened a few days ago, but exact same scenario as described before. See report:

 

Fault bucket 120786652171, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.0.28.21686
P3: 594a7255
P4: menus.dll
P5: 4.0.28.21686
P6: 594a71cc
P7: c000041d
P8: 0000000000005100
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB6D6.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7B2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7B3.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB7C4.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_9eb9d8d87e64ad31853d64b932b07e1fd28bc4_305ee810_0bdac647

Analysis symbol:
Rechecking for solution: 0
Report Id: dd7bff95-5b12-4544-9ebb-d203cc941ea4
Report Status: 268435457
Hashed bucket: 684799d30bfa640bc5326ff33878dc0d

----------------------

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: 0xc000041d
Fault offset: 0x0000000000005100
Faulting process id: 0x1684
Faulting application start time: 0x01d305920e8f2d8d
Faulting application path: E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: E:\Lockheed Martin\Prepar3D v4\menus.dll
Report Id: dd7bff95-5b12-4544-9ebb-d203cc941ea4
Faulting package full name:
Faulting package-relative application ID:

--------------------------------

 

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: 0x1684
Faulting application start time: 0x01d305920e8f2d8d
Faulting application path: E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: E:\Lockheed Martin\Prepar3D v4\menus.dll
Report Id: 02acc00a-fc4b-4427-a017-85a759db777e
Faulting package full name:
Faulting package-relative application ID:

 

---------------------------------

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

[Viking01 183]

I don't have any of the mentioned airports, sorry.

I did not have my headset plugged in when the CTD happened. I use a Logitech 3way surround system which is connected to my OnBoard sound card (no USB).

[PMDG777 231]

49 minutes ago, kityatyi said:

I will certainly give this one a try and see. Oh, and by the way, at some of the crashes that occured during the previously described scenario, sometimes, I did get a footprint in the Event Viewer that pointed out menus.dll as the cause of the crash. I actually do have one such report saved, this crash happened a few days ago, but exact same scenario as described before. See report:

Faulting application path: E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: E:\Lockheed Martin\Prepar3D v4\menus.dll

Yeah unfortunately it's such a generic module that it doesn't really give us many leads.

27 minutes ago, Viking01 said:

I don't have any of the mentioned airports, sorry.

I did not have my headset plugged in when the CTD happened. I use a Logitech 3way surround system which is connected to my OnBoard sound card (no USB).

Are you also using GSX?

[Viking01 183]

No, GSX is not on my system.

[Meekg 86]

Another CTD on touchdown...

So far these are the different conditions I've been using:

- Scenery default/add on

- Weather - AS ON/OFF

- AFE ON/OFF

- USB headset (connected but not used as default speakers)

- FSUIPC registered version, no brake or flight controls axis other than "steering set"

- no GSX installed
 

I have to be honest I'm very frustrated after 20 years of PMDG without a flaw.

[Meekg 86]

Somehow a CTD event was finally triggered upon touchdown.

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: 0xc0000005
Fault offset: 0x00000000000155d1
Faulting process ID: 0x2600
Faulting application start time: 0x01d30bc39967c588
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v4\api.dll
Report ID: 8aa7e2db-df61-4209-bda4-736a4d414422
Faulting package full name:
Faulting package-relative application ID:

 

Hope this helps.

[PMDG777 231]

6 hours ago, Meekg said:

Somehow a CTD event was finally triggered upon touchdown.

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: 0xc0000005
Fault offset: 0x00000000000155d1
Faulting process ID: 0x2600
Faulting application start time: 0x01d30bc39967c588
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v4\api.dll
Report ID: 8aa7e2db-df61-4209-bda4-736a4d414422
Faulting package full name:
Faulting package-relative application ID:

 

Hope this helps.

Unfortunately it really doesn’t. API.dll is a generic P3D dll that could be anything. 

[kityatyi 78]

Have been testing the Cloudmaster with GSX completely uninstalled from my system but the crashes keep coming. So far I could not find anything that might logically trigger them. Most of the time my crashes occur shortly after commencing taxi - rolling approximately 100 meters and then bang. Other times they happen at the moment of touchdown.

My latest taxi crash resulted in an error message and Event Viewer registered it. Most crashes happen without any messages. I crashed on exact same scenario today after trying to depart Minneapolis St Paul. Just left the stand, and shortly after came the CTD.

I have been using the AFE all the time for every single flow. I have also been using the animations that can be activated in the Ramp Manager. I have been using the NO GPS setup, it's radios only. P3DV4, Windows 10 here.

Below are the crash logs.
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.0.28.21686
P3: 594a7255
P4: KERNELBASE.dll
P5: 10.0.15063.483
P6: aa6457d1
P7: c000041d
P8: 0000000000069e08
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD62D.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD709.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD70A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD71B.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_7bf29b32c4a041f7ecb324f73f73d14657c5722b_305ee810_1b5add22

Analysis symbol: 
Rechecking for solution: 0
Report Id: 8c0708f8-88ca-4b7c-a94d-f861afe5d986
Report Status: 97
Hashed bucket

Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: KERNELBASE.dll, version: 10.0.15063.483, time stamp: 0xaa6457d1
Exception code: 0xc000041d
Fault offset: 0x0000000000069e08
Faulting process id: 0x2068
Faulting application start time: 0x01d30d3653855d3f
Faulting application path: E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 8c0708f8-88ca-4b7c-a94d-f861afe5d986
Faulting package full name: 
Faulting package-relative application ID: 

[PMDG777 231]

Well consider me well and truly stumped!!

[Viking01 183]

Have you ever tried pressing "abort" for the AFE after he completed every active flow? I do that and never had CTD anymore.

[kityatyi 78]

7 minutes ago, Viking01 said:

Have you ever tried pressing "abort" for the AFE after he completed every active flow? I do that and never had CTD anymore.

Interesting observation Günter. Do you mean that I wait until each flow is completed and then press "abort" then? Let's say, I run the preflight flow, then press abort once done. Then run the after start flow, and the press abort when done. Like so? I will give this a go. If I can avoid the crashes this way then it's pretty much certain that it's the flight engineer that cannot behave himself. Needs to undergo some refreshing CRM course then. :-P

[kityatyi 78]

Unfortunately "aborting" the AFE after each flow did not solve the issue. Crashed again, shortly after commencing taxi out of KMSP. I now suspect SODE as the cause of these crashes as I so far had these crashes at the new Drzewiecki NYAV2 which uses SODE and now Flightbeam's KMSP which also does. My touchdown-crash last time was at Flightbeam's KIAD, also a SODE equipped scenery. I am now gonna try and depart from a non-SODE airport and land at another non-SODE scenery. If it  goes without crashing to desktop, it's very much likely that SODE has to do with the crashes. 

I did many flights between FSDT KMEM and FSDT KIAH, no issues there. Also did flights between FSDT KMEM and FSDT KCLT, no issues. The only confusing thing is that I already managed to successfully fly out of DD NYAV2 KLGA where I also experienced many crashed after commencing taxi. And I also managed to depart from Flightbeam's KIAD successfully without crashing, although I did end up with a CTD when coming in to land from KCLT. If my theory holds true and it's SODE related then I need to add that CTD occurs 50-75% of the times when departing from or landing at SODE equipped scenery but not necessarily always.

My latest CTD - with aborting the AFE after each flow - again gave a report which highlights menus.dll as the module to blame.
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.0.28.21686
P3: 594a7255
P4: menus.dll
P5: 4.0.28.21686
P6: 594a71cc
P7: c000041d
P8: 0000000000005100
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER863D.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8719.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER871A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER872A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_9eb9d8d87e64ad31853d64b932b07e1fd28bc4_305ee810_12958e99

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3e766271-73ee-4ba5-8dbf-26fdb15682d2
Report Status: 97
Hashed bucket: 

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: 0xc000041d
Fault offset: 0x0000000000005100
Faulting process id: 0x1348
Faulting application start time: 0x01d30d3d0d6b9096
Faulting application path: E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: E:\Lockheed Martin\Prepar3D v4\menus.dll
Report Id: 3e766271-73ee-4ba5-8dbf-26fdb15682d2
Faulting package full name: 
Faulting package-relative application ID: 

[r_stopnicki 92]

Unfortunately, I have to join this conversation, as I am having CTD since the recent update to Version 1.20.8418

My CTD has occurred at several airports, including those where I had not had CTD's (actually never had them at all!) as recently as last week, before the update.

Of interest, is that at a particular airport (SLSB), I will get a CTD at exactly the same point while taxiing for departure. However, if I head to another runway, I will not get the CTD.

I have had a couple of CTD upon taxiin after landing, but never right at touch down.

I have ORBX Base Pack and South Ame3rica, as my scenery add-ons.

I have a number of Go Flight modules, however, the only ones related to the DC-6 are the throttle quadrant and the landing gear.

I continuously update FSUIPC and I have recently updated to FSUIPC5.11

My system is:

Windows 7 Pro x64

Intel Core i7-4790K

Ram 16GB

Nvidia GeForce GTX-780

All my other PMDG aircraft are operating OK.

I have noticed that the log.txt file has not updated since July 30th

Of final note, sometimes the CTD comes with a warning window (program has stopped .... etc) and others, the simulator simply stops without warning and the screen simply returns to my normal desktop.

I am following this thread with much interest.

Roberto

[kityatyi 78]

2 minutes ago, r_stopnicki said:

Unfortunately, I have to join this conversation, as I am having CTD since the recent update to Version 1.20.8418

My CTD has occurred at several airports, including those where I had not had CTD's (actually never had them at all!) as recently as last week, before the update.

Of interest, is that at a particular airport (SLSB), I will get a CTD at exactly the same point while taxiing for departure. However, if I head to another runway, I will not get the CTD.

I have had a couple of CTD upon taxiin after landing, but never right at touch down.

I have ORBX Base Pack and South Ame3rica, as my scenery add-ons.

I have a number of Go Flight modules, however, the only ones related to the DC-6 are the throttle quadrant and the landing gear.

I continuously update FSUIPC and I have recently updated to FSUIPC5.11

My system is:

Windows 7 Pro x64

Intel Core i7-4790K

Ram 16GB

Nvidia GeForce GTX-780

All my other PMDG aircraft are operating OK.

I have noticed that the log.txt file has not updated since July 30th

Of final note, sometimes the CTD comes with a warning window (program has stopped .... etc) and others, the simulator simply stops without warning and the screen simply returns to my normal desktop.

I am following this thread with much interest.

Roberto

Exactly the same way as I get my crashes.