CTDs occurring persistently

Hello everyone :),

first, I’d like to introduce myself.
My name is Alex and I’m from Germany…

I have huge problems with CTDs occuring nearly everyday right now…
Mostly when using the Fenix A320…

No matter which graphics settings I use, I get CTDs on almost every flight.

Here is the entry of the event manager:
Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.38.2.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.22621.3593, Zeitstempel: 0x10c46e71
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000014f71
ID des fehlerhaften Prozesses: 0x0x4240
Startzeit der fehlerhaften Anwendung: 0x0x1DB678E1D83001B
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Windows\System32\ucrtbase.dll
Berichtskennung: 8031f569-5104-4865-9039-f317d849fefc
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

This is my system
Intel i9-14900KF
Nvidia RTX4080Super

Can you maybe give me an advice?
Would be very cool.

Regards,
Alex

I’m having this problem in the MSFS 24 too, but I’m using the A320 v2 from Inibuilds (game default)

Today I had 2 CTDs in a row during flights (one in the morning and one at night). Both CTDs were in the Descent phase, but at different points, one near the approach and the other at the beginning of the descent.

I’m not sure, maybe I’ll test it later… but it’s possible that both CTDs happened at the time I was fiddling with the camera to put the approach data into the FMGS. Maybe it’s a coincidence.

This didn’t happen any time in the previous days.

I wonder if there was an update in the backend? How can something that worked until yesterday suddenly stop working?

Now I don’t want to try to fly for a third time because I don’t want to waste my time.

Another thing: Windows updated something today before I turned on my computer (updates KB5049621 AND KB5049981). Then I’ll see if I can uninstall these updates to test (or not, because I’m angry and I don’t want to waste my time for nothing).

Oh, and in my crash log file there’s
“/!/ CRASH /!/TOML
[OnCrash]
Msg=”_handleSEH"
Type=“SEH”
Code=0xC0000005
(…)"