2 small flights with the default C152 over Barcelona and Lisbon and it crashed about 20min after starting the flight no 3rd Party addons. One of the crashes caused by ucrtbase.dll? That’s new for me. Live weather and Multiplayer etc off
Been flying bush trips today for a few hours with no CTDs during the flight, then I switch to the 737 and I got to CTDs without even getting of the ground. I guess the biggest difference there is that the bush trips use preset weather/time and no AI traffic, so might these things causing the CTDs? All this in the SU10 beta, but had the same CTD issues over the last few days with the SU9 live version.
First crash without ntdll.dll:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.27.16.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.27.16.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000002273b73
ID des fehlerhaften Prozesses: 0x4be8
Startzeit der fehlerhaften Anwendung: 0x01d8b583db5b39a7
Pfad der fehlerhaften Anwendung: N:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pfad des fehlerhaften Moduls: N:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Berichtskennung: fc32cf9a-2dda-417c-85ca-dde15d3167c6
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Second crash was pointing to the ntdll.dll (actually had a disconnect from server message before this one. When it came back, boom, CTD):
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.27.16.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.1806, Zeitstempel: 0x1000a5b9
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000ff609
ID des fehlerhaften Prozesses: 0x5010
Startzeit der fehlerhaften Anwendung: 0x01d8b589856f540f
Pfad der fehlerhaften Anwendung: N:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: 45ffb323-2ffb-462c-a557-c32acc928378
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
It’s not related to NVidia drivers. I have CTDs on different versions these last 2 days.
1 Like
Definitely no, same problem with driver that are a few months old.
It has to be server side issues. Maybe with live weather or AI, I use AIG traffic, but maybe the Live services are sending some bad data to the sim and it just hangs it. I really hope this is solved soon.
Photogrammetry, Live Weather and Real Traffic disabled doesn’t help either. A streamer just had PG and Live Weather disabled and CTDed twice, I have real traffic disabled the whole time and had the CTD.
What remains is basically just Bing data (Mesh/Imagery/Autogen) and XBox Game Services I guess.
Yes I also have this a few times that I have to end MSFS with the task manager
1 Like
Same here!! 4 Flights today and 4 CTD with ntd.dll.
I have not had a CTD in the last few months. I could not complete a single flight today.
Live Weather was on.
In my case my exe.xml was faulty.
Fiddled around with encoding (but forgot about it)
Changed the exe.xml now and everything is fine.
Haven’t been able to complete a flight since around the 18th August. CTD anywhere from 20 minutes to 1 hour into the flight. Haven’t had nay start up issues or before 20 minutes. Reasons are the MSFS app crashing out or the most common crash out caused by ntdll.dll. Must have happened around 8 times now. Coincidentally it started around the time my PC ran updates.
Even though this topic is reserved to ntdll.dll faults, just a friendly reminder people also referenced ucrtbase.dll and VCruntime140.dll as faulting modules. I get that ntdll.dll seems to be faulty module for the majority of the CTDs, so the fact that there are other faulting modules seems to be interesting. The ntdll.dll is just a Windows kernel DLL - but the others are related to the Visual C++ runtimes.
1 Like
Same issue today, 2 random ctd, but a 3th attempt was succesful (eham-lszh). I disabled fsuipc on the last flight, probably not the cause, but just mention the difference
I wasn’t aware. I apologize. Will refrain from doing so in the future!
4 Likes
The cause seems to be more complex when there are multiple modules in the logs (like ntdll.dll, ucrtbase.dll and VCruntime140.dll).
But even 2 times I had reported FlightSimulator.exe, version: 1.26.5.0, timestamp: 0x00000000 as the faulty module.
Strange!
Crashing with the ntdll.dll is like a canary in a coal mine. Something is wrong, but not necessarily related to the actual DLL. Exception code 0xc0000374 is heap corruption, and I would imagine Asobo would start from there.
There’s a lot of posts right now and theories, but there are clues in the error reports hinting at heap corruption.
4 Likes
Could be a fluke or a solution. Set the weather to live then using the slider move it back or forward 1 hour. I seem to be having luck with that!! It then changes to Preset I know it is then not Live Live but its an hour, you could try less maybe 10 mins?
But it seems to be ok thus far
1 Like
That’s what I was trying to say earlier. Don’t see how we can limit the thread to only look at ntdll when these other errors are also clues (at least to someone that actually knows how this stuff works) to what’s going on. It’s got to be part of the same issue - including the memory faults too. Anyway I won’t say more about it at risk of getting into trouble again.
3 Likes
I’ve had a few CTD’s (3 out of 8 flights between Fri-Today) coincidentally after buying and using the new Beechcraft V35, but that is all I’ve been flying for last day or so.
Tonight I switched to 737-700 which has always been stable, 1 hr into flight CTD.
Same error code as stated in title thread. I’ve not added much other than the V35 recently, and everything has been fairly crash free for me up until this weekend.
Before the CTD, the sound stuttered/stopped/continued, then the 2nd time sound went, the sim crashed.
(SU9, Windows 11, NVidia drivers 516.94)
Log-
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: 0xc0000005
Fault offset: 0x000000000002bc9c
Faulting process id: 0x6a00
Faulting application start time: 0x01d8b5842e195f89
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: a321a9f1-6130-4522-a382-5d91f1cd06b7
Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
I had two crashes. One ntdll.dll and the second one 0xc0000005 but I’ve never had any crash before in two years. So the crashes are multiple, not only caused by ntdll.dll
1 Like
here my report from last crash today
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.26.5.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.22000.832, Zeitstempel: 0x3907dfbc
Ausnahmecode: 0xc0000374
Fehleroffset: 0x000000000010c9a9
ID des fehlerhaften Prozesses: 0x23d4
Startzeit der fehlerhaften Anwendung: 0x01d8b561c2a32f32
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: 71705e2d-a593-49f2-b6dd-79d5cc45a3bc
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
Fehlerbucket 2162368263839962399, Typ 5