VCRUNTIME140.dll Error

Hi Guys,

Pre-1.8.3.0 patch my MSFS2020 was working like dream. Now I am finding that my game crashes after getting into a flight and crusing anywhere between 30-60 minutes. I never had the issue prior to this patch but it seems to have plagued my system since this patch was released.

  1. I have tried uninstalling and reinstall MS Visual C++ 2015-2019 Redistributable (x64) and (x86) twice as well as preparing this.
  2. I have enabled virtual memory and set this to system managed as suggested by someone in another forum.
  3. I have also updated from OS 1909 to 2004 in a bid to help fix this issue, although many users on 2004 are reporting issues with their MSFS2020.

Has anyone else ran into this issue and if so have they found a work around for this? Do we just have to wait till an update is released to fix this issue? Thanks for your assistance in advance.

Event viewer log for the crash is attached below:
Faulting application name: FlightSimulator.exe, version: 1.8.3.0, time stamp: 0x5f5f47ed
Faulting module name: VCRUNTIME140.dll, version: 14.24.28127.4, time stamp: 0x5d8e68d2
Exception code: 0xc0000005
Fault offset: 0x00000000000012de
Faulting process id: 0x2bc0
Faulting application start time: 0x01d690c1d04f6566
Faulting application path: D:\Custom Steam Library\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: fc89816d-b63b-4337-bb60-d3193d009d89
Faulting package full name:
Faulting package-relative application ID:

Run System File Checker to see if the system does not contain corrupted/outdated/damaged files.

  • Use windows search to find Command Prompt. type CMD @ Start
  • Right-click on it and select Run as administrator.
  • Then, type sfc/scannow command. Press Enter to execute it
1 Like

I may have just fixed this issue so far. I am testing at the moment still.

It was suggested on discord to go to Options > General > Sound and change the Text-to-Speech-Settings from Azure to Windows Offline.

So far I have been in a 1.5 hours flight without any CTD. I will keep you posted as this is a 4-hour flight if all goes well hopefully this can be a temporary fix.

2 Likes

I will give this a go if my current temporary fix which has so far been OK, fails. Thank you for you response FSEINDHOVEN.

@FSEINDHOVEN Okay the game crashed exactly after 1 hour and 45 minutes into my 4 hour flight… I may have to try give the SFC scan a go now.

Faulting application name: FlightSimulator.exe, version: 1.8.3.0, time stamp: 0x5f5f47ed
Faulting module name: VCRUNTIME140.dll, version: 14.27.29016.0, time stamp: 0x5ee8384d
Exception code: 0xc0000005
Fault offset: 0x00000000000012de
Faulting process id: 0x2320
Faulting application start time: 0x01d6918450529aaf
Faulting application path: D:\Custom Steam Library\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 8cfedad7-95df-4f25-b52b-6aa7ee018df4
Faulting package full name:
Faulting package-relative application ID:

I found a similar issue with PMDG:
QUOTE
*I got the solution , just go to this link and download the .dll *
https://es.dll-files.com/vcruntime140.dll.html
if the file who is missing name is vcruntime140_1.dll, just search it on the same web page , download the latest version( the first option you see while scrolling down) corresponding to your win version 64 or 32 bits , once the download is complete unzip it wherever you want just open C:\Windows\System32 and paste and replace the file it could be either VCRUNTIME140.DLL or vcruntime140_1.dll .
then try open OPS Center again .
Good luck…
unquote

In WIndows system32 rename before you go …

Thanks for your message. I tried that and it just made my MSFS very buggy.

I have since had a new CTD error show up within event viewer. Still no fix for this…

Faulting application name: FlightSimulator.exe, version: 1.8.3.0, time stamp: 0x5f5f47ed
Faulting module name: FlightSimulator.exe, version: 1.8.3.0, time stamp: 0x5f5f47ed
Exception code: 0xc000001d
Fault offset: 0x0000000001415edd
Faulting process id: 0x80
Faulting application start time: 0x01d6940d6b93ed9d
Faulting application path: D:\Custom Steam Library\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\Custom Steam Library\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 56895761-628f-44d7-9c6f-eefce8050965
Faulting package full name:
Faulting package-relative application ID:

