may be users did again a “tweak” and new install of OS removed that tweak. Similar to the TDRLevel change, which some users did and now not getting the DLSS option till they removed the registry entry ( or set it to the value which is the default 3 ).
This topic becomes slowly similar to the “memory could not read” topic: some users get it and most users never get the message.
I don’t think it has anything to do with it. In the whole beta process I didn’t have a single ctd. In my case I have done absolutely nothing. Just update windows 11 and on the other hand get out of beta. This bug was already reported during the beta by many people and apparently it is present in the update 10 code. Which happens randomly regardless of whether you have windows 10, 11 and multiple hardware configurations.
Since I upgraded to SU10 I have been getting this error in the menu or while loading. This has nothing to do with windows updates or graphics settings. I’ve never encountered such an error before SU10. I also got a CTD 10 miles from the T/D on my 2 hour flight. Please fix it!
I agree, these type of CTDs were present in the beta two weeks before the arrival of 22H2.
I had this error a couple of times after SU10 install.
I deleted the files in the Direct X shader cache and have not had it again.
Seems to be another, most common bug/error with new update SU10. Well done devs!
Same error in my sim this morning …and i believe this is replenish error from memory leak (what is commonly known from previous versions of the game) to that one.
Game close itself, restart again and now running well. Don’t know how long
In my case, any major tweaking of the graphics section seems to encourage this error. A reboot between settings changes seems to reduce the frequency of the problem. It could be coincidence.
I gather that the Studio Driver doesn’t activate the DX12 improvements (which I believe that Asobo won’t release until the game ready driver is out) so there is no real benefit in installing them, and it has no effect on the error messages in any case. Am I correct ?
On Dx11 i‘m with you. At the moment i‘m testing Dx12 with 517.40 and have a couple of hours collected without Crash. „Fingercross“
Can u tell us, where the files to find?
DX12 has the same issue for me. It’s so random, that it’s easy to think it’s been resolved, only to reappear.
ZENDESK immediately flagged my bug submission as “Solved” !
then dont use the “DX12 (BETA)” setting 
here you can find the meaning of solved : https://flightsimulator.zendesk.com/hc/en-us/articles/360014232420-Zendesk-Bug-Reporting-FAQ
I don’t normally use the DX12(BETA) setting, I was saying that trying the DX12 setting doesn’t solve the error message issue in my case.
Still happens, with DX12, latest Nvidea Studio Driver - even not loading a flight, on startscreen… Asobo ! Please do something! It’s (FS) messed up!
a question, because I not find a answer
Is there any additional message within the Windows Event Viewer if you get these Popup ?
As example:
Did all of affected users see the NVLDDMKM error within the Log ?
MOD EDIT: Please do not tag staff.
Any updates on this issue?
My 1080ti works just fine when it works, and the 1660 ti in laptop works just as good if not better then the 1080.
No because people with expensive hardware are having a bad time as well.
Zendesk gave me this solution ‘Please turn “Hardware Acceleration GPU scheduling” off.’ Did you try it?
I have no more crashes when loading msfs or a flight.
