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

[fhgh]

I keep experiencing same WTF.DLL crash to desktop. Four times in a row.

Log Name:      Application
Source:        Application Error
Date:          4/28/2025 11:19:09 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-GBL7CC9
Description:
Faulting application name: FlightSimulator2024.exe, version: 1.3.25.0, time stamp: 0x00000000
Faulting module name: WTF.dll, version: 0.0.0.0, time stamp: 0x6749d236
Exception code: 0x80000003
Fault offset: 0x00000000000023cb
Faulting process id: 0x3a68
Faulting application start time: 0x01dbb8536bc45ba3
Faulting application path: C:\steam\steamapps\common\Limitless\FlightSimulator2024.exe
Faulting module path: C:\steam\steamapps\common\Limitless\WTF.dll
Report Id: f9ff0120-154e-4e3e-b916-e377273d91f8
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" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2025-04-28T21:19:09.3650532Z" />
    <EventRecordID>130789</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-GBL7CC9</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator2024.exe</Data>
    <Data>1.3.25.0</Data>
    <Data>00000000</Data>
    <Data>WTF.dll</Data>
    <Data>0.0.0.0</Data>
    <Data>6749d236</Data>
    <Data>80000003</Data>
    <Data>00000000000023cb</Data>
    <Data>3a68</Data>
    <Data>01dbb8536bc45ba3</Data>
    <Data>C:\steam\steamapps\common\Limitless\FlightSimulator2024.exe</Data>
    <Data>C:\steam\steamapps\common\Limitless\WTF.dll</Data>
    <Data>f9ff0120-154e-4e3e-b916-e377273d91f8</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

[WarDog]

Had the same issue, sudden CTD.

One time due to CoherentUIGT.dll and one due WTF.dll.

Both times at around a 1H25min-1H39min mark

Quote

Faulting application name: FlightSimulator2024.exe, version: 1.3.23.0, time stamp: 0x00000000
Faulting module name: WTF.dll, version: 0.0.0.0, time stamp: 0x6749d236
Exception code: 0x80000003
Fault offset: 0x00000000000023cb
Faulting process id: 0x0x12C8
Faulting application start time: 0x0x1DBB9B76CF96A94
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\WTF.dll
Report Id: 24ba6f63-b44b-49fb-a458-d97dc11ed7da
Faulting package full name: Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Quote

Faulting application name: FlightSimulator2024.exe, version: 1.3.23.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: 0x0x87AC
Faulting application start time: 0x0x1DBB9A5C9E99EA9
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\CoherentUIGT.dll
Report Id: 67e68e63-6c87-4664-b670-e55914d8d69b
Faulting package full name: Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

 

[fhgh]

On 4/25/2025 at 9:21 AM, Eddie said:

Hello,

To you all that are having this issue, please attempt the flight in which you crashed using SIM DEFAULT NAVDATA instead of Navigraph source and let me know if that makes a difference. Apologies for the inconvenience. 

Thank you

I can confirm that I didn’t esperienze any wtf.dll issues if using SIM DEFAULT NAVDATA. 

[JS2Tango]

Same issue here. Engaging AP after loading from an autosave produces a nose up pitch and sends the aircraft into A.FLOOR 

[Him]

Hi inibuilds developer,

Here is the case for CTD due to WTF.dll (really wtf...), hope can locate and describe the root cause asap

Flight: RKSI-VHHH

Nearest airport when CTD: RCTP

Sim Time from launching MSFS2024 application to CTD: around 2 hours

Navdata: Navigraph

I have tried to delete all folders related to a350 in both community and WASM folder, also disabled realtek audio in device manager as advised by some users encountered WTF.dll error. I can successfully have a VHHH-RKSI full flight without any CTD yesterday (also using navigraph nav data). But the CTD happened today again.

For time being, is it a workaround that delete all folders related to a350 in both community and WASM folder before starting every full flight to prevent such CTD error?

Thanks.

Edited May 4 by Him

[GL_McQUEEN]

Like i said before for me it's related to the autosave funktion.

 

After recovering I am allways exactly where the sim CDTed.

 

The timestamps of the CTDs and the last autosaves are allway virtually the same.

Edited May 4 by GL_McQUEEN

[Him]

7 hours ago, Him said:

Hi inibuilds developer,

Here is the case for CTD due to WTF.dll (really wtf...), hope can locate and describe the root cause asap

Flight: RKSI-VHHH

Nearest airport when CTD: RCTP

Sim Time from launching MSFS2024 application to CTD: around 2 hours

Navdata: Navigraph

I have tried to delete all folders related to a350 in both community and WASM folder, also disabled realtek audio in device manager as advised by some users encountered WTF.dll error. I can successfully have a VHHH-RKSI full flight without any CTD yesterday (also using navigraph nav data). But the CTD happened today again.

For time being, is it a workaround that delete all folders related to a350 in both community and WASM folder before starting every full flight to prevent such CTD error?

Thanks.

Sadly, I can confirm NOTHING help for delete all folders related to a350 in both community and WASM folder before starting every single flight.

Just CTD again during climb to near TOD for a VHHH-WSSS flight...

[yves3550]

I have few CTD with the -900, but every time I try a glight with the -100,  I have a CTD.

Yves

[Shug]

I don't have autosave enabled. Every day I get crashes either to do with CoherentUIGT.dll or WTF.dll. I haven't found any solution to avoid this. 

Can't Inibuilds advise what we should do? 

I'm feeling that I've just wasted my money and am so disappointed.

[Xenon341]

Did you tried what is suggested in this thread by ini ?

[Cursory]

I believe I've identified what’s causing the WTF.dll module to crash, and here’s how I came to that conclusion:

