maybe you dont understant that the problem start with the new beta relasese for the SU10 that in some way affecting SU9 user
The new beta build on Friday was released after players started seeing the ntdll.dll crash. The timing is coincidental, and we have no reason to believe they are related.
9 Likes
The exception code 0xc0000374 is related to heap corruption. The referenced ntdll.dll doesnât mean that DLL is corrupted, but rather itâs the DLL that threw the exception code. If you further search, you will find Itâs quite common to have this throwing the exception code for heap corruption.
This does not mean everyoneâs ntdll.dll is magically corrupted.
2 Likes
That I can confirm: Massive CTD started before I updated WU6 on Friday evening.
There have not been any updates to SU9, just a small update to an earlier WU and problems occurred both before and after that ud occurred. The same goes for Windows updates too. To be honest if people read the thread from beginning to end they would have a better understanding of what is happening.
2 Likes
Does anyone know what the ucrtbase.dll ctd could be? Ive had 2 ctds with this now i did think it would be the ntdll one causing my ctds but its notâŚ
Quick google search says that it is software component of microsoft visual c++
Just about to finish work no chance this will be fixed by the time I get home? 
Seriously though its unplayable atm with the ctd lingering over you feel like your flying on egg shells the whole flight.
2 Likes
Thanks ill see what i can do about it
Have you checked if the ucrtbase.dll crash was the exact same time your sim crashed? I also had a couple of ucrtbase.dll crashes in my event viewer but these were not at the time I had my CTDs. At the time my sim crashed I had no event in the log.
Yes, I would discard beta client release and the WU updating as well. In particular the WU only changed the POIs pack and a couple of airports but the issue is reproduced worldwide, even when flying on 100% generic areas and while being both airborne or on ground. I doubt it´s dealing with any game files local to players (meaning the official content, scenery or aircraft) because when they are local they don´t need any update from servers and they just load directly on the client.
As issue is also reproduced with all online services disabled (traffic, weather, etc) and also without addons the only things which are left that everyone still needs when flying over generic areas are the Blackshark buildings and the terrain mesh. That, together with Bing textures, failed to load during the weekend in different areas of the world and for different users which were also on both SU9 and beta (including me). I think there is where we could get some extra info. Post #295 shows the effect. I can confirm to have seen the same (flat terrain, no buildings, no textures and only the parked cars) also on beta when I started a flight at Hawaii.
Cheers
Right now, just crashed to desktop with SU10 beta5. Yesterday I had 5 out of 6 tried flights. Online data on, but no MP,PG, LT. only Live Weather and Bing Maps.
âTheyâre investigatingâŚâ
2 Likes
I did check and it showed as crashing a few minutes prior to the sim ctd⌠ive had a google around for possible fixes which im going to try later on
Hi, in my case (i7, Nvidia gtx1060) the annoying "ctd"s of my last few days immediately disappeared when I stopped my antivirus software (Norton). I also gained a few frames per second.
All as an aside, could it be plane you are flying? So, when posting CTD, tell us what plane maybe itâs that, but the âserverâ could be it too. I am in USA, so far, no CTDâs period, flying PMDG-737BDSF model. Testing my working checklist and learning where stuff is located. Now come to find, my camera controls are causing me grief. Asobo, we need a xxxjdlj âmanualâ on all the settings, and how to configure them.
but what if the same servers and/or the same network infrastructure that are serving up the updates for beta 10 and the WU updates are shared by the infrastructure that is being used by simmers on SU9 and SU10?
If that is the case, then MSFS clients might be experiencing greater delays/error rates and that could be a factor in the CTD.
As I said, it shouldnât because the client software should be able to handle such a situation.
By the way, i have followed the thread, but i would be more than happy for you to point out exactly what i might be misunderstanding.
Another CTD about 10 minutes ago, once again flying up the coast from Brisbane in Australia.
Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.22000.832, time stamp: 0x3907dfbc
Exception code: 0xc0000374
Fault offset: 0x000000000010c9a9
Faulting process id: 0x4908
Faulting application start time: 0x01d8b6380d90533a
Faulting application path: G:\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: 8f074a1f-3482-4b89-9894-08a076fab32a
Faulting package full name:
Faulting package-relative application ID:
These crashes started to occur before updates or beta updates occurred. This has been confirmed by the MS team.
When looking for clues to faults the most important thing is being methodical. When you eliminate a cause which in this case is updates because the CTDs were occurring before they were implemented, its a bit pointless to continue looking at them as a possible cause.
1 Like
Resume,
The CTDâs have nothing to do with mods, SU10 betaâs and/or utility programs because the CTDâs where also seen by users of SU9 in Vanilla state. It start happening a few days ago by a big group of users. So not all users where effected by this event.
Asobo is trying to locate the problem, but still has not find it.
All tests flights of the Asobe crew where without CTDâs.
Reactions on forum posts regarding this CTD problem can be found at, Msfs community team - Microsoft Flight Simulator Forums
2 Likes