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 
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
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:
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 
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”
and additional… some test-case with disabled XMP mode can also be helpfull.
I did a Memtest and got no errors, i also disabled the XMP Profile afterwards. My FPS are already limited to 20FPS via Nvidia control panel. I got German and US English as language packs now in windows.
I were in flight for about 2,5 hours and it crashed again.
20 fps V-sinc is bad, turn of v-sinc and adjust settings for a minimum of 24fps at busy airports.
20FPS is just fine, its very smooth even on busy airports. With Vsync off its stuttering and laggy while looking around with the camera. With Vsync 20FPS i can use 4K and Ultra Settings without any laggs
yep… v-sync is not bad and the fps you have to set just depends on your monitors fps-rate ( most have 60fps 4k monitors, then 20 does match ).
I assume, what we can see is, that the “new” issue ( after full re-install ) is a different one than before ( not longer vcruntime140.dll ). Can you agree that ?.. have you in new-installation different error-messages than the 00005 in log ( e.g. 800…3 ) or still vcruntim… ?
In general with the current infos we are back by “may be a issue with hardware” ( where we now lower the possibility a bit ) , " a random issue which let the game crash, e.g. network/usb/… " , or just a bug in-game.
Do you use the nvidias 497.09 driver version ?.. lots of user report issue with these version and that thay rollback to former version. And… also check that usb-power-save is disabled. It caused also trouble for some users.
Enjoy your CTDs as your cpu says that’s your lot for today.
i was using the version before 497.09 until yesterday, just updated after i saw there is a new driver available. Im in game now for several hours without a CTD yet, maybe its fixed even without doing anything, so weird.
IMO the 497.09 is mostly hitting those of us that have tuned the sim to the nth degree … How it’s resolved is going to be interesting.
Since this morning MSFS crashes after checking for updates every time I start it (tried about 10 times). I’ve never had this before. Until yesterday everything worked fine. I haven’t changed or installed anything. Windows is up to date and the community folder is empty. According to the Event Viewer it’s the following problem:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 0.0.0.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: VCRUNTIME140.dll, Version: 14.30.30704.0, Zeitstempel: 0x615a9215
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000001470
ID des fehlerhaften Prozesses: 0x486c
Startzeit der fehlerhaften Anwendung: 0x01d7eccd483346b3
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.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Berichtskennung: 9644fa6f-0144-450a-8808-55a6b070cf1a
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.21.13.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
Does anyone have an idea how I could solve this?
I’m not sure if this is relevant but before the problem started something weird happened. I loaded a flight plan from Simbrief and wanted to change the parking position. Strangely I could only select the takeoff runway; SIDS, STARS and approaches weren’t shown - it just said “automatic” or something like that. Never happened before. I then closed the sim to try again and that’s when the whole mess began.
Does the flight sim run well on anything without a glass cockpit?
in my case the sim runs well with and without glass cockpits 
Can you explain more detailed how your question relates to VCRUNTIME140.dll error message ?
I receive CTDs with the fault at VCRUNTIME140.dll also. But, only in planes with a glass cockpit, such as a G1000 system. Planes without, like the c150 run perfectly well.
Perhaps narrowing down the problem of how the G1000 system is triggering a VCRUNTIME140 fault, if that happens to be the case, may be worth looking into.
ah… I remember about an existing relation to the G1000 and searched for it… and it was within this topic 
May be not exact same, but possible helpfull.
CTD after 8h00 of flight !
Nom de l’application défaillante FlightSimulator.exe, version : 1.27.21.0, horodatage : 0x00000000
Nom du module défaillant : VCRUNTIME140.dll, version : 14.32.31332.0, horodatage : 0xefff39ad
Code d’exception : 0xc0000005
Décalage d’erreur : 0x00000000000015f9
ID du processus défaillant : 0x2a44
I7-4770K RAM 24Go RTX 2080Ti. directx 12