of cause 
āPS: these manual setting for a app āhigh performanceā is and should not necessary for a normal pc. User fiddle to much with the settings 
ā
ok, will try it without, anyway - no change in windows setting or FS setting can avoid this error.
Iām using an external yamaha AG03 usb sound mixer device for all sounds.It has itās own driver.
Ive done a full reinstall of the Geforce Nvidea driver too, without success. Got a Nvidea 2080GTX soundcard.
Never had problems since SU10 beta (3rd release). SU9 was causing heavy stutter, thats why I take part in BETA.
Just reported it again!
I try to deactivate Nvidea Audio drivers, will test if it helps
I am sorry. I guess my English is not good enough to communicate well.
I donāt think the sound driver has anything to do with this msfs dialog.
In my environment, after the dialog appeared, the graphics card was not recognized in the device manager.
This is a rare problem that has happened in other games, and in my environment, it was happening especially when I used the graphics card in the background.
This may not be fixable by us.
It has happened with both nvidia graphics cards and AMD cards, so Iām sure the developers will fix it.
I love msfs. It seems you do too. I hope it will be fixed, but I think you should wait until the developer fixes it. If you change the settings too much, you will break Windows.
Sorry I canāt help you.
I donāt speak English, I translate at DeepL.
I have had this CTD three times - at the moment I am testing limiting FPS in the Nvidia panel to 35 FPS - so far seems ok.
Not saying this is a fix - just commenting on my progress, Anyone else who experienced the CTD tried this?
I feel the same as you and love MSFS since FS2004 Yes , you may be right. We cant fix it, because it has nothing to do with our windows installation nor with our hardware. I think most have a common and actual PC and GPU, so it is just a programming failure that has to be fixed by Asobo. Anyway Ive written a Zendesk report.
I believe that reducing the performance is decreasing the possibility getting CTD or this erroro message. But if you try higer settings, complexer scenery or aircraft than the risk increase. Thats my expirience.
This is the first time Iāve had to look at this since the one and only previous time, and that flight resulted in this error. Iām absolutely confident that settings and RAM/VRAM usage has nothing to do with this.
Iāve just done a cold start up etc at inibuilds LHR in the Fenix A320 with live traffic (AIG models), live weather, GSX Pro and Navigraph all going. Iāve not changed my settings (which are effectively Ultra with TLOD of 250) since before .18 and in this example my VRAM was full the whole time in DX11. At close to 4K resolution it really doesnāt get much heavier at the minute than this in terms of performance draw. It wonāt surprise anyone to know that there was no crash. Iām now airborne so weāll see what happens.
This is nothing other than an issue in the game code introduced with .18 and later. Iāll keep saying it until Iām blue in the faceā¦this has absolutely nothing to do with graphics settings.
ps My Nvidia GPU is overclocked (as it always has been) and my AMD CPU is undervolted allowing it boost to 5.1ghz. Again, the issue is the game, not our systems.
AMD and Nvidia!!! ā¦ My best advice is to make sure your mainboard, processor and chipset drivers are all up to date and do not overclock the gpu.
never done itā¦
Ive tried it - but than I ve got average fps about 18 :-/ (with Kodiak 100 - which is payware and may use more fpm)ā¦ Of cause - its a beta and should only use default to test. But who uses default? Fact is, the more performance an addon need the higher the risk of this error message and CTD. Indepentend from the hardware, drivers or windows settings - Ive tried all - and without overclocking. My system is 2 years old an fits the specifications of MSFS (i7 with GTX 2080).
Usally I always had between 35-65 fps - before the last beta - and never had CTD/error.
Maybe there is also a Problem with the Kodiak 100:
The main reason for this is running MSFS in DirectX 12 mode. DX12 is an experimental, incomplete implementation and therefore it could crash for unknown reasons. We recommend not using DX12 with the Kodiak. Another potential reason are nVidiaās latest drivers at the time of release. These have been known to cause crashes and FPS problems with MSFS in general, so we would recommend rolling back to the previous version.
Iāve been running the SU10 beta in VR in a mix of ultra and high settings until today with no issue. Amusingly, today I dropped all the ultra settings to high and had this graphics error window when I exited my flight to the main menu. Strange that it did it with lower settings!
With medium settings the chance to get this error is decreasing - with higher settings CTD are there more often. Also if using complex addons. So I believe that FSMS are not optimized to handle the GPU effective this time (since Beta .19 and till Beta . 21)
i think you are right - my last crash was in the Kodiak - though i am in DX11, not 12.
Cant remember what i was in before that.
Interesting - thanks
I was having this issue very single time I opened the simā¦ Iāve deleted the driver via DDU and install the 472.12, just made a 4 hours flight without any issue so farā¦ I have 5600x with the GTX 2060Super and 32gb of ramā¦
I did the same thing (but used 516.94) and, Iām pretty sure the issue went away.
I also reinstalled the sim after renaming my content directory.
Hard to know which of the two had any bearing, but I havenāt seen the error since.
Do you have the same issue if you follow the OPās steps to reproduce it?
Yesterday, at the start of FS2020, that inscription appeared on my screen.
Provide extra information to complete the original description of the issue:
New HW Asus ROG strix Z690-A Gaming WiFi D4, Gainward 3080 12GB RAM, Win 11 Pro, 64 GB RAM
Are you using DX12?
no
Are you using DLSS?
yes
If relevant, provide additional screenshots/video:
no
This evening I was flying a long time without issues. Im not sure but:
there was a small FS update this evening (only a few mb and no new FS version number, still . 21
set my Nvidea settings for MSFS to a limit of 60 fps
set back GPU Settings āonā
So - I m not sure if the error message/CTD problem is really gone , until now I m testing with āmediumā MSfS Graphics settings - useally "high end " should be and was possible with my system.
I got this error only once 5 days ago just after an beta update and starting the first flight. I found an error log file named āMicrosoft Flight Simulator-8408-1.nv-gpudmp.jsonā in the āLocalCacheā directory that was generated at the time of the error. Renamed the extension .txt and attached it to this post.
You should check your own error dumps and upload your logs with your Zendesk ticket.
Microsoft Flight Simulator-8408-1.nv-gpudmp.json.txt (2.4 KB)
