I had the same errors 5mins after taking off.
I use several connected softwares as Ivao/Vatsim, SLC, FS realistics/ Pushback Helper and… AIG Traffic!
It seems that the problem comes from AIG Traffic on my side. Indeed, on some flights, nothing happens, everything work well.
But I have the feeling that I tried 3-4 flight with AIG Traffic injected and the problem happened…
Try to not use it during flights and maybe it will solve your issues.
Unfortunately I’m still getting these CTDs… It’s getting quite tedious as I’m lucky to be able to finish a flight. I’m out of ideas here. 
I am 2 crashes in 3 flights this week. Tonight I hope I can even up the score.
I don’t use AIG traffic so that’s not the problem I think…
yep, thats what other users reported too.
Your RAM is not explicitly mentioned within the QVL. But I assume its a hardware-version only ( “D” in QVL vs. “E” you own ). The existing profiles are for me a bit “hmmm”, e.g. why is there no JEDEC max profile 2666 ? This RAM is without OC’ing a 2133 RAM and then they do a big jump to 3200 ( you also see the huge increasment in necessary memory voltage ).
But good that this little change in frequency works fine. Let us know whether this change in frequency works stable over same days.
If something happens, I’ll let you know. by the way a quick question is it normal that mfs2020 does not use more than 65% of my components?
ah, thats another topic, e.g. “limited by mainthread” , also some topics about memory consume ( working vs. commited set ) , etc. . But Su10 is near and I would not spend to much time into that. Quick note: do not set tLOD too high ( not more that 200, better test with much lower value ).
1 Like
Ok, thank you very much, it has been a great help
2 Likes
Another CTD this morning, this time without the “memory error” message BUT, I have inspected the windows event monitor and the cause is rooted to the same file (ntdll.dll) than the other 2 crashes of yesterday with the “memory error” message.
Blockquote Nombre de la aplicación con errores: FlightSimulator.exe, versión: 1.26.5.0, 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: 0x4b74
Hora de inicio de la aplicación con errores: 0x01d8b4827950166c
Ruta de acceso de la aplicación con errores: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Ruta de acceso del módulo con errores: C:\Windows\SYSTEM32\ntdll.dll
Identificador del informe: bd20ba6d-1d8e-4ae3-b0ef-6eb67314d748
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:
Blockquote Depósito con errores , tipo 0
Nombre de evento: APPCRASH
Respuesta: No disponible
Identificador de archivo .cab: 0
Firma del problema:
P1: FlightSimulator.exe
P2: 1.26.5.0
P3: 00000000
P4: StackHash_56ea
P5: 10.0.19041.1806
P6: 1000a5b9
P7: c0000374
P8: PCH_21_FROM_ntdll+0x000000000009DA94
P9:
P10:
I even tried to do the “sfc /scannow” to see if it solves the problem.
Happens quite frequently here too, sometimes the error message will pup up but MSFS continues to work, only the dam error window is forever there till I click ok then MSFS closes, 95% of the times, CTD instantly, so frustrating. Also only been happening since the last big update
Nope, still another crash and without IVAO (the other 3 was online on IVAO) and no AI traffic, no multiplayer planes.
I will try with other plane to see if maybe it’s the plane (It was FENIX A320), but I am really tired that after 2 years, this is still “Microsoft Debug Simulator”
EDIT: At this point I don’t know If I should do another post about this crashfest that started yesterday (and I didn’t update anything or installed any plane or mod to the sim or changed any config of my system or MSFS)
EDIT2: At least now it didn’t say that the crash is caused by ntdll.dll. Coincidence maybe? 
Since yesterday.
Short flight with SR 22 manual and IVAO : ok
Medium Flight with A20N (fbw) and IVAO (between malta and genava) : crashed over alpes
Long VFR Flight between with BE58 and autopilot and IVAO : crashed after take off, then after 2 hour flight when switch AP mode NAV to HDG
This morning :
Another try to my IVAO A20N flight : chrashed over cicilia when change AP altitude
Short VFR flight with SR22 on IVAO : ok
Short VFR flight with SR22 with AP and IVAO : crashed short after take off.
So, for now and my experience
2 flight without AP : no crash
5 flight with AP : 100% crashed at different moments.
can be random… the ntdll.dll / 0xc0000374 can also happen in case of map-issue (.e.g. ) or others . Are you sure that the error message “memory could not read” correlates to that ?
1 Like
And the read error is back… Fenix & MSFS having been stable for quite a few days. Fed up with it. 4 sticks, 2 sticks RAM makes no difference. XMP or no XMP still results in random read error. could be days apart, or hours apart.
Ran some more tests and passes every time.
Wait… mine was “could not be written”
Maybe we should start another thread about this bug then. This make it unclear to have relation with the bug of this post, sorry.
Some of us are starting to thing that maybe is a Fenix related issue but… the crashes didn’t totally correlate with Fenix. People are having them with other planes.
1 Like
Some interesting information from Matt…
Memory cannot be referenced - Microsoft Flight Simulator (2020) - The AVSIM Community
1 Like
I have them with all kinds of planes, in all places. Doing a round the world trip and changing planes depending on the legs. I’ve had this all the way from Jakarta to Toronto, in SU9 and SU10. Payware planes and default planes, it’s the same. 100% vanilla sim, no addons = still CTDs.
I didn’t have these before upgrading from a 10900KF to a 12900KF and at the same time switching to a z690 motherboard with 32GB of DDR5.
What I’m not sure of though, is if I had the CTDs before upgrading to Win11. I simply can’t remember…
we have an ( better more ) existing topic about " … written" 
Also, have you seen the other topic which I linked to your post. Other users report same ntdll issue and/or at least more CTDs in last days in generally.
So, may be “yes”… its may be not related to that issue here ( what my guess was too ).
And yes… what I read in that topic, it is independ of the airplane.
1 Like
just got this again with the Fenix on approach to PMI… back to square one 
i’m afraid XP12 is my only hope can’t be dealing with this buggy game anymore
CTDs are increasing at the moment. Yesterday four times. Today at the first flight after 15 minutes and after restart again at 30 minutes flight time.(WIN10, CJ4 working title KBOS-CYFC)