Download and run memtest86 on your system:

https://support.microsoft.com/en-gb/help/2977003/the-latest-supported-visual-c-downloads
May be this info can sort out the issue on your end.

Yeah, I have reviewed that. In fact, I uninstalled every single one of these, restarted my PC and reinstalled them before making this post, twice.

It’s basically unenjoyable at this state right lol :\ So frustrated, I never had these problems with FSX or even X-Plane 11 so I am quite sure something else is going on with the game…

1 Like

After this new 1.9 Japan update the crashes are just worse lol. Now it’s a different error too…

Faulting application name: FlightSimulator.exe, version: 1.9.3.0, time stamp: 0x5f6cd7d4
Faulting module name: FlightSimulator.exe, version: 1.9.3.0, time stamp: 0x5f6cd7d4
Exception code: 0xc0000005
Fault offset: 0x00000000004ef07a
Faulting process id: 0x47b0
Faulting application start time: 0x01d6970701f8695a
Faulting application path: D:\Custom Steam Library\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: D:\Custom Steam Library\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: fc8b36c3-e68f-4518-89c8-a887f831967c
Faulting package full name:
Faulting package-relative application ID:

Is your Windows 10 Up to date?

Yeah it’s on 2004. This crash is no longer occuring in my last 3 flights. All crashes now seem to be when I try open the VFR map which seems to be widely now reported by many users.

I think this was certainly an issues due to the 1.8.3.0 patch but fixed itself once 1.9 was released (I hope).

I guess it just comes back to the fact the game is a bit glitchy and they are still yet to get rid of bugs. The crashes that occur when the VFR map is opened do not produce the VCRUNTIME error I had here so I think that proves enough for now.

:slightly_frowning_face:

So wait for the next update Oct 15th

Getting the same error every time. Frustating

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, timestamp: 0x5f6cce4b
Faulty module name: VCRUNTIME140.dll, version: 14.28.29231.0, timestamp: 0x5f4c66c9
Exception code: 0xc0000005
Fault deviation: 0x00000000000012de
Failed process ID: 0x508
Failed application start time: 0x01d69b41754005da
Faulting application path: C: \ Program Files \ WindowsApps \ Microsoft.FlightSimulator_1.9.3.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: 779655d3-bff1-4864-8d9f-f904e180b79c
Failed full package name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe
Failed package application ID: App

Getting the VCRUNTIME error when trying to load the game. I get the “Checking for updates” screen then it bombs out:

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f6cce4b
Faulting module name: VCRUNTIME140.dll, version: 14.28.29231.0, time stamp: 0x5f4c66c9
Exception code: 0xc0000005
Fault offset: 0x00000000000013b8
Faulting process ID: 0x6cc
Faulting application start time: 0x01d69cc0dae7761f
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.9.3.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: 957b335c-005c-4533-bde5-a1017cc7eebc
Faulting package full name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

IME this error seems to happen when changing views, like from external to cockpit or when switching from “normal” to rear view outside. I’ve also had it happen in a fairly sharp turn, and simply moving straight in fog and thunder between Courchevel and the next airstrip. Seems to be related to fast graphical changes mostly, but that last one simply points to heavy GPU usage after all. I’ve already downclocked my GPU, so these crashes shouldn’t be caused by the GPU as such.

1 Like

Tried every option I found here and on other sites and couldn’t get this to work. Uninstalled and reinstalled and all is good.

I get this error, too, however, it is always coupled with an unhandled .NET exception.

Error 10/13/2020 12:18:46 PM .NET Runtime 1026 None
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 00007FF8F1BF12DE

Error 10/13/2020 12:18:46 PM Application Error 1000 (100)
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f7c8cf2
Faulting module name: VCRUNTIME140.dll, version: 14.28.29231.0, time stamp: 0x5f4c66c9
Exception code: 0xc0000005
Fault offset: 0x00000000000012de
Faulting process id: 0x2900
Faulting application start time: 0x01d6a176cfc839f2
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.9.5.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: 9a845596-fe0a-4c3a-b1e9-8e9dc0ce4538
Faulting package full name: Microsoft.FlightSimulator_1.9.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App