Warning: Your graphics device has encountered a problem

Since new gpu driver can’t get as far as the game.. fails in launching. Sound breaks first pictures flash and CTD. The 40th has been a disaster for me crashing all over the place, aircraft Veering off course, but the CTDs!! I’ve turned down settings to ease the strain on the gpu but no improvements. Monitoring the gpu temps and loads etc nothing appears stressed.. so why all the ‘it’s the graphics adaptor fault’ dialogues! Frankly tired oh so tired of the sim. What are we to do Jorg?

Just updated to the latest Nvidia driver. Nothing changed. It crashes halfway thru launch “Graphic driver…”

sorry didnt understand your post 100% - i am not running any OC - by bug report was why we cant OC our system and run MSFS but im trying without OC as well and still getting constant crashes

I not want discuss about your bug-report, it just tell me that you play with OC ( PS: OC of a 13900k is absolutly pointless ) and so I guess that may be you done also other system settings which relates here. As kind of OC we also mentioned e.g. RAM XMP mode ( at least try not the highest ddr speed ), and others. The other solutions like HAGS , limiting fps, etc. we mentioned so often and I’am assume you not tried that. In special the constant time factor let all my instincts say “it is some kind of a system issue”. But , to be fair: because we not 100% sure, we still hope there is a bug in game which can be fixed. But only 377 votes over 3 months not let me see a general problem with the application - if that would be the case, we would see thousands of votes.

And an additonal PS, just because my english is not allways the best and can may be misleading. With system-issue is not allways meant that users did something wrong ( often the case, but not allways ). In special with all these bit newer hardware ( e.g. also ddr5 , gpu’s) is the net full of reports of trouble.

i would say that things like using ram xmp and HAGS and unlimited frame rates are normal things and if these are causing crashes then that is a bug in MSFS and a temporary solution.

i dont think that running our hardware sub optimally is the right solution

well , e.g. XMP its still OC and there are many " be aware " in the mainboard documentations.
Same for additional GPU overclocks, where most of the users buy a gpu model which is already factory pre-overclocked.

( HAGS not, that was long time the source of BSODs because of windows / or gpu-drivers ).

And unlimited framerates are useless. These was since ever useless and is also in year 2022 useless. Set a usefull max limit so that your gpu not renders 1000fps somewhere and overstress your PSU or whats ever. If the system crash because of that, the problem here lies still in the hardware and not in the application, because a application can of course consume 100% of the system load and the system must can handle that, otherwise it is not stable.

It is just: makes it sense to get 300fps , if for each human eye 100fps is sufficent ? - no. And because of the lower system usage you get with a usefull max fps limit, you can save energy and not produce (expensive) heat for your room. That human eyes needs hundred of fps is nothing else as a kidding from the gpu manufactors ( plus monitor manufactors ).

But, we come up from the topic. The point was: please do some tests, e.g. try out some recommendations from the community. As example set a max fps limit to 60fps, or 30fps ( depends what you get now, just a bit lower ) and check whether that will work. Same for the other given hints.
Then you can report back what you tried, what not worked and that is more usefull for the users ( like some of the users report a relation to the gpu driver version ).

note: MSFS did for me never crash in that way and I tried a lot to reprode/duplicate that issue.

A great many people who have fixed it or never had the error, how do you blame the program for that?

I bumped my fan curve and it went away, oddly I can’t seem to make it come back?

Peak last 24 hours 8k were on the Steam version, who knows how many X-Box or MS Store users?

Why do I only have it under DX12. I can also overclock under DX11 and it runs very stable! As soon as I turn on DX 12 immediately.

without overclocking of course

may be because with dx12 the hardware is used in different way ( e.g. usage of vram , more system utilization, etc ).

It works in my case also fine with dx12. If you have currently issues with dx12, then just use dx11.
But if its not related to the “beta” state of dx12 impl, then may be you get also in future releases in that problem and we are back by possible reasons like system issue, or somewhat about drivers, or or…

So do I understand correctly that it runs better with DX 11?

I am currently using DX12 and now I get the GPU error very often.

I’ll try the DX11

DX 12 in most cases unless you have the absolute newest hardware is expected to give worse performance in all games Battlefield, Cyberpunk and every other game hardware reviewers use. It’s also listed as experimental, if you’re having issues it should be the first thing you shut off.

I do not have this message error with DX12. Every since upgrading from an RTX2060super to an RX6800 I haven’t had them really, maybe once and never saw it again. It was lot more frequent on my RTX 2060 super.

since middle of SU10 , and since I can enable HAGS without that it cause BSOD’s of windows ( not in game ) I’am testing “DX12(beta)” and with feelt bit better performance ( I not do hard perf tests, I will fly and not play the game “catch lowest fps in dev-mode” ). But it seems there is a wide range of reports here. At least I have also no crash with dx12 ( 2080TI (far away from “newest”) , 3840x1600 , ultra ). If a application offer worst fps with dx12, then it means the implementation is not good enough. DX12 is a low-level api and offers so more possibilities in development, but on other side its also more necessary to use it.
But yes, as mentioned.. if a feature which is flagged with “Beta” cause issues, users can report it back and simple use the stable dx11 :slightly_smiling_face:

:wave: Thank you 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?

YES

Brief description of the issue:

After about 2 minutes of flight I get Your graphics device has encountered a problem and Microsoft Flight Simulator will exit" error message. The solution provided in Assistance needed with "Graphics device has encountered a problem" - #46 by MichaMMA did not help. The sim was working flawlessy since SU10 and now crashes every time I play. I have tried, older nvidia drivers, latest nvidia drivers, clean install of drivers. DX12, DX11, DLSS on/off low settings, ultra settings. I don’t overclock. Sim was rock solid until a week ago.

Provide Screenshot(s)/video(s) of the issue encountered:

It’s just the box that saysy "Graphics device has encountered a problem.

Detailed steps to reproduce the issue encountered:

Start a flight, wait 2 minutes

PC specs and/or peripheral set up if relevant:

Ryzen 3600 32GB RAM, RTX2060 Super, Windows 11

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fault bucket 2200673235493628662, type 5
There’s also an error just before it:

Build Version # when you first started experiencing this issue:

Not sure, about a week ago

——

Moderator Edit: this post was merged into the topic

The error that occured in ny event log is as follows:

Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x000000000204148e
Faulting process ID: 0x0x54C
Faulting application start time: 0x0x1D90902C8F7A030
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 654f0b4c-084a-41b3-9323-12259e096b67
Faulting package full name: Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Same error for me this evening, with all the driver updated.


After a long time without this error (but it has never really gone) again:

It’s so sad and annoying.

Have always the latest updates in use, like GPU Drivers etc.

DX12 or DX11 ?

Its broken on dx11 AND 12
11 is worse for me though (more frequent crashes)