Hi @MortThe2nd, @Roland7807
to be sure: can you have a look at the timestamp from these file ?
Or also checking Programme/Feature whether the c++ lib was updated in meanhwile ?
Having the VCRUNTIME140.dll issue constantly, whether running in flat-screen mode (either full screen or windowed) and VR (HP Reverb G1 Pro). Iām using an i9 9900K and 2080ti, every other title works fine.
Have been trying to fix this for about three days now, Iāve done everything mentioned in this thread, including uninstalling all previous .NET installations and doing a clean install, fresh install of Windows 10, fresh install of MSFS20, overridden graphics to max performance in nVidia panel, etc. Nothing works.
1 Like
After the latest update, I keep having ctd just moments after takeoff due to vcruntime140.dll. This is frustrating because the system is 4 weeks old and was running fine before the msfs 2020 update. Any suggestions?
AMD Ryzen 5 3600
Radeon 5700xt
32GB memory
512GB SSD 1TB hard drive
msfs 2020 on SSD
Log Name: Application
Source: Application Error
Date: 2021-01-05 12:58:30 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-JAS76D3
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba
Faulting module name: VCRUNTIME140.dll, version: 14.28.29231.0, time stamp: 0x5f4c66c9
Exception code: 0xc0000005
Fault offset: 0x0000000000001550
Faulting process id: 0x3b88
Faulting application start time: 0x01d6e33fea84059e
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Report Id: d3258743-c80f-4815-8303-da9c6629af7d
Faulting package full name: Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Get into START/Device Manager/Display adapters and double clik AMD Radeoan RX 5700 XT; then Uninstall device; restart PC and let Windows rebuild the driver; check the WINDOWS driver version 2-12-2020 version 27.20.145002.208. Donāt let AMD push you any driver update and remove the AMD folder from C:
(I assume you have W10 updated already)
I canāt find that driver version 2-12-2020 version 27.20.145002.208. Do you have a link where i may download it from? Yes, I have Win10.
Thanks
There is no link; after uninstalling the current AMD drivers (see previous post), Windows will install the drivers.
What he means is that the driver version windows installs is different than the one you listed in your earlier post.
I tried the same while troubleshooting, and Windows will install the 27.20.1034.6 driver version, not the 27.20.145002.208 you mentioned in your post.
100% confirmed; removed AMD drivers with their tool, deleted the AMD folder on my C drive, and manually downloaded and installed the drivers through Windows Update (I donāt use MS Store).
I never use AI traffic, only Live traffic.
2 Likes
Hi, sorry, so does this work with this solution?
With which TOOL do you uninstall the AMD driver?
And ā¦sorry, which version of the drivers do you install manually?
Thanks in advance
Bye Massimo
no, it didnāt work for me, but maybe it will work for you.
But here is the tool: https://www.amd.com/en/support/kb/faq/gpu-601
And the driver I just let windows install, and then checked windows update (optional updates); should be an updated AMD graphics driver there.
Thankyou, I will try ā¦
in this way but you have lost amd catalyst control center. .. right?
Massimo
yep, but I donāt really use that for anything anyways.
well, Some good news at last.
I have no clue what changed, but just as sudden as the crashes started, they have stopped again.
Managed to do two 300 miles flights (for the Jack of all planes achievement) in a row tonight. Did the Extra 330 and the VL3. Both pretty long flights (for non AP aircraft), and no issues in either flight.
Hope it stays solid.
Only thing that I did notice is that the Oculus Link software got an update last night, maybe that fixed it somehow. VCRuntime is a weird beast.
1 Like
And sadly itās back again, right at the end of an 8 hour flight. 
Same here. Can`t fly. Hope for a Fix. For me this Trouble startet with the last big Update. (The one includes the VR)
After last update had some nice 12hr flights without issue then two days of many CTD VCRUNTIME errors, some 8hrs into flight and some 10 minutes. Very strange since I have made zero changes to setting or PC. This build does seem to be much improved though performance wise.
The Exception Code: 0xc00000005 is the code for āAccess Violationā, which means that the application tried to read or write to a memory address which didnāt belong to it. VCRUNTIME140.dll is a library of common functions that C/C++ applications can call. The Fault offset gives you the relative virtual address of the faulting instruction. The nice thing about the c runtime dlls is that you get symbols from the Microsoft symbol server with line names and line numbers and if you have Visual Studio, then you have the crt source code as well. Looking at some of these crashes, they are mostly doing memory copies of various flavors and walking off the end of buffers.
Unfortunately, the logs themselves arenāt going to be too helpful because memory copy functions are going to be called far too many times in too many contexts to be able to know what higher level call was responsible for triggering the bug. Asobo would need a crash dump (a mini dump would probably be sufficient) to track down the issue. The mini dump would provide a call stack, which would inform Asobo as to what part of their code was responsible for calling the memory copy incorrectly and triggering the crash. Depending on what is going on, it could be possible to determine a likely cause of the crash without having access to Asobo source or symbols by examining the memory being copied at the time of the crash. That would require a full memory dump. It is possible that the contents of the memory might be recognizable, which could suggest a possible cause.
Generating a crash dump requires turning on a some registry settings and is described here. Be aware that generating crash dumps takes some time. Mini dumps get generated fairly quickly, but a memory dump will have to write some 15+ gb of memory to your machine. In any case, if you turn this on and FlightSimulator.exe crashes, it will appear that the application has hung while the OS is writing out the dump.
It may be that Asobo is starting to capture crash dumps. I saw something in my event log recently that suggested that could be the case. However, if I were consistently getting crashes like this Iād still create a Zendesk ticket and attach a crash dump.
1 Like
This is a very good description of the situation. I have been hoping to have the error occur since I started working on a solution. I set up to capture a dump. Feel like I am fishing in a barrel without fish. Have not had a CTD since installation so it may be a while before I get the dump to analyze.
I have a suspicion however that either memory or memory controller stability may actually be flushing those buffers before the call is made. Otherwise this error would be affecting WAY more systems.
Ah, after days of no issues with VC runtime dllā¦ i am happy to say its backā¦ I really enjoy getting ready to descend into the destination, only to be booted to desktop nearly every flight now.
1 Like
I was 1:26 into a flight to Baghdad this evening in the A320 ā¦ no issues whatsoever, but as I was descending I clicked āTerrain Radarā on the cockpit panel and it instantly CTDā¦ not sure if it was a coincidence or not, but things were going very smoothly up until that point.
Checked application error log and sure enough, VCRUNTIME140.DLL
Sig[0].Name=Application Name
Sig[0].Value=FlightSimulator.exe
Sig[1].Name=Application Version
Sig[1].Value=1.12.13.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5fda3fe4
Sig[3].Name=Fault Module Name
Sig[3].Value=VCRUNTIME140.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=14.27.29016.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5ee8384d
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000014b4