then possible the older posts about hardware problems in relation to the VCRUNTIME140.dll error are relevant… 8hours where your system is in full load…
PS: do you have still 100gig rolling cache ? then set it do 8gig… who knows 
I made shorter flights with CTD, but I’m less angry when it appen after 30mn.
I didn’t see anything I didn’t test before posting.
I started seeing this randomly over the weekend, when flying around parts of New Zealand. I don’t have WU 12 installed. This is the first time I’ve seen it and it usually results in a hard crash to the desktop. I tried the same flight again and the same thing happened - seemed to be very random.
Further to my post, it seems that it crashes in the exact area each time in New Zealand - as I’m approaching Auckland. 4 attempts, 4 crashes. I do not have WU 12 installed. I’ve never had this problem ever and I’ve owned MSFS since launch. Very odd.
if possible add a screenshot from map , or share the coords , etc… so that we can re-test it.
There are situations, and we have some topics ( e. linz ) , where rare geo-locations can cause such kind of problems ( caused from map or the navi, who knows… )
I think I have the same issue. Attempting to load the third leg of the NZ north island bush flight reproducibly leads to a CtD with VCRUNTIME140.dll. Same thing when loading the previous leg and using the dev mode to teleport to the start of leg 3.
Exactly the same has just happened to me in the Auckland area!, it seems that this seems to be the culprit, I’ve never had a runtime error before!
I seem to have fixed my crash by going to the list of installed apps and selecting “modify” and then “repair” for the Microsoft Visual C++ 2015-2019 Redistributables.
For those having any CTD issue/s try the following…
Run the following commands in Powershell (admin rights)…
Go through each of the following steps one at a time. Copy each line, one at a time , paste it into the Dos window (crtl + V) and press return
and it will then run. Wait until each runs and finishes before you move on to the next one.
When you are completely finished, Restart your computer and then try to see in MS2020 will start and run properly
Dism.exe /online /Cleanup-Image /checkhealth
Dism.exe /online /Cleanup-Image /scanhealth
Dism.exe /online /Cleanup-Image /Restorehealth
sfc /scannow
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
Dism.exe /Online /Cleanup-Image /StartComponentCleanup
RESTART your computer as the last step. Then go for a test flight.
1 Like
This seemed to work for me, I can happily buzz around Auckland now without a CTD 
would like add the following link, just because Auckland was mentioned.
So, seems most probaly a rolling.cache file issue, or problem caused from a different cached file within app-data.
1 Like
THANK YOU! You are a legend mate, this completely resolved this issue for me around the Auckland area and any CTD related to it. Now NZ is true fun to enjoy and I can fly hassle and worry-free. People like you are what make this community golden, thank you again!
Hello, everyone.
So, everything worked well and then I just got such an issue
Faulting application name: FlightSimulator.exe, version: 1.37.19.0, time stamp: 0x00000000
Faulting module name: VCRUNTIME140.dll, version: 14.36.32532.0, time stamp: 0xc94bf788
Exception code: 0xc0000005
Fault offset: 0x0000000000002571
Faulting process id: 0x33dc
Faulting application start time: 0x01dad76c2e009ec4
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll
Report Id: dd083479-4c1b-427b-9324-117ee88c5795
Faulting package full name:
Faulting package-relative application ID:
I have exactly the same error since this morning aswell
I’ve just started getting this today also… odd.
I’ve been getting it since yesterday. Immediately after the Oculus software update.
Unfortunately I didn’t run MSFS yesterday before the oculus update.
However I had no issues with MSFS the day before.
1 Like
I also had the Openxr faulting module path. I deleted Ocules for windows and i seems to work now will do a test flight right now to make sure!
I can confirm that exiting the oculus BETA resolved the MSFS crashes for me
2 Likes
Ah, good shout! I’m on the PTC for Oculus too. Will revert. Thanks.
Hi, everyone.
I resolved the issue.
So, I just deleted all Oculus soft from my PC and now it works.
Maybe later I’ll try install older version of Oculus software.