The CTD issues in FS is truly a love hate relationship.   Anyone getting CTD's over the same exact locations everytime they try?  I'm finding flying west south of Birmingham Alabama from any airport in the Atlanta area (KATL, KFFC) I never fail to get a CTD.  Right as I'm at the top of climb from KFFC which is usually over the south Birmingham area there goes the 0xc0000005 error.  Another guaranteed location is flying from the Minneapolis area mainly KFCM with a top of climb over Rochester MN, BAM CTD error 0xc0000005 in event viewer...

What I've found to get around this is setup the flight plan to fly around these areas then it works.  I usually use the 'Jump To' feature after reaching cruise altitude which is nice for longer flights but not being able to reach cruise when flying over smaller cities is a problem.  It's hard to trace something like this down.  

Well, I'd take a location based CTD over a random one any day. Never had those, but I guess the way MSFS scenery works, there's always the chance to tap into some data the sim just can't digest. I think some day, those issues will be fixed, just like some day, we'll have realistic traffic... patience, the must have for simmers.

Try flying into the area from different directions, and see if you can narrow it down to an individual airport or scenery. Then report it on ZenDesk. It worked for me when I was getting CTDs near Seoul Korea airport.

Had my first CTD last night, flying over the Toronto area.  I had never flown there before.

Just before the CTD,  I noticed a very large amount of AI traffic in Little Nav.  Possibly not the number, but density of AI or other aircraft is causing a memory overflow?

I need to test more, but just a thought.

 

Best,

Mark

 

I started getting CTD’s not too long after takeoff with the latest patch after rarely seeing any in MSFS previously.  I tried removing a few things (the new freeware Goose including the hotfix and the previously freeware now payware winter trees mod) and turning off multiplayer traffic.  This stopped the CTD’s after takeoff.  I’m still in the process of putting them back in to see if I can trigger the CTD’s again.

I read elsewhere that some were having CTD’s caused by other people using the Carenado C182 in multiplayer hence why I disabled multiplayer (I don’t own the 182 so I’m not sure if that could still be a factor for me or not with multiplayer enabled).  I recall @Bert Pieke had reported this issue with the C182.

To be clear I haven’t determined if either of those mods are an issue (I downloaded the Goose with the hotfix so I doubt that’s it), just thought I’d share what I’m doing to try and track down my CTD issue.

Edited December 25, 20205 yr by regis9

1 hour ago, Dillon said:

The CTD issues in FS is truly a love hate relationship.   Anyone getting CTD's over the same exact locations everytime they try?  I'm finding flying west south of Birmingham Alabama from any airport in the Atlanta area (KATL, KFFC) I never fail to get a CTD.  Right as I'm at the top of climb from KFFC which is usually over the south Birmingham area there goes the 0xc0000005 error.  Another guaranteed location is flying from the Minneapolis area mainly KFCM with a top of climb over Rochester MN, BAM CTD error 0xc0000005 in event viewer...

What I've found to get around this is setup the flight plan to fly around these areas then it works.  I usually use the 'Jump To' feature after reaching cruise altitude which is nice for longer flights but not being able to reach cruise when flying over smaller cities is a problem.  It's hard to trace something like this down.  

I don’t see the same from KRYY or KFTY. Could it be something specific to your setup?

1 hour ago, regis9 said:

(I don’t own the 182 so I’m not sure if that could still be a factor for me or not with multiplayer enabled)

If you do not have the C182 installed, this would not be the cause..

Hey Dillon, would you please lay down the love part of your relationship with CTD's for me? I tried really hard to come up with these...

• Loving to run a sim so advanced it cannot not crash.

• Loving that the PC runs super cool after the CTD killed all the system load.

• Loving the kind reminder to get on with real life.