Constant CTD every flight now (ntdll.dll)

[Majjistral]

Hi. Thanks. But what of this kind of CTD? This accounted for 2 of my 5 CTDs today (the other 3 being ntdll):

FlightSimulator.exe
1.27.16.0
00000000
FlightSimulator.exe
1.27.16.0
00000000
80000003
0000000001c54f52
1d00
01d8b53d2d67b985
C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
93bd4aef-78ec-4a63-bc0a-7becc083b146

FlightSimulator.exe
1.27.16.0
00000000
FlightSimulator.exe
1.27.16.0
00000000
c0000005
00000000008dbfb0
3568
01d8b56cb67a7b69
C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
e3d1fdce-f51a-4345-bc32-a5cbee21075c

[SeedyL3205]

@Ithendyr

Thanks, happy to see a CM here.

CMs (both myself and @Jummivana) have been very active in this thread since yesterday.

[SJB1325]

Just had a ntdll error about 10mins after take off in the Fenix from Edinburgh → London Heathrow.

Error log:

Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.19041.1806, time stamp: 0x1000a5b9
Exception code: 0xc0000374
Fault offset: 0x00000000000ff609
Faulting process ID: 0x7c58
Faulting application start time: 0x01d8b57857d9aa23
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report ID: 3ab01925-4b1c-4ce9-a635-2233deb81d4b
Faulting package full name:
Faulting package-relative application ID:

Latest Nvidia Drivers: 516.94
32GB Ram
AMD 5950x
Nvidia Founders 3080ti

Online services: ON
Live Weather: YES
Live Traffic: NO
Sim Update: 9 (Current Stable)
Windows 10

[ThePLAGUEisON]

I got two CTD error messages in the event viewer on the ntdll.dll initially on the 20th August:

First being:

Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.19041.1806, time stamp: 0x1000a5b9
Exception code: 0xc0000005
Fault offset: 0x000000000002e3cb
Faulting process id: 0x4160
Faulting application start time: 0x01d8b48260d0a884
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 9c55171e-7ca2-4c97-b878-09640885d7a3
Faulting package full name:
Faulting package-relative application ID:

And the second being:

Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.19041.1806, time stamp: 0x1000a5b9
Exception code: 0xc0000005
Fault offset: 0x000000000002e414
Faulting process id: 0x398
Faulting application start time: 0x01d8b4a96fbe7f92
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: dcb15677-5417-43ca-a00f-08082682e65d
Faulting package full name:
Faulting package-relative application ID:

Then today day I got a CTD on a d3d11.dll:

Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: d3d11.dll, version: 10.0.19041.1865, time stamp: 0x8ff19571
Exception code: 0xc0000005
Fault offset: 0x00000000000d3d34
Faulting process id: 0x202c
Faulting application start time: 0x01d8b4ef33b5cf55
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\d3d11.dll
Report Id: 8d8f7a3b-75de-42c0-8932-4de020d93d38
Faulting package full name:
Faulting package-relative application ID:

Not sure if the two can be related just wanted to post this observation.

Do you have any mods installed? If so, which one(s)?
PMDG 737-600/700, PMDG DC-6, LHsimulations Budapest/West Hungary, Fenix A320, DA40/62 Improvement package, WT CJ4/Garmin

What plane were you flying?
In case of the latest CTD Arosoft CRJ-900

What were your departure and arrival airports?
LRSB - LHBP

Did you have live weather enabled?
Yes

Did you have live traffic enabled?
Yes

Are you on SU9 or SU10 beta?
SU9

Are you using DX11 or DX12?
DX11

What is your GPU and what driver version are you using?
RTX 3080ti with the latest driver

Are you on Windows 10 or 11?
W10

Location: Netherlands

[Hester40MT]

Yes, it does.
Be nice if we had a way to force that with an option.

[eGGii90]

Really, you saved my day!
Had random CTD’s and FPS drops after 2hrs+.

After disabling Live Weather it runs like butter. Constant FPS in the air and on the ground without FPS drops after 2hrs or any CTD.

Hope it really fixed it temporarily!
Also hope that they can find a fix for that soon!

[CBCDES]

Agreed, it would be very useful.

[Ithendyr]

I’ve tried, doesn’t work for me.

[CBCDES]

Did you try switching off all of the lower 3 options in the data connection menu?

[hobanagerik]

You should be able to do this to force safe mode:

Command line parameter to start the sim in SAFE MODE

Ah, so if we were to manually create that file, say as part of a “Safe Mode” script, we could force the sim to launch in safe mode. If the sim removes that file automatically for a clean shut down from Safe Mode, we wouldn’t need to script its removal either. Checking another post, this file should be in the “LocalState” folder. So in theory this should work. copy nul > C:\Users\%USERNAME%\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\running.lock

[Moridin8615]

I already mentioned this, but just so the relavant people see this:

MSFS has also crashed while in SAFE mode, flying a stock 747.

[MetalPlains3097]

is this the ntdll.ll crash or some other?

Faulting application name: FlightSimulator.exe, version: 1.27.16.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.27.16.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000227ecb7
Faulting process ID: 0x1954
Faulting application start time: 0x01d8b585af57d335
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 1e29a547-8438-48ad-8a26-0ff4b0dd8ccd
Faulting package full name: Microsoft.FlightSimulator_1.27.16.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

sorry i not good on event viewer, i don’t know what it means, only i never have CTD before, then yesterday and today every flight

[StillDanny1314]

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

[ToriDadriel]

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:

[NvH69009]

It’s not related to NVidia drivers. I have CTDs on different versions these last 2 days.

[michihimself]

Definitely no, same problem with driver that are a few months old.

[SuperSixBravo]

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.

[Hester40MT]

@Noctover @dustNinja7871 @Majjistral
While anyone who is at Trust Level 2 or higher can flag posts, only Admins, Community Managers and Moderators can hide posts.

A reminder that discussing moderation on the forum is not allowed. Please review the Code of Conduct

Keep posts on-topic.

Thank you.

[CopperNu]

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.

[Xelli7500]

@GrizzlyBearSims

Just to add my recent experiences. I purchased MSFS on day one, but for the first 18 months or so really only used if for GA flying and mostly spent my sim time in P3D flying jets. When Fenix released their A320 and PMDG the 737, I made the move to MSFS. I’ve flown it exclusively the past 3 months or so and have accumulated a few hundred hours and probably 200 flights. Before mid last week, I could count the number of CTD’s experienced on one hand. I would estimate only 2-3. Beginning last week this changed.

While I’ve been fortunate my CTD’s have not happened in flight, I do get multiple CTD’s sometimes when starting up the sim. Last night I had 3-4 before MSFS would finally load up. However, this morning MSFS launched without issue and I managed two one hour flights with no issue.

The one thing that I have noticed is MSFS will no longer shut down all the way to desktop. I have to end task on it to get it to fully close. Anyone else seeing this?

Yes I also have this a few times that I have to end MSFS with the task manager