Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Couatl (GSX) prevents SIM from loading and crashes itself

Featured Replies

Since GSX, I have MSFS freezing (minutes) upon load and sometimes crashing (does not load at all but remains frozen).

Today MSFS received a small update and now the sim freezez and an error message is shown stating that an application is preventing Couatl to load and if I skip to load it, the sim works perfectly.

Gerald K. - Germany

AMD 7800x3D / ASUS ROG X670E-Gaming / ASUS Strix  RTX 3090 OC / 64 Gb RAM GSKILL.

"Flightstick" = X56 HOTAS RGB Logitech

And why do you post this first here on avsim and not in the GSX MSFS Support forum over at FSDT? Personally, I never had any issue with loading of MSFS and Couatl so far... 

Greetings, Chris

AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024

I also have sim freezing on load-up lately (directly after spawning in)  although I'm not quite sure if it's to do with GSX.  That doesn't bother me so much because it sorts itself out.

The occasional Couatl crash is a long standing GSX'ism which I've given up stressing about.

Edited by ErichB

  • Commercial Member
1 hour ago, GEKtheReaper said:

Since GSX, I have MSFS freezing (minutes) upon load and sometimes crashing (does not load at all but remains frozen).

It's not possible that Couatl could prevent the sim from loading, since it's an external .EXE and, by definition, and external .EXE cannot prevent the simulator from loading. Not a normal .EXE like that, which runs as a user-level program and surely doesn't do anything weird, like attaching itself to the simulator like a Debugger, which would be the only way in which it could possibly affect its process or its memory space.

 

1 hour ago, GEKtheReaper said:

Today MSFS received a small update and now the sim freezez and an error message is shown stating that an application is preventing Couatl to load and if I skip to load it, the sim works perfectly.

The simulator is possibly trying to start Couatl by itself ( normal, since it is added to the EXE.XML ), so maybe it's reporting the real cause of the problem: that "application" might be the antivirus that has blocked it and, opposite to Couatl, which is an user-level program that has no access whatsoever to the simulator process and memory, antivirus use lower-level services that DO have the ability to block other apps and potentially make them fail.

Configure the antivirus to add the whole Addon Manager folder to the antivirus Exclusions and, while you are at it, configure it to exclude the whole MSFS folder and Community/Official folder. In addition to not being mislead again GSX "crashed your sim",  which it can't, your simulator will start faster and will run better.

Edited by virtuali

  • Author
12 minutes ago, virtuali said:

It's not possible that Couatl could prevent the sim from loading,

Name der fehlerhaften Anwendung: couatl64_MSFS.exe, Version: 4.8.0.5105, Zeitstempel: 0x639b573b
Name des fehlerhaften Moduls: couatl64_MSFS.exe, Version: 4.8.0.5105, Zeitstempel: 0x639b573b
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000195ae9
ID des fehlerhaften Prozesses: 0x0x6AE4
Startzeit der fehlerhaften Anwendung: 0x0x1D916A639915DB0
Pfad der fehlerhaften Anwendung: E:\FSDT\Addon Manager\couatl64\couatl64_MSFS.exe
Pfad des fehlerhaften Moduls: E:\FSDT\Addon Manager\couatl64\couatl64_MSFS.exe
Berichtskennung: 3323c335-96ad-489c-8723-6ae101abef74
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: 

 

 

Exceptions are in place (Bitdefender and Win). MSFS still hangs on load at about 50% (maybe more).

Edited by GEKtheReaper

Gerald K. - Germany

AMD 7800x3D / ASUS ROG X670E-Gaming / ASUS Strix  RTX 3090 OC / 64 Gb RAM GSKILL.

"Flightstick" = X56 HOTAS RGB Logitech

  • Commercial Member
1 minute ago, GEKtheReaper said:

Name der fehlerhaften Anwendung: couatl64_MSFS.exe, Version: 4.8.0.5105, Zeitstempel: 0x639b573b
Name des fehlerhaften Moduls: couatl64_MSFS.exe, Version: 4.8.0.5105, Zeitstempel: 0x639b573b

What that error log is saying that Couatl has crashed BECAUSE the sim crashed, which is normal since, if the sim crashed for other reasons, it would break the Simconnect connection abruptly, which will like MADE Couatl crash as well.

Nowhere that log indicates Couatl was the cause of the crash. In fact, it was likely the victim.

  • Author

@virtuali but the sim did not crash, it loaded perfectly well by unloading Couatl (after the error message was displayed).

Look, you are probably right in all that you say because you are the developer but on my end it looks like:

- no GSX -> no issues at all with loading the sim and using the sim

- with GSX -> loading hangup's and crashes

Except 3 airports, some PW ACFT and FSLTL, I don't have any MSFS modificators (so my sim is almost vanilla and crashes were a rarity).

Gerald K. - Germany

AMD 7800x3D / ASUS ROG X670E-Gaming / ASUS Strix  RTX 3090 OC / 64 Gb RAM GSKILL.

"Flightstick" = X56 HOTAS RGB Logitech

  • Commercial Member
4 minutes ago, GEKtheReaper said:

Look, you are probably right in all that you say because you are the developer but on my end it looks like:

- no GSX -> no issues at all with loading the sim and using the sim

- with GSX -> loading hangup's and crashes

If your antivirus ( following your report that MSFS said "an application prevented to load Couatl" ) is messing up with the startup of the programs, IT CAN crash the sim ( the antivirus can, Couatl cannot ), so you can be easily mislead GSX caused the crash, just because you don't have the crash without it.

Don't you think if GSX *really* caused a crash, we would have know it by now, and we would have both our forum and everywhere else flooded by similar complains, same as when GSX came out, when because of an issue on MSFS servers happened exactly when GSX came out, we DID had the forum and everywhere else flooded by CTD reports, which obviously turned out not to be related to GSX in any way ? That is just to say, if this really happened to lots of people, we would have heard it by now.

  • 4 weeks later...
On 12/23/2022 at 9:42 PM, GEKtheReaper said:

@virtuali but the sim did not crash, it loaded perfectly well by unloading Couatl (after the error message was displayed).

Look, you are probably right in all that you say because you are the developer but on my end it looks like:

- no GSX -> no issues at all with loading the sim and using the sim

- with GSX -> loading hangup's and crashes

Except 3 airports, some PW ACFT and FSLTL, I don't have any MSFS modificators (so my sim is almost vanilla and crashes were a rarity).

I have the same issue and will be dumping GSX. Rather fly and use ambitious pilots pushback than to continue crashing. Just the way it is I guess for some. 

3 minutes ago, Aussie_Dave_04 said:

I have the same issue and will be dumping GSX. Rather fly and use ambitious pilots pushback than to continue crashing. Just the way it is I guess for some. 

I don't think he has updated this in quite some time.  Does it still work?  I might so the same

I've used GSX since the beginning. It has never crashed my sim.

i9-10850K, ASUS TUF GAMING Z490-PLUS (WI-FI), 32GB G.SKILL DDR4-3603 / PC4-28800, GIGABYTE RTX5080 16GB WF OC 3 FAN running 3440x1440 

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.