Just got it after a few flights in SU10. Never got it while in the beta. Only change to my system that I can think of was installing the latest nVidia studio driver. Win 11 22H2.
Very disappointing that SU10 was released two weeks after this error was first reported.
Out of memory would be regarding VRAM, not system RAM. Regardless, I and other users with a 3090 also get this error, so clearly VRAM is likely not the main cause.
Yeah I now have a 12GB 3080 I upgraded to just about a week ago so yeah either way it still shouldnât be an issue. I believe itâs the memory leak they have still yet to fix. Hopefully this was a one off thing for me. As my sim did make it 12+ hours and it only CTD on approach even though everything was smooth. No stuttering or anything.
Do you have the same issue if you follow the OPâs steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
Started randomly happening
Are you using DX12?
No
Are you using DLSS?
Yes
If relevant, provide additional screenshots/video:
Looks like everything was good for a SINGLE DAY and now the sim has gone to â â â â again. I downloaded the update Wednesday morning everything was perfect completed a full 18 hours flight from Boston to Changi. Hopped on today and now out of the blue. Constantly over and over âYour graphics card has encountered an errorâ no overheating nothing on the hardware side I DID NOT install anything new I only kept the things I tested yesterday before doing my Changi flight. So my folder was near empty with the except of the liveries and the Fenix that didnât cause any issues. But today when I try to do the flight back I canât even load into the sim. As I said itâll say âyour graphics card has encountered an errorâ when I hit okay it then shows âa breakpoint has been reachedâ if I couldâve stayed on SU9 I wouldâve because in the end SU9 calmed down and I was able to fly for quite a while with no issues.
Do you have the same issue if you follow the OPâs steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
RTX 3070 / i9-10850 / 32Gb Ram / Graphic Settings Low, Medium, High and Ultra. The problem is on all Settings
Are you using DX12?
both / Dx11 & Dx12
Are you using DLSS?
No
If relevant, provide additional screenshots/video:
i hate, that Asobo ignores this problem in the Beta.
Solution from: @thinkglobal
it was not possible to rollback to â22h1â, so i had to do a clean Win11 installation without â22h2â and have installed out of the BOX the new Studio Driver. First flight in DX11 without Crashes. We will see - i keep u informed.
MSFS Settings: High Preset
GPU: RTX 3070 8Gb
Driver: 517.40
CPU: i9-10850K
RAM: 32GB
OS: Win 11 / Clean 22H1 ISO Installation
This problem was never before, and starts with a special SU10 Beta build.
How did you do a clean reinstallation without dx12?
i don´t know what u mean. i did a Win 11 Clean Installation and start the Sim in Dx11 - Dx12 is also available but not tested at this moment.
in my case it is the same - if MSFS crashes (with or without this error message) I always see this 2 instances.
I was in BETA and got this error since the version 1.27.18 or 19 of MSFS. (I think now itâs version 1.27.21.0.
Now I ve left BETA and im on v. 1.27.21.0. official.
Still got this error when using more complex airliners or sceneries or changing graphic settings to âhigh endâ. These errors are not frequently but very often, even on start screen of MSFS without loading any flying situation. Happens on ground when loading or after many minutes of flight.
Before SU10 I never had these issues. My GPU is an GTX 2080 Super with sufficient memory (8 GB) and my PC system is an i7 - which always was good enough for high or even ultra settings. Now I have to play in medium settings 
Now I downloaded the latest studio (!) driver of Nvidea (v. 617.40 of 20th of Sept. 2022) and switched MSFS settings to DX 12 Beta. Iâm still testing but I believe, that I have had less CTD/error messages since testing that.
Hopefully it helps!
But one fact is clearly visible: The named error - even was marked here as solved - still remains for many users which now changing from SU9 to SU10 Ive written 2 reports to ASOBA Helpdesk as a BETA âtesterâ, still havent got an answer and they havenâs solved the problem yet.
So they ignore it an now are all SU 10 User in a new BETA testing phase
It is an MSFS / Asobo issue in the way handling with GPU and NOT an user issue, it do not depent on your hardware, windows config/reg., drivers or not enough memory. We can do nothing because we discuss it here since weeks, but the error is still there. Iâll will never got to BETA again, bacause they ignore this problem. Sorry, canât say more to thisâŚ
To all users: - please be so kind to write a zendesk report as the error wasnt fixed even is an issue since many weeks (also in BETA, since v .18 or 19).
The problem was marked as solved but is surely NOT SOLVED!
Reducing graphic settings to medium is no workaround as I now that my GPU and PC was always sufficient and strong enough to drive MSFS with highend or even ultra settings!
The error appears also in safe mode or without community folder.
The error is less often in medium setting but still happens, and surely often when using more complex sceneries or aircraft (jetliners).
My system:
In addition to the ingame error message Ive got this messages:
May that be also be an Windows issue?
Windows 10? so last year, needs updating
same, i had no restore Point.
i´ve done the 22H1 Installation with Rufus.
I experienced this error as I was loading into a flight. I was also poking around trying to find out why I get a CTD on launch if I enable DX12. I found a new file along with a JSON file in the main MSFS folder that was created at the same time I had the error. Within the JSON file it gets very specific:
âFault Descriptionâ: âA shader instruction caused an MMU fault when accessing memory.\nThis can be cause by a shader bug, shader microcode corruption, shader compiler bug, or binding setup issue.â,
âŚandâŚ
âFault Typeâ: âFailed to translate the virtual address.â,
âGPU virtual addressâ: 12763070464,
âFault Nameâ: âMMU Fault Errorâ,
âShader GPU Addressâ: âcompute_01 @ 0x000002b0â,
âShader mappingâ: null
I wonder if both the title error and the CTD when launching with DX12 are related.
nice that u found this!
That only means that the report has been handled by Support and forwarded to Development.
Confusing, I know, butâŚ
Asobo NEED to fix this ASAP
every second start up crashes now after su10 update. no matter which settings/driver.
Im really surprised the forum isnt raging about this, should it really stay like this until the next update? come on⌠5 minutes loading and then crash⌠its absolutely ridiculous they released it like this.
gonna get xplane 12 this weekend. Im done for now with this piece of software
I donât understand what you mean in a clean win 11 reinstallation. Have you reinstalled the game or win 11?
Already did it 
Sorry, but u dinât read my post right.