Yesterday, I began running test flights:
I completed a ~3-hour flight in the -900 variant using the default sim NAV data and the all-white livery. The flight went smoothly from gate to gate with no issues.
I followed up with a much longer ~8-hour flight in the -1000 variant, which ended up lasting nearly 10–11 hours total. This time, I used NAVIGRAPH navigation data, but again stuck with the all-white livery. No issues or crashes occurred.

Today, I decided to fly the FINNAIR livery from Helsinki to Tokyo and during this flight, the WTF.dll module crashed again. While I can’t be 100% certain yet, the pattern suggests that the crashes may be related to liveries, not the navigation data or aircraft variant. I haven’t yet reinstalled the liveries (since I doubt it’ll change anything), but I’ll try that next and share an update tomorrow.

In the meantime, I recommend that anyone experiencing similar issues try flying with the all-white livery, even if it breaks immersion. At least that way, your aircraft should remain functional.

 

[Shug]

6 hours ago, Xenon341 said:

Did you tried what is suggested in this thread by ini ?

The last couple days I have not been able to view the display screens to change the navdata. When I try to load on the runway, all the screens are blank and I get an audio STALL STALL message even though the aircraft is on the ground.

When I try to load at a gate the EXT 1 and EXT 2 show AVAIL but when I click on BAT 1, all I hear is a faint click and nothing powers up. I've tried using the all-white livery but that hasn't made a difference.

[Cursory]

3 hours ago, Shug said:

The last couple days I have not been able to view the display screens to change the navdata. When I try to load on the runway, all the screens are blank and I get an audio STALL STALL message even though the aircraft is on the ground.

When I try to load at a gate the EXT 1 and EXT 2 show AVAIL but when I click on BAT 1, all I hear is a faint click and nothing powers up. I've tried using the all-white livery but that hasn't made a difference.

The all-white livery is what I found resolved the wtf.dll module crashing for me. The only thing I would suggest is a full reinstall if you haven’t tried that already because what you are describing is not what I have seen or heard of until now so nothing as far as I am aware is known about the issue you are having.

[Xenon341]

That is very interesting.
On Discord, according to multiples users, CoherentGTUI.dll seems to be solved with a Nav data change (revert to sim default) but WTF.dll had no lead.

The livery lead might be promising !

For thoses with WTF.dll crash, did you tried to uninstall and re install the liveries ?

[Cursory]

I can pretty much confirm that reinstalling the liveries and then flying with one just causes the WTF.dll module to crash again flying the same route I flew yesterday with the all-white livery without issues. 

[Cursory]

Update:
I just finished a flight with the A350 from gate to gate without issues when flying the all-white livery again so I am 99% sure that the WTF.dll crashes are related to the liveries. I haven't tried flying the inibuilds house livery but it either crashes because it is a livery being applied to the default white one or it doesn't crash because it was included with the plane installation and is not a separate instance. 

If immersion is everything to you don't fly the A350 for the time being, if you don't care: fly the all-white livery and default sim nav data to be on the safe side.

[coxman69]

Same crash for me with WTF.dll

Did anyone try already to check how things work with 1.0.9?

[Him]

For those who faced WTF.dll error, can try not to click the navigraph chart or enroute section in the OIS (can still use navigraph data in 3rd party section) in the whole flight. I have tried multiple flights (using v1.0.8, flight time around 2-3 hours) by doing this seems didn't CTD again. Not sure if it is related.

[coxman69]

5 hours ago, Him said:

For those who faced WTF.dll error, can try not to click the navigraph chart or enroute section in the OIS (can still use navigraph data in 3rd party section) in the whole flight. I have tried multiple flights (using v1.0.8, flight time around 2-3 hours) by doing this seems didn't CTD again. Not sure if it is related.

All I can say is after 1.0.9 rolled out I started a flight without any problems, 12 hours into DOH-JFK without issues and I noticed an improvment in sim performance, so the problem was related to something wrong with 1.0.8

[JS2Tango]

Two WTF.dll errors since installing v1.0.9

[fhgh]

Just completed a flight with version 0.9 and didn’t experience any problems. Hope it was not just luck. 

[Cursory]

11 hours ago, Him said:

For those who faced WTF.dll error, can try not to click the navigraph chart or enroute section in the OIS (can still use navigraph data in 3rd party section) in the whole flight. I have tried multiple flights (using v1.0.8, flight time around 2-3 hours) by doing this seems didn't CTD again. Not sure if it is related.

I never use enroute section but I do use navigraph charts and I had issues when using liveries and didn't when using the all-white livery, this does not necessarily mean anything but I observed consistent crashes and it just working based on if I am flying a livery or all-white. I am still thinking it's the liveries that are involved somehow and maybe even multiple systems contributing to these crashes.

[tkemp66]

4 hours ago, JS2Tango said:

Two WTF.dll errors since installing v1.0.9

I woke up this morning and saw my sim crashed with the WTF.dll error. I'm also runnning V1.09. This flight was from LTFM-KMIA. I haven't completed a flight yet with the A350 in 2024. 

[JS2Tango]

2 hours ago, tkemp66 said:

I woke up this morning and saw my sim crashed with the WTF.dll error. I'm also runnning V1.09. This flight was from LTFM-KMIA. I haven't completed a flight yet with the A350 in 2024. 

I've got over 100 hours in the aircraft in MSFS24, but the two flights I've tried since v1.0.9 have crashed in the first hour with the WTF.dll error. 

Edited Saturday at 07:35 PM by JS2Tango
spelling

[N77022]

Just got a faulting module mimalloc.dll crash on 1.0.9 in FS2024 after about 6hours of flying. So so disappointing. I gave ini the benefit of the doubt and assumed maybe it was something on my end, but the 777-200ER proves that wrong... I've completed probably a dozen long hauls since that airplane's launch. Can't even get halfway through a longhaul on the A350.