Lol, just had a good laugh. Decided to try playing the game again after a few week break. Disabled all the mods, updated the base game, flew from UIBB to UIII and the game crashed less than a mile before landing. I switched to outside view to take a screenshot of me flying over the city, the game started stuttering and boom, my desktop I see.
Before anyone says anything - no, it’s not my system. I’m playing with MSI 3090, 5950X and 32GB of 3600 RAM. The game worked just fine before the previous update (was it 5 or something?). I think I’m done with it. I’m tired of wasting hours of flying only to get f**ked a mile before landing. Just not worth my spare time anymore. Doesn’t look like Asobo are fixing anything, acknowledging the problem or even asking for logs (because there aren’t any client side logs to start with :D).
P.S.
I have graphics set to high/ultra, all ground, AI transports and all possible sliders to max.
This. From March (when they upgraded CTD fix status to “ASAP”) until now, they’ve done very little to fix anything at all. Essentially only a very few specific cases which have nothing to do with 99% of the CTDs reported in these forums.
So you ran that command I listed, and you have no FS related events in the Application event log? I have to ask again as you have not specifically stated this. You will only see logs in a single place, the Application event log.
If you aren’t seeing anything there, and I can’t see how you wouldn’t as its the only place, then perhaps you have disabled the Application log? I’ve never looked to see if that is even possible, short of stopping a service, and therefore all logging.
If you are looking for some text file somewhere then don’t bother looking, as it doesn’t exist. But it is a often requested feature.
I’m one of those people who experiences the vcruntime140.dll error while flying. It tends to happen spasmodically. It started for me around Christmas time and can plague me for a month or so then magically stop. At the moment I am enjoying flying having not seen a CTD for a week.
My pc is used exclusively for MSFS and everything else is on a second pc. There is never any change to my setup to cause the CTDs aside from behind the scenes Windows updates. In the past I have tried all the snakeoil fixes suggested on the forums however now I just put up with the problems when they occur knowing it will clear itself eventually. Nowadays I just leave AI and live traffic turned off in order to minimise the CTDs as back at the start that was the single issue that did seem to make a difference.
What I have noticed however is that if I am going to have a CTD it normally happens on the first flight of the day. Rarely (though not exclusively) have I seen myself boot back up and refly only to experience another CTD. It’s almost as if the CTD flushes something out of memory that has been left over during booting up my pc.
Whatever the reason, and I’m sure there is more than a single reason to account for the CTDs I find it very frustrating to see this problem still just as prevalent 6 months on without any real admission from Asobo as to it being recognised or indeed if there is anything being worked on. I never hear it being mentioned on Dev Q & As, instead we have piles of fanboi jizz over photrealistic POIs or the Northern Lights. I know this isn’t an issue that affects the entire community however I’m sure there is a hefty number of customers that don’t bother flying anymore because of it,
The command listed would bring up all event log entries of that type, not just those related to MSFS. It is extremely unlikely that your Application log is empty of errors that are unrelated to MSFS. The command I listed would show them all, regardless of the application that generated them.
If Outlook ever crashed on you, or a browser, that command would have listed them also.
Ok just tried this and after 3 months of CTD on every flight and trying every fix i could find on this forum. I just completed my first flight KTPA to KMCO
Now i know this is just one flight. But man did it feel good. and i will leave it at that
don’t want to jinx things. I will report back if things return to the crapper
Hello all,
I’ve got CTD happening on load, the window pops up black with the loading circle in the bottom right for just a second, and then it CTD’s with no error message.
Core i9 9900k, RTX 2080, 32gb RAM, Windows 10, all drivers and windows updates are current, etc. Here’s the eventlog:
Game used to work fine up until a month ago or so? I tried once, figured I needed to restart my PC, tried again today and was like “Wait what?” and now I see the rabbit hole that is the CTD community of this game.
Did you make sure you ran Empty Standby List while in the sim at the menu??
Because the first time i tried i ran Empty Standby List inside the cockpit and the sim crashed shortly after.
Rebooted my computer after crash just for the hell of it and tried running
Empty Standby List when i got to the main sim menu.
After running Empty Standby List while in the sim main menu, i then went into VR and setup my flight and after that all went well and i finished my first flight in 3 months
Welcome To The Club… The best i can tell you after 3 months of CTD and trying everything in these forums is somethings work for some and not for others. I just tried idoleo2001 idea and so far this has worked for me. Well one flight so far.
Now i may be wrong on this but another poster on another thread had said he found DirectX 12 code imbedded in some of the sims files. that very well may have been put there during the updates over the last few months
This would also explain all the IT RAN FINE posts prior to the last update. That you will find here. Also IT IS NOT YOUR SYSTEM no matter what people here tell you.
THE SIM IS BROKEN for many. And I HOPE AND I PRAY that the reason Asobo is so quite about all the CTD problems people are having is because they know that DirectX 12 will fix the CTD problem.
So far at this point it just may be a memory problem that affects people with higher performance systems. Again just a guess from reading the posts here and idoleo2001
post that cleans parts of your memory prior to flying.
If all else fails you… July 27th is just around the corner for DirectX 12 And i will tell you one thing if my sim CTD after that date… Well can anyone say Class Action lawsuit.
100%. It’s super frustrating knowing how much cash I’ve invested in the PC, the game, and the flight stick / controls only to be met with this virtual brick wall. I’ll keep an eye out for the DirectX 12 Update, thanks for the luck <3
“ucrtbase.dll”, I believe, is often related to not having the US English language pack installed.
But that is often linked with a different exception code to yours, “0xc0000409”.
It’s worth a shot all the same. The other suggestion was to clear the rolling cache.
If you wish to investigate further, enter those terms into the search at the top right, the little magnifying glass. It will lead you to loads of threads discussing these issues.
don’t believe all the negative answers you get ( in special from user which wanted de-install DircectX-12 from Windows )
Your error is 0xc0000005 at ucrtbase.dll ( not mix it up with the …00409 errornumber ).
With this you can do some searches within the forum.
I remember me at some possible reasons, eg. issue with windows audio service or audio drivers. Also a case about a installed mod. May be you find another solution…
Update: @hobanagerik I’ve seen your post after hiting send
)