Same here. On top of all BRAND new, top notch hardware, I JUST installed a new Plat 1000W PSU… no change.
AMD Ryzen R9 3900X | 64GB DDR4 3600| AMD Radeon RX 6900 XT | Samsung 970 Evo 1TB NVME | HP Reverb G2
F*** this sim. I want my $$ back
CTD with amd window telling me that I have a driver time out. Using newest drivers.
PSU is fine, furmark @ 115% power usage (in amd radeon settings) + prime95 max power is handled well for long times. AMD Radeon 6800 XT @ 8700k (non oc) @ asus z370-i and 32 GB 3200 mhz xmp ram (on xmp settings).
20 runs in Linpack extreme says my hardware is stable.
Unusable in VR now.
The microsoft event viewer (open “windows logs” and then “application”) shows this error message:
Faulting application name: FlightSimulator.exe, version: 1.17.3.0, time stamp: 0x00000000
Faulting module name: VCRUNTIME140.dll, version: 14.28.29910.0, time stamp: 0x602478b9
Exception code: 0xc0000005
Fault offset: 0x00000000000014d3
Faulting process id: 0x2fbc
Faulting application start time: 0x01d76c580730468f
Faulting application path: D:\Games\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: e3a66f59-9b69-4eb0-b3bd-610f41fe0479
Faulting package full name:
Faulting package-relative application ID:
Maybe try reinstalling VC++ Runtime? (Latest supported Visual C++ Redistributable downloads | Microsoft Learn)
The version I have installed is 14.29.30037.0, yours is 14.28.29910.0.
So I tried to fly the CRJ 700 with HP Reverb G2 earlier today. and I had several crashes, some as far as 10 min apart. Some when trying to either enter og exit VR.
My system is 5800x x570, 64GB RAM, 6800XT
The odd thing is going into the Microsoft event viewer there are several different issues.
Twice was that VCRUNTIME. My version was 14.29.30035.0
The exception code 0xc0000005 was consitant with all errors.
Other errors include d3d11.dll, versjon: 10.0.19041.746
And alo this one:
Application: FlightSimulator.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF6E07AC296
So seems like there is a deeper root cause. I am curious to how many of us with issues have either Steam or MS Store solution.
I have MS Store but installed at other than default location.
But ofcourse still some of the core files are locked away in the Microsoft folder.
Many of us have tried everything we can possibly think of reinstalling sim, OS, VC Runtime, registry edits, power table mods, swapping out components. This particular problem (either VCRUNTIME140.dll or d3d11.dll crashing the sim) is specific to AMD GPUs and Reverb G2. It is related to how the SIM/GPU utilizes RAM and no work around will fix this until Asobo/AMD/HP will get their acts together. We are now up to 52 votes. Let’s try to get Asobo to take this more seriously. Nearly 6 months of silence and ignoring a reproduceable bug is really unacceptable.
Hi,
The CTDs are not only limited to the G2. I get constant CTDs with my Valve Index, and my Pimax 8kx and 5k+. using a RX 6900 XT card.
Tried all the steps suggested by the reply from Zendesk, but to no avail.
DCS and X-Plane 11 on the other hand run flawless in VR. Go figure…
It’s not specific to G2.
I have a Samsung Odyssey WMR (the first model) and can’t flight in VR without CTDs and other kind of erros.
Pancake mode (2D) works flawless.
Other games (XPlane, Project Cars2, Elite:Dangerous, No Man’s Sky) works without problems.
Which GPU do you use? What is the error message in the event viewer?
There are all sorts of CTD, but this particular issue relates to VCRUNTIME140.DLL or D3D11.DLL crashing the sim. If you are getting the same error, I may rule out headset as the source of the problem.
Can i edit the thread title or only the post body? Would this keep the upvotes?
I’m thinking to condense information from all those that posted and present it neatly so if a developer reads it it will be easier.
Really hoping the July Sim Update will resolve these issues. Per their Twitch Q and A with the devs, it sounds like VR may see an improvement with the changes made. Less stuff forced on a single thread and the GPU will have its fair share of work to do, which is fantastic! It also appears that they’ve cut down on how much VRAM and RAM will be used even in dense areas with Ultra settings. Fingers crossed!!! I’m experiencing issues in both VR and 2D (CTD within an hour of launching the game) with my 5900X and RX 6800XT since the last update.
I have a Sapphire RX 5700 XT.
The last I have is in the MSFS itself:
Nome do aplicativo com falha: FlightSimulator.exe, versão: 1.17.3.0, carimbo de data/hora: 0x00000000
Nome do módulo com falha: FlightSimulator.exe, versão: 1.17.3.0, carimbo de data/hora: 0x00000000
Código de exceção: 0xc0000005
Deslocamento da falha: 0x0000000001705534
ID do processo com falha: 0x1864
Hora de início do aplicativo com falha: 0x01d7689946ed42c4
Caminho do aplicativo com falha: E:\Steam Games\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Caminho do módulo com falha: E:\Steam Games\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
ID do Relatório: f6bd0673-598e-4d22-a4d7-2d82b639910f
Nome completo do pacote com falha:
ID do aplicativo relativo ao pacote com falha:
But I had all kinds of errors (VCRuntime related, DirectX related, WinXrRuntime related).
Not only AMD, the nVidia 1660 is the same. I was wondering why MS decided choose Asobo to build this game.
Doing some testing atm and am curious how many of you with AMD graphics cards AND VR headsets are having issues in 2D. I’ve noticed that my CTD’s in 2D have increased since I’ve had my HP Reverb G2 connected to my computer (even when not in VR and the software is shut down). I get a weird error about a USB device not being recognized and a CTD shortly there after. Since disconnecting the USB from the G2 to my computer, my sim appears stable and hasn’t crashed over the last 2 hrs. I’ll keep y’all posted, but worth a shot if you have the same config.
Edited Note: Could be related to the USB Port issues on the AMD X570 and B550 boards, but interesting none the less. Never had any issues with my Rift S, but the G2 is definitely more powerful/higher res.
I’ve have a Quest 2 and 6900xt but don’t leave it plugged in unless I’m in it. I’ve not had any CTD in 2d just vr.
Oculus just released through the beta Channel an update that has allowed me to fly more than 40 minutes 3 times tonight without a crash which is unusual and when looking side to side often to get it to crash.
Hope this is getting fixed!
In reliability monitor now after closing those 3 flights was just …bad module error… and not the flightsim error.
Adding… I’m running 21.3.2 Radeon driver as it’s the fastest for vr so far and no tweaks to the card.
2D is back to normal!!! Yay!!! Still have issues with my RX 6800XT in VR though. We’ll see what SU 5 brings.
This last few days have improved with less ctd after I moved all my stick ,throttle and pedal usb cables off the front of my case,round to the back usb’s which are much newer.
I have found the best plane for me is the Cessna Citation.I believe there may have been some conficts going on here with these older usb ports.I have flown from Goose Bay MA to Greenland from Greenland to Iceland from Iceland to Norway with no crashes.
I also tried rolling back the Amd driver to the first release for 6000 serries cards but still had one crash.I am still currently using that driver.What I will try next is moving back to a newer driver to improve frame rates.I will continue testing to see if less ctd’s occur flying over water!My next flight will be over land.
I had three ctd’s yesterday flying out of San Pablo Airport in Spain in the 172 g1000 at low altitude heading south west very early in the flight.So its not perfect but I hope someone may benefit from this post.
Same here, stuck on driver 10.1.20 with my AMD Radeon RT5700XT. Any driver newer than that I get CTDs with MSFS2020.
I’ve tried everything to fix this problem!
Same here ! Good job Asobo !
6900XT w/ G2
Hi,
Since I installed the 21.3.1 driver I was actually able to complete a flight. For several days there were no more CTDs with MSFS in VR with my RX 6900 XT card. So far so good. 
21.3.2 driver and newer always resulted in CTD.
To start I run 6900xt Sapphire Nitro SE edition, 5800X, 64 gigs Gskill 3600 XMP @ 16 22 22 22 42 and VR Quest 2 @ 1.2 SS @ 90hz anything more will CTD the Sim, Using AMD driver version 21.5.1 and have tried everything form original 6900 drivers from AMD to the latest but have settled on the 21.5.1 as these have been most stable.
I have since dug out some old gold 32 gig G-skill 4x8 cl 15 3600mhz XMP 15 15 15 15 35 ram I had in my old build from Intel Z390 days.
First thing I did was take the Old Ram from 3600 mhz xmp with same timings to 3800mhz @ 1.40v from 1.35v with infinity fabric @ 1900mhz. Thought I’d get a CTD right away but I did not get a crash in the testmem5 or errors or the latest flights I’ve done which was a little strange as my 64 gig kit of G-skill 3600 with xmp @ 3600 1.380v or 1.420v I would just quit to desktop at a drop of the hat looking out to the left or right of my aircraft in VR running the quest 2 @ 90hz and 1.3 SS.
I’m going to leave the 32 gigs of G-skill ram in for now even though it is only 32 gigs. So far MSFS is more stable in VR and I’m not getting a CTD with the higher SS in quest 2 settings @ 1.5 and render scale @ 100 and both LOD’s @ 150.
Strange to say the least. Maybe MSFS or AMD drivers not playing well with the 64 gigs of G-Skill?
Note: I have tried the 64 gig kit @ stock but still was getting the CTD with it.