FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: Ricie on January 17, 2025, 01:44:09 pm
-
Hello,
I have this error almost anytime midflight, msfs2024.
(https://cdn.discordapp.com/attachments/1322655501938327612/1322655502097842299/image.png?ex=678b5fad&is=678a0e2d&hm=47ca0b93e7fcb009bcd60ef41b603f576960754fa9e41ccd8838a9a654eff347&)
How can i fix it?
-
What are your system specs.
-
AMD Ryzen 7 7700X, 32GB DDR5, RTX 4070 Super. Had never problems to run GSX. It's since msfs 2024. Have used it so many times in 2020. But this error is always in 2024 midflight. At the start of the flight everything works well.
-
Getting the same in MSFS 2024.
-
Please Attach your restarter log, found here:
%APPDATA%\Virtuali\couatl64_boot.log
-
Please Attach your restarter log, found here:
%APPDATA%\Virtuali\couatl64_boot.log
Sorry, that it took so long. Here is one example ...
Oliver
-
It's strange, your log doesn't show any errors.
-
Okay, lets try again with this one ...
Oliver
-
Can you point me to the GSX custom profile you are using ?
-
I'm having the same popup error.
It's boring because it puts itself in focus and move the game to background, forcing to close it.
Seems it happens when approaching an airport which may not be covered or prepared for GSX.[/img]
-
Have the same issue. It went away after I removed the x64 version MS Visual C++2015-2022 Redistributable.
It came back today with an update to my AMD adrenaline software.
Is it possible to force GSX Pro the refer to the x64 redistributable ? (Presuming that is the culprit)
Application: couatl64_MSFS2024.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FF9D085657C (00007FF9D0850000) with exit code 80131506.
-
I downloaded the latest versions of both the x86 and x64 versions but it did not help.
https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-supported-redistributable-version.
Is it possible to disable the concurrent garbage collector for couatl64_MSFS2024.exe ?
Also:
2025-10-29 9:24:03 PM: Couatl64_boot Log started
2025-10-29 9:24:03 PM: Working folder set to F:\Addon Manager\couatl64 according to FSDT registry root key
2025-10-29 9:24:03 PM: Thread "couatl64_MSFS2024.exe" added to monitoring
2025-10-29 9:24:03 PM: Starting couatl64_MSFS2024.exe
2025-10-29 9:24:03 PM: Process couatl64_MSFS2024 started successfully with ID 18768
2025-10-29 9:24:04 PM: Connected to Couatl64 shared memory
2025-10-29 9:30:03 PM: No processes found for couatl64_MSFS2024.exe during update
2025-10-29 9:30:03 PM: Process is null or has exited. Attempting to restart.
2025-10-29 9:30:03 PM: RESTARTING couatl64_MSFS2024.exe
2025-10-29 9:30:03 PM: Process couatl64_MSFS2024 started successfully with ID 23948
2025-10-29 9:30:03 PM: Will monitor focus for 60000ms after restart
2025-10-29 9:31:03 PM: No processes found for couatl64_MSFS2024.exe during update
2025-10-29 9:31:03 PM: Process is null or has exited. Attempting to restart.
2025-10-29 9:31:03 PM: RESTARTING couatl64_MSFS2024.exe
2025-10-29 9:31:03 PM: Grace period ending - performing final focus check
2025-10-29 9:31:03 PM: MSFS already has focus at end of grace period
2025-10-29 9:31:03 PM: Process couatl64_MSFS2024 started successfully with ID 21932
2025-10-29 9:42:29 PM: MSFS has exited
2025-10-29 9:42:29 PM: Task was cancelled.
-
Is it possible to disable the concurrent garbage collector for couatl64_MSFS2024.exe ?
THere's no garbage collector at all in couatl64_MSFS2024.exe , it's not a .NET app, it's a native x64 unmanaged app, so it handles memory on its own, without any connection to the .NET garbage collector.
-
same here; downloaded both, tried the game and seemed to be everything fine.
today new game, the error returned.
-
Try running the FSDT updater now, we released a small hotfix to the couatl64_boot.exe that *might* improve this.
-
That FSDT updater fix did not work - sadly.
fwiw - I started noticing this issue after switching from an IPS monitor to an OLED TV where I enabled HDR, DolbyVision and switched from 8 bpc to 12 bpc colour depth.... I doubt this is relevant but there you have it.
Thanks for trying to fix the issue.
-
For me, errors continue to appear even after updated (as suggested).
thanks!
-
Jepp, still the same here.
Getting the error midflight, on approach or departure. In various European regions and Japan.
No matter what aircraft, without ANY GSX airport/ aircraft profiles, even with CLEAN Community folder ...
Reproducible, taking off from EDDF heading west, half way between EDDF and ETOU (one example of many ..)
MSFS 2024 SU Beta 4 (latest) but also SU-3
(incl. fresh install, due to SSD change)
Windows 11 Pro (up2date) Latest nvidia driver ( 581.80)
The couatl log and bootlog do not show any errors or hints ...
-
AND this one while spawning in with full Community folder at EDDF (Aerosoft)
First time i am seeing this happen ...
Oliver
-
Please try setting compatibility mode to Windows 8 for couatl64_MSFS2024.exe
Seems to have worked for me..Before the change I had half a dozen Couatl warnings at CYYC. After the change - no warnings.
Did another arrival into EDDF - no warnings either...
-
I'll try that and report back, today ...
Thanks for suggesting ...
-
Did another loop around KDEN - no warnings.
3 in a row so far...
-
Also did a 1hr flight around EDDF and EDFW, EDGU in the Comanche.
I can report not having this error again. (for now ...)
I will continue to test and report here. Since it was reproduceable in above scenario, i strongly believe, this solves the issue ...
I am on a Windows 25H2 install, 23H before , btw ...
@virtuali
-
Please try setting compatibility mode to Windows 8 for couatl64_MSFS2024.exe
Seems to have worked for me..Before the change I had half a dozen Couatl warnings at CYYC. After the change - no warnings.
Did another arrival into EDDF - no warnings either...
gm,
since applying THIS, i've had NO error message popping up,
several flights , several regions ...
-
Problem remains in latest GSX update when running as provided.
WITH the Windows 8 compatibility set -> No issues (as before)