@hobanagerik I was on an i7 7700k & RTX 2080 Super When I started getting CTD after World Update 3
Was it a total OS rebuild after the upgrade? Even if you did, if you redid what you did before it could still be a software issue.
Are the messages you see in the Event Viewer exactly the same code as you had before? If not, you may have an entirely different reason for them now.
Yeah I’ve reinstalled twice, Formatted ssd for a clean start 90% of the time the error is vcruntime140.dll and occasionally some other error but its mostly vcruntime140.dll
I didnt get what you meant by “Even if you did, if you redid what you did before it could still be a software issue.” ?
What I meant was if you are either installing something each time that is causing the problem, or perhaps not installing something you should, each time you rebuild, then you will get the same outcome.
I can’t think of much else off the top of my head.
Install English US language pack, for ATC voice support
Install the latest C++ 2015-2019 runtimes
You’ve probably already tried those.
Hello everyone,
I love this gorgeous simulator. It isso much fun to fly and see the world and it is my favorite pc program.
All the hardware is set-up and ready, e.g. yoke, throttle etc.
I create an IFR flight, set it up in the FMS, wait for passengers to board.
I take off over London (beautiful). I fly for hours. Never have been to the destination airport, so I begin my final descent, while scanning the horizon permanently to find the airfield. The cabin is ready for landing and I am perfectly on time. Finally the runway from EGXP comes into sight. What a relief, so now only a smooth landing is missing.
Suddenly, no sound, no motion. ME: NO,NO.NO,NO,F***…CTD.
Extended version
I have this simulator since launch, and I think I had a lot of patience. Never even bothered zendesk or the forum because of a CTD, but having it crash on me on final, just instantly destroys all the fun and good experience. This is not the first time this happend, but the bug that caused it last time was fixed with a hotfix, since it happend at every custom airport and scenery that used a certain file type. That fixed bug cost me several hours, since I tried to load my saved flight, but every time the simulator crashed just before landing. It has been long enough. I will saidly not touch the simulator again untill it is in a stable condition, and I hope the next sim update can achieve it.
Performance is currently not my problem. Everything is currently smooth (a few updates ago London was a stutter party on my machine but not even that was the case when I took of from EGLC). It is of cause only smooth, as long as I don’t drag any MSFS window onto my second monitor, which only took me 3/4 year to find out, that that caused stutters…
Crash data
For detailed spec info, see my profile.
GPU: 5700xt, newest driver (I always update the driver hoping it would improve the CTD situation without luck).
CPU: 5800x
RAM: 4*8gb 3600mhz
Windows 10, everything up to date.
I don’t have an empty comunity folder, but in order to prevent issues, I only have high quality, payware mods enabled, e.g. Orbx, Asobo CRJ, navigraph.
I am a programmer and therfore use my pc for all kind of heavy tasks, without issues.
No overclocking, except AMDs defaults.
Crash log:
On Wed 23/06/2021 21:53:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20210623-2153.dmp
This was probably caused by the following module: amdkmdag.sys (0xFFFFF8017A614B90)
Bugcheck code: 0x141 (0xFFFFCF816D2C5050, 0xFFFFF8017A614B90, 0x0, 0x31D4)
Error: VIDEO_ENGINE_TIMEOUT_DETECTED
file path: C:\WINDOWS\System32\DriverStore\FileRepository\u0368764.inf_amd64_e28d3b9d143c5eb9\B368707\amdkmdag.sys
product: [ATI Radeon Family](http://www.google.com/search?q=ATI Radeon Family)
company: [Advanced Micro Devices, Inc.](http://www.google.com/search?q=Advanced Micro Devices, Inc.)
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that one of the display engines failed to respond in timely fashion.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Thanks for reading if you did.
I have a lot of CTD’s also. Allmost all flights between 5-30 min in flight. Today I tried different settings and had a good and long flight (almost 2 hrs with the TBM from Faroer to Iceland) without a CTD, live weather, no multiplayer, no traffic.
The thing I did differently is that I switched OXR Tools to “off” (no preview, no render scale). The rest is more or less the same: 100% TAA in game high/ultra settings, AMD Chill max/min @ 30FPS, custom fan, minimum freq. 2000Mhz, resize BAR off, XMP on. My system is a 5800X, B550 MB, 6900XT, 32Gb CL16-3600.
It ran fine and stable. Maybe something to check out… No guarantees 
I feel your pain. Back when we had that MP bug, you may remember the ghost cockpit issues of last year, I quite often crashes on final. It was proximity to other people.
The timeout issue rings a bell. I’m sure someone mentioned editing a registry key to increase a timeout value. It may even be in this very thread.
1 Like
I was fine for about a week for no special reason.
Now, since yesterday, it’s back to MSFS normal… so many CTDs I can’t even complete the 2nd leg of the Iceland bush trip.
As usual, I check every crash dump. This week, it’s 100% of the time caused by the Path::Create and its null pointer in VCRUNTIME (memcpy).
This is getting REALLY annoying.
Agree completely. Just had another try after some weeks away, and then only because Nvidia sent a GPU upgrade.
Tried to take off from Courvechal, CTD on takeoff three times in a row. Didnt even register as a flight. Fourth time took off ok, couple of landing and crashes, then CTD on landing. Its just not worth mucking around with flight planning or really trying to get involved in flight simming. WAFTM.
Trying to get going with X Plane but its not nearly as intuitive and the graphics are awful.
So I am past getting REALLY annoyed, I have been so since December. If this was an ordinary product, the consumer affairs people would be ripping them a new one.
I too feel your pain, and your thoughtful remarks jogged my memory on something I had not noticed before. My post a little further on talks about 3 CTDs from Courvachel. I failed to mention that on each of them the ATC screen was open on my second monitor when I pressed fly. Thats never happened before that I can recall. On each occasion I closed it but it reappeared on the main screen. I then closed it again. On the fourth try I left it open on the second monitor and was able to get about 15 minutes of flight before CTD on landing. I am now (for some months) deeply suspicious of trying to do anything but simply pick an airport and press Fly. If I do that sometimes I get to fly for a while, then CTD
Only three months? Lucky you. I havnt had a decent flight since the US release in December and there are still people trying to tell us its not the sim
2 Likes
Zendesk have had my stuff for months, received my dump and other files, made multiple suggestions and achieved precisely nothing. So I agree, remain hopeful but learn to use X Plane
1 Like
Oh my, not again the “it must be your system” argument.
If this was the case, we wouldn’t have 4100+ posts in this 10-month old thread, nor would there be over a 1000 votes making this topic the 3rd most popular bug (probably #1 if you include all the CTD topics raised in parallel). If it were THAT simple, we would all have found a solution by now by trying the 34597 different workarounds that are out there (many of which are “official”).
Where there’s smoke, there’s got to be some fire around.
I’ll just make a reference to the last post of mine: Crash to desktop without error message - #4160 by Zeppos
Game works OK 100% of the time for some aircraft with GPU factory settings, crashes almost immediately for others, underclocking works very inconsistently between various aircraft and no other software/game/app on my PC has any of these issues (they all happily work with factory settings while MSFS doesn’t). So how does this make it an issue with MY system if it’s only MSFS that crashes (and not always)?
No one is saying it’s MSFS alone. It’s almost always MSFS along with some weird combination that causes it to crash, be it hardware clocking, random 3rd party addons, VCruntime libraries, paging memory etc, all of which affect MSFS alone but not other software.
Sometimes the fault is clearly with the 3rd party software (nevermind that MSFS should be more resilient) or it’s a known issue with a known and easy workaround. But not always. It’s as if MSFS can be vulnerable to a million different things and you just pray you never fall into the CTD pit because if it happens (and it has to plenty of people out of the blue), there’s no efficient way to debug it. You just try things in random and hope for the best.
2 Likes
So in other words the system MSFS is running on? No one is saying a persons system is broken, but there is something about that system that MSFS doesn’t like, and won’t run reliably.
So my point stands. There is something about a system that is causing the crashes. It may not for other software, but it does for MSFS. Mine was the same, and as I said I found out what was causing mine by not using two mods for a whole month without crashes, and later a workaround was found to allow me to use those mods reliably.
So it was my system causing the problem, with “system” being that combination of software/hardware you describe.
2 Likes
@hobanagerik I have yeah, Thanks anyway
2 Likes
my ctd never had any kind of log
But there are also plenty of people that don’t use any mods at all and still have loads of CTD’s (I’m one of them). Some have reinstalled windows, reinstalled MSFS, reinstalled their drivers (with DDU), etc (I did all that). The hardware is new too and tests without faults.
The problem is we don’t know where to look and we’ve come to the conclusion that it must be the sim because w’ve tried everything, nothing seems to solve it and everything else works fine. I know it could be lots of things. Drivers, MB BIOS, G2 software (or hardware), OpenXR, WMR, Windows 10, …
But I wish that someone would acknowledge the problem. Just a “we know about the problem, we are investigating, we are working on it, we don’t know yet what causes it, we’ve identified an issue, …” would be enough. My hope is the new DX12 code solves the problem. But it’s just hope. Let it not be delayed disappointment…
2 Likes
So your sim crashes, and you don’t see anything at all in the Application event log? That seems hard to believe.
Run this in Powershell:
Get-EventLog -LogName Application -Source “Application Error”
What do you see there?
Have you went to your event viewer and looked for the error under “Applications”? You should see the CTD there.
eaxactly this, but as you cna see, the people here dont wanna hear that.
fact is, most, not all, ctd´s are at the user end.
the whole windowsystem is very complicated.
1 Like