exactly for these reason we try to find out first, whether your hardware is okay and whether well known hints/solutions will works.
The thread here was a bit specical, because the issue with “VCRUNTIME140.dll” comes normaly from the version of c++ libs… We currently not know why this is not the case…
But If we assume your system is fine, you find often such posts:
But is of course also mentioned within the big CTD thread.
In special if your MSFS runs long time okay and rare CTDs occurs, it can be some network stuff… can be, because of course hardware issues also possible. These game use 100% all of the time and a single weakpoint…
PS.: searching an issue is not an easy thing… and if users report an issue with only one sentence, you must understand that the reaction is mostly also not the nicest one
I have had problems with CTDs from the beginning, usually with the VCRUNTIME140.dll error, usually I get a CTD after 20 to 60-90 minutes of flight.
My system: Motherboard AMD X570 PRO4 AMD Ryzen 5 3600 6-Core Processor 3.59 GHz 16.0 GB RAM AMD Radeon RX5700 XT - 8 Gb Windows 10 Home version 20H2 Build 19042.685 Power supply Corsair RM750x 3 ACER screens 2560x1440 (VG271U, XV270U, CB271HU) 1 DDC display (from VRinsight CDU II) When I fly with FSX, I also use a 10 ”Android tablet connected to the PC via USB and SuperDIsplayals extra screen without any problems. Track IR 5
I have tried the suggestions for a fix for @willisxdc’s VCRUNTIME140.dll error from Dec 22, 2020.
Solution 1
In Bitdefender, I created an exception rule for the ransomware remediation for MSFS. however it did not tix the CTD’s, after about 90 minutes I got again a CTD with VCruintime140.dll error.
Solution 2
After that I also tried solution 2. I have set MSFS to High Performance in graphics mode.
This helped, I could finally fly without CTDs and have already made several flights, including one of about 6 hours.
However, I only use the 3 - 2560x1440 screens in AMD Eyefinity mode, where I use MSFS on the center screen and on half of both screens on the left and right side.
If I detach the G1000 clear glass cockpit windows and put them on the android tablet and the screen of the VRinsight CDUII, I do get CTDs with a ntdll.dll error, but also again with VCRUNTIME140.dll.
Conclusion
I can now finally fly without CTDs if I only use the 3 screens and do not try to put the G1000 glass cockpit windows on extra screens.
Friendly reminder to Asobo that I cannot play the game still, left with no update, no dev response.
I have tried several more fixes today with no luck, reseated ram, reinstalled gpu drivers again, used a single monitor instead of 2, tried using various graphical settings, still nothing.
Is it me or do these kind of issues only get worse as time goes on, I never remember anyone having problems like this in the 90’s.
Thanks MichaMMA for your advice…
The correct C++ libs were already installed
Unfortunately setting the virtual memory to min 4 and max 20 does not have the desired result. The VCRuntime140.dll CTDs in combination with the extra screens have not been remedied.
It was a “bit” annoying. But hey, hopefully there will be a solution for that or at least something which gives us more insight what could cause this issue.
I’ve been flying without issues for months, and I am sad I have to say that the past couple of days I’ve been having these crashes as well, most of the time after 10-30 minutes of flying.
No updates, no driver changes, no overclocks… basically no changes on the whole setup and the software. It just started crashing a couple of days ago with the same error most in here seem to be getting:
Seems like you have done most of things I would suggest.
I have been working a hunch on this error. I have not been able to get mine to CTD so don’t have a way to test my theory. If you would like to be a Guinea pig…
I’ve skimmed over that post earlier. I’m assuming you’re pointing at Solution 1 here, since I don’t have onboard graphics, and I would think that Solution 2 wouldn’t help me.
For solution 1; I don’t think it’s an Access violation / Exception Violation, since that isn’t mentioned in the event viewer anywhere? Or is that what the Exception code: 0xc0000005 is telling you.
I’m not really comfortable disabling Ransomware Protection in this day and age, but might give it a try tomorrow (it’s too late in the evening now) and make sure I have no other programs opened whatsoever (especially browsers). Might be an interesting experiment, but I’m not hopeful.
I’ve had the same thing happen over the last few days (72-96 hours?) Sometimes I fly for three hours without any issue. Other times I’ll get three crashes in an hour. Go figure.
Yesterday I only had one in over six-plus hours of “saddle time.”
No changes whatsoever to my system since the “spike” update.
You mentioned you have a B540 MB. I may be wrong depending on the version you have but I am pretty sure the 540s have onboard video. If you look at the ports on the back you will see at least 1 HDMI port and possibly even a Display Port and HDMI.
It is important that the onboard IS disabled.
ps: 0005 is an exception code
If I assume that both you and @MortThe2nd have in fact no changes to your system since your MSFS was stable, then the only variable here is network. Start by doing a router reboot first. Test. Still CTD then try turning off “LIVE” options. No live traffic/weather/players.
Might seem to be a long shot and shouldn’t throw an exception error but the network options have been causing CTDs for some users, although usually NOT VCRUNTIME errors.
