Crash/Freeze when closing the sim 2024

[senchay]

Hello Umberto.
Since the update (or maybe since install, both lie near to each other) my sm freezes whn closing the sim. Dont see a log created, last entry is from 2022.

But windows error log says this

Name der fehlerhaften Anwendung: Couatl64_MSFS2024.exe, Version: 4.8.0.5556, Zeitstempel: 0x673e2b0d
Name des fehlerhaften Moduls: clr.dll, Version: 4.8.9290.0, Zeitstempel: 0x67214bca
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000000657c
ID des fehlerhaften Prozesses: 0x2bd4
Startzeit der fehlerhaften Anwendung: 0x01db3e9387dbc1ed
Pfad der fehlerhaften Anwendung: E:\FlightSim\Tools II\Addon Manager\couatl64\Couatl64_MSFS2024.exe
Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll

[RogerWilco]

Same issue a hundred times per day. Also happens with weathercreator.exe, which is REX Atmos.

Faulting application name: couatl64_MSFS.exe, version: 4.8.0.5565, time stamp: 0x6744682e
Faulting module name: clr.dll, version: 4.8.9290.0, time stamp: 0x67214bca
Exception code: 0xc0000005
Fault offset: 0x000000000000657c
Faulting process id: 0x0x9B0
Faulting application start time: 0x0x1DB6EB317FC6FCE
Faulting application path: M:\Tools\Addon Manager\couatl64\couatl64_MSFS.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll

[Panamericana85]

same for me on Msfs2020 and Msfs2024, we need a fix  :'(


Name der fehlerhaften Anwendung: couatl64_MSFS.exe, Version: 4.8.0.5565, Zeitstempel: 0x6744682e
Name des fehlerhaften Moduls: clr.dll, Version: 4.8.9290.0, Zeitstempel: 0x67214bca
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000000657c
ID des fehlerhaften Prozesses: 0x0x1180
Startzeit der fehlerhaften Anwendung: 0x0x1DB6EF4E5308592
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
Pfad des fehlerhaften Moduls: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Berichtskennung: 6c87135e-ad9f-4b09-9908-57954f48e693
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

[virtuali]

Same issue a hundred times per day. Also happens with weathercreator.exe, which is REX Atmos.

You are confusing the effects with the cause. Those apps ( REX and GSX ) are both VICTIMS of the real issue, which is MSFS crashing on exit for some reasons. What you see is the EFFECT: the sim crashing on exit, is CAUSING those apps to also crash themselves.

You see them listed in the Event Viewer, so you think they are "causing" the crash, but it's the other way around, and it's easy enough to verify: the Event Viewer has timestamps when the event happened, and I'm fairly sure if you check those as well, you'll see that Flightsimulator.exe likely crashed a few seconds before all those other apps, which is a clear indication that it was MSFS who made those apps crash, no the other way around.

[Panamericana85]

for me it was everytime the first timestamp of an error...there was no error before the cuatl error

[virtuali]

for me it was everytime the first timestamp of an error...there was no error before the cuatl error

You are the first ever reporting this. Each and every user reporting these crashes realized the sim crashed before, usually a few seconds before, so they realized what really happened.

But that's not really the point, the point is the previous timestamp would be useful just to you as a proof who caused the crash, so you didn't have to trust my explanation about the Couatl engine not being able to crash the sim (it just can't). So now, without this, you don't have any other choice other than trust my explanation, because you don't have the extra proof given by the timestamps in the event viewer.

[Panamericana85]

So another app could have crashed even without a timestamp?

[virtuali]

So another app could have crashed even without a timestamp?

The simulator itself crashed, and made the couatl engine crash as well. As I've said, you are the first ever reporting FlightSimulator.exe crashed without an Event, which is unheard of but, we can only accept it might still happen.

Note that, even if couatl could possibly crash the sim ( it can't ), you would have a Flightsimulator.exe crash event recorded. As I've said, it's the first time ever somebody reported the sim crashing without an event.

[Panamericana85]

i dont know what to do now.  wait for windows update or so

[Panamericana85]

Find in a forum that connection issues with internet or with the lost of onlineservice from asobo can cause ctd without any errors in eventviewer

[Panamericana85]

no lost of connection...crash again and again without a other crash before  also do a "sfc /scannow" thing without any error

[trisho0]

no lost of connection...crash again and again without a other crash before  also do a "sfc /scannow" thing without any error

Maybe BIOS update is needed.

Patricio Valdes