I reinstalled all VC++ packages for x64 and x86 from 2010 to 2019.
Reinstalled FS and the add ons… actually to get rid off the stuttering.
Getting runtime error CTDs now after a few minutes of flight.
I changed one thing: I reenabled my ram xmp profile as it was off somehow…I saw somewhere that xmp can produce runtime errors
In some cases perhaps, but if the solution were as simple as that we’d all be free of those CTD issues now. Also it would be understandable if XMP was causing crashes across a number of applications, but what happens if it’s only MSFS that’s allegedly affected? Whose fault is it? XMP’s or MSFS’s? Why is MSFS notorious when it comes to even slight amounts of overclocking where everything else works OK?
Also XMP is essentially controlled factory overclocking: we’re talking about RAM modules that have been manufactured specifically to be pushed to very specific timings using predefined motherboard settings and operating within predetermined margins. We’re not talking about user overclocking in the wild. Even so there are many people (myself included) who saw no improvement after disabling XMP, or others who replaced their memory modules and still had no luck with CTDs.
I can only assume vcruntime140 is a super-generic error that can happen because of a ton of root causes (due to MSFS’s often inherent instability in some systems). I’ve stopped looking at event viewer vcruntime logs for some time now, as the GPU timeout driver error always happens before the vcruntime one. So the latter doesn’t really matter until proven otherwise.
yep… overclocking… CTD Help, Possibly - XMP II - Overclock - #8 by MichaMMA
we already mentioned the most probaly reasons we know… ( e.g. )
Again if it was THAT simple, most of us would have solved our issues by now. I’ve tried with XMP off, 1 and 2. The results were the same. Meanwhile those exact RAM modules were running happily at XMP2 between November and March with zero CTDs. It all started to go bad when I installed my 6800XT and MSFS released its March update.
The other probable reasons have helped several users debug their issues and even find a solution, but not everyone (I’d argue most people with chronic CTDs continue to have CTDs even after testing all said reasons).
Personally I’m hoping that DX12 will do the trick because SU4 certainly didn’t.
what I have in mind is, that XMP mode usually not caused the vcrun…dll issue. Would then more another unspecific …0005 error. As the old posts mention, it is often a GPU thing ( these 6800xt we had since a long time under suspection ). It was interessting to read, that a user reported also a relation to the xmp mode. On other side it is realy interessting that MSFS bring issues with xmp mode on top.
I fear DX12 will not fix these issue, but let us hope for the affected users.
I noticed, that my TM A320 Stick slider overreacts in the lowest part since recently… I wonder if this issue causes CTDs… the mapping of the stick is somehow gone
if the stick also disconnect then there is also a CTP possible… what I have in mind is, that MSFS is bit sensible in this point. And I remember me at a post about the TM A320 and a CTD… may be I find it…
But not sure about the vcr…dll message in this case.
Upd: I have such disconnects sometime/rare with my Hotas in case I move very quick on my chair or stand up very fast. I assume it’s because the electricity which may be cause issues with usb. I never seen a issue with MSFS, but DCS tell me in case it happens ( and/or get the disconnect windows sound ).
( device xxx removed / disconnected )
I had runtime crashes.
Reinstalled all C++ from 2010 to 2019 for both x86 and x64.
Set my 3900x in ryzen Master to default.
Removed OC on my card… but then FS started to crash due to nvlddmkm (Nvidia driver).
DDU everything and reinstalled 466.77 driver. This time without PhysiX, only driver and HD audio driver. All works fine now… no crashes so far…
I’ll test the overclock again.
Will install…even if I doubt it helps 
I want to like this product, but today, I’ve had 7 attempts for short journeys and actually finished only once. All the other attempts resulted in a CTD during the gameplay, and a VCRUNTIME140.dll error in the event viewer. I’ve reinstalled C++, drivers and no overclocking whatsover.
I’ve had the sim for a couple of months now and the longest I’ve been able to go without a CTD has been 4 marvellous days without any sort of CTD. And yes, I’ve done tested just about every “solution” on this and other forum but to no avail. I’ve opened a ticket on Zendesk, but they barely helped.
The sim is just so broken.
It is so frustrating that this wonderful simulator is totally unplayable at the moment.
Got another crash today. The first time in a few hours of flying. Strangely, it didn’t generate an error in Event Viewer - instead I got the standard driver crash message from Radeon, but Windows reported in my task bar that the application has been blocked from accessing the graphics hardware - but this was apparently due to Twitch.
Make of that whatever you will, plus when I’m not even getting an Event Viewer error…
Okay, after months of CTDs, mostly from the Main Menu, and having tried every possible solution, I finally solved the problem.
Two days ago, completely at wits end, I wiped my HD, reinstalled Windows, and reinstalled MSFS. Nice and clean. But…game CTD’d within 2 minutes of sitting on Main Menu. Argh.
On a complete whim, I opened my PC case, disconnected Power Supply, unseated video card and put it back in. Nothing appeared problematic.
Booted back up, launched game. No more CTD, no more VCruntime nonsense. Its been running fine for close to 24-hours straight.
My suspicion is this: I used to use MSI Afterburner to adjust fan speeds. Methinks those fan settings stayed resident on the card and were only removed after unseating the card.
Now I have loud-■■■ fans but a working, stable game.
Probably not the solution for most of you, but it will be for some.
I’ve been having several VCRUNTIME CTDs recently. When I ran the Reliability Report, it shows that Windows found a hardware problem with my video card. It looks like Windows deliberately and without asking me killed MSFS generating the VCRUNTIME140.dll CTD. I’ve replaced my video card once before which took about two weeks under warranty. There needs to be a better way of reporting problems to users. I could have spent a lot of time trying to fix the VCRUNTIME CTD when the root cause is a hardware problem and how Windows tries to fix things.
I very much doubt your video card has suddenly gone bad. Do you have issues with any other software? If the answer is “no” then you can likely point to MSFS as the root cause of the reported issue.
Occam’s Razor.
Same issue here for several months. 22 games + 2 other simulators and no crashes. This one crashes with this error all the time. In fact, sometimes it BSOD or hard crashes the system without a BSOD. Nothing in the community folder and all drivers updated with no overclock.
Do you know what really ■■■■■■ me off about this is that these days the CTDs always seem to happen on the first flight of the day? Usually during cruise. It makes me feel, you know what, ■■■■ it, I can’t be bothered going through all that again especially if it happens again, I’m going to do something else today. Microsoft were pretty smart not making this a subscription service.
I’ll add a little something into the mix.
I bought a new PC to run MSFS and don’t use it for anything else. My configuration was decided upon after watching a lot of the guys on YouTube with pre-approved beta access.
ASUS ROG STRIX B459-F Motherboard
AMD Ryzen 5 3600XT CPU
Radeon RX5700XT GPU
32gb RAM
No overclocking and the sim is installed on a SSD.
Initially, I had no issues then around Christmas I began to experience the occasional CTD. After skimming through Reddit and these forums I turned off AI traffic and everything returned to normal.
Fast forward a further couple of months and the CTDs began to reappear. It’s at this point I, along with many others, began to come up with their own pet theories and developed killer fixes which worked for a week or so then the CTDs returned.
My version of the CTD always seemed to revolve around the VCRUNTIME140.dll error and occurs sometime after the first 30-60 minutes of flight. I have tried updating the C++ drivers, removing everything from the Community folder and even increasing the virtual memory swapfile
The other thing I have noticed recently is that a CTD usually occurs on the first flight of the day if it’s going to happen. Because this pc is only used for MSFS it is the first application to be used after boot up and I’ll have given it a good hour in order to allow it to go through any background processes. The fact that once it’s crashed and subsequent flights can be more likely to be successful I began to wonder if there was something going on with the operating system that gets flushed out by the CTD.
Here is a screen grab of my pc’s Reliability History
and details of the latest crash:
Do you think there is anything in my idea that the initial CTD flushes some inconsistency out of my setup to allow future flights to proceed successfully? It seems odd that recently the first flight crashes maybe 90+% of the time whereas subsequent flights will only CTD <10% of the time. Whatever the reason it remains intensely irritating and dissuades me from attempting any long distance flights until this is sorted.
It won’t change anything as the cause of the CTD is not in VCRUNTIME itself but rather triggered by the caller of “memcpy” within it passing a null pointer.
