8 hours ago, sniper31 said:

Okay, another update. Turns out this was NOT a solution for my CTD's, which I say once again, ONLY started with SU13. I managed only three successful flights with the Offline AI Aircraft turned off. Fourth flight, same CTD, same Event Viewer error code. I am fast running out of options. I am now testing the lowering of my NIC bandwidth, as some of you have suggested worked for you, even though I abhor the idea of suddenly having to lower my data speed just because MSFS, after three years of being released, decides it doesn't want to work with high-speed data service. IF this turns out to be a work around, it does NOT give me a lot of confidence that the upcoming MSFS 2024 that is supposed to rely on more streaming and cloud service is going to pan out well. But I digress. Back to MSFS 2020 and my current CTD SU13 issue. I have a grand total of ONE successful flight running at 100Mbps, half duplex on my NIC. That was last night. Just having time today to try and get some more attempts in, so let's see what happens. More to follow. 

 

Have you run a stress test on your hardware? It's easy enough to do and that way you can rule it out and move on the other possible solutions.

1 minute ago, Gate99 said:

Have you run a stress test on your hardware? It's easy enough to do and that way you can rule it out and move on the other possible solutions.

I am assuming you are making that suggestion because you have not read the entire thread (which, I can understand...it is lengthy). That said, yes, I have stressed test my system plenty. I have a long history of custom building PC's , so stress testing is something I do regularly, sometimes just for fun. Besides all that, as I covered earlier in the thread, in order to rule out hardware, I completely changed out my CPU, motherboard, RAM and GPU as I have plenty of spare parts available. It made no difference. Hardware is not the cause of my CTD's which specifically started with SU13. 

2 minutes ago, sniper31 said:

I am assuming you are making that suggestion because you have not read the entire thread (which, I can understand...it is lengthy). That said, yes, I have stressed test my system plenty. I have a long history of custom building PC's , so stress testing is something I do regularly, sometimes just for fun. Besides all that, as I covered earlier in the thread, in order to rule out hardware, I completely changed out my CPU, motherboard, RAM and GPU as I have plenty of spare parts available. It made no difference. Hardware is not the cause of my CTD's which specifically started with SU13. 

As the OP, i appreciate your tireless efforts Sniper in doing all of this arduous testing to try and figure out this elusive anomaly... one day it will be solved..who knows how or why... thought I'd report back after doing some testing of my own... no where near as rigorous as Snipers and others...

Suffice to say.. i cleaned out my NVIDIA driver and installed a fresh latest driver version... re-set all of my settings in NCP (not using the old replace the 2 files nvdrsdb0.bin and 1.bin files to save time)... cleaned out my community folder and started agin with very few addons... uninstalled GSX...was a pain anyway... removed FSLTL and now restored it back to the comm folder... uninstalled mixed reality and reinstalled that fresh... went about updating a few files like FSUIPC (free version to latest).... and hence so far ive done 5 flights of varying length in both VR and pancake mode, all with no crashes... now whether its something i have removed or reinstalled or replaced, or a windows update...i have no clue... my brain is too tired to even guess anymore... but for some reason it now works... it truly is enough to do your head in!

2 minutes ago, vonduck said:

far ive done 5 flights of varying length in both VR and pancake mode, all with no crashes..

Don't let it go to your head! I've had good days too. It'll crash tomorrow.  😆 

52 minutes ago, odourboy said:

Don't let it go to your head! I've had good days too. It'll crash tomorrow.  😆 

I must admit... every time the sim stutters (which is not that frequent)..my heart stops and i expect the CTD! I only start breathing again when it carries on !🙃🤣

I have not followed this thread but I will say this if a entertainment product put stress on me to the point of worrying about my mental and overall health I would probably step back and give it a break for while. Did it a many of the old FSX days.

Carry on...

9 minutes ago, JBDB-MD80 said:

I have not followed this thread but I will say this if a entertainment product put stress on me to the point of worrying about my mental and overall health I would probably step back and give it a break for while. Did it a many of the old FSX days.

Carry on...

...Just as well i play golf too! That's most therapeutic....although I tend to CTD in that as well!!! 🤤🤪

8 hours ago, sniper31 said:

I am assuming you are making that suggestion because you have not read the entire thread (which, I can understand...it is lengthy). That said, yes, I have stressed test my system plenty. I have a long history of custom building PC's , so stress testing is something I do regularly, sometimes just for fun. Besides all that, as I covered earlier in the thread, in order to rule out hardware, I completely changed out my CPU, motherboard, RAM and GPU as I have plenty of spare parts available. It made no difference. Hardware is not the cause of my CTD's which specifically started with SU13. 

Well I'm glad that you were able to rule out it being a hardware issue. It does seem to be a perplexing issue that is affecting some users but not others. Hopefully you'll be able to track it down soon. 

At some point I uninstalled all photogrammetry cities via content manager. That fixed stutters and ctd for me.

at eham (fly tampa) with installed photogrammetry cities I have times with single digit FPS.  With uninstalled cities I get around 40 FPS. 
When the photogrammetry cities are uninstalled it doesn’t matter if you have photogrammetry on or off in the data section. For me that was the key.

