[MSFS 2024] GSX Pro – Couatl64_MSFS2024.exe deterministic CLR access violation (

[thegreek]

Thanks again for the detailed input. I continued testing to narrow this down as cleanly as possible.

To rule out any SU4 beta-specific behavior, I completely opted out of the SU4 Beta and reverted MSFS 2024 back to SU3 (official stable version).
After the downgrade, I tested again with the same aircraft (Fenix A320), same settings, same route and again with GSX fully installed.

Here are the results from SU3:

1. Flight was stable until shutdown and deboarding
I completed the flight without any issues.
After parking, shutting down engines and starting the GSX deboarding, everything seemed fine.

2. Crash occurred again shortly afterwards
This time on SU3 I got the exact same two errors as before:

Couatl64_MSFS2024.exe → clr.dll 
Exception code: 0xc0000005 
Offset: 0x657c 
Exit code: 80131506

followed again by:

FlightSimulator2024.exe → dxgi.dll (0xc0000005)

So the full crash chain is identical on SU3 and SU4.

3. Crash signature is always the same
Regardless of SU3 or SU4, the fault offset and exit code match 1:1 across all tests.
This makes it extremely unlikely that the issue is related to Navigraph, Windows, drivers, antivirus, or file corruption on my system.

4. With GSX uninstalled, both SU3 and SU4 run completely stable
No errors in Event Viewer, no clr.dll entries, and no CTDs at all.


Based on all these tests, the issue seems to be reproducible on both SU3 and SU4 as long as Couatl64_MSFS2024.exe is running.
If needed, I can provide the WER crash reports, but the signature is always identical.

Happy to offer any additional logs if that helps to track down the root cause.

Best regards

[BrzI]

Try setting Couatl64_MSFS2024.exe to Windows 8 compatibility mode.

[srcooke]

Try setting Couatl64_MSFS2024.exe to Windows 8 compatibility mode.

That appears to have worked for me.

[virtuali]

I'm sorry but, I can only repeat and confirm those events you are seeing are MISLEADING you GSX is the "cause" of the crash, when in fact is the victim. Yes, you said without GSX is not happening, but that must have been a coincidence during the flight.

The ONLY thing that you can "relate" to GSX is a problem with Navdata (and with "Navdata" I don't automatically mean "Navigraph", anything is Navdata, from default to add-on airports) and that's the only case where you will be seeing something that happens with GSX and doesn't happen with GSX and would make the sim crash, but it's NOT GSX's fault, it's a fault of the Navdata. Again, either the API or the Navdata itself, it can be ANY of these two things.

This would cause the Couatl engine to crash because the bad Navdata it received in input made it crash, and the CLR.DLL "error" is not even a real error, it's completely harmless and it's related to the way resources are cleaning due to the abrupt crash.

Then, the simulator is crashing itself for the same reason, and you are mislead it's the Couatl engine that caused it, but just because the bad data that made GSX crash, is also making crash the sim crash because GSX queried for it

In any case, in the upcoming update, we added a lot of extra checks to be sure we catch bad Navdata that comes back from the sim, so it should be more unlikely that you'll see a crash in flight because of that.

[72westy]

Received these December 02, 2025...(MSFS 2024 SU3)


Log Name:      Application
Source:        Application Error
Date:          12/2/2025 1:50:24 PM
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:     
User:          DESKTOP-AFGL0LD\usnao
Computer:      DESKTOP-AFGL0LD
Description:
Faulting application name: couatl64_MSFS.exe, version: 5.0.0.6196, time stamp: 0x6915c947
Faulting module name: clr.dll, version: 4.8.9323.0, time stamp: 0x68c9b9f3
Exception code: 0xc0000005
Fault offset: 0x000000000000657c
Faulting process id: 0x29C8
Faulting application start time: 0x1DC63D2B7606078
Faulting application path: C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 0e4f3635-b11a-46db-b9a6-5bfcb5db42fd
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-12-02T21:50:24.6014621Z" />
    <EventRecordID>88107</EventRecordID>
    <Correlation />
    <Execution ProcessID="8652" ThreadID="22396" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-AFGL0LD</Computer>
    <Security UserID="S-1-5-21-2400603791-3703659137-366786281-1002" />
  </System>
  <EventData>
    <Data Name="AppName">couatl64_MSFS.exe</Data>
    <Data Name="AppVersion">5.0.0.6196</Data>
    <Data Name="AppTimeStamp">6915c947</Data>
    <Data Name="ModuleName">clr.dll</Data>
    <Data Name="ModuleVersion">4.8.9323.0</Data>
    <Data Name="ModuleTimeStamp">68c9b9f3</Data>
    <Data Name="ExceptionCode">c0000005</Data>
    <Data Name="FaultingOffset">000000000000657c</Data>
    <Data Name="ProcessId">0x29c8</Data>
    <Data Name="ProcessCreationTime">0x1dc63d2b7606078</Data>
    <Data Name="AppPath">C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe</Data>
    <Data Name="ModulePath">C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll</Data>
    <Data Name="IntegratorReportId">0e4f3635-b11a-46db-b9a6-5bfcb5db42fd</Data>
    <Data Name="PackageFullName">
    </Data>
    <Data Name="PackageRelativeAppId">
    </Data>
  </EventData>
</Event>


Log Name:      Application
Source:        .NET Runtime
Date:          12/2/2025 1:50:24 PM
Event ID:      1023
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-AFGL0LD
Description:
Application: couatl64_MSFS.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFE6293657C (00007FFE62930000) with exit code 80131506.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1023</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2025-12-02T21:50:24.1097232Z" />
    <EventRecordID>88106</EventRecordID>
    <Correlation />
    <Execution ProcessID="10696" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-AFGL0LD</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: couatl64_MSFS.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFE6293657C (00007FFE62930000) with exit code 80131506.
</Data>
  </EventData>
</Event>

[72westy]

I also ran the following commands (w/admin rights) and all completed successfully and without error/s. In the following order:

Dism.exe /online /Cleanup-Image /checkhealth

Dism.exe /online /Cleanup-Image /scanhealth

Dism.exe /online /Cleanup-Image /Restorehealth

sfc /scannow

Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Dism.exe /Online /Cleanup-Image /StartComponentCleanup

RESTARTED computer as the last step.

I did prior to the aforementioned event log (on this page) deactivate and uninstall GSX and the sim (MSFS2024 - SU3) ran without any event log/s showing up for several days.

System specs:

MSI Codex Series R2 B14NUC7-095US
Windows 11 Home 25H2 26200.7309
i7 14700F
MSI Pro B760 VC Wifi II (AMI BIOS 7D98vBG 2025-09-04)
RTX 5060ti OC - Drivers 581.80
32GB DDR5 5600mhz
2TB MSI M482 nVME (C:)
Neo Forz a NFS011SA31T-60 SCSI Disk Device (E:)
Kingspec SATA SSD 4TB (I:)
4TB SPCC SSD 4TB (D:)
4TB Crucial CT4000P3PSSD8 nVME (F:) MSFS20/24 Installed here
Seagate Backup+ Drive (G:)
650w Gold PSU

[72westy]

Screenshot of event log....

[72westy]

The following was while just in the menu of the sim (no flight). The sim itself did not crash. Also another round (2) of the same previous event logs as post #19

Source
Couatl™ Scripting Engine for MSFS/P3D

Summary
Stopped working

Date
‎12/‎4/‎2025 11:14 PM

Status
Report sent

Description
Faulting Application Path:   C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS2024.exe

Problem signature
Problem Event Name:   APPCRASH
Application Name:   couatl64_MSFS2024.exe
Application Version:   5.0.0.6195
Application Timestamp:   6915c8fa
Fault Module Name:   clr.dll
Fault Module Version:   4.8.9323.0
Fault Module Timestamp:   68c9b9f3
Exception Code:   c0000005
Exception Offset:   000000000000657c
OS Version:   10.0.26200.2.0.0.768.101
Locale ID:   1033
Additional Information 1:   57d1
Additional Information 2:   57d1b217b3631ca7a6013087c8f7eca7
Additional Information 3:   c538
Additional Information 4:   c538e722e53794d13501ae6b830c110e

Extra information about the problem
Bucket ID:   ee91ad65579dd474f675171d89ddc200 (1618225056744063488)

[virtuali]

The following was while just in the menu of the sim (no flight). The sim itself did not crash. Also another round (2) of the same previous event logs as post #19

Sure, the sim won't crash, we already established the Couatl engine cannot crash the sim. I still cannot reproduce this, even making hours-long flight. Have you possibly changed something in the properties  for the Couatl .exe ?

By default, we install it with NO compatibility options so: "Running as Admin" is not enabled and no Compatibility option is enabled either so, first, verify they are like this. However some user reported they had better results by enabling Windows 8 compatibility, this is likely depending by which version of .NET they have installed.

[72westy]

No changes after clean install. It is strange indeed.

What is odd is the sim works as does GSX if I pull the menu up from within the sim.

[72westy]

Saved event log

[72westy]

Enabled compatibility mode ( for couatl64_MSFS & couatl_MSFS2024 and have yet to see anymore events in Windows log thus far. Will monitor.

[PilotGW]

I've not tried the compatibility mode workaround yet (I kind of feel like we shouldn't have to do that), but this is still happening, multiple times per flight. I can't catch a diagnostic log, because the log resets every time couatl automatically restarts, and no panic log is generated.

Code: [Select]

Faulting application name: couatl64_MSFS2024.exe, version: 5.0.0.6219, time stamp: 0x69497eb7
Faulting module name: clr.dll, version: 4.8.9310.0, time stamp: 0x67db4f32
Exception code: 0xc0000005
Fault offset: 0x000000000000657c
Faulting process id: 0x3DA0
Faulting application start time: 0x1DC74C403000721
Faulting application path: E:\Microsoft Flight Simulator Common\Addons\Utilities\Addon Manager\couatl64\couatl64_MSFS2024.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 1cecb814-9752-4ffb-8cfb-6b4443f5a00b
Faulting package full name:
Faulting package-relative application ID:

To add to the fun, couatl64_MSFS2024.exe is now randomly crashing while boarding / deboarding since 3.7.4. All vehicles, passengers, VDGS just randomly disappear at times.

Code: [Select]

Faulting application name: couatl64_MSFS2024.exe, version: 5.0.0.6219, time stamp: 0x69497eb7
Faulting module name: couatl64_MSFS2024.exe, version: 5.0.0.6219, time stamp: 0x69497eb7
Exception code: 0xc0000005
Fault offset: 0x000000000005f66e
Faulting process id: 0x1AD4
Faulting application start time: 0x1DC74C544F7B0AE
Faulting application path: E:\Microsoft Flight Simulator Common\Addons\Utilities\Addon Manager\couatl64\couatl64_MSFS2024.exe
Faulting module path: E:\Microsoft Flight Simulator Common\Addons\Utilities\Addon Manager\couatl64\couatl64_MSFS2024.exe
Report Id: bd1a1e0d-b189-4357-b8cc-cd600586a963
Faulting package full name:
Faulting package-relative application ID:
And yes, I've tried completely uninstalling and reinstalling GSX again, too.

[tommydude2002]

I see this exact same issue and it has been happening to me for quite some time. Whenever I reposition the aircraft after spawning from free flight world map, the couatl will immediate ly crash and the VDGS will quickly flash WAIT/TEST in red. Event viewer caught well over 100 of these crashes in the past few months.
 AppName couatl64_MSFS2024.exe
  AppVersion 5.0.0.6213
  AppTimeStamp 6943dd1a
  ModuleName clr.dll
It always points to  ModulePath C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll

[tommydude2002]

Every single of these entries are caused by couatl crashing with clr.dll. It crashed 65 times since November 30th. And to add on what PilotGW has described. The APIS/APIS Small modules in 3.7.4 are randomly disappearing either right at the beginning of the boarding process or a few minutes into it.