Agree. A lot of persons still think turning fully OFF the PC, wait a little, and turn it ON, is better to clear all, than doing a Windows->Restart. We have this philosophy from our electronic devices
But it’s wrong with Windows. With Fast Boot ON (ON by default), the OS save part of the memory and devices states on the HDD before shutdown to speed up next turning ON, even if it’s days after.
So better to Windows->Restart, or turn OFF the Fast Boot.
I say that in case some may need to be educated around, always useful to know IMHO
After a week or so, if there are still numerous CTD reports here, I propose that since the CTD’s (I used to have) are marked with a “report sent” indication, that the MSFS team make a way to publicize these CTD’s. How many CTD’s - How different many users with CTD’s; updated like the weekly bug/wish list’s. Perhaps even a real time feed across the top of the official site and/or the official forum would be possible??
There is nothing like shedding light on a problem to hasten the solution.
If its not that big a problem, then show us its not that big of a problem.
That would be a good idea to fix CTDs… The Garmin G1000 mod was creating CTDs every time I was trying to use the stock BeechBaron. I was hoping that today’s update would fix the problem
Unfortunately it did not so I removed the mod Garmin NXI from the content manager and no more CTDs when using Baron or any other plane which has G1000
Today I had three CTD events in a row. That’s a rare occurrence.
For grins I decided to log out and log back on. The apron - full of aircraft prior to that - was nearly empty. Ground personnel were nowhere to be seen. I took that as empirical evidence that something had changed on the server side.
It’s been smooth sailing… er… flying all afternoon.
EDIT: Just landed at KPRB. Empty. 100% empty. Not a single aircraft on the apron. No ground personnel. Nothing. That’s a first…
I have it too, and I have no idea what you guys are talking about as i am not an IT savvy person
Can’t get past the loading stage till Slide 4 “Take the pilots seat”…and then CTD…100% everytime since Update 5. Have no idea what happened…something like the Titanic!!!
Turns out there is a conflict between MSFS and Capture One. Who would have thought to test that!?
If you’re a Capture One user, please read this thread. TLDR - there is a DLL that MSFS appears to be loading and causing CLR.dll and other errors. Who knows what other software could also be causing similar errors.
If I wanted for example, start at the Reagan airport in Washington DC it always crashed at the loading screen with those .dll files loaded. Without them I dont have an CTD with the 0xc0000005 error code in combination with either the ntdll.dll, clr.dll or ucrtbase.dll anymore.
So its the reason why MSFS crashed all the time since WU5 for me. Other programms could also conflict with the MSFS because it loads up .dll files that are made for other programms.