I suspect most of my CTDs have resulted from incompatible add-ons or simply just trying to run too many of them.  Assuming hardware issues have been ruled out (I've only read a part of this thread) then maybe cull the addons or even ser what happens with an empty community folder.

I run Littlenavmap, FSLTL and TrackIR software in the background and do get a few simconnect errors as a result leading to a CTD.

ASOBO have recently included an object limit which can cause a CTD.  GAIST is a big problem for me as a result of this limit.  I'm not sure why it was introduced or whether there is any scope to increase it, though I do recall reading that too many objects were causing stability issues.  That said, addon scenery is held in RAM and some of us have more of that than others.

I once had a bad stick of RAM that was causing issues intermittently and also a PSU starting to fail with similar results (sometimes the intermittent faults are the most difficult to track down).

Finally any sign of overheating, especially the CPU and GPU need an eye kept on.  I run Coretemp to keep track of my CPU and Afterburner for my CPU.  I've also heard of NVMe drives getting too hot if they are not installed correctly.

3 hours ago, cianpars said:

I suspect most of my CTDs have resulted from incompatible add-ons or simply just trying to run too many of them.  Assuming hardware issues have been ruled out (I've only read a part of this thread) then maybe cull the addons or even ser what happens with an empty community folder.

I run Littlenavmap, FSLTL and TrackIR software in the background and do get a few simconnect errors as a result leading to a CTD.

ASOBO have recently included an object limit which can cause a CTD.  GAIST is a big problem for me as a result of this limit.  I'm not sure why it was introduced or whether there is any scope to increase it, though I do recall reading that too many objects were causing stability issues.  That said, addon scenery is held in RAM and some of us have more of that than others.

I once had a bad stick of RAM that was causing issues intermittently and also a PSU starting to fail with similar results (sometimes the intermittent faults are the most difficult to track down).

Finally any sign of overheating, especially the CPU and GPU need an eye kept on.  I run Coretemp to keep track of my CPU and Afterburner for my CPU.  I've also heard of NVMe drives getting too hot if they are not installed correctly.

Everything you covered has long been tried and checked off earlier in this thread by my thorough and relentless efforts. To summarize, running a clean vanilla MSFS install, empty Community folder, have swapped out all hardware and tested, no overclocking (I am running a 7800X3D) and I have been using Coretemp to monitor temps for over ten years now. I use an Arctyx AIO cooler and my temps while running MSFS are around 50 degrees Celsius. Thanks anyway. 🙂

 

1 hour ago, sniper31 said:

Everything you covered has long been tried and checked off earlier in this thread by my thorough and relentless efforts. To summarize, running a clean vanilla MSFS install, empty Community folder, have swapped out all hardware and tested, no overclocking (I am running a 7800X3D) and I have been using Coretemp to monitor temps for over ten years now. I use an Arctyx AIO cooler and my temps while running MSFS are around 50 degrees Celsius. Thanks anyway. 🙂

 

Thanks again for your continual testing and relentless pursuit of a solution for all of us. I too have tried all those things, short of a complete hardware change. The only (so far) 100% solution has been the 100 Mbit half duplex solution.

I'm convinced something in SU13 or server-side around around the release of SU13 caused an error in transmission /error handling or processing that is making the program crash when it doesn't recover/receive what it expects in the necessary timeframe and that it's tied to Bing Data/Photogrammetry. When we limit the network bandwidth, I think we're allowing for enough time for that data to get processed/not missed because everything is flowing down the connection slower.

I will try the uninstallation of the photogrammetry cities to see if that has any effect.

19 minutes ago, mmcmah said:

Thanks again for your continual testing and relentless pursuit of a solution for all of us. I too have tried all those things, short of a complete hardware change. The only (so far) 100% solution has been the 100 Mbit half duplex solution.

I'm convinced something in SU13 or server-side around around the release of SU13 caused an error in transmission /error handling or processing that is making the program crash when it doesn't recover/receive what it expects in the necessary timeframe and that it's tied to Bing Data/Photogrammetry. When we limit the network bandwidth, I think we're allowing for enough time for that data to get processed/not missed because everything is flowing down the connection slower.

I am starting to agree and lean to the same thoughts with the cause and also the work around. I am on my 6th successful flight after the 100Mbps Half Duplex change, and no CTD's yet. My MSFS install is still in a vanilla state, and I am still flying default everything. Still need to knock out some more successful flights in default mode, then eventually start to add in some addons and see what happens. 

The only time I CTD lately seems related to State Saving where a particular livery on an addon will seem to CTD for a bit on load but usually eventually come good. No rational explanation for it.

19 hours ago, sniper31 said:

Already there my friend. When I reinstalled MSFS a several days ago, I have since kept it completely vanilla for troubleshooting purposes. As in, nothing, no addons, nada, nix, zip. I did mention that I was going to add FSLTL yesterday, but that was only IF the Offline AI Aircraft potential solution worked, which it didn't. So, I never reinstalled FSLTL yet. I have still, a vanilla install of MSFS. To that end, I have installed the USA WU just so I can at least have a few more Asobo updated airports do vary my testing out of during this troubleshooting process. But, otherwise it's default everything....default scenery, default weather, default planes, default flight planner, you get the idea. And, I don't use FSUIPC, SPAD or anything software like that either. My Windows install itself is pretty vanilla, because in general, I don't like bloatware and I don't like a lot of apps running in the background. I've also not installed any new hardware peripherals in the last 6 months.

I am about to start my third test flight with the 100Mbps Half Duplex work around, so we'll see what happens.

That is some weird stuff going on then. Sorry for my error (on a phone) and my apologies.

I do wonder though.....if you should install all available world updates first? Maybe something is not compatible with an older version?