I have AMD
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: 0x4160
Startzeit der fehlerhaften Anwendung: 0x01d8b3cbdf4b172a
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: 0f5b4d58-fd72-4179-8a3d-9920e9764210
VollstÀndiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
+++++++++++++++++++++++++++
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: 0x4754
Startzeit der fehlerhaften Anwendung: 0x01d8b3b2261201b0
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: 959a1d4a-1b07-4ad9-a39a-69aabce03795
VollstÀndiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
++++++++++++++++++++++++
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: 0x1c44
Startzeit der fehlerhaften Anwendung: 0x01d8b3a22d8253b1
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: f8b7b2f8-9eaa-4d0e-9f5e-44c6ea107108
VollstÀndiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
+++++++++++++++++++++++++++
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: 0xc0000005
Fehleroffset: 0x000000000002e3cb
ID des fehlerhaften Prozesses: 0x1638
Startzeit der fehlerhaften Anwendung: 0x01d8b39fcc377223
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: a8315f9c-f332-4cd8-827c-431ad547b23c
VollstÀndiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
++++++++++++++++++++++++++++++
NO crashes prio to Aug 19th! Sim config, hardware config, drivers all the same. SU9, Win10.
Yes!
CTD only since yesterday 15:00 Zulu for me
Good theory, except for one thing I rolled back my drivers to 4.57.nn drivers and still am getting the crashes. Turn of PG and Live weather and the sim runs better, but as soon as you go into a menu ⊠crashâŠ
1 Like
No.
I had previous version and itâs because I got CTDs that I install the latest one⊠But Iâm still having CTDs.
Itâs not related to a specific Nvidia driver.
2 Likes
GPU is not the problem. NVIDIA and AMD affected
Iâve opened a ticket today, closed few hours later with a generic message to solve problems.
The ticket was opened with all informations needed.
They donât care.
1 Like
I did have them in the event monitor, but I donât know where it says that it have reported the crash.
By the way⊠remember to vote the thread if you are having this bug. It started on another subforum I think, and that is why I didnât have voted this 
Out of the blue Iâm now a member of the CTD club, too. 
Never had one on msfs2020 before
Had a CTD today.
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: 0x7cc
Startzeit der fehlerhaften Anwendung: 0x01d8b5782c5d0d34
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: f4d24286-81d3-4fe8-bc86-a0e449ab8805
VollstÀndiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App
Got an error message, stating that some memory couldnât be readâŠ
Yep same,
Thought GSX was the cause but its becoming clear a spike in CTDs are occuring regardless of the presence of GSX.
Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000002145305
Faulting process ID: 0x1330
Faulting application start time: 0x01d8b57b230ea0f3
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 5148ee2e-152b-4ac5-8229-4cbcb5afac90
Faulting package full name: Microsoft.FlightSimulator_1.26.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
New computer, installed MSFS on it this afternoon. Every flight CTD after about 10 minutes.
Tried SFC /Scannow but no joy.
Out of curiosity tried to recreate some of my manual cache areas from the old PC. Small areas seem to download ok. Larger areas, CTD after approximately 10 minutes.
Nope, this thread now is isolated to the ntdll.dll issue. For the âmemoryâ issue there is another MSFS Application Error - memory could not be read
3 Likes
Agree, this doesnt make sense.
Nvidia 516.94 has been very stable for me since its initial release.
Today is the first day Iâve experienced CTDâs in a while - and consecutive at that. All during loading of MSFS.
I finally completed loading of MSFS and was able to take a quick hop around Toronto by selecting SAFE MODE during start up.
BTW, I flew both Friday & Saturday without issue and havenât installed any new add-ons since earlier last week, so I donât feel itâs an add-on problem.
1 Like
Yes, this is the crash of concern. I didnât get a pop up message though, just the crash with the identical code.
1 Like
Everyone,
We have asked you to keep discussion in this thread specifically about the new ntdll.dll crash that has started to appear within the past few days. This is NOT a catch-all thread for all CTDs. If you are experiencing the âmemory could not be readâ error, please post your feedback in the appropriate thread, not this one.
Thanks,
MSFS Team
3 Likes
Never had any CTDâs in 2022, but this weekend CTD every singel time. 2 CTDâs today from Ă lesund to Cologne. Could it be an Asobo server issue - Has anyone tried an older Nvidia graphic driver?
Surely running the sim in Safe mode automatically excludes addons that were bought in Market place?
1 Like
Thanks, happy to see a CM here.
Iâve opened a ticket with all informations needed on ZenDesk, support doesnât care⊠Closed with a generic message to solve common problems. (with no questions askedâŠ)
Fear the problem isnât be solved fastâŠ