couatl64_MSFS2024.exe randomly crashing in the background

Products Support > GSX Support MSFS

<< < (2/6) > >>

virtuali:
The error seems to indicate a problem with .NET, which is quite strange, since the Couatl64 .exe is NOT a .NET app, it's a native x64 app that doesn't do any call to the .NET framework. So, I wonder if this might be something else entirely, like another app (antivirus, maybe) that DOES use .NET and attaches to the Couatl64.exe, which is what antivirus usually do to check.

72westy:
Sorry for the late response. I use Avast free edition and I have exception within it for... c:\Program Files (x86) Addon Manager\*

Also found these in event viewer...

Log Name: Application
Source: Application Error
Date: 11/4/2025 7:07:17 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: DESKTOP-AFGL0LD\usnao
Computer: DESKTOP-AFGL0LD
Description:
Faulting application name: Couatl64_MSFS2024.exe, version: 5.0.0.6020, time stamp: 0x68a72d4d
Faulting module name: ucrtbase.dll, version: 10.0.26100.7019, time stamp: 0x55eee9bf
Exception code: 0xc0000409
Fault offset: 0x00000000000a4ace
Faulting process id: 0x2594
Faulting application start time: 0x1DC4DFE922FC8A8
Faulting application path: C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS2024.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 3fdd62ea-fba5-4aea-84fd-cc970ca2341e
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
<EventID>1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2025-11-05T03:07:17.6403883Z" />
<EventRecordID>79914</EventRecordID>
<Correlation />
<Execution ProcessID="7880" ThreadID="22860" />
<Channel>Application</Channel>
<Computer>DESKTOP-AFGL0LD</Computer>
<Security UserID="S-1-5-21-2400603791-3703659137-366786281-1002" />
</System>
<EventData>
<Data Name="AppName">Couatl64_MSFS2024.exe</Data>
<Data Name="AppVersion">5.0.0.6020</Data>
<Data Name="AppTimeStamp">68a72d4d</Data>
<Data Name="ModuleName">ucrtbase.dll</Data>
<Data Name="ModuleVersion">10.0.26100.7019</Data>
<Data Name="ModuleTimeStamp">55eee9bf</Data>
<Data Name="ExceptionCode">c0000409</Data>
<Data Name="FaultingOffset">00000000000a4ace</Data>
<Data Name="ProcessId">0x2594</Data>
<Data Name="ProcessCreationTime">0x1dc4dfe922fc8a8</Data>
<Data Name="AppPath">C:\Program Files (x86)\Addon Manager\couatl64\Couatl64_MSFS2024.exe</Data>
<Data Name="ModulePath">C:\WINDOWS\System32\ucrtbase.dll</Data>
<Data Name="IntegratorReportId">3fdd62ea-fba5-4aea-84fd-cc970ca2341e</Data>
<Data Name="PackageFullName">
</Data>
<Data Name="PackageRelativeAppId">
</Data>
</EventData>
</Event>

72westy:
Log Name: Application
Source: Windows Error Reporting
Date: 11/4/2025 7:07:20 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: DESKTOP-AFGL0LD\usnao
Computer: DESKTOP-AFGL0LD
Description:
Fault bucket 1399046419245935729, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: Couatl64_MSFS2024.exe
P2: 5.0.0.6020
P3: 68a72d4d
P4: ucrtbase.dll
P5: 10.0.26100.7019
P6: 55eee9bf
P7: 00000000000a4ace
P8: c0000409
P9: 0000000000000007
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0c4f4571-80bc-4cb5-8837-6fea3401bbef.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.049f1ced-cbf1-4200-a769-a4267adad72d.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20251101_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.22c03db1-593a-4184-a30d-2761ecd1d691.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ccd1acad-0d95-4f81-8ec7-f34ba0a1df95.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1ec01ea5-2bc6-491f-b57f-b626e4ae5c4d.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bc711c2b-9ba7-4310-bd72-c37ae324c7ff.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f845049c-d1a5-4bf7-8f67-756633bfc71a.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Couatl64_MSFS202_8edc393eafdcf9a555c2499e7b4b2a6d5c2f1_617723cf_777cb840-f05b-4c88-802e-64d21f635bcb

