Since the last 2-3 patches all I get is CONSTANT CTDs with EVERY flight on my VANILLA sim. Seems that VCRUNTIME140.dll is the error. This is so frustrating as it was fine before previous patches. I am really at a lost and extremely upset. I feel like the release version was the best one to date. Asobo, if you read this PLEASE look into this as they is a huge thread on the FS forums where a lot of people are having the same issue. 

 

Faulting application name: FlightSimulator.exe, version: 1.12.13.0, time stamp: 0x5fda3fe4
Faulting module name: VCRUNTIME140.dll, version: 14.25.28508.3, time stamp: 0x5e155520
Exception code: 0xc0000005
Fault offset: 0x00000000000012de
Faulting process id: 0x4df8
Faulting application start time: 0x01d6df90befc5e4b
Faulting application path: D:\Program Files\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
Report Id: 2a570d87-6203-44a5-9d06-2671594f4849
Faulting package full name: 
Faulting package-relative application ID: 

You may want to do some research and read here https://forums.flightsimulator.com/t/vcruntime140-dll-error/282497/5

also I recommend to submit it  to Asobo

Do you have all the C++ redistributables?

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

With each new patch for those having this issue like me delete your rolling Cache then set it up again (choose a location on the same drive as your FS install).  Some areas you may have to fly over twice to get them marked in Rolling Cache.  Fewer spots will always have a problem.  The point is doing this will wipe out the issue in your most frequented routes.

Asobo needs to address this on a more permanent bases.

Edited December 31, 20205 yr by Dillon

6 minutes ago, sd_flyer said:

You may want to do some research and read here https://forums.flightsimulator.com/t/vcruntime140-dll-error/282497/5

also I recommend to submit it  to Asobo

Thank you and I already did do some research. Nothing solves it at this time. 

5 minutes ago, ryanbatcund said:

Do you have all the C++ redistributables?

https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

Yes, I even re-installed them.

I have windows digital store version and never had problem with that error. Perhaps steam community can shed some light on that?

Also at which point you get those CTD randomly or during particular operations?

A few fixes suggested changing the graphics settings for MSFS to high-performance:

https://forums.flightsimulator.com/t/vcruntime140-dll-error/282497/70

• Launch the Settings application. You can do this via the Start menu or by pressing Windows + I.
• Click on the System label after the home screen of Settings shows up.
• After the System interface opens, scroll down to the bottom of the Display tab and click on the Graphics Settings option.
• Once the Graphics Settings screen appears, click on the Browse button under the “Choose an app to set preference” drop-down menu.
• In the Open dialog that shows, navigate to the installation folder of MSFS, go to the game’s EXE file and select it, and then click on the Add button.
• Now, back at the Graphics Settings screen, select MSFS, then click on the Options button.
• Once the Graphics Specifications dialog shows up, click the radio button for High Performance, and then click Save.

Edited December 31, 20205 yr by DylanM

Hi @DylanM that is an old possibility, which has no effect as to what is happening since the last update. However, as it seems to be happening in different parts of the Globe, I came across this and it seems to have it's roots with booth Asobo and 3rd party modders for scenery and airports. Go figure!

https://forums.flightsimulator.com/t/scenery-creators-please-move-or-rename-your-modellib-bgl/307563

Martin

I had this CTD for the first time cimbing out from EIDW to EHAM. I was over England at the time.

I purchased from the MS Store. I was using the FBW A320. Latest flighjt was fine (over the US).

41 minutes ago, sd_flyer said:

I have windows digital store version and never had problem with that error. Perhaps steam community can shed some light on that?

Also at which point you get those CTD randomly or during particular operations?

It happens randomly with all aircrafts.

31 minutes ago, DylanM said:

A few fixes suggested changing the graphics settings for MSFS to high-performance:

https://forums.flightsimulator.com/t/vcruntime140-dll-error/282497/70

• Launch the Settings application. You can do this via the Start menu or by pressing Windows + I.
• Click on the System label after the home screen of Settings shows up.
• After the System interface opens, scroll down to the bottom of the Display tab and click on the Graphics Settings option.
• Once the Graphics Settings screen appears, click on the Browse button under the “Choose an app to set preference” drop-down menu.
• In the Open dialog that shows, navigate to the installation folder of MSFS, go to the game’s EXE file and select it, and then click on the Add button.
• Now, back at the Graphics Settings screen, select MSFS, then click on the Options button.
• Once the Graphics Specifications dialog shows up, click the radio button for High Performance, and then click Save.

Tried that, did not fix it. 

1 minute ago, Clem116 said:

It happens randomly with all aircrafts.

Tried that, did not fix it. 

Could it be your hardware. It could be GTX1080 is not up to task.

Also note I did had CTD often in alpha. So opted to replace my GTX1080 to RTX2080 Super. It helped with CTD back then

8 minutes ago, sd_flyer said:

Could it be your hardware. It could be GTX1080 is not up to task.

My setting are not even being pushed...My 1080TI is however at 99%.

This happend to me as well, after spending a lot of time unstalling 3 times fs and all other tools, what did it for me was to uninstall all versions of visual studio and reinstall only the 2017 and 2019 x64. Later i re installed the versions needed for other tools, have no ctds anymore ! Happy new year to the great members here on AVSIM from France ;-)

24 minutes ago, Clem116 said:

My setting are not even being pushed...My 1080TI is however at 99%.

I figure my issue was not cpu but rather GPU memory