Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Continue crashing MSFS2020

Featured Replies

Good Day 

I am seeking some help and advise about my new issue started last week , after running the sim for 10 minutes and regardless in VR or not my MSFS2020 crashes and shuts down with the following error . I tried reading what is the reason by searching but no luck. Anyone can  advise me what to do I will really appreciate it .

Kind Regards 

 

Faulting application name: couatl64_MSFS.exe, version: 4.8.0.5381, time stamp: 0x65de2a30
Faulting module name: ntdll.dll, version: 10.0.19041.3996, time stamp: 0x39215800
Exception code: 0xc0000374
Fault offset: 0x00000000000ff349
Faulting process id: 0x2db8
Faulting application start time: 0x01da72f00203dae4
Faulting application path: C:\Program Files (x86)\Addon Manager\couatl64\couatl64_MSFS.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 74247168-0c1d-4983-a276-cfcbbede8026
Faulting package full name: 
Faulting package-relative application ID: 

My system specs :

OS Name    Microsoft Windows 10 Pro
Version    10.0.19045 Build 19045

System Name    ASUS-PC
System Manufacturer    Gigabyte Technology Co., Ltd.
System Model    Z790 AORUS MASTER X
System Type    x64-based PC
System SKU    Default string
Processor    Intel(R) Core(TM) i9-14900KF, 3200 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date    American Megatrends International, LLC. F5, 12/14/2023
SMBIOS Version    3.6
Embedded Controller Version    255.255
BIOS Mode    UEFI
BaseBoard Manufacturer    Gigabyte Technology Co., Ltd.
BaseBoard Product    Z790 AORUS MASTER X
BaseBoard Version    x.x
Platform Role    Desktop
Secure Boot State    Off
PCR7 Configuration    Elevation Required to View
Windows Directory    C:\WINDOWS
System Directory    C:\WINDOWS\system32
Boot Device    \Device\HarddiskVolume2
Locale    United States
Hardware Abstraction Layer    Version = "10.0.19041.3636"
User Name    ASUS-PC\admin
Time Zone    Eastern Daylight Time
Installed Physical Memory (RAM)    64.0 GB
Total Physical Memory    63.8 GB
Available Physical Memory    53.1 GB
Total Virtual Memory    112 GB
Available Virtual Memory    96.4 GB
Page File Space    48.0 GB
Page File    C:\pagefile.sys
Kernel DMA Protection    Off
Virtualization-based security    Not enabled
Device Encryption Support    Elevation Required to View
Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions    Yes
Hyper-V - Virtualization Enabled in Firmware    Yes
Hyper-V - Data Execution Protection    Yes
 

 

Ask for help to the FS Dream Team (GSX) guys. Looks something's wrong with their Couatl module and your installation, most probably it was not properly updated/installed, who knows?

Cheers, Ed

MSFS2020 Steam  // Rig: Corsair Graphite 760T Full Tower - ASUS MBoard Maximus XII Hero Z490 - CPU Intel i9-10900K - 64GB RAM - MSI RTX2080 Super 8GB - [1xNVMe M.2 1TB + 1xNVMe M.2 2TB (Samsung)] + [1xSSD 1TB + 1xSSD 2TB (Crucial)] + [1xSSD 1TB (Samsung)] + 1 HDD Seagate 2TB + 1 HDD Seagate External 4TB - Monitor LG 29UC97C UWHD Curved - PSU Corsair RM1000x // Thrustmaster FCS & MS XBOX Controllers

13 minutes ago, edpatino said:

Ask for help to the FS Dream Team (GSX) guys. Looks something's wrong with their Couatl module and your installation, most probably it was not properly updated/installed, who knows?

 

Edited by sonny147
deleted

ROG Crossair Hero X670e , 9900X, TUF 4090 , X4 NVME's. OS  2TB 980 Pro , MSFS  2TB WD Black , Kington Fury 64GB ram ( 6000) Corsair RM1000 PSU, Artic Freezer iii 360 AIO  . Phanteks P600s Case ,TCL QM8B 50" 120 Hz  TV,second 24 inch screen for charts you tube etc, and 11" touch screen for the EFB. Warthog Stick and TCA Captains throttle ( full pack)  Velocity 1 Rudder Pedals , extreme3D for the Tiller,Streamdeck XL x2 / Streamdeck +/Streamdeck mini because i like pressing buttons 

just realised that link had my info on it lol

