Author Topic: Constant CTD Immediately After Update to 3.7.4  (Read 1444 times)

robtheump

  • Newbie
  • *
  • Posts: 14
Constant CTD Immediately After Update to 3.7.4
« on: December 27, 2025, 10:19:55 pm »
Hello, I have had absolutely no issues with MSFS2020 until updating to GSX 3.7.4 the other day. After updating GSX Pro to 3.7.4 I get a CTD within 20 seconds of loading into the simulator at a gate. This has happened with numerous repaints using both the PMDG 737-800 and 737-900.

I have tried closing out Couatl before loading a flight and have not had a single CTD when Couatl is not running. If I launch Couatl after loading in the sim it's 50/50 if the sim will CTD while it's loading the GSX database.

I know I've read on here that GSX doesn't cause CTD's but I respectfully have a hard time believing that when I have had nothing but CTD's after the last update and experience no issues when Couatl is not running.

Everything in my sim and my computer is up-to-date and there were no issues until the GSX Pro 3.7.4 update. Any guidance would be appreciated. I think I uploaded the correct log files, if not please let me know what other info you need.

Thank you,
Rob

couatl64boot log:
Quote
12/27/2025 9:50:21 AM: Couatl64_boot Log started
12/27/2025 9:50:21 AM: Working folder set to C:\Program Files (x86)\Addon Manager\couatl64 according to FSDT registry root key
12/27/2025 9:50:21 AM: Thread "couatl64_MSFS.exe"  added to monitoring
12/27/2025 9:50:21 AM: Starting couatl64_MSFS.exe
12/27/2025 9:50:22 AM: Process couatl64_MSFS started successfully with ID 16020
12/27/2025 9:50:22 AM: Connected to Couatl64 shared memory
12/27/2025 10:01:20 AM: Couatl has been closed by user, we are not restarting it
12/27/2025 10:01:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:01:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:01:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:02:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:02:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:02:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:03:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:03:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:03:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:04:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:04:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:04:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:05:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:05:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:05:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:06:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:06:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:06:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:07:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:07:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:07:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:08:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:08:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:08:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:09:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:09:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:09:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:10:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:10:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:10:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:11:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:11:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:11:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:12:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:12:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:12:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:13:22 AM: No processes found for couatl64_MSFS.exe during update
12/27/2025 10:13:22 AM: Process is null or has exited. Attempting to restart.
12/27/2025 10:13:22 AM: Not restarting couatl64_MSFS.exe because shouldRestartCouatl returned false.
12/27/2025 10:14:11 AM: MSFS has exited
12/27/2025 10:14:11 AM: Task was cancelled.

vandalay

  • Newbie
  • *
  • Posts: 6
Re: Constant CTD Immediately After Update to 3.7.4
« Reply #1 on: January 02, 2026, 07:58:45 pm »
Same for me. Since 3.7.4 there is a 50:50 chance for a CTD. Never had these before and what I read all over the internet there are quiet a few reports on CTDs with 3.7.4

DownedAviator

  • Newbie
  • *
  • Posts: 48
Re: Constant CTD Immediately After Update to 3.7.4
« Reply #2 on: January 05, 2026, 09:16:18 pm »
3.7.4 definitely does. 3.7.3 definitely did not.

robtheump

  • Newbie
  • *
  • Posts: 14
Re: Constant CTD Immediately After Update to 3.7.4
« Reply #3 on: January 06, 2026, 01:51:26 am »
What I've found after updating to 3.7.4 is that if I wait to launch AIG Traffic Controller until AFTER I load into the sim and COUATL/GSX is loaded, then I do not get a CTD.

There are numerous threads on the AIG forums about CTD using MSFS and AIG TC after the GSX 3.7.4 update was released.

DownedAviator

  • Newbie
  • *
  • Posts: 48
Re: Constant CTD Immediately After Update to 3.7.4
« Reply #4 on: January 06, 2026, 04:36:11 am »
What I've found after updating to 3.7.4 is that if I wait to launch AIG Traffic Controller until AFTER I load into the sim and COUATL/GSX is loaded, then I do not get a CTD.

There are numerous threads on the AIG forums about CTD using MSFS and AIG TC after the GSX 3.7.4 update was released.

That is the same way that I use the sim, MSFS and GSX which is started by exe.xml are already running. I start AIGTC after I have loaded into my departure airport. As soon as the injector begins to load AI traffic the sim CTD's instantly with 3.7.4 . It never did this with 3.7.3 and that is the only thing that has changed on my computer.
« Last Edit: January 06, 2026, 04:44:19 am by DownedAviator »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 53389
    • VIRTUALI Sagl
Re: Constant CTD Immediately After Update to 3.7.4
« Reply #5 on: January 07, 2026, 03:24:05 pm »
Is anybody having crashes without using any traffic injector ?

robtheump

  • Newbie
  • *
  • Posts: 14
Re: Constant CTD Immediately After Update to 3.7.4
« Reply #6 on: January 11, 2026, 01:44:45 am »
Just wanted to report no further CTD's after updating to 3.7.5.

Thank you for the fix!

Maverick3333

  • Newbie
  • *
  • Posts: 16
Re: Constant CTD Immediately After Update to 3.7.4
« Reply #7 on: January 11, 2026, 08:51:54 am »
okay 3.7.4 where with PMDG and BATC and without stable but nice to hear that there is 3.7.5 out.
General question:

What is the recommend way to update (because I don't see for what is what) to use the FSDTInstaller or FSDT Liveupdate (are there generally the same)?

best regards

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 53389
    • VIRTUALI Sagl
Re: Constant CTD Immediately After Update to 3.7.4
« Reply #8 on: January 14, 2026, 11:20:57 pm »
What is the recommend way to update (because I don't see for what is what) to use the FSDTInstaller or FSDT Liveupdate (are there generally the same)?

They are exactly the same identical .exe, just that:

- when you call it from the "Live Update" icon, it will run with a minimized interface and will do only ONE thing: update all FSDT installed products at once.

- when you call it from the "Installer" icon, it can do many other things (install/uninstall/activate/deactivate, etc.) and you decide what you want to update.