46 minutes ago, Bobsk8 said:

First flight of the day around 90 miles. Made it about 80 miles.......CTD....

[...]
Exception code: 0xc0000005
 

I know how that feels. After weeks of trying to solve this I am almost at the point that I dread starting up the sim again.

Early february things seem to go right for me. I reinstalled the sim and was able to complete a few longer flights. Each flight (from France to Sweden via Germany)was over 3 hours in the Carenado Mooney and went without a problem. Even running several external programs, community addons like GNS530 and AI switched on.

Thinking the problems was finally solved, I looked forward to the UK World Update and purchased my last addon, Orbx Dundee airport.

As soon as the World Update was installed, I took off from ESUE with destination EGPN, hoping to not only visit my new airport but also enjoy the updated UK scenery. Then, about halfway the North Sea, I again had a CTD, the same as you have.

So naturally I again disabled all community addons, switched off Online AI and refrained from using Simconnect but everytime I did the same flight, the CTD would be there somewhere along the route. Filed another ticket with Asobo, got the same useless troubleshooting guide.

Since reinstalling obviously didn't help, I did a complete reinstall of windows on another drive but after finding out that it was even worse I sort of broke down and haven't touched MSFS since, apart from flying a few circuits to test out my yoke which I also had to RMA several times already. It seems that I have run out of luck somewhere along the route.

Edited March 6, 20215 yr by orchestra_nl

7 minutes ago, orchestra_nl said:

I know how that feels. After weeks of trying to solve this I am almost at the point that I dread starting up the sim again.

Early february things seem to go right for me. I reinstalled the sim and was able to complete a few longer flights. Each flight (from France to Sweden via Germany)was over 3 hours in the Carenado Mooney and went without a problem. Even running several external programs, community addons like GNS530 and AI switched on.

Thinking the problems was finally solved, I looked forward to the UK World Update and purchased my last addon, Orbx Dundee airport.

As soon as the World Update was installed, I took off from ESUE with destination EGPN, hoping to not only visit my new airport but also enjoy the updated UK scenery. Then, about halfway the North Sea, I again had a CTD, the same as you have.

So naturally I again disabled all community addons, switched off Online AI and refrained from using Simconnect but everytime I did the same flight, the CTD would be there somewhere along the route. Filed another ticket with Asobo, got the same useless troubleshooting guide.

Since reinstalling obviously didn't help, I did a complete reinstall of windows on another drive but after finding out that it was even worse I sort of broke down and haven't touched MSFS since, apart from flying a few circuits to test out my yoke which I also had to RMA several times already. It seems that I have run out of luck somewhere along the route.

I just discovered that within 15miles of KMSP , I get a CTD. Guess I will have to start a list of airports that I have to stay away from. 

3 hours ago, orchestra_nl said:

I do wonder if everyone that has these issues is using an AMD platform. AMD is currently researching a possible issue with their X570 USB controller which might be related since most other games I play only need keyboard and mouse.

On the other hand, not everyone with these errors is using an X570 motherboard. I am not even sure if it is limited to the AMD platform.

 

That's very interesting, Allard.
X570 mobo here as well.

The CTD issue began with WU3, just after I switched from an i9 9900K to an AMD platform.
 

X570 M/Board here as well. just done another flight and again no issue, hopefully the turning off of Rolling Cache seems to have cured it so far. (And i am not using the VFR map either)

Edited March 6, 20215 yr by Car147

2 minutes ago, Car147 said:

X570 M/Board here as well. just done another flight and again no issue, hopefully the turning off of Rolling Cache seems to have cured it so far. (And i am not using the VFR map either)

I finally made a successful flight from LIPR to LIPZ.  ( Got out of the US)

For some reason my issues were worse in Europe, (especially over France)

2 minutes ago, Car147 said:

For some reason my issues were worse in Europe, (especially over France)

Funny, but I CTD going into KSMP twice in a row at just about the same spot in the flight path, I am wondering now if this has something to do with the size of the airport or the scenery MS 2020 has to download from the server causing these issues. 

Edited March 6, 20215 yr by Bobsk8

On 3/5/2021 at 1:24 AM, Bobsk8 said:

