Constant CTD every flight now (ntdll.dll)

After 2 two days, I can again do flight from A to B without a CTD but with live weather OFF.

If I turn off Live Weather, I don’t get CTD, are you sure?

Just a trial with “Weather OFF”. CTD after 5 minutes. No solution for me. I finish my trying for today. It is useless.

Yes but make sur this option is OFF in data section before you choose your flight

yep… for me is that the only relevant NEW error which never happens for users before and which started some days ago.

May be one exception is the “memory could not read”, but here we are still collecting informations “within the responsible topic for that error” whether also “more NEW occurances” ( starting with same day as the ntdll issue ).

1 Like

thats for me another issue where we have an existing topic:

If possible describe the exact location within the other topic and users can then retry this position.

FBW A320NX (Experimental version)
ENCN - ENGM (just prior to pushback for the return sector - same session as the first leg)
Live weather on
No live traffic, but on VATSIM (with AIG model matching)
Nvidia 3090

Faulting application name: FlightSimulator.exe, version:, 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: 0x1d4c
Faulting application start time: 0x01d8b552fe47f4d2
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: 3ba17534-0412-4b14-b74e-bb695fe82451
Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

i had many CTD´s last 2 days, mostly with ntdll.dll

i tried:

  1. uninstall GSX
  2. sfw /scannow via commd prompt
  3. set pagefile to 50GB (i have 32 gb ram)

i am not sure this is solution, but now i fly 4th flight without ctd…weather on, online on vatsim now TVS98PO…

Is not related to data update of WU6 or GSX :
CTD come before WU6 package update and i doesn’t have GSX.
Did a “sfc /scannow”, didn’t fix.

It’s just random.

This post merged into this topic.

As the header says i encounter crashes at nighttime. Since i started flyin at night time recently i cannot say if it would have been better some months before. At daytime i have no problems actually.
I tested actual and old grafic driver from NVIDIA but the night crashes still occour. I found some information within Windows (10).

The ID is 1001 and the Source is Windows Error Reporting.
Fehlerbucket 2255942993912543198, Typ 5
Ereignisname: MoAppCrash
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

P1: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
P2: praid:App
P4: 00000000
P5: StackHash_e741
P6: 10.0.19041.1806
P7: 1000a5b9
P8: c0000374
P9: PCH_DD_FROM_ntdll+0x000000000009DA94

Angefügte Dateien:

xml version=“1.0” encoding=“UTF-16”?>10.019043(0x30): Windows 10 ProProfessional19041.1889.amd64fre.vb_release.191206-14061889Multiprocessor FreeX641031MoAppCrashMicrosoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwepraid:App1.26.5.000000000StackHash_e74110.0.19041.18061000a5b9c0000374PCH_DD_FROM_ntdll+0x000000000009DA9410.0.19043. manufacturerSystem Product Name140716061574841601-01-02T22:07:04Z-01:000a4d1a758-7661-4cfa-a8d9-bf70306b90992022-08-21T12:30:26Z

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version:, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.19041.1806, Zeitstempel: 0x1000a5b9
Ausnahmecode: 0xc0000374
Fehleroffset: 0x00000000000ff609
ID des fehlerhaften Prozesses: 0x1f10
Startzeit der fehlerhaften Anwendung: 0x01d8b546bbe2212a
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: 94ca1e25-37f6-4b6d-8a46-862308998dff
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App


1000 0 2 100 0 0x80000000000000 44903 Application DESKTOP-DP29DA6 - FlightSimulator.exe 00000000 ntdll.dll 10.0.19041.1806 1000a5b9 c0000374 00000000000ff609 1f10 01d8b546bbe2212a C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe C:\WINDOWS\SYSTEM32\ntdll.dll 94ca1e25-37f6-4b6d-8a46-862308998dff Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe App

My Specs:
AMD Ryzen 7 3800x 8 core, 64GB RAM, NVIDIA GeForce RTX 2070S (8GB RAM) nothing oc, PSU 950 Watt, 50Mbit Internet.

I found one thread already but it is one year old and i did not wanted to dig out a corpse. Hope i did not wrong.

Although I seldom CTD I have noticed many ‘Side by Side event 59’ errors in Windows (11) event viewer.

Run the Windows Store Apps troubleshooter and then starting at the bottom Modify/Repair all the Visual C++ installs that let you. Then run the troubleshooter again, if all is well it should then tell you it cannot find the problem.

Hope this helps with CTDs but if nothing else at least your MSFS load times should be quicker.

Some people say they turned off live weather in the data menu and it seems to fix it. The issue screams server sided problems.

I just performed 4 different tests the first:

  • a flight between brussels and corfu with gsx and online service = CTD
  • Same flight without gsx and online service = CTD
  • Same flight with GSX and offline service = NO CTD
  • I then returned to corfu - brussels with gsx and offline service = NO CTD
1 Like

What do you mean by “online services”? Turn off the internet?

Now everything is really slow. Takes ages to load and it doesn’t load terrain and objects. Its all blurry.

There is no way, this simulator is becoming a real headache, since the 17th there is no way to fly a complete flight, MSFS? are you going to publish something?

Nombre de la aplicación con errores: FlightSimulator.exe, versión:, marca de tiempo: 0x00000000
Nombre del módulo con errores: ntdll.dll, versión: 10.0.19041.1806, marca de tiempo: 0x1000a5b9
Código de excepción: 0xc0000374
Desplazamiento de errores: 0x00000000000ff609
Identificador del proceso con errores: 0x4768
Hora de inicio de la aplicación con errores: 0x01d8b5583d1db272
Ruta de acceso de la aplicación con errores: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Ruta de acceso del módulo con errores: C:\Windows\SYSTEM32\ntdll.dll
Identificador del informe: e1018134-9c8e-4592-9d00-1955da943351
Nombre completo del paquete con errores: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Identificador de aplicación relativa del paquete con errores: App

Same here, 3 CTDs in the last 3 days, never had a CTD before in 1.5 years of running MSFS.

RTX 3070, 2 out of the 3 times were on Vatsim with Vpilot injecting traffic so I assumed it was to do with that, but not sure. One was ntdll.dll, the other was VCRUNTIME140.dll, the other idk.

All crashes happend on takeoff or landing, when switching camera to the outside view (i.e rendering something weather, satelittle imagery etc).

Something has definitely changed to cause this, as i’ve never CTD before.

1 Like

This more often than not seems to be the case.

When a spate of CTDs hit (and I’ve been hit with a few this weekend, whereas I’m generally CTD-free) I tend to veer towards live weather, or other server issues.

Getting CTDs on airliners, so I moved to the 414 and 1/2 hours in got a CTD. I’d expect the same to happen on the C172 if I go for a long enough session.
Oh well, time to enjoy some IRL time.

Also 2 CTDs out of 5 flights, but no windows event is showing up. Yesterday I had also 1 flight when my sim froze during final.
First time it happened was on friday aswell. Before I had no issues with CTDs.