Constant CTD every flight now (ntdll.dll)

I had a CTD today when flying the Fenix A320 near the coast of Engeland towards EGKK. Never seen that Faulting module name before.

Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: grammar.pggmod, version: 76.0.0.3, time stamp: 0x61977cfe
Exception code: 0xc0000005
Fault offset: 0x0000000003eace61
Faulting process ID: 0x4e1c
Faulting application start time: 0x01d8b53a6619b50b
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: \?\C:\Users\username\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\bf-pgg\PGG\grammar.pggmod
Report ID: 0425e9ea-995c-46a3-97b8-a5e4e89ed0dd
Faulting package full name:
Faulting package-relative application ID:

It is really weird. So far I had 1 CTD with GSX installed on Friday, but none thereafter in the next 5 flights with the Bonanza, Islander and Fenix. All with Live weather, SU10beta. Hope it stays like that, but it sure is a shame for those who suffer from this!

CTD every attempt currently on multiple aircraft, routes and scenery.

Win10, Live weather on, no traffic, multiplayer off, SU9

Error from event is always ntdll.dll

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: 0x498
Faulting application start time: 0x01d8b5579c4c845d
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: 85497312-bf08-4f9f-b119-db2b09e7e202
Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

really hope Asobo sort out these CTD and memory error issues, its getting annoying for alot of people

..and if you haven’t already and you are getting the “memory could not be read” message, please vote on the thread where that CTD has been discussed at length.

I posted the link earlier in this thread.

I have taken a Flight from EDDB - EDDK with Live Weather, Live Traffic (AIG), Acars, and GSX, everything was fine and GSX had worked also fine. My Last Driver Update is 4 Weeks or more ago.

Also no Worldupdates etc. taken in the last Weeks.

Yesterday and this morning I also had a couple of CTD’s, with or without GSX (SU9). Yesterday came another update of the world UpdateVI, maybe this is the cause of the CTD’s,?

Is not related to data update of WU6, CTD come before.

2 CTD for me today - one over UK and another on approach to Toulouse (LFBO) - SU10B.

Don’t normally suffer from these.
CTD upon approach to LFBO after approx 1.25hours of flight time


CTD over UK South Coast with 20mins of flight time

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.

https://forums.flightsimulator.com/t/constant-ctd-every-flight-now/537543/296

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.

CTD:
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)
SU9
DX11
Nvidia 3090
W10

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: 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.

MODERATOR EDIT:
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

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

AngefĂźgte Dateien:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9218.tmp.WERInternalMetadata.xml

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.2.0.0.256.481031e741e7416f17cba8c0ab30fa39851c7eafcf2c3a2c3a61935d46a331d0e430dae9a0650eE258741F-4C8C-42B7-A875-890F26D65BCBSystem manufacturerSystem Product Name140716061574841601-01-02T22:07:04Z-01:000a4d1a758-7661-4cfa-a8d9-bf70306b90992022-08-21T12:30:26Z

General:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.26.5.0, 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

…

EventData

1000 0 2 100 0 0x80000000000000 44903 Application DESKTOP-DP29DA6 - FlightSimulator.exe 1.26.5.0 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.

P.S.
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.