CTD since last update 2.8.2

[streichholz]

Hi

Today I tried several flights, all ending in CTDs at the airport, during TO or during flight.

All ended with the same issue:

Name der fehlerhaften Anwendung: couatl64_MSFS.exe, Version: 4.8.0.5302, Zeitstempel: 0x6536a93f
Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.22621.608, Zeitstempel: 0xf5fc15a3
Ausnahmecode: 0xc0000409
Fehleroffset: 0x000000000007f61e
ID des fehlerhaften Prozesses: 0x0x5E24
Startzeit der fehlerhaften Anwendung: 0x0x1DA0FD721603F52
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
Pfad des fehlerhaften Moduls: C:\Windows\System32\ucrtbase.dll
Berichtskennung: ab3d109c-d085-40e5-ad6a-f54fbad7a564
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:


I hope someone can help!

Philipp

[M@th44]

Same

[zebraleet]

I am also getting crashes. I don't know if it's GSX or not... I will need to test without it. But MSFS ends in the below:

Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000029650a0
Faulting process ID: 0x0x3638
Faulting application start time: 0x0x1DA101F6309BA8C
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report ID: a6b4ca9d-ae8e-4d90-80e7-61dac48819df
Faulting package full name:
Faulting package-relative application ID:

[virtuali]

When I check the event viewer i can see that couatl crashes first and then the sim.

This has been discussed so many times on the forum, you are being mislead by the event viewer and are assuming that, just because you see Couatl crashed, it was the cause of your MSFS crash, but it's not.

The couatl engine, as an .EXE, doesn't have ANY access to the Flightsimulator.exe process, meaning it cannot possibly cause a crash. This is granted by the OS at the lowest level, and programs that don't attach to a process like debuggers ( and Couatl surely doesn't ) and/or are not lower level services or drivers, simply cannot crash other apps.

On the other hand, when Flight simulator crashes for any other reason, it will abruptly disconnect its communication with the Couatl program, which is waiting for a proper "quit" command ( which hasn't arrived, because the sim crashed ), to exit cleanly.

So, what really happened here, is that MSFS crashed for another completely unrelated reason, and it MADE Couatl crash too, because of the unexpected disconnection, and you are being mislead assuming Couatl has something to do with it, because you are seeing it referenced in the event viewer.

As discussed in this other post:

https://www.fsdreamteam.com/forum/index.php/topic,29540.msg191735.html#msg191735

If you checked the timestamps of the Event, it's likely you'll see that Flightsimulator.exe crashed BEFORE Couatl64_MSFS.exe, which means it was the simulator that made GSX crash, not the other way around.