I’m not sure if any of you realise in the base installation folder whenever the warning dialog happen, there are two dump files to inspect whats happen:
You can open the json file it is more human readable to figure out what is wrong with your previous session
E.g. i have a bunch PAGE_FAULT which related to DMA error from RTX3080 Ti
Which make me think probably the my nvidia driver or memory corruption is the culprit
Flew a couple of flights in the PDMG 737-700 today in and out of complex airports with no issue then loaded a flight in the Caravan in the middle of nowhere and bam, this error message. Weird!
Trying a solution. With the drivers of May 512.95 without install Geforce Experience yesterday flying 4 hours and any CTDs. Windows 11 H2.
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:
12900k stock clock, ROG Strix 3800, 32GB DDR5 6400. Error first occurred 09/24. Loading up PMDG 738 on DD EPMO or EPWA will cause it within 5 minutes. Crashes either with or without the error message. Reverted from 517.48 to 512.95 - no effect. Been running this config stable for months with no issues at all, only started with SU10.
Are you using DX12?
No
Are you using DLSS?
No
If relevant, provide additional screenshots/video:
Clues from jsons:
[
{
“Base info”: {
“Application name”: “flightsimulator.exe”,
“Dump date”: “Thu Sep 29 13:55:38 2022”,
“Graphics API”: “Direct3D 11.2”,
“PID”: 7648
}
},
{
“OS info”: {
“Build number”: 22621,
“Service pack major version”: 0,
“Service pack minor version”: 0,
“Windows major version”: 10,
“Windows minor version”: 0,
“Windows product type”: 1
}
},
{
“Display driver info”: {
“Version”: “512.95”
}
},
{
“Device info”: {
“Adapter reset occurred”: false,
“Device state”: “Error_DMA_PageFault”,
“Engine reset occurred”: true
}
},
{
“GPU info”: {
“Adapter LUID”: 68041,
“Adapter name”: “GA102-A”
}
},
{
“Page fault info”: {
“GPU virtual address”: 0,
“Resource”: {
“Buffer heap”: false,
“Context pointer”: 2328619254408,
“Create destroy tick count”: 424843,
“Depth”: 1,
“Destroyed”: false,
“GPU virtual address”: 0,
“Height”: 1440,
“Mip levels”: 1,
“Placed Resource”: false,
“Render target / Depth stencil view heap”: false,
“Requested API format”: “DXGI_FORMAT_B8G8R8A8_UNORM”,
“Size”: 31457280,
“Static texture heap”: false,
“Width”: 5120
}
}
},
{
“ApplicationName”: “Microsoft Flight Simulator”
},
{
“ApplicationVersion”: “1.27.21.0”
}
],
[
{
“PageFaultInfo:”
“Faulting GPU VA : 0”
“FaultType: GFSDK_Aftermath_FaultType_Unknown”
“AccessType: GFSDK_Aftermath_AccessType_Unknown”
“Engine: GFSDK_Aftermath_Engine_Unknown”
“Client: GFSDK_Aftermath_Client_Unknown”
“ResourceInfo:”
"Resource GPU Virtual Address: 0 "
“Resource Size: 31457280”
“Resource width: 5120”
“Resource height: 1440”
“Resource depth: 1”
“Resource mip levels: 1”
“Resource Format (to cast to DXGI_FORMAT): 87”
“Resource is Buffer Heap : false”
“Resource is Static Texture Heap : false”
“Resource is Is RenderTarget or Depth stencil view heap : false”
“Resource is Placed Resource : false”
“Resource Was Destroyed : false”
“Create destroy tick count : 424843”
",
“ActiveShaderInfo:” ,
“ShaderLookup:” “”
[
{
“Base info”: {
“Application name”: “flightsimulator.exe”,
“Dump date”: “Thu Sep 29 13:30:06 2022”,
“Graphics API”: “Direct3D 11.2”,
“PID”: 11868
}
},
{
“OS info”: {
“Build number”: 22621,
“Service pack major version”: 0,
“Service pack minor version”: 0,
“Windows major version”: 10,
“Windows minor version”: 0,
“Windows product type”: 1
}
},
{
“Display driver info”: {
“Version”: “517.48”
}
},
{
“Device info”: {
“Adapter reset occurred”: false,
“Device state”: “Error_DMA_PageFault”,
“Engine reset occurred”: true
}
},
{
“GPU info”: {
“Adapter LUID”: 53412,
“Adapter name”: “GA102-A”
}
},
{
“Page fault info”: {
“Access Type”: “Read”,
“Client”: “Graphics Processing Cluster”,
“Engine”: “Unknown”,
“Fault Type”: “Failed to translate the virtual address.”,
“GPU virtual address”: 71689895936,
“Resource”: {
“Buffer heap”: false,
“Context pointer”: 1890523800408,
“Create destroy tick count”: 2377421,
“Depth”: 1,
“Destroyed”: false,
“GPU virtual address”: 71689895936,
“Height”: 256,
“Mip levels”: 1,
“Placed Resource”: false,
“Render target / Depth stencil view heap”: false,
“Requested API format”: “DXGI_FORMAT_R8G8B8A8_TYPELESS”,
“Size”: 262144,
“Static texture heap”: false,
“Width”: 256
}
}
},
{
“Shader infos”: {
“Info”: {
“Shader hash”: 4456501539687578903,
“Shader name”: “compute_01”,
“Shader size”: 1280,
“Shader type”: “Compute”
}
}
},
{
“ApplicationName”: “Microsoft Flight Simulator”
},
{
“ApplicationVersion”: “1.27.21.0”
},
{
“Active Warps”: [
{
“GPU Address”: “compute_01 @ 0x00000260”,
“Shader mapping”: null,
“Warp count”: 32
}
]
},
{
“Faulted Warps”: [
{
“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.”,
“Fault Name”: “MMU Fault Error”,
“Shader GPU Address”: “compute_01 @ 0x00000200”,
“Shader mapping”: null
}
]
}
],
[
{
“PageFaultInfo:”
“Faulting GPU VA : 71689895936”
“FaultType: GFSDK_Aftermath_FaultType_AddressTranslationError”
“AccessType: GFSDK_Aftermath_AccessType_Read”
“Engine: GFSDK_Aftermath_Engine_Unknown”
“Client: GFSDK_Aftermath_Client_GraphicsProcessingCluster”
“ResourceInfo:”
"Resource GPU Virtual Address: 71689895936 "
“Resource Size: 262144”
“Resource width: 256”
“Resource height: 256”
“Resource depth: 1”
“Resource mip levels: 1”
“Resource Format (to cast to DXGI_FORMAT): 27”
“Resource is Buffer Heap : false”
“Resource is Static Texture Heap : false”
“Resource is Is RenderTarget or Depth stencil view heap : false”
“Resource is Placed Resource : false”
“Resource Was Destroyed : false”
“Create destroy tick count : 2377421”
",
“ActiveShaderInfo:” “Active shader hash: 3dd8ac89ee0f3d17”
“ShaderHashForShaderInfoh : 3dd8ac89ee0f3d17”
“Instance: 000001b315ced660”
“Type: 6”
“Internal: true”
,
“ShaderLookup:” “”
*3080 RTX, typo.
thats intressting… There is an update in that lib , the former one was 2.11 ( in my backupof 31.07.2022 ), now it is 2.18 .
What this lib do:
NVIDIA Nsight Aftermath SDK is a simple library you can integrate into your graphics applications’s crash reporter to gather additional information or generate GPU “mini-dumps” when a TDR or exception occurs.
so… it points still that somewhat determine an issue with your GPU.
BUT:
R470 : Fixed misreporting of any GPU exception as a page fault.
sounds near by " Error_DMA_PageFault " , but of course rerported for R470 cards… but who knows.
Maybe someone is brave enough and tries the previous version of the dll 
PS: biggest guess I ever had and I also never seen that error popup
at last a proper crash dump , now will any Asobo dev please step up.
PS: dont forget to add all that infos at the ZenDesk ticket ( json + dump ).
one wierd issue i noticed while updating to SU10 is that there was a particular packeges that were not updated, the installer just skipped them (their size Approximately 4.5 GB out of 16 GB), so if these files are not related to the update, why to include them in the update installer in the first place. so if thats an error and not a regular installation proccess in the SU10 update, maybe it has to do with this gpu error, by being files are missing or corrupt or something. thats just an idea.
the problem is, that sometimes I can fly several hours without message or CTD but than suddenly , again this error/CTD. So it is hard to find the reason. Pse give a message if your problem was healed threw this driver version in long term testing.
With the last drivers of NVIDIA (DDU first) and HAGS desactivated i don´t have now CTDs.
So is there any solution to this?
yes… see one post above yours…
PS. kind of useless such questions
I’ve done exactly what is above and still get same error and CTD…
PS. kind of useless to talk down to people when the solution doesn’t work for everyone…
Thats just one users case. I wouldnt ask if it solved the problem for me…brb
Is there any way we can bump this up to “Bug-Logged” status. I think it’s gone beyond “feedback”.
This severely impacts the reliability and playability of this sim
(I hope everyone posting here has voted at the top of this thread)
Asobo’s response is nonsense. This needs to be escalated and fixed. It happens very regularly on the new nvidia drivers and SU10, and has never happened before on any prior update. Nothing changed about my hardware or software setup except SU10 and the nvidia drivers we were officially recommended to install along with it.
Not to mention that it happens even before the flight has finished loading, a point at which you should never, ever have run out of GPU memory on my RTX 3060. Yet it doesn’t do it every time with the same setup, only intermittently. With the exact same settings it will regularly and happily work fine for a 6-8 hour long flight with a consistent 50+ fps and basically no stuttering. But every handful of attempts, it will fall on its face before it even starts the flight.
Either Asobo has a problem, nvidia has a problem, or you both do. This is clearly affecting many users and is a new bug; fix it.
Absolutely 100% correct. The problem occurs even before flights have started and on machines which are regularly able to run for many hours at high, stable frame rates with the exact same settings. There is a 0% chance that it is caused by VRAM running out, @SeedyL3205 . @FlyingNautiker 's screenshot proves this, as VRAM can’t “run out” in the main menu of a properly-functioning program before it has even started to load a flight.
Nor are we talking about marginal machines here; mine happily runs for 6-8 hour flights at 50+ stable fps with these exact same settings most of the time, and yet you expect me to believe my card doesn’t even have sufficient memory to start the game with those settings because it randomly falls on its face before it even loads a flight at all? Nonsense!
Instead of dismissing this out of hand as a user issue, please acknowledge that literally hundreds of Asobo customers have actively gone out of their way to report this problem (which means that tens or perhaps hundreds of thousands will be silently experiencing it too). And that those same customers unanimously agree that we had NO such problems on the exact same hardware and settings prior to SU10 and the latest nvidia driver update that Asobo told us we should be using.
Please listen and help fix the problem.
I do not know, the same as most contributors , but I suspect that if Asobo knew the reason for the issue that they would tell use all. Any criticism therefore is totally useless because they have no reason to hold back a solution that would give them more credibility.
Unfortunately this started happening on the penultimate beta build when using the previous drivers.
This isn’t a new / post-release problem, and Asobo’s proposed cause and fix (via Mods/Community Managers in this forum) is just plain incorrect. As I’ve said repeatedly based on my own experience, this is nothing to do with VRAM, it is nothing to do with RAM, it’s nothing to do with graphics settings, nothing to do with drivers (at least not in any way we can control) and it is not adding a message to previously unidentified crashes.
Thankfully, I’ve only experienced this crash 3 times (which is enough frankly), but I really feel for those for whom this is making the game unusable.
Just be aware that relentlessly installing / uninstalling drivers, changing bios settings, fiddling with Windows etc WILL NOT fix this crash, doing so is wasting your time. There is a problem in the game and only Asobo can fix this.