Counting the seconds until someone tells you  your system is NG, because only those people get CTDs'''     🤣

I seem to remember maybe it was back in the FS2002 or maybe FS2004 and very earliest FSX days we started to get the first serious repeated crash errors. I am the first to put my hand up in declaring it was badly setup or built machines. From memory it was one of the first terrain related issues fixed up by a patch. Oh for the days of simple downloadable patches that actually fixed things without breaking something else.

I am starting to very fondly look back on the era 1999 - 2007 as a golden age where things essentially either worked out of the box (literally) or did not stay disfunctional for very long.

Is it only in specific flying area that you get CTD ?   I never had a CTD in MSFS but I mostly fly in NA. Maybe I need to go across the pond and see if I can get a CTD as well.

1 hour ago, Bobsk8 said:

Funny, but I CTD going into KSMP twice in a row at just about the same spot in the flight path, I am wondering now if this has something to do with the size of the airport or the scenery MS 2020 has to download from the server causing these issues. 

I had lots of problems around KLBX. Tried flying from there a dozen times to KBTR. I often CTD'd early, somewhere around KBPT, but sometimes the CTD occured on approach to KBTR rwy 22R.

Suspecting USB issues, I even removed every single USB device except my mouse, and let the AI pilot fly the same route. He had the same CTD, but perhaps it took a bit longer.
And it is always the exact same error. The only time I had a different error code was when I experimenting with virtual memory settings in Windows. I had set it to a fixed 8GB since I have 32GB RAM I thought it was enough. It wasn't, and I learned that sometimes, MSFS can use over 30GB of memory.

33 minutes ago, fogboundturtle said:

Is it only in specific flying area that you get CTD ?   I never had a CTD in MSFS but I mostly fly in NA. Maybe I need to go across the pond and see if I can get a CTD as well.

I think I had very few problems in Alaska, a repeatable one in Washington just south of W16 (First air airport), but that was before the US world update. After the US update I flew without issues around Nevada and Oregon. California wasn't that bad, but problems started around the gulf of Mexico.
Come to think of it, I mostly flew short hops before I reached California. After that I started flying longer flights.
I had no issues flying in Europe over the Alps, Italy and France but the UK is hit or miss, even before the UK world update. I do have quite a few UK third party airports there.

Edited March 6, 20215 yr by orchestra_nl

34 minutes ago, fogboundturtle said:

Is it only in specific flying area that you get CTD ?   I never had a CTD in MSFS but I mostly fly in NA. Maybe I need to go across the pond and see if I can get a CTD as well.

The only time i had ctd's in a particular area was before WU3. Everytime i flew near LFRS it would crash. I took the cordinates and sent them to Zendesk and within 24hrs that issue disappeared.

But since WU3 it can happen anywhere, either still in the initial climb, (Rarely) Crz (even rarer) and mostly in descent or approach.

Edited March 6, 20215 yr by Car147

I wonder if this is not a Azure server issue. If you disable photogrammetry, do you still CTD ?

2 minutes ago, Car147 said:

The only time i had ctd's in a particular area was before WU3. Everytime i flew near LFRS it would crash. I took the cordinates and sent them to Zendesk and within 24hrs that issue disappeared.

But since WU3 it can happen anywhere, either still in the initial climb, (Rarely) Crz (even rarer) and mostly in descent or approach.

Haven't thought about that. but you are right. It is always in descent or approach, never had one in climb, and I have had too  many of them. 

I just went through my eventlog again. When Flightsimulator crashes, I get the 0xc0000005 error in the Application log. I also get a warning in the System log, saying disk 5 (or 6) has been surprise removed around the same time.
I don't have a disk with that number though, but it might be a scratch disk that MSFS creates for caching purposes. It MSFS crashes, it might be logical to get this error but I do wonder if others get that too.

16 minutes ago, orchestra_nl said:

I just went through my eventlog again. When Flightsimulator crashes, I get the 0xc0000005 error in the Application log. I also get a warning in the System log, saying disk 5 (or 6) has been surprise removed around the same time.
I don't have a disk with that number though, but it might be a scratch disk that MSFS creates for caching purposes. It MSFS crashes, it might be logical to get this error but I do wonder if others get that too.

Yes, i have seen the same error message, or another favourite is the VCcruntime dll. Even tried removing them and re-installing them as directed by Zendesk.

Edited March 6, 20215 yr by Car147