you just wrote that other games have same issue at your PC 
But anyway…
you already increased virtual memory to max 20Gig ?
And reset setttings within nvidia control panel to default 
I also had another CTD yesterday. While in flight I paused the game by pressing Esc because I went away for a short time. When I came back to my PC 10 minutes later the game was closed. I had the x000005 error code as always.
I struggle too.
CTDs EVERY single time. It’s impossible to make a flight. Crashes occur sometimes once FS started already in the home menu, sometimes during taxi, sometimes during flying.. very often around 5 min of flight.
tried everthing i can, clean reinstall, registry clean, c++ re-installation, removed overclock, limited frames to 30 fps, lowered resolution.. no help.
Windows event log sayis following, in the same pattern over and over again:
Failure 1:
\Device\Video3
Graphics SM Warp Exception on (GPC 2, TPC 0, SM 1): Out Of Range Register
Failure 2:
\Device\Video3
Graphics SM Global Exception on (GPC 2, TPC 0, SM 1): Multiple Warp Errors
Failure 3:
\Device\Video3
Graphics Exception: ESR 0x5147b0=0x12000d 0x5147b4=0x4 0x5147a8=0xf812b60 0x5147ac=0x1174
and then the famous 0xc0000005 code and VCRUNTIME140.dll and FlightSimulator.exe seem to crash.
it seems the “nvlddmkm” make trouble prior to the crash, this is the nvidia driver. Asobo told they have made some improvements to some card users.. maybe they have messed up here?
Ryzen 9 3900X
Aorus RTX 3080 Extreme
Aorus X570 Extreme
32 GB 3,6 GHz G.Skill
FS is installed on a 1TB EvoPlus SDD
crash after 10 minutes of flight in snowy condition…restarted the sim…went back into the same conditions and it crashed immediately once im in cockpit. no error message just straight to desktop. sound freezes and then 2 seconds later the game closes. now i made a third try…same…the game closes immediately once im loaded into cockpit
I get CTD’s with only one scenery, when I am in vancouver wuth fsdreamteam
I increased my virtual memory to 200000, no more CTD’s as of now. Thanks for the advice.
1 Like
press the like 
EDIT: ah.. I mixed up you with @Player448336125
1 Like
If you have CTD without an error message (even with 20GB of virtual memory), just check a load of RAM and this virtual memory size.
After the last update in heavy scenery this file is filling up to 19999MB and if my ram goes higher than 14GB (16 in total) - 100% CTD in the next few minutes.
I am sure, that there is a memory leak in FS2020 after the last update, or maybe even “waterflow”.
CTD became more often for the community,
Same here, MSFS Crash spontaneous. It looks like old problems are back after update 2 with VR support. Also noted that Runways are missing in FMC and stars.
RAM currently using 13GB in flight. Was 19GB highest. It was around 10-11GB previously, but I guess this is because of my new RTX3080 which runs in 4K.
After I tried just everything possible, I have rolled back my Nvidia driver to 457.51
460.89: released on 15.12, causes almost instantly crashes.
457.51: released on 02.12, runs ok as of now, 40 minutes of flight on ultra and heavy covered clouds in 4K. No crashes yet, couldn’t make to this point before, I crashed already during taxi before
The FS update was released on 22.12.
Well, after a few months of going back to P3D for a while, I thought I would try MSFS again… It took 2 hours to download the ~26GB update, which promised various stability improvements and crash fixes.
Well, MSFS crashed within 30 mins on the main menu screen. Needless to say, I am very disappointed in Asobo’s reaction to attempting to fix this bug. They seem to be preoccupied with developing new content, rather than supporting/fixing the stability issues.
I have raised several support requests on Zendesk, only to find an automated response to clean various things and attach an event log… which I have done, and I guess so many of us have done in the past.
Being a software engineer myself, I took it upon myself to do my own investigations. However, my investigations are only limited to my setup.
Cutting a long story very short, I was able to determine that my GPU was being throttled BEFORE it reached its prescribed throttle temperature. My GPU’s (GTX 1080ti) prescribed throttling temperature is 84C, but started throttling at 72C. A little while after GPU throttling, MSFS crashed every time.
How did I temporarily fix the throttling? I used MSI Afterburner to create a custom fan profile, so when the temperature reached 60C, the fan would go to 100%. The temperature never went beyond 72C, therefore was not throttled AND I was able to play MSFS for a few hours without any crashes.
It seems as though MSFS has run into the same problem Lockheed Martin was getting with P3D and their DXGI_ERROR_DEVICE_HUNG when GPUs are being throttled.
@Asobo, please please read these messages, investigate, diagnose and fix this bug!
Meanwhile, I shall be going back to P3D… again. As I prefer stability over graphical quality
1 Like
I am going to take a shot in the dark…
The majority of systems released recently have some sort of accelerator built into either the bios or running in the background. Most memory and CPU’s become more unstable as the clock speeds/voltages are tweaked by these accelerators. Take some time to make sure that those boosts are disabled and the system is running at stock speeds. This includes the video card accelerators.
Once your system is running at pure stock speeds and voltages, reboot completely update Windows. (remember that many of the Windows updates require multiple restarts to successfully install).
Now you are ready to retry MSFS, also in its pure state. NO files in the community folder or background helpers like FSUIPC or FaceTrackNoIR, etc. Also ensure that your virus/malware software is disabled. If you still have CTD problems, you may need to REMOVE and reinstall your video and sound drivers.
You should now be able to run MSFS without crashes. You may now start adding back the extras. ONE AT A TIME. Trying MSFS each time. Hopefully you will discover what is causing the issues.
Yes, same problem.
I turned off AI traffic when I first installed MSFS. I only use Real Time Traffic. Have never encountered a CTD.
Coincidence?
1 Like
ive tried everything i can think of and still get cdt
from fresh install i can start a flight and even get in VR but after 5mins it CDT
then after that i get constant CDT whilst loading either at Asobo logo or as the main menu appears…now fed up reinstalling
back to xp11 for now i think…feel cheated after purchasing 23/12 and not been able to have one descent fly
1 Like
Reinstalling is seldom the solution. There is obviously an underlying issue that is causing your CTDs.
If you would like to start by posting the specs of your system, including…
- CPU
- GPU
- Motherboard
- memory
- power supply
- resolution settings
Any mods, background add-ons or AV/AntiMalWare
as well as any Windows error logs…
it may be possible to narrow down the cause.
I m having the same problem. Steam won’t launch the Sim. Tried unistalling the whole thing and now not even able to install again. Straight CTD after pressing play in Steam. Any solutions? Thank you
im running
ryzen 3600 aio cooled
msi b450 carbon pro ac (lastest dec bios)
32gb oloy rgb ddr4 3200 (xmp timings and 1.35v rec. by manufacturer)
asus rog strix 1080ti
650w semi modular psu
2x2tb sabrent nvme ssd
nothing is overclocked…xmp is only used to select oloys suggested timing and voltage (use to have stability issues until this was done)
What mods are you running? Any liveries?
im running fresh clean install…no mods watsoever
my purchase was from microsoft store so not steam…have fresh installed 3 times now
also not firewall or antivirus