Xbox series X user here. Many XBox simmers have had CTDs on xbox s/x. I’d divide them into two categories
long flights over 2hrs (running out of system resources perhaps)
random CTDs for no reason whatsoever
I fall into second category. I always do a clean boot into FS2020 as opposed to resuming a suspended one.
Prior to WU6 I reduced CTDs to the point of near extinction by switching AI traffic off as the ‘known issues’ guide suggested. I also ensured my flights were shorter than 2 hrs.
This morning I booted FS and did landing challenges for 30 mins, had one FS2020 freeze (no response, frozen screen) so I quit to dashboard of XBox and quit FS2020. I rebooted FS2020 to triy again and loading another landing challenge led to a CTD. I switched off at this point and gave up.
Came back this afternoon and managed to do several landing challenges and a 40min flight with no issues whatsoever. FS2020 is Jekyll and Hyde like. I wish they’d install a CTD monitor/auto reporter as we all have our own non scientific story based evidence, making it hard for anyone to replicate/debug, and that is a major issue.
I read your post, and I just wanted to pass something along. I have an i9-10850k with an RTX 3070, and starting a few weeks ago, I began to get CTDs just as you did. Flying along, all is well, then boom, back to desktop or unexpected reboot. Another time I simply tried to move one of my MSFS screens and the same happened. I looked around the NVidia site and found that the latest NVidia driver (471.96) was causing problems with the 3070 with the same symptom – all was fine, then crash and sometimes reboot.
I backed off to 471.41 and have had not a single CTD or spontaneous boot since. When I installed 471.41 I also left all the 3D settings at default, because I wasn’t sure if one of those might have caused the problem. I’m not saying this will solve your problem, and could be completely unrelated since you have a 2060, but it’s worth a shot. Clearly you’ve tried just about everything else you could have.
Regardless though, you’re absolutely correct that we need some tool from MSAsobo that will either create a log file or an automatic debug reporter or something. Anything.
I had a couple more CDTs today too. Strange that 80% of the CDTs I’ve had in 11 months of using MSFS have been in the past two days.
I’m in the mood for a rant: Reading through what players/simmers go through to solve issues with this program is incredible. Imagine buying a new vehicle, home appliance or other product and the customers have to try to figure out why the product doesn’t work. Then, when enough customers complain about a problem, the manufacturer may throw out a couple more fixes while countless others await their attention.
who use xmp memory watch io and sa voltages in bios, you can found info about undervolt in internet, same as cpu, in my case i had problem after 3 years with it, untill undervolt sa and io voltages, and this problem wasn’t about just ctd, this was very hardcore black monitor problem without possibility to open bios with reassemble ram inside slots one by one with check all sticks first one then two of them then three then for, and only after that i could open bios, first symptom it works only without xmp, second after start xmp again rig was dead till ram was removed then set sticks back, and then i undervolted sa and io, and then everything back ok… all you buy was tested maximum mounth, and only tested exemplares, any other tested much less time, so it is possible something will wrong after year - two - three… so if you can found maximum info about your components and use only so volts as your system really need for cpu, and specially for memory controller in there, you can found really overkill voltages for cpu and sa/io(with xmp enabled) and this is can harm system or kick it very strong as was with mine
In some cases it can be hardware issue, but if I can run any game on max settings with high fps without any issues, I think I can say that this is a software issue. I can play high CPU load racing sims without any issues (Assetto Corsa with a lot of AI opponents), I can play ray tracing games without any issues (Control, CP2077). I’ve tried monitoring every hardware component and none of them had any outstanding values. Even I can run CPU, RAM and GPU stress tests at the same time, so my PSU is capable of keeping my system up (650W PSU for about 400W power consumption from the socket). Even though I can’t fly constantly since SU5.
Please let us to downgrade/roll back to the previous non-crashing state.
We can’t. Diagnosis is pretty much impossible. You can try all the sorts of things above but beyond that there’s nothing much anyone can do. The “advanced” install is really just more of the same. About the only thing you can do is look for some commonality in the crashes.
Or install FSX, X-Plane, P3D or Flightgear and wait, or put up with it.
you have nothing to be sorry, is my english terrible, you know it:) , i doesn’t talking about gpu voltage, only about cpu, it can be and some time have to become just a bit lower, than bios set in auto, but this is not so important as two another voltage sa and io, both set too high values in some system if memory use xmp, so better than read my round dance of drunk letters… just open google “xmp” "sa " “io” voltage
Frustrated as hell and trying a clean install for 20th time. I can relate to author of this post. HAve tried everything from clean installing windows multiple times. Since thursday i could do flights, multiple ones without crashing to desktop… FINALLY!! so i downloaded a couple of SU5 tested liveries. and crashes appeared again. Removed liveries and crashes remain. Now reinstalling a fresh copy of sim! had a wonderful three days… o well…