Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
Are you using DX12?
Are you using DLSS?
yes
If relevant, provide additional screenshots/video:
yes
This has been happening for me for about 3-4 weeks. Never had this message before. Every flight I run it gives me the same message after about 2 hours of flight time. 2080 Super using Nvidia Experience optimised settings. If I roll back to two GeForce versions ago (forgot the version number) it works fine however.
It’s annoying having to roll back just for one game in my library. I hope it’s fixed soon.
All forums are flooded with this problem with the exit from the game due to overheating of the video card.
Do you really believe it’s not the game?
I rolled back the drivers to the previous version, and reduced the simulator settings to the minimum without addons.
I have Radeom RX590 graphic card - and maximum temperature for as 85 C.
Why game crased on 76 C?
Spontaneous crashes - developers, will you fix the simulator ???
3 Likes
Rolled back the drivers to version 531.29 (from official Nvidia cite). No more any CTD’s teel now. Check version of your’s drivers.
3 Likes
I have Radeom RX590 graphic card
the game determine a problem ( any kind of ) and stop the game before its crash 
Therefore checking the event log about existing error messages is important.
I switched back to DX11 after my first notice of this problem and have not had it since. That’s not a guarantee that DX12 was the cause, as I have been using DX12 without issue for a long time.
It’s nothing to do with overheating but everything to do with video memory clockspeed and data source synchonisation. Tolerances are limited so if you happen to overclock your gpu then you’d best be certain that the rest of your system can present multiple data streams in an uninterupted fashion.
I just got this error message.It might have to do with my GPU set to oc mode which I normally have disabled.
Thought I’d try 531.68 today. Not getting the crash and ‘graphics message’ but it’s quite stuttery, not as smooth as 528.49… so I’ve gone back to that one. DX12 seems to be better than DX11 for me. Great advice given to me was to clear the shader cache after changing a driver.
3080, Ryzen 9 5900X, 32 RAM. (Quest2).
I just rolled back to 531.68 and am still getting the graphics message. Only got it once or twice with the previous MSFS versions. Since sim updated yesterday MSFS is crashing 100% of the time. GPU memory usage is maxed or nearly max’ed out continuously since sim updated. It is now never lower than 10+GB, even at alt. Previously it would spike (10GB to 11GB) at high demand scenery but at alt would hum along around 7GB to 8GB.
I’m going to try going back to 528.49 as you have and see what I get. Aside from that, I see the notice that ‘This topic has been resolved’ as I’m typing. Could someone please tell or point me to the prescribed ‘resolution’?
Thanks.
And again a loop: the issue is since 531.41. Thats mentioned in million of posts in that topic and also within the official FAQ. That mean: rollback to 531.29 or try to use with DX11 setting ( not DX12(beta) ).
If you got the error already before that driver, check the other existing hints in that topic ( reduce system load, remove OC, etc ).
About the .49 and .68 we still have reports that the issue persist. So no recommendation to upgrade..
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons?
No
Brief description of the issue:
This is what I am getting at some random time during MSFS flights
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
I have a modern graphics card (and PC), NVidia GeForce GTX3080,with the latest drivers, and the fault seems to occur at some random time during every MSFS flight. But not in X-Pane 12 even with “heavy use” aircraft like the Flight Factor A320 . I have limited the FPS to 30 in MSFS and dialled back the settings to “default” from those optimised by Nvidia. But still this occurs. Can anyone advise. (PC has been well cleaned of dust etc)
Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version (Learn how to find your current graphics card driver version):
Nvidia GeForce RTX3080 Driver Version 531.68 released 04/18/2023
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Thanks for the commentary, sorry but I’m not sure what you are getting at in it exactly. You seen to be complaining about too many unnecessary posts on a topic by posting a completely unnecessary post to the very same topic. Again, please forgive me if I am misunderstanding your comments.
I was just a general statement and request for help.
BTW, I rolled back to driver version 528.49 and have not gotten an error since doing so. 
This “solution” is embarrassingly inaccurate. Looks more like deflecting the issue.
I have a RTX3090 with 24GB VRAM and 128 GB RAM. Newest drivers for the graphics card. No overclocking. I always reboot my computer before trying to play MSFS, but get this annoying error message almost every time. And sometimes before pressing GO FLY.
So until Asobo tells us what they have done to provoke this error I am not buying the excuse. Oh, an by the way, after the crash I tend to start a game much more labor intensive to the graphics card to blow of some steam. Never crashes. This is a MSFS issue that Asobo need to take seriously or the customers will end up with an alternate vendor for flight sim.
5 Likes
I simple repeated the well known workaround.. I also mentioned, taht we have reports where users get with all versions greater than .29 the issue ( when dx12(beta) is used). I mentioned because you mention you will try these .49 version, which may be again will fail. The “loop” is , because the topic is full of the same “solution” you asking for. Its also explained why the solution-marker is on the topic and for what it is. It is explained that we have two different kind of reasons why users get the isseu ( the older original one and the new since 531.41 ). Its just seemingly necessary to repeat that often.
It is recommended that you do a “clean” install of the latest driver version. Rollback is not an option for me.
1 Like
that will not help … if you not want to rollback the driver, then ( as mentioned also often ) the workaround is to use DX11 and not DX12(beta)
So I would like to repeat one of the summary and the link to the official FAQ
I installed 531.68 right after it came out (18 APR I think) in the hope that it would fix the .41 issue, just to find out today that it CTDed again with the known pop-up window.
Following most suggestions in this thread, I re-installed 531.29 and will see how it goes.
I’m on a 2070Super with DX12.
1 Like
Same here..I rolled back to DX11 and no issues ( so far) Running latest NVIDIA for 14 months and never seen GPU CTD until WORLD UPDATE XIII.
RTX3080 12 GB.
1 Like