Hello,
I have tried to read other topics and cant seem to understand what anybody is talking about. Just got off a PVG-FRA flight 12.5hrs in and it decides to bring me to my desktop as im setting up my descent. I get the error or VCRuntime140.dll. I have tried to reinstall microsoft C++ and I am 99% that isnt the issue or I didnt do it right because the installer dosent seem to be changing anything.
Any other suggestions?
Thanks
I’ve started getting this over the last couple of days. I’ve also tried reinstalling Microsoft C++ but that hasn’t worked…
allways at same geo-location ?
Interestingly had this happen to me for the first and it’s over the exact same point each time.
What point is it so we can all test?
therefore my question… we have a topic about.
Please mention in that case allways the area, location where it happens, so that users can compare 
It’s at/around waypoint LAMSI - 48°39’12.0"N 013°34’60.0"E
Flight from EGKK to LTBS - Up to waypoint TENLO - 49°31’34.0"N 011°2’40.0"E all OK, no issues. Past that towards LAMSI (above), it does the CTD.
I’m loading up again past that point at SASAL 47°17’5.4"N 016°28’27.5"E to see what happens
Here are the error logs previously:
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: VCRUNTIME140.dll, version: 14.32.31326.0, time stamp: 0x49b85383
Exception code: 0xc0000005
Fault offset: 0x000000000000162e
Faulting process ID: 0x0x789C
Faulting application start time: 0x0x1D912DDE5FE6D90
Faulting application path: G:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report ID: f025e7ca-0b75-42ab-a996-3d3dec30968b
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: VCRUNTIME140.dll, version: 14.32.31326.0, time stamp: 0x49b85383
Exception code: 0xc0000005
Fault offset: 0x00000000000015f9
Faulting process ID: 0x0x1350
Faulting application start time: 0x0x1D912CC67D6D83B
Faulting application path: G:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report ID: 2c8f0910-20ec-449c-940c-23dad684e5ac
Faulting package full name:
Faulting package-relative application ID:
I’m currently back at cruise past the point mentioned above (photo from Volanta attached for better reference)
-Red = Crash location
-Blue = Depature points
-Yellow = Current
Hope this helps.
Will report any changes.
may be…
That looks like a Microsoft Visual C++ error.
Interesting that it seems to be around LOWL for a few people. It’s within the same proximity as the above issue.
In addition to this if I don’t pass this small area I don’t have an issue.
I’ve just installed it again. I don’t understand why now though after doing this flight only a few weeks agoh no issue.
Mine also seems to been around vienna. That is at least where I crashed last. I recently had a crash somewhere outside texas but I didnt check the log too see if it was related.
Unfortunatley I am retrying my Long haul from ZSPD-EDDF, however this time I am flying north of Vienna. If I get a crash I will report it.
Edit: I decided to test it on a shorter flight so I rerouted
and you’re sure you installed the latest vcredist from here: Latest supported Visual C++ Redistributable downloads | Microsoft Learn
Because I got rid of these CTDs with a vcruntime140.dll Error in the logs with the latest vcredist x86 and x64 version. Uninstalled it completely and reinstalled the latest version. For me the CTDs occurred mainly when spawning into EIDW. Not sure if related but it sounds similar.
