Bug Report: MSFS 2024 Crashes Related to WTF.dll & FMA Issues

[tkemp66]

Just got myself another error also after flying more than 4hrs from KMIA-KSFO, in a default A350 (white livery) and stilll about 300nm to go:

Faulting module name: grammar.pggmod, version: 76.0.0.3, time stamp: 0x63ee0f54

I took PMDG 772 in the skies on Friday night and completed an 11 hour flight no problem. Either way, I'm not sure what/who to blame at this point.

Edited May 11 by tkemp66

[tesla]

I have noticed that many people have this issue, which occurred after the 1.0.8 version update. Before, I had no problems, but now I am unable to complete any flight, even if it is only an hour long route,I have used various methods, such as those suggested by the team or other brothers in the forum.

I fly every day and I also have two simulators for 2020 and 2024,There won't be any problems in 2020, even if it flies for a day and a night,At first, I thought it was a problem with my own simulator, but the 2020 A350 and 2024 Boeing 777 proved otherwise.

We all love A350 very much, so we really hope to use it to complete every flight mission, but the current results are not like that,Many people have raised this issue, wondering if the team should take it seriously. We have spent money but cannot fly, so there should be no such reason. I have no responsibility to anyone or complain about the quality of the plane, but I just want it to be taken seriously. I don't think this is excessive. Thank you very much for every update from the team.

[JS2Tango]

Sim just crashed flying KDFW to LFPG - no error in the event viewer, just closed down. No other aircraft does this in the sim. So frustrating, third long haul attempt with v1.0.9 and third crash - I had a usable aircraft prior to this update! 

[CR7]

Not just the 2024!

I got twice the WTF.dll crash in MSFS2020. 

Edited May 11 by CR7

[San Lin]

In 1.0.9 still got coherentuigt.dll crash yesterday if I use navigraph data.

But in the next flight,I change the Navdata to sim-default,the sim didnt crash.

This bug still not be fixed,right？

Edited May 12 by San Lin

[AVGA]

Also got a coherentUIGT error my first time out with the latest update. Hadn’t happened with prior versions, so didn’t know about the nav data workaround. Will try it, but the bug is definitely not fixed with the update. 

[Galf]

Just crashed, again, CoherentUIGT too for me. About 30 minutes after takeoff from LIMC, happened when I pushed the reset view button - it always happens when you press a button, even though it may be a random one, it never happens if you do not interact with anything.

this is my CTD history on Discord: https://discord.com/channels/535246634448191499/1364649314399424626

This is the current case from today:

Edit I AM USING SIM DATA NOT NAVIGRAPH! 
 

Quote

Faulting application name: FlightSimulator2024.exe, version: 1.3.25.0, time stamp: 0x00000000 Faulting module name: CoherentUIGT.dll, version: 2.9.5.0, time stamp: 0x6749d3e5 Exception code: 0xc0000005 Fault offset: 0x000000000007877c Faulting process id: 0x79F0 Faulting application start time: 0x1DBC3EA1DC5FC85 Faulting application path: H:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe Faulting module path: H:\SteamLibrary\steamapps\common\Limitless\CoherentUIGT.dll Report Id: af17b19d-fd3d-4a41-946b-538a3e7e18e8 Faulting package full name: Faulting package-relative application ID:

 

Edited May 13 by Galf

[N77022]

Crash within 30 seconds of loading into 1.0.10

 

Faulting application name: FlightSimulator2024.exe, version: 1.3.23.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.3.23.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000037548ca
Faulting process id: 0x10C8
Faulting application start time: 0x1DBC404439C474B
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Report Id: 42281190-ff38-42b9-9633-cb876391d581
Faulting package full name: Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

 

Edited May 13 by N77022

[SUB750T]

Guys,

 

Latest Nvidia Drivers are the issues for the crashes 10.0.10/9/8. Use 572.83 (CLEAN INSTALL) as any newer diver does WTF.dll crash your game or a freeze. Using 5080 Water Force Gigabyte and have this problem with anything 576.02 and up. The plane work great now on long hauls 15 hours +. using the -1000 variant as -900 has still no in cockpit copilot. Happy flying.

[Galf]

On 5/14/2025 at 11:01 PM, SUB750T said:

Guys,

 

Latest Nvidia Drivers are the issues for the crashes 10.0.10/9/8. Use 572.83 (CLEAN INSTALL) as any newer diver does WTF.dll crash your game or a freeze. Using 5080 Water Force Gigabyte and have this problem with anything 576.02 and up. The plane work great now on long hauls 15 hours +. using the -1000 variant as -900 has still no in cockpit copilot. Happy flying.

 

This is incorrect, I also have a 5080 by the way. Nvidia drivers are not related to the crash, or at least none of the versions solve it. Clean installs do not solve crashes. I had these same exact crashes with older drivers, and a clean DDU reinstall from safe mode did not solve them. (I am on 576.52 now)
Also, this is the only plane that crashes.

Just had another CTD: CoherentUIGT.dll - this time almost completed the flight, I had just taxied out of the runway.

Faulting application name: FlightSimulator2024.exe, version: 1.4.20.0, time stamp: 0x00000000
Faulting module name: CoherentUIGT.dll, version: 2.9.5.0, time stamp: 0x67b87f2f
Exception code: 0xc0000005
Fault offset: 0x00000000000787bc
Faulting process id: 0x71A8
Faulting application start time: 0x1DBCBCCBF566505
Faulting application path: H:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe
Faulting module path: H:\SteamLibrary\steamapps\common\Limitless\CoherentUIGT.dll
Report Id: cdd9ab9c-6d5e-47b9-8cb4-7c326e0da363
Faulting package full name: 
Faulting package-relative application ID: 

I pasted the crash dump inside the relevant discussion un Discord as it's too large to attach here.