What is super frustrating is that someone with Windows OS knowledge should be able to look at the stack traces from the Windows Event Viewer and diagnose what is going on.  You'd think being a part of Microsoft and all and having sold $160 million worth of copies of MSFS that the Flight Simulator team might be able to send some logs over to the Windows team and request a few minutes for them to review.

I have been thinking about this, and even thought about server issues when this CTD started. 

 

1 CTDs only happen on approach, never on take off or departure.

2. CTDs only seem to happen at very large airports surrounded by big cities or dense population areas. 

3. If I have a CTD like I did this morning flying into KMSP, and I do tghe same exact flight, it CTDs in about the same area on approach. I have had this happen many times before in places like London, LA area, Toronto, Montreal  etc.  

 

I think the reason that this doesn't happen on the departure leg, is because when you load the flight it has all kinds of time to get all the scenery required from the server. On approach, it's a different story. You are losing altitude which requires more data for detail in the lower altitudes of scenery, and you are approaching an area where this data is needed. 

This has nothing to do with the persons ISP, but more with the servers . This may be why Asobo doesn't seem to be able to solve this problem, because they are right next to the severs more than likely so they don't experience this issue. 

 

Now I may be totally wrong with this theory, but so far I have not read one suggestion by anyone that seems to cure this problem. 

2 minutes ago, marsman2020 said:

What is super frustrating is that someone with Windows OS knowledge should be able to look at the stack traces from the Windows Event Viewer and diagnose what is going on.  You'd think being a part of Microsoft and all and having sold $160 million worth of copies of MSFS that the Flight Simulator team might be able to send some logs over to the Windows team and request a few minutes for them to review.

I agree, it doesn't seem like they are focusing on this issue at all. They are worried more about the eye candy in the sim. 

2 hours ago, Bobsk8 said:

I have been thinking about this, and even thought about server issues when this CTD started. 

 

1 CTDs only happen on approach, never on take off or departure.

2. CTDs only seem to happen at very large airports surrounded by big cities or dense population areas. 

3. If I have a CTD like I did this morning flying into KMSP, and I do tghe same exact flight, it CTDs in about the same area on approach. I have had this happen many times before in places like London, LA area, Toronto, Montreal  etc.  

 

I think the reason that this doesn't happen on the departure leg, is because when you load the flight it has all kinds of time to get all the scenery required from the server. On approach, it's a different story. You are losing altitude which requires more data for detail in the lower altitudes of scenery, and you are approaching an area where this data is needed. 

This has nothing to do with the persons ISP, but more with the servers . This may be why Asobo doesn't seem to be able to solve this problem, because they are right next to the severs more than likely so they don't experience this issue. 

 

Now I may be totally wrong with this theory, but so far I have not read one suggestion by anyone that seems to cure this problem. 

So far my theory has panned out. I have gone on 4 flights today averaging around 120 miles each. I stuck to smaller airports away from very large cities. Last flight was into Anchorage, and even though it is a very large airport, the city around it is pretty small.  No CTDs!!!! I am going to continue doing this and see what happens. 

Just done KMIA-KIAD A320NX no issues to report. hopefully my ctd's  have gone as thats 48hrs and around 7 flights.  Love flying in the US  as it's so much busier with air traffic  than Europe just now.

8 hours ago, Bobsk8 said:

I am seriously considering downloading P3D V5 today. My guess is it will not CTD once. 

I have both sims and P3Dv5 with Orbx TrueEarth is smooth as glass with frames unlimited then 4K TV set to 30hz and no CTDs or strange drops to 15 FPS.

My only caution is VRAM...I find myself using a good 8-9 GB of my RX 6800 sometimes.

I actually enjoy both sims a lot, hope they fix the few bugs in MSFS soon.

 

Looks like i got hit with this tonight for the first time. Mid cruise Dallas to Denver. Cruising along at 40 to 50 fps then freeze and crash.

This last world update in my opinion is getting to be just as bad as the update that borked the A320 when the sim just came out. Getting real annoyed to spend all this money for a rig and sim that cant seem to get its QA house in order and keep putting out buggy updates that aren't fully vetted. I don't need scenery updates every month if almost EVERY ONE breaks something!!

16 hours ago, Bobsk8 said:

I have been thinking about this, and even thought about server issues when this CTD started. 

 

1 CTDs only happen on approach, never on take off or departure.

2. CTDs only seem to happen at very large airports surrounded by big cities or dense population areas. 

