Last couple days while flying Cessna 414 even before and after SU 10 update I will get a warning that MSFS 2020 is going to close due to GPU overheat. After shutting down I'll pull up MSI monitor and the temp is well within normal limits. I have my fan running high when playing any PC stuff. Never happens with XP11.

13 minutes ago, t4murphy said:

After shutting down I'll pull up MSI monitor and the temp is well within normal limits.

Sounds like you’ve got the “you’re graphics device has encountered a problem” CTD. It could be due to running graphics settings higher than your rig can handle, in particular excessive VRAM usage. 

 

I had that about a hour ago as well. Now it's fine. I'm plumping for a server issue as the cause. But amongst the various voodoo fixes my favourite is to  delete the shader cache using Disk Cleanup.

The graph log on temperature shows no temps coming any where close to a critical temp. The overheat warning is random. Couple at initiation of flight and one soon after 1 hour flight taxiing to the ramp. Like I said there is no evidence of overheating on GPU temp monitor. 

23 minutes ago, t4murphy said:

The graph log on temperature shows no temps coming any where close to a critical temp. The overheat warning is random. Couple at initiation of flight and one soon after 1 hour flight taxiing to the ramp. Like I said there is no evidence of overheating on GPU temp monitor. 

Nothing is overheating. It's a bug.

I am getting this quite often too now. Same aircraft and same graphic settings I have always had. I think it started for me after SU10.

Programmers seem to adhere to the old adage that "a poor excuse is better than none".  Usually the error messages both here and other instances, have absolutely nothing to do with the problem.  My new 4k TV would not play the program I wanted and it said that my TV doesn't support HDMI and to change the connections to Component Cables to view the program. The next day it was working fine.

In the sim I get these "Lost Connection, check your internet" messages, which are totally false.

Roy

 

It is a bug. I got it too.

All of a sudden in the last week I'm getting it. I've changed drivers and no luck.

I had this problem too ever since the last windows update/nvidia drivers update. 

I found this forum that described the same issues I was having. For me, I did two things and ever since I did them, I haven't had any issues.

First, (as some suggested in the above forum) I turned off HAGS in my windows settings.

Second, I limited my frames in MSFS to 40 using Nvidia Control Panel. 

My current settings are the default "high-end" with some select items turned up to Ultra. I have vsync on and set to 100% Monitor Refresh Rate (60fps for me) but it is limited to 40 by Nvidia. I'm running 1080p, DX11, and TAA.

I hope that helps. It made all the difference in the world for me. Before doing this, pretty much every flight either froze 5 min to 2 hours in or I'd get the error your described. Ever since doing the above, I have not had that error or any ctds at all. Running perfect!

I get them every once in a while. Usually when I'm trying to start a flight. I just ignore it, and restart. It's a SW or data error triggering a false message. Eventually, Asobo will do something that makes them go away just as quickly as they appeared