yep.. this is only event type , not a dll 
Let us know whether you can re-create the CTD at the same coords.
Hi
I won’t be able to reproduce the CTD as i just pass on the coords point and i went trough.
Sort out this one.
Now need to check other coords where i have CTD too.
The CTD i was having is at ODVOD intersection north EGMA airport in England.
The other one i have is at HIJ VOR in Spain when i do the flight LEMD to SAEZ on the B787-10
A lot of the cleaning files done by Amswsoft PC Optimizer where on appdata\Local\Temp folder.
Oh well.
I can’t even start MSFS anymore without getting a CTD just before the main menu. This has happened before (it has started with Sim Update 4), has worsened over time (CTD every 2nd time I open the game), but since a few days it has become impossible to even start the game.
Of course, no error message, no logs, only the cryptic Windows event log because why giving your customers a clue about what’s happening, right?
Needless to say, nothing changed on my PC since these problems started to happen and then worsen, and all other games still run just fine.
I think I’ll give up at this point and hope they fix their product at some point. Just like back in October, when clouds started flickering, and they didn’t fix it until December.
I’m just super glad I didn’t invest any more money into this apart from the initial shelf price. I’ll update my product review accordingly. Good luck to everyone else.
3 Likes
.. it would be very unfortunate for you if you continue to use this game against your will ..
@Gsx31 I wanted to invest in the CRJ But since having these problems there’s no point in purchasing anything else for MSFS
1 Like
I will send you a private message
1 Like
show us the message 
Are this still your PC specs ?
I would be shocked to see this rig launch MSFS back in August. I had very similar spec on release and couldn’t get it it fire up. I had already ordered new hardware at the time but wanted to see if I could maybe pass the old system to my son so he could run MSFS, even dialed back. NOPE.
That GPU exceeds the minimum but does not quite the recommended. I remember some arguments about how the required spec has shifted upwards during development. I would imagine this will continue as DX12 comes in, and new effects are added by developers.
The GPU is borderline yes, but that 6700 plugs into the 100 series MB. It isn’t always about CPU/GPU. Sometimes its about the pipes in between.
1 Like
Version=1
EventType=MoAppCrash
EventTime=132682468739462833
ReportType=2
Consent=1
UploadTime=132682468812599471
ReportStatus=268435462
ReportIdentifier=f180b0f1-021f-4513-a949-f51db17cd61a
IntegratorReportIdentifier=638c140a-85c4-4f26-92d8-16f791918c87
Wow64Host=34404
NsAppName=praid:App
AppSessionGuid=00002bf0-0002-013b-672f-cc4ff961d701
TargetAppId=U:Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe!App
TargetAppVer=1.16.2.0_x64_!2021//05//19:14:34:31!0!FlightSimulator.exe
BootId=4294967295
TargetAsId=2053
UserImpactVector=269497136
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=07ef316c8e83cb0144b901610641d187
Response.BucketTable=5
Response.LegacyBucketId=1493226267678462343
Response.type=4
Sig[0].Name=Nome completo pacchetto
Sig[0].Value=Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe
Sig[1].Name=Nome applicazione
Sig[1].Value=praid:App
Sig[2].Name=Versione applicazione
Sig[2].Value=0.0.0.0
Sig[3].Name=Timestamp applicazione
Sig[3].Value=60a521f7
Sig[4].Name=Nome modulo con errori
Sig[4].Value=xgameruntime.dll
Sig[5].Name=Versione modulo con errori
Sig[5].Value=10.0.19041.7547
Sig[6].Name=Timestamp modulo con errori
Sig[6].Value=3342cc8a
Sig[7].Name=Codice eccezione
Sig[7].Value=c0000005
Sig[8].Name=Offset eccezione
Sig[8].Value=00000000000652fb
DynamicSig[1].Name=Versione SO
DynamicSig[1].Value=10.0.19043.2.0.0.256.48
DynamicSig[2].Name=ID impostazioni locali
DynamicSig[2].Value=1040
DynamicSig[22].Name=Informazioni aggiuntive 1
DynamicSig[22].Value=85de
DynamicSig[23].Name=Ulteriori informazioni 2
DynamicSig[23].Value=85de6de0f85ec6108091f6fd860f4f51
DynamicSig[24].Name=Ulteriori informazioni 3
DynamicSig[24].Value=4772
DynamicSig[25].Name=Ulteriori informazioni 4
DynamicSig[25].Value=4772db3a76ed304ebe70287960b226e5
UI[2]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
System Information
Time of this report: 6/15/2021, 21:36:06
Machine name: MIG
Machine Id: {9DAF5CD7-006A-45CE-B6A1-6EF753CAB44C}
Operating System: Windows 10 Pro 64-bit (10.0, Build 19043) (19041.vb_release.191206-1406)
Language: Italian (Regional Setting: Italian)
System Manufacturer: ASUS
System Model: System Product Name
BIOS: BIOS Date: 11/02/20 17:00:46 Ver: 05.00011 (type: BIOS)
Processor: Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 CPUs), ~3.8GHz
Memory: 32768MB RAM
Available OS Memory: 32668MB RAM
Page File: 6205MB used, 33885MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 168 DPI (175 percent)
System DPI Setting: 144 DPI (150 percent)
DWM DPI Scaling: Disabled
Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.0928 64bit Unicode
Display Devices
Card name: NVIDIA GeForce GTX 1080
Manufacturer: NVIDIA
Chip type: NVIDIA GeForce GTX 1080
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Device Key: Enum\PCI\VEN_10DE&DEV_1B80&SUBSYS_37171458&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 24412 MB
Dedicated Memory: 8079 MB
Shared Memory: 16333 MB
Current Mode: 3840 x 2160 (32 bit) (60Hz)
HDR Support: Not Supported
Display Topology: Extend
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.633789,0.340820), Green(0.311523,0.635742), Blue(0.158203,0.061523), White Point(0.312500,0.329102)
Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
Monitor Name: Generic PnP Monitor
Monitor Model: U28E590
Monitor Id: SAM0C4D
Native Mode: 3840 x 2160(p) (59.997Hz)
Output Type: Displayport External
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: Not Supported
Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a494df49ba2f9f36\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a494df49ba2f9f36\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a494df49ba2f9f36\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a494df49ba2f9f36\nvldumdx.dll
Driver File Version: 27.21.0014.6627 (English)
Driver Version: 27.21.14.6627
DDI Version: 12
Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 2.7
Hardware Scheduling: Supported:True Enabled:True
Graphics Preemption: Pixel
Compute Preemption: Dispatch
Miracast: Not Supported by Graphics driver
Detachable GPU: No
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:True
Driver Attributes: Final Retail
Driver Date/Size: 23/04/2021 02:00:00, 1050080 bytes
with copy and paste … it’s a pleasure! Anyway I saved you from copying the whole thing … it’s just a taste for MS / Asobo. 
This is only the second time I have seen xgameruntime.dll error. This is a /win32 file. Probably the first thing would be an integrity check. Replacing the .dlls, xgameruntime.dll gameconfighelper.dll gamingservicesproxy.dll. would be step two.
I have seen this failure in a couple UnReal Engine titles over the years. Only once before in MSFS.
1 Like
MSFS CTD start up problems since SimUpdate 4 finally resolved for me!
I have tried everything recommended by Zendesk and the forums to resolve this problem, but having recently come across some earlier comments recommending switching Bullgard off, I tried this and couldn’t believe it when MSFS immediately restarted!
I have used Bullgard for years without any MSFS problems, but for some reason SIM Update 4 clearly seems to have triggered a blocking mechanism within my Bullgard antivirus.
I would recommend that anybody suffering CTD’s with Bullgard, installed should also try this.
Unbelievably major breakthrough. By further decreasing GPU Max Frequency to 70% via AMD Adrenalin, I’m not getting any CTDs at all. After months I can finally load Icon A5 or WT CJ4 (which at default AMD settings would CTD 100% of the time within a minute or two) and fly with either aircraft for at least 10-20 minutes without any issues. Today I may try longer flights. No CTDs in main menu either, which was the biggest of my problems.
CTDs still happen when Max Frequency is at 80%. Essentially we’re not talking about disabling overclocking (as many of you may jump in and remind me), we’re talking about underclocking standard factory GPU settings, ie. decreasing advertised performance of the GPU to make it work with MSFS. First time I see this in my 20+ years of PC gaming…
Max Voltage doesn’t seem to play any part in this, no CTDs between 90-99% so I’ll just leave it at 100%. I suspect that Max Power Limit may also be relevant but I’ll have to do additional testing.
The obvious problem is that by limiting GPU Max Frequency to around 70% I’m getting significant fps loss, especially when turning the camera left and right. But at least it’s tolerable and I have something which I can build on and try to find a sweet spot or further experiment with AMD settings.
ps: crossing fingers and assuming the above workaround fixed my CTDs, it’s still an MSFS issue. Other games are not only happy to work at GPU factory defaults, but they can even tolerate extra overclocking. MSFS needs to be underclocked to work with 6800XT? Wth? Not to mention that certain aircraft never CTD even at default GPU settings. So definitely not a GPU thing.
4 Likes
Dude, you sound exactly like me. I also got GIGABYTE RX 6800 XT and have massive CTD between few seconds (main menu even, bur rarely) up to 2 hours. Yesterday I was able to stream MSFS via Twitch for over 11 hours without CTD - solution? LOW GRAPHIC SETTINGS. As soon as I came back to medium/high/ultra it started to crash again.
Now, out of curiosity - download OCCT5.5.6.exe (THIS AND ONLY THIS VERSION!!! IMPORTANT) and run VRAM test. My RX 6800 XT failes this test and throw error or even BSOD.
And just for information what I’ve done in past 2 months
- overclocking/underclocking GPU
- default BIOS settings (no overlock, no XMP)
- update BIOS
- turning ON “Re-size BAR Support” - known as SAM - Smart Access Memory
- different PSU
- different RAM
- turning off freeSync
- unplugging second monitor (I have two screens)
- switching GPU PCIE port to second one
- and many, many, many things that I even forgot but did not help
In my opinion:
a) we got faulty VRAM on our GPUs
b) MSFS got bug that crashes VRAM on GPU
I wish there was a way to lower clock of memory of our GPUS to find it out… But there is no support of this.
Well, it might be an issue with your particular GPU, or even your system in general.
Any Nvidia users care to comment on this?
A faulty GPU would most likely crash randomly, not only in MSFS but in other games as well. Mine never crashes in other apps, passes all stress tests, works perfectly fine with CP2077 and also with MSFS when I’m flying C152/172 or Piper Arrow. So nothing inherently faulty with the 6800XT.
On the other hand MSFS always CTDs for several other aircraft (default or not) or quite often in the main menu. With or without addons, after Windows/MSFS clean install etc.
Sounds too specific to be a random hardware fault. The rest of the system is fine, MSFS was working OK with it for months and I didn’t change anything except the GPU.
It’s MSFS and that’s the end of it. Something’s causing it to break under specific circumstances when GPU frequency is left at 80% or above AND certain aircraft are loaded. But Piper Arrow working at 80% or even 100% frequencies is perfectly fine. Doesn’t sound like hardware.
2 Likes
Yes. Just google “msfs vcruntime140.dll rtx” and you will see people that got RTXs and have same issue.
As I said before:
a) vaulty VRAM (either AMD or NVIDIA - whate are memory manufactures? Hynix? Samsung? Anyone more?
b) msfs got nasty bug with GPUs VRAM.
Have you done OCCT5.5.6.exe VRAM test? Please try it. I would to know if it crashes on your PC too.
Because OCCT5.5.6 and MSFS are only software that crashes. No other problems.