I'm have a rash of intermittent CTD when I try to fly into KSEA. I've had this happen in the PMDG 737 and 777. It always seems to happen in the descent between 17000 and 12000 feet and always from the south or south east. What happens is the sim will pause for a few seconds as the icon spins and CTD. There is no messages in Event Viewer or AppCrashViewer. I can fly in from Alaska and have not had a CTD yet. I can fly out of any of the local airports with no CTD. I have followed Jim Youngs advice when it comes to add-on.cfg and scenery.cfg using NotePad++ and I get no errors when I check them with Addon Oraganizer.  I have no other 3rd party scenery in the area except FSDT Vancouver to the north. i have the following installed:

• Taxi2Gate KSEA
• DD Seattle Airports (KSEA Not Selected)
• FTX Global (No PNW)
• FTX Landclass

Any suggestions would be appreciated. 

Perhaps you could remove each of the airport add-ons (one at a time) to see if the CTD continues to occur.  That way you can isolate the issue to a particular add-on.  I would start with DD Seattle Airports, then Taxi2Gate.  I doubt the FTX products are causing this.

Edited October 20, 20187 yr by dmiannay

Sounds like a plan. Problem is I have to do a flight from LAX to SEA each time to isolate. I was hoping someone else had experienced the problem. Well time to fly the first test to get a good CTD location and then disable scenery from there and fly it again and again, LOL 

This is the first time I have heard of a crash from LAX to SEA.  So, if you fly out of Portland to SEA, there is no problem?  I cannot see how a flight from LAX to SEA would create the issue and a flight from Portland to SEA would not.  If you didn't have a 64 bit app, I would suspect an out of VAS error but that's impossible with 64-bit apps.

I have all of the products you have installed and have had no issues.  What AI program do you have installed?

Since you did not get a crash report or anything in the Event Viewer, an AppHang usually is caused by a call by the application for an object on the ground or in the air and the sim cannot find it or it is incompatible. 

Do you have Autosave turned on via the FSUIPC?

You can also run Process Monitor (see page 18, AVSIM CTD Guide).  I would pause the flight just before you think the crash will occur (at FL 220?), open up Process Monitor and set it up to show only the P3DV4 process.  Then, when you see the icon spinning, you can go the the Process Monitor and look at what was loading by starting about a minute or two before the crash.  If it is SeattleX, then you know it is probably at fault.  Still, photographic scenery from around the world loads even if you are landing at KSEA and there could be an issue there too.