VCRUNTIME140.dll Error

Remember to install the vcdistrib files in the correct order as an older update can cause problems, usually due to an app install has installs these as a dependency.

he have done it already :wink:

@StratocasterBLN
Some hints about possible reasons for none-VR we gave already , e.g. summary

Thus may be check that points… in special drivers, parallel running apps and hardware stuff ( like heat ).

EDIT: I also seen your MSInfo…
A much more common error in your case is the generally 0x80000003. Check that you not hard limited your pagefile, this was often a reason… There are also lots of “ucrtbase.dll 0xc0000409”… thus check sound-drivers and anti-virus tool. Also wuauclt.exe crashed one time, which sounds not good.

I already reinstalled the Game 2 times, after that i reinstalled Windows + FS2020 another time. The Download of FS2020 takes forever. I have a 1GB connection but the dl speed in FS2020 is just about 60-100 Mbits/s.

chkdsk and scannow resolved in no errors to fix.

FS2020 is installed on the C: NVMe AppData Folder

@ MichaMMA
luckily i was able to fix that error already :slight_smile:

I deleted all vcdistrib and reinstalled it with the “app aio-runtimes_v2.5.0”

note, that VCLib version was not the only possible reason ( and also not the most common , so far I remember ( its a while :joy: ) )

which VCLib version is the possible reason? Which one should i reinstall?

I mean the vclib is not the only reason which can cause these error message… More common are the other points from the summary I linked. I also edited (“EDIT”) my post above some minutes ago.

I left the Page File on automatic. Well i guess i have to reinstall everything again :confused: Thanks for the help guys

This might be a good time to try Windows 11 … If you do then install it fresh from an iso and not the upgrade. If it helps their latest offering is very solid.

not sure about …

As mentioned… test to close applications which runnning in parallel , check that all drivers up2date ( dont forget the mainboard stuff and sound ) , try to disable to a test-case your anti-virus app, may be to a test-case with a manuall pagefile on minimum 8192 and maximum 20000 , also because you report that it happens after 1-2hours try to open your pc-case to check whether it’s over-heating issue, dont disconnect usb-devices while playing,… may be I forgot some points… ( assume sfc , dism checks you already done )

thats of course also true… but seems its PC is not ready with current settings ( TPM )

Very easy to turn on in bios security settings although it may take two visits as TPM options may not be visible until after a restart

1 Like

Hey Guys,

after hours of reinstalling everything im on Windows 11 now. It still crashes…

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000001b1a80a
ID des fehlerhaften Prozesses: 0x1714
Startzeit der fehlerhaften Anwendung: 0x01d7e7b03b2ecf87
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 4dca49de-fb3e-4bef-8c60-fc68427070f1
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

1 Like

Well that went well! :roll_eyes: I guess the mods won’t like Italian either.

DensestSnail693 said:
Maybe a missing US English language Pack?

StratocasterBLN said:
Hm. You mean a missing language pack for windows? I just set the FS2020 to english because i was setting up my hotos while watching a a youtube video about the config in english so the menu matched.
Before i switched to english FS2020 were already crashing tho

You need to install the American English package because Azure and ATC use it. Even us British must do this … Unless this has recently changed (and it may well have done since Xbox).

I installed the American English language pack, started the game, prepared the A320 for like 30min, was just about to taxi to the runway and it crashed again… I hate my life :confused:

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000001bd5223
ID des fehlerhaften Prozesses: 0x1bc4
Startzeit der fehlerhaften Anwendung: 0x01d7e7d1a09bc305
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: d0372a5d-43f5-4f1a-b0d2-ad7763d95ca8
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Fehlerbucket 1877119930536409851, Typ 5
Ereignisname: MoAppCrash
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 0.0.0.0
P4: 00000000
P5: FlightSimulator.exe
P6: 0.0.0.0
P7: 00000000
P8: c0000005
P9: 0000000001bd5223
P10:

Angefügte Dateien:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2494b3c0-d7ae-47a3-9c12-67a967c28ee9.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1eac85bd-f076-4235-965b-e3c827630a57.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f91d841a-72a9-4a45-9e2a-da56567b5e45.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.037ee96a-db20-41b2-8618-5e8ae84ad798.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a1f38ec7-8970-46b0-98fc-4b99f6b0e7c7.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_9168431432dc7fda14c7e210f2facdac2c75211_0a81039e_bc2419f0-e1b1-4b58-ac17-b326ae2ade8b

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: d0372a5d-43f5-4f1a-b0d2-ad7763d95ca8
Berichtstatus: 268435456
Bucket mit Hash: 76a62dee2949c2b2ea0cdea1a46dbafb
CAB-Datei-Guid: 0

If I’m right, that error code references an access violation. I suspect there’s an issue with your RAM or disk.

Hmm, i really doubt that cuz the hardware is brand new. just build that pc like 1 month ago.

It just crashed again after like 3 hours of flight. I almost thought that it got fixed somehow :confused:

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000001bb9904
ID des fehlerhaften Prozesses: 0x48bc
Startzeit der fehlerhaften Anwendung: 0x01d7e815c62229ee
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 2c018e97-41d5-4120-ad5e-b98533aa9471
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

Fehlerbucket 2099218939351570577, Typ 5
Ereignisname: MoAppCrash
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 0.0.0.0
P4: 00000000
P5: FlightSimulator.exe
P6: 0.0.0.0
P7: 00000000
P8: c0000005
P9: 0000000001bb9904
P10:

Angefügte Dateien:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d4735ba0-67a1-410d-b1b5-502388e3dbf3.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2fd72b93-fdec-4f13-9ae3-c91a3557b994.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8dac1a0e-8fb6-429f-b249-d7327c158401.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f48cf633-d2ba-49ac-ab9b-156cf28ca9b8.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.da7eccdb-f8cb-4038-8bf7-519eb41fdf96.tmp.txt

Diese Dateien befinden sich möglicherweise hier:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_cebfeb2adfe991231fbbbe531ad8e7bb5b55a7_0a81039e_9a086c92-75d0-4035-a64a-9e6dee7d165c

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 2c018e97-41d5-4120-ad5e-b98533aa9471
Berichtstatus: 268435456
Bucket mit Hash: 7b77c0e91bceb707dd21ec80d1d29891
CAB-Datei-Guid: 0

As per the previous comment, I would suggest running a memtest on your machine. New RAM can also be bad so best check it now and get it swapped out if faulty.

1 Like

note: the error message in case of missing installed language pack US is normaly a different one as “00005”. But just to be sure:
image

we have not less cases in forum where users was exactly in this situation… From loose cables, wrong settings, not optimal cooling, till defect new hardware… we have seen all :slight_smile: Of course , we all know that bugs are allways possible.

EDIT: you can also do test-cases with a a limit of max fps… if its help, its may be somewhat with “heat”