Analysis symbol:
Rechecking for solution: 0
Report Id: 3fdd62ea-fba5-4aea-84fd-cc970ca2341e
Report Status: 268435456
Hashed bucket: 8b684033b82d1550136a694e4b6fac71
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" />
<EventID>1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2025-11-05T03:07:20.6923455Z" />
<EventRecordID>79915</EventRecordID>
<Correlation />
<Execution ProcessID="7880" ThreadID="22860" />
<Channel>Application</Channel>
<Computer>DESKTOP-AFGL0LD</Computer>
<Security UserID="S-1-5-21-2400603791-3703659137-366786281-1002" />
</System>
<EventData>
<Data Name="Bucket">1399046419245935729</Data>
<Data Name="BucketType">5</Data>
<Data Name="EventName">BEX64</Data>
<Data Name="Response">Not available</Data>
<Data Name="CabId">0</Data>
<Data Name="P1">Couatl64_MSFS2024.exe</Data>
<Data Name="P2">5.0.0.6020</Data>
<Data Name="P3">68a72d4d</Data>
<Data Name="P4">ucrtbase.dll</Data>
<Data Name="P5">10.0.26100.7019</Data>
<Data Name="P6">55eee9bf</Data>
<Data Name="P7">00000000000a4ace</Data>
<Data Name="P8">c0000409</Data>
<Data Name="P9">0000000000000007</Data>
<Data Name="P10">
</Data>
<Data Name="AttachedFiles">
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.0c4f4571-80bc-4cb5-8837-6fea3401bbef.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.049f1ced-cbf1-4200-a769-a4267adad72d.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20251101_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.22c03db1-593a-4184-a30d-2761ecd1d691.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ccd1acad-0d95-4f81-8ec7-f34ba0a1df95.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1ec01ea5-2bc6-491f-b57f-b626e4ae5c4d.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bc711c2b-9ba7-4310-bd72-c37ae324c7ff.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f845049c-d1a5-4bf7-8f67-756633bfc71a.tmp.xml</Data>
<Data Name="StorePath">\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Couatl64_MSFS202_8edc393eafdcf9a555c2499e7b4b2a6d5c2f1_617723cf_777cb840-f05b-4c88-802e-64d21f635bcb</Data>
<Data Name="AnalysisSymbol">
</Data>
<Data Name="Rechecking">0</Data>
<Data Name="ReportId">3fdd62ea-fba5-4aea-84fd-cc970ca2341e</Data>
<Data Name="ReportStatus">268435456</Data>
<Data Name="HashedBucket">8b684033b82d1550136a694e4b6fac71</Data>
<Data Name="CabGuid">0</Data>
</EventData>
</Event>

srcooke:
Seeing the same issue with the exact same details posted by the OP.

thegreek:
Hi,

after several test flights and detailed Event Viewer / WER log reviews, I can confirm a consistent crash chain related to GSX (Couatl64_MSFS2024.exe) when running the MSFS 2024 SU4 Beta.
The issue occurs reproducibly during approach or shortly before touchdown.

Error pattern
Each sequence follows the same pattern:

Couatl64_MSFS2024.exe → ucrtbase.dll (0xc0000409)
Couatl64_MSFS2024.exe → clr.dll (0xc0000005)
[repeats several times]
FlightSimulator2024.exe → dxgi.dll (0xc0000005)

After the initial Couatl64 crash, the simulator continues for a while, then terminates with the usual DXGI Access Violation.

Technical observation
The statement that “Couatl64.exe is a native app not using .NET” does not fully explain the logs.
Windows Event Viewer clearly identifies clr.dll (Common Language Runtime) as the faulting module, which can only appear if a managed (.NET) component or runtime dependency is being loaded.

Couatl internally relies on Python and SimConnect, using Microsoft Visual C++ Runtimes and occasionally .NET-bound libraries through the bglmanx64 bridge.
The simultaneous faults in ucrtbase.dll (C Runtime) and clr.dll (.NET Runtime) strongly indicate a thread or memory-race condition inside the Couatl process itself, not an external injection.

If antivirus software were responsible, crash offsets and modules would vary between users.
However, multiple users (see https://forums.flightsimulator.com/t/couatl64-msfs2024-exe-issue/743940
) report the identical crash offset 0x657c in clr.dll, regardless of whether they use Defender, Avast, BitDefender, or no antivirus at all.
This consistency rules out external processes as the root cause.

Relation to SU4 Beta changes
MSFS 2024 SU4 introduced asynchronous SimConnect calls and new internal caching for Atmosphere / Airspeed SimVars (see changelog: “Fixed concurrent accesses …”).
It appears GSX may still perform synchronous or unsynchronized writes to these SimVars, which results in the .NET and C-Runtime exceptions in Couatl64 and ultimately leads to the DXGI crash in the simulator.

Suggested next steps
• Review Couatl’s SimConnect threading and exception-handling layer under SU4.
• Add diagnostic logging around SimVar writes or network threads.
• Reproduce with GSX active, no other add-ons, DX12 enabled, SU4 Beta.

This issue is reproducible and independent of antivirus software.
It would be very helpful if the dev team could investigate the Couatl64 → clr.dll crash path directly, as it consistently precedes every dxgi.dll CTD.

Best regards

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version