I know nobody likes to hear that their system may be causing problems so I won’t actually say that. We know from the roadmap and previous updates that Asobo acknowledges there are some bugs that cause CTDs to occur when the perfect storm of parameters are met. They have fixed some and are actively searching for others to conquer. We also know that there have been many that participated in this thread that are now CTD free and out flying, so obviously not ALL are caused by the sim. How do we tell the difference? Eliminate the variable we have control over.
Your system may be stable with all other software, but flight simulators (not just MSFS) have always pushed systems to their limits, at the time of their release. Sims like DCS, P3d and Xplane are no longer out there on the edge. Not only have they matured but hardware has caught up as well.
We are still out there at the hairy edge with this new sim. Sometimes the only solution is to back the load off until we can achieve a stable running product. Once we get there, it is a relatively easy process to start moving things back to the right. One at a time and bit by bit until we have a stable computer running the sim at acceptable levels based on our own preferences and the capabilities of our particular rig.
Start by getting the system base lined and then the sim itself. (Click the links for more info on how to do that). Be patient with the process. Don’t skip steps. Be ruthless about getting that base. Chances are pretty good you will end up with an overclocked system running 4k nice and smooth if you have the hardware for it.
There is an alternative for those that believe all the problems are the sim itself and it is not up to the user to make it run. Do nothing. Trust your configuration is perfect and that one day Asobo will make the software compatible with your system and settings.