couatl64_MSFS.exe causing CTDs

User Support Hub Crashes (CTDs)
, ,
1

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

No. Completely disabling GSX may resolve the problem, but it is normally started with MSFS.

Brief description of the issue:

The coatl64_MSFS.exe app causes CTDs at random times. This app is part of the GSX suite. GSX is not being used when the crashes occur. Multiple aircraft are affected (TBM850, FSR500, PMDG 737). The CTD always happens in mid-flight, not at an airport. No specific route of airport appears to be involved. It does not seem to be associated with any GSX profile.
The error occurs in VR (Quest3 headset, Virtual Desktop, VDXR runtime) and has not been tested in flat mode.
Provide Screenshot(s)/video(s) of the issue encountered:

Faulting application name: couatl64_MSFS.exe, version: 4.8.0.5307, time stamp: 0x6541355c
Faulting module name: ntdll.dll, version: 10.0.22621.2428, time stamp: 0x806d3ecf
Exception code: 0xc0000374
Fault offset: 0x000000000010c849
Faulting process id: 0x0x585C
Faulting application start time: 0x0x1DA1593EB1398F2
Faulting application path: C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 0fedbfa4-4ce7-4208-b1f7-2df16397da2f
Faulting package full name:
Faulting package-relative application ID:
Detailed steps to reproduce the issue encountered:

Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version (Learn how to find your current graphics card driver version):

Nvidia GTX 4080 - Driver version 545.84

PC specs and peripheral set up:

AMD 5800X3D processor, 64GB ram, 5TB M2 SSD storage, Nvidia GTX 4080 GPU, Quest3 VR headset, Honeycomb Alpha yoke, Honeycomb Bravo throttle quadrant. Dedicated 1Gbit WiFI6 connection.

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

Fault bucket 1240214271321529594, type 4
Event

Build Version # when you first started experiencing this issue:

This has occurred since SU13,

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

2

Couatl won’t crash MSFS. But MSFS crashing will crash Couatl. Your Event Log will most likely have an entry for an flightsimulator.exe crash before the entry for the Couatl crash.

3

Agree, Couatl itself crashes quite often, but at least in my experience it (never?) drags down MSFS to crash also.
Wen Couatl is dead, just starting it again should restore its functionality without affecting the stability of MSFS. There is now an entry in the toolbar “Restart Couatl”, so that if the ground services are not responding, you can restart it even from inside VR.

4

Hi there,

Thank you for your report! The purpose of the Bug Reports category is to discuss issues that affect the base simulator. If you are having issues with a 3rd party product, please be sure to file a bug report via the developer’s preferred support method.

You can also check out the General Discussion & Community Support sub-categories to see if others have your 3rd party issue to help troubleshoot.

If you believe your issue may be caused by a third-party addon/mod, empty your community folder, restart the simulator and try to reproduce the error.

All issues caused by, or involving third-party addons/mods should be reported to the third-party developer. All issues related to the core simulator can be reported here on the forum or reported through Zendesk.

5

As with any add-on program, having too many objects displaying or too many actions occurring simultaneously will put extra stress on your sim and push it beyond what it can handle. As with all flight simulators, the important thing is to find a balance your setup can manage. That may mean turning down the settings (including GSX’s).

That said, agree with both @MikeB54331 and @jfoguet61, Couatl crashing is a symptom of MSFS CTDs rather than the cause of them.

The Windows Event Viewer will show a Flightsimulator.exe error just prior to a couatl64_msfs.exe error listed in the events log.

6

I have it starting via exe.xml and it starts fine. However it frequently crashes just upon main menu loading (after game finished loading). So this may point to a Simconnect initialization issue.

Cheers

7

You are correct. MSFS is indeed crashing before Couatl!

8

This is the correct answer. MSFS is a very processor intensive application and running too much third party software alongside MSFS can cause problems. Some third party apps such as GSX Pro and FSRealistic tend to cause more issues than others from my experience, especially when paired with the more advanced airliners like the PMDG, Fenix A320, etc.

2 Likes
9

If that was the case then MSFS could not handle the native AI traffic, nor the native airport services or the native wind turbines animations. At Alta wind farm you can see how game handles 2500 windturbines, together with existing scenery, existing AI traffic and existing weather. That alone are much more simultaneous objects and instances that the ones GSX or any other third party apps need to manage at once. Third party software is not the reason for all problems in this world.

Cheers

1 Like
10

not to mention its a bug ridden sim

11

It cant crash MSFS by itself, because it is running completely separate from MSFS. This was confirmed by the developer. Couatl crashing, will not lead to an MSFS crash. It has to be the other way round: MSFS crashed and therefore Couatl crashed. Check the Eventmanager BEFORE the couatl crash in the log.

Unbenannt
Unbenannt1536Ă—357 88.9 KB