3. If I have a CTD like I did this morning flying into KMSP, and I do tghe same exact flight, it CTDs in about the same area on approach. I have had this happen many times before in places like London, LA area, Toronto, Montreal  etc.  

 

I think the reason that this doesn't happen on the departure leg, is because when you load the flight it has all kinds of time to get all the scenery required from the server. On approach, it's a different story. You are losing altitude which requires more data for detail in the lower altitudes of scenery, and you are approaching an area where this data is needed. 

This has nothing to do with the persons ISP, but more with the servers . This may be why Asobo doesn't seem to be able to solve this problem, because they are right next to the severs more than likely so they don't experience this issue. 

 

Now I may be totally wrong with this theory, but so far I have not read one suggestion by anyone that seems to cure this problem. 

My case is different then, since it happens mostly enroute.In my last attempts I had CTD's in the middle of the North Sea, with no land whatsoever within 75 NM. A few times I had CTD's on approach to KBTR, but is not a very large airport.
I am currently attempting the same dreaded flight from ESUE to EGPN for the umptenth time, about ~3,5 hrs, 586nm. I have switched to PCIe 3.0, but others have stated that doesnt't help, and I am using other USB cables. I do have local AI traffic on and the GNS530 mod, so it's not a clean run
I forgot to delete the rolling cache so I have done this just now during flight.

The frustrating thing is that Microsoft could probably solve this by analysing our error reports to see what is really going on. That error code must mean something to them. At least they could have given us pointers based on the specific error code instead of the standard troubleshooting guide we get after filing a ticket.

9 minutes ago, orchestra_nl said:

My case is different then, since it happens mostly enroute.In my last attempts I had CTD's in the middle of the North Sea, with no land whatsoever within 75 NM. A few times I had CTD's on approach to KBTR, but is not a very large airport.
I am currently attempting the same dreaded flight from ESUE to EGPN for the umptenth time, about ~3,5 hrs, 586nm. I have switched to PCIe 3.0, but others have stated that doesnt't help, and I am using other USB cables. I do have local AI traffic on and the GNS530 mod, so it's not a clean run
I forgot to delete the rolling cache so I have done this just now during flight.

The frustrating thing is that Microsoft could probably solve this by analysing our error reports to see what is really going on. That error code must mean something to them. At least they could have given us pointers based on the specific error code instead of the standard troubleshooting guide we get after filing a ticket.

Have you tried this yet?   

 

25 minutes ago, Bobsk8 said:

Have you tried this yet?   

 

MSFS has just CTD'd again. The good news is that I can try again with the suggestion you posted.
Will report back, if it works, it will be several hours if it works, otherwise earlier.

I have just done this 'vaccine' install and intend to try it throughout this afternoon and evening.  I'm in for an interesting night one way or another! 

Mine seems fine now, after doing the following i have no issues. (Hope it remains that way )

1 Rolling cache off

2 I hardly use the VFR Map ( as this seemd to be causing fps drops to single figures, only to clear if you moved the map around)

3 No OC at all

4 All drivers, apps, OS upto date

5 I don't know if it helps, but i use the Addon Linker and only load in the requirements for that flight only. (ie A320NX, Livery, dept and arr airports, )

6 My GPU drivers were rolled back to the version that is stable (Radeon 20.8.3) otherwise i get Driver timeout crash every flight! ( Power Colour RX5700XT 8gb)

 

Hopefully this can help someone else....

Edited March 7, 20215 yr by Car147

So far Iam having excellent results staying away from large cities and airports. On my 8th flight so far, and no CTDs. 

One long flight around the British Isles for me (about 90 minutes).  Lots of added scenery in the community folder, and the new shipping pack added (nice to see the new ships about!).  I did some minor 'teleport' jumps across the Irish Sea.
Flight was RAF Valley - around Anglesey - North Wales - back across Anglesey to Dublin - back across to South Wales - Bristol Channel, and landing at Bristol Airport. 

Absolutely no problems for me except some delayed texture loading.  I swear they have problems with the servers when a lot of people are online on a Sunday.  It kept saying it wanted to turn off my Bing data as it couldn't download quickly enough, but I checked my speeds twice and they are fine. 

Anyway, the short story is all good up to now!  

Edited March 7, 20215 yr by bobcat999

1 hour ago, Bobsk8 said:

So far Iam having excellent results staying away from large cities and airports. On my 8th flight so far, and no CTDs. 

Well a flight into a small airport KSFM just now, 10 miles away, and a CDT...Nuts!!!