53 minutes ago, Clem116 said:

My CPU is only OC to 4.7GHz and temps are always under 60c and is ~30% utilized

Have you tried running without the OC? TBH a 650w psu seems a bit of a gamble with an OC and all the hardware.

10 minutes ago, scotchegg said:

Have you tried running without the OC? TBH a 650w psu seems a bit of a gamble with an OC and all the hardware.

Sorry, 750W. Corsair RMX Series, RM750x, 750 Watt, 80+ Gold Certified, Fully Modular Power Supply

At work with these sort of  random "now you see it now you do not" faults (where everything tests OK until suddenly it is not)  we generally start swapping parts out from unused known good spare servers but that is a bit tricky when fault finding at home.

Generally weird random crashes tend to be resource leaks, drivers or hardware as already mentioned but on the odd occasion the cause can be external, for example noisy or variable quality mains power.

One amusing example was a remote server that randomly crashed for months until someone thought to ask the office staff if anything unusual was going on when it crashed ... the reply was "well it does seem to mainly happen when the guys in the workshop fire up the MIG welder" ..

Edited January 4, 20215 yr by Glenn Fitzpatrick

On 12/31/2020 at 5:44 PM, ryanbatcund said:

Do you have all the C++ redistributables?

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

Is there a easy way to find out if I already have these installed?

55 minutes ago, EvidencePlz said:

Is there a easy way to find out if I already have these installed?

Your current redistributables are listed in:

SETTINGS -> APPS -> APPS AND FEATURES

7 hours ago, Clem116 said:

Sorry, 750W. Corsair RMX Series, RM750x, 750 Watt, 80+ Gold Certified, Fully Modular Power Supply

That P/S is more than enough. You shouldn't be OC'n the CPU while troubleshooting though, turn that off...

I'd be trying different memory next, because it's small and a relatively inexpensive component that you can easily return, you'll have to pay restocking depending on where you buy it from and the reason of return, but it's better than not knowing. I would still install the gamepass version just as a 'fringe' test, it's $1 if you never had it before, otherwise $10. 

I don't think you'll easily figure this out without swapping stuff around. Bad hardware can be 'barely bad', where it makes you think the problem is software. 

30% CPU uitilization is likely for Multi Core. I can imagine one core runs at a much higher rate (which is not unusual). I would try to run the game in the lowest possible graphics settings, if the crash still occurs, it might be hardware related, but still software related.

Second, try to unplug all unnecessary hardware components, consider buying an electrical power meter (its also useful for other things) and finally I would not invest any more than on that. I for my side think that it is software related.

 

So if does not work, don`t  waste your time.

Just to share my initial experience, I also faced multiple CTDs after Dec 22 update. I followed the advise to delete all said runtimes, reboot, then install the latest x64 and x86 runtimes and currently do my second flight. so far no CTD. knock on wood. will try some LOWW-LSZH later. FWIW, I also slowed down my memory in the BIOS to the next lowest freq. 

2 hours ago, BigDee said:

Second, try to unplug all unnecessary hardware components, consider buying an electrical power meter (its also useful for other things) and finally I would not invest any more than on that. I for my side think that it is software related.

It really appears like a hardware setting or bad hardware, but it's hard to say when a third-party is doing the work and you're not sitting there yourself. He said he already reinstalled Windows from scratch and the game, and all the other stuff. I've got 3 copies of FS 2020 on 3 different machines, and another user on another different machine. Though all the machines have had CTD's from long flights or third-party addons, I've certainly never heard of or seen instant CTD's right after loading the game in a Vanilla (fresh install) state. Even if that has occurred for a few users, it still occurring after a fresh Win install, hmm.

Sounds like bad OC settings or bad hardware, unless there is something he isn't telling us. I agree to mess with memory timing and other similar things before replacing stuff, but he hasn't really communicated enough info to know either way.
 

Edited January 4, 20215 yr by Alpine Scenery

Reporting back here! After rolling back the NVIDIA drivers and installing the new ones and limiting my FPS to 30, I am no longer getting any CTDs for now. My GPU runs cooler and is not at 99%. I am a bit surprised that my 1080TI can't handle 99% at 79c. Anyways, I should be getting my new Asus 3080 ROG STRIX next week. I hope this will help at 1440p 🙂

48 minutes ago, Clem116 said:

Reporting back here! After rolling back the NVIDIA drivers and installing the new ones and limiting my FPS to 30, I am no longer getting any CTDs for now. My GPU runs cooler and is not at 99%. I am a bit surprised that my 1080TI can't handle 99% at 79c. Anyways, I should be getting my new Asus 3080 ROG STRIX next week. I hope this will help at 1440p 🙂

It might be reporting the wrong temp, those things are not always perfectly accurate, fairly, but not perfectly. MB temps are the most incorrect though.
That is kind of borderline I suppose, but generally it's not "supposed" to be hot enough to cause fatal exceptions in a healthy PC if it hits that temp short-term, it may long-term.

It may just be the heat is bleeding off to other components, maybe increase cooling in the case somehow next time you swap cards just to add an extra layer of protection. I've seen problems quite a lot where a video card is close to the memory and the memory is getting too hot. It's helpful to have a fan blowing over the memory.

Edited January 6, 20215 yr by Alpine Scenery

But again CRAZY that when I run many other games at the same temp and usage I never get ONE CTD. 

25 minutes ago, Clem116 said:

But again CRAZY that when I run many other games at the same temp and usage I never get ONE CTD. 

Not really because it only takes small variances and games generate different levels of total heat, because heat is a culmination of all components working hard together.
Increase the cooling in the case will probably fix it.

7 minutes ago, Alpine Scenery said:

Not really because it only takes small variances and games generate different levels of total heat, because heat is a culmination of all components working hard together.
Increase the cooling in the case will probably fix it.

I respectfully disagree with you. My feeling is that it's a combo with my GPU & MSFS 2020 and not just my GPU.As mentioned in my original post, in the first few patches I NEVER got one CTD and my GPU temp and usage were the same as today where I now get CTDs. 

23 minutes ago, Clem116 said:

I respectfully disagree with you. My feeling is that it's a combo with my GPU & MSFS 2020 and not just my GPU.As mentioned in my original post, in the first few patches I NEVER got one CTD and my GPU temp and usage were the same as today where I now get CTDs. 

You can respectfully disagree, and not to sound disagreeable, but I'm just basing it on things I've seen from thousands of PC's from years and years of seeing issues...

There are too many variables for me to say "ABSOLUTE" without actually examining and testing the issue. I am just telling you which steps may help your issue. The bus controller chips overheat on some boards, almost more than half the motherboards report the incorrect temps. Memory can run too hot. Memory has QC variances and it's especially apparent when you are OC'n the CPU like you are, this exposes potential memory bus issues. The thresholds are tiny tiny variances and these thresholds can change over time (even if just barely), plus variance in room temps. There are a lot of tests you can do to further rule out the issue. MSFS runs the bus controller and the memory chips and CPU much harder than almost any other game, this is because the network stack is constantly streaming and de-compressing data in real-time as well as the sheer amount of data it has to pre-load off the drives as well. So it's pushing multiple things harder, it's not just about one thing necessarily. This is kind of like if you were to play a game but also to be constantly UNZIPPING files at the same time, no other game pushes the totality of the PC like MSFS does (at least not that I know of).

So although there is a "fringe chance" it could be related to software, it's unlikely it would only show up at higher temps, and it's probably related to you being on the edge of a threshold so to speak. That said, I don't have near enough data to conclude, but it's not all that hard to isolate it.  

 

Edited January 6, 20215 yr by Alpine Scenery