ROG Crossair Hero X670e , 9900X, TUF 4090 , X4 NVME's. OS  2TB 980 Pro , MSFS  2TB WD Black , Kington Fury 64GB ram ( 6000) Corsair RM1000 PSU, Artic Freezer iii 360 AIO  . Phanteks P600s Case ,TCL QM8B 50" 120 Hz  TV,second 24 inch screen for charts you tube etc, and 11" touch screen for the EFB. Warthog Stick and TCA Captains throttle ( full pack)  Velocity 1 Rudder Pedals , extreme3D for the Tiller,Streamdeck XL x2 / Streamdeck +/Streamdeck mini because i like pressing buttons 

  • Author

Thanks a lot for the help I did remove the whole program to test if it affects still and yes again crash of MSFS after an hour flight before landing

Faulting application name: FlightSimulator.exe, version: 1.36.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.36.2.0, time stamp: 0x00000000
Exception code: 0xc000001d
Fault offset: 0x00000000026852ed
Faulting process id: 0x4430
Faulting application start time: 0x01da74927c7b0def
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 71bb405d-dff9-42d4-be57-bb611b3fde03
Faulting package full name: Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I did upgrade my processor , memory recently to I9 however I did a copy of everything ( ghost copy) and recopied back but I did not reinstall everything back could this be the reason ? 

Should I delete MSFS2020 and reinstall the program again and all its supportive programs  ? I appreciate the advise 

Edited by king1706

5 hours ago, king1706 said:

 

I did upgrade my processor , memory recently to I9 however I did a copy of everything ( ghost copy) and recopied back but I did not reinstall everything back could this be the reason ? 

 

Are you overclocking anything? Memory, CPU, GPU? If you have had issues shortly after getting new hardware (a whole new computer), then it could well be that something is not correctly set up (or overclocked). MSFS is very sensitive to overclocking and things that work on other games can cause it to crash.

I would start by running MemTest and a 3d Mark stress test (or other stress tests) to make sure the system is fully stable first. Then look at MSFS specifically. 

9800X3d, 4090, 64 GB DDR5 6000 RAM, 4 TB NVME (2x2), 4K Ultra + Framegen

22 hours ago, king1706 said:

Thanks a lot for the help I did remove the whole program to test if it affects still and yes again crash of MSFS after an hour flight before landing

Faulting application name: FlightSimulator.exe, version: 1.36.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.36.2.0, time stamp: 0x00000000
Exception code: 0xc000001d
Fault offset: 0x00000000026852ed
Faulting process id: 0x4430
Faulting application start time: 0x01da74927c7b0def
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 71bb405d-dff9-42d4-be57-bb611b3fde03
Faulting package full name: Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

I did upgrade my processor , memory recently to I9 however I did a copy of everything ( ghost copy) and recopied back but I did not reinstall everything back could this be the reason ? 

Should I delete MSFS2020 and reinstall the program again and all its supportive programs  ? I appreciate the advise 

Exception code: 0xc000001d is an "invalid instruction" error.

All of us are running the same version of MSFS, so there obviously isn't an actual invalid instruction or we would all be seeing it. Therefore, you most likely have an issue with a supporting routine, like the VC runtime libraries or an OS module that is out of date.

If it was me, I would start by making sure that Windows was fully updated, and that all my Visual C libraries are fully up to date.

I just noticed the CPU upgrade part. Try updating the chipset drivers using the motherboard manufacturer's update checker.

Edited by MDFlier

i9-10850K, ASUS TUF GAMING Z490-PLUS (WI-FI), 32GB G.SKILL DDR4-3603 / PC4-28800, GIGABYTE RTX5080 16GB WF OC 3 FAN running 3440x1440 

 

  • Commercial Member
23 hours ago, king1706 said:

Thanks a lot for the help I did remove the whole program to test if it affects still and yes again crash of MSFS after an hour flight before landing

I wanted to suggest you doing that, so you could have definitive proof GSX didn't had anything to do with the crash, but I see you already done that.

What really happened, and your test without GSX confirms it, the sim crashed for other reasons, and it **made** the Couatl engine crash because, when there's an abrupt crash like that, the Couatl engine, which it's a native, unmanaged, Win64 application so it's tasked to do its own memory clean up instead of relying on the .NET framework to do that, won't get a chance to do its normal cleanup on exit, because the "CLOSE" message from Simconnect it was waiting for never arrived and the connection with the sim was broken abruptly ( because MSFS crashed ), which caused the program to crash, with an Event in the Event Viewer.

This can easily mislead thinking Couatl64_MSFS.exe was the cause, when in fact it was the victim of the unrelated crash in the sim.

  • Author

Thanks for all of you on all these suggestions I will start doing these suggestions and hopefully the issues will be resolved , I really appreciate all the assistance. 

 

Best Regards 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.