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
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.
Yes, this is the crash of concern. I didn’t get a pop up message though, just the crash with the identical code.
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
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?
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…
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
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
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
Yes, it does. 
Be nice if we had a way to force that with an option.
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!
Agreed, it would be very useful.