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

[pijnackerpilot]

Description: I have encountered persistent crashes in Microsoft Flight Simulator 2024 (MSFS 2024) while flying, with the application consistently failing and crashing due to issues with the WTF.dll module. The crashes occur intermittently during the flight, specifically either during the flight loading process or during the cruise phase of the flight. This issue started about a week ago after I installed version 1.0.8 of the inibuilds A350.

Additionally, I have encountered several bugs after recovering a flight via autosave, including:

1. Inability to activate ALT CRZ mode in the FMA.

2. During Open Descent or Climb, the aircraft busts through the set altitude and does not follow the altitude constraints, unless manual level off is used.

3. ALT CRZ mode remains blue in the FMA and does not engage properly.

Crash Details:

• Faulting application: FlightSimulator2024.exe

• Version: 1.3.23.0

• Faulting module: WTF.dll

• Exception code: 0x80000003 (breakpoint)

• Fault offset: 0x00000000000023cb

• Faulting process ID: 0x1050

• Crash occurs during: Flight loading or cruise phase.

• Log Entries:

  • First crash: Occurred at 16:48 UTC, with the WTF.dll error, while trying to load or during cruise.

  • Second crash: Another instance at approximately the same time, with the same error related to WTF.dll.

Steps Taken So Far:

1. Reinstalled GPU drivers: I updated my graphics drivers (NVIDIA drivers) to the latest version, but the issue persisted.

2. Checked for Mods: No new mods or add-ons were added recently to the community folder, and all add-ons were disabled to test the issue.

3. WTF.dll found at C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\WTF.dll.

4. Problem began: The issue began after installing version 1.0.8 of the inibuilds A350 addon.

5. Bugs after autosave recovery:

   • ALT CRZ mode in the FMA cannot be activated.

   • During Open Descent or Climb, the aircraft busts through the set altitude unless using manual level off.

   • ALT CRZ mode remains blue and does not engage properly.

Observations:

• The crashes do not occur during landing or approach, but only during the flight load process or while cruising.

• The issue seems to be related to the WTF.dll file, as indicated by the crash logs.

• The application repeatedly crashes with the same error in WTF.dll, even after troubleshooting steps.

• The FMA bugs (unable to activate ALT CRZ, altitude busts during open descent/climb, and ALT CRZ staying blue) only appear after recovering from an autosave.

System Information:

• OS: Windows 11

• GPU: RTX3080

• MSFS Version: 2024 - 1.3.23.0 

• Driver version: Latest NVIDIA driver 

Request: I am requesting assistance with troubleshooting or a possible fix for this issue. Has anyone else experienced similar issues with the WTF.dll file in MSFS 2024, particularly after installing version 1.0.8 of the inibuilds A350? Additionally, has anyone encountered the bugs related to ALT CRZ mode and autosave recovery? Any advice or solutions would be greatly appreciated.

Edited Tuesday at 06:35 PM by pijnackerpilot

[ButterTheRunway]

I also have an issue with wtf.dll CTDs after updating to v1.0.8 with the same exception code. So far I was not able to complete even a single flight without interruptions after V1.0.8. I would just be cruising (with the elapsed time ranging from 3 - 6 hours) without touching anything and all of the sudden the sim just closes. V1.0.7 worked fine for me and it would be great if there can be a solution for it. 
 

Steps taken:

Installed latest driver, cleared WASM folder, emptied community folder

Specs: i7-13700K + 64GB ram + 4070Ti

Driver: Latest NVIDIA driver

 

Edited Tuesday at 08:37 PM by ButterTheRunway

[GL_McQUEEN]

Same here every flight.

Edit: Seems to be related to autosave.

The timestamps of the crashes and the last autosaves are allways the same.

Edited Thursday at 12:37 AM by GL_McQUEEN

[macflo19]

Same for me, since the last update I tried to do 5 flights and all 5 ended in CTD (during the Cruise) 

florian P

[haza2]

On 4/22/2025 at 7:34 PM, pijnackerpilot said:

Description: I have encountered persistent crashes in Microsoft Flight Simulator 2024 (MSFS 2024) while flying, with the application consistently failing and crashing due to issues with the WTF.dll module. The crashes occur intermittently during the flight, specifically either during the flight loading process or during the cruise phase of the flight. This issue started about a week ago after I installed version 1.0.8 of the inibuilds A350.

Additionally, I have encountered several bugs after recovering a flight via autosave, including:

1. Inability to activate ALT CRZ mode in the FMA.

2. During Open Descent or Climb, the aircraft busts through the set altitude and does not follow the altitude constraints, unless manual level off is used.

3. ALT CRZ mode remains blue in the FMA and does not engage properly.

Crash Details:

• Faulting application: FlightSimulator2024.exe

• Version: 1.3.23.0

• Faulting module: WTF.dll

• Exception code: 0x80000003 (breakpoint)

• Fault offset: 0x00000000000023cb

• Faulting process ID: 0x1050

• Crash occurs during: Flight loading or cruise phase.

• Log Entries:

  • First crash: Occurred at 16:48 UTC, with the WTF.dll error, while trying to load or during cruise.

  • Second crash: Another instance at approximately the same time, with the same error related to WTF.dll.

Steps Taken So Far:

1. Reinstalled GPU drivers: I updated my graphics drivers (NVIDIA drivers) to the latest version, but the issue persisted.

2. Checked for Mods: No new mods or add-ons were added recently to the community folder, and all add-ons were disabled to test the issue.

3. WTF.dll found at C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\WTF.dll.

4. Problem began: The issue began after installing version 1.0.8 of the inibuilds A350 addon.

5. Bugs after autosave recovery:

   • ALT CRZ mode in the FMA cannot be activated.

   • During Open Descent or Climb, the aircraft busts through the set altitude unless using manual level off.

   • ALT CRZ mode remains blue and does not engage properly.

Observations:

• The crashes do not occur during landing or approach, but only during the flight load process or while cruising.

• The issue seems to be related to the WTF.dll file, as indicated by the crash logs.

• The application repeatedly crashes with the same error in WTF.dll, even after troubleshooting steps.

• The FMA bugs (unable to activate ALT CRZ, altitude busts during open descent/climb, and ALT CRZ staying blue) only appear after recovering from an autosave.

System Information:

• OS: Windows 11

• GPU: RTX3080

• MSFS Version: 2024 - 1.3.23.0 

• Driver version: Latest NVIDIA driver 

Request: I am requesting assistance with troubleshooting or a possible fix for this issue. Has anyone else experienced similar issues with the WTF.dll file in MSFS 2024, particularly after installing version 1.0.8 of the inibuilds A350? Additionally, has anyone encountered the bugs related to ALT CRZ mode and autosave recovery? Any advice or solutions would be greatly appreciated.

Thank you very much for your detailed feedback, will send onto the team.

[pijnackerpilot]

It happened to me again today on a longhaul flight from Brisbane back to Hong Kong. See information below

🛑 Crash 1 – mimalloc.dll

• Module: mimalloc.dll

• Occurance: in the late climb already from FL300 to FL380

• Exception code: 0xc0000005 (Access Violation)

• Symptoms: Simulator crashes shortly after launch or loading a flight.

• Likely Cause: Memory allocation error, possibly linked to the WASM environment used by the aircraft systems in the A350.

• Confirmed by users?: Yes – several users on the iniBuilds forum have reported this crash starting with version 1.0.8 of the A350.

---

🛑 Crash 2 – CoherentUIGT.dll

• Module: CoherentUIGT.dll

• Occurance: when attempting to load the aircraft just after crash 1

• Exception code: 0xc0000005 (Access Violation)

• Symptoms: Crash during UI rendering, likely while displaying cockpit interfaces or menus.

• Likely Cause: Conflict between the aircraft's UI components and either:

  • an overlay (e.g., Discord, MSI Afterburner),

  • or corrupt Coherent UI cache files.

• Confirmed by users?: Yes – multiple users on iniBuilds' forums have experienced this with v1.0.8.

 

After restoring the flight using autosave, again I experience the bug with not being able to enter ALT CRZ. Nothing thelps to get the aircraft back into standard cruise modus. Additionally, the aircraft will not respect the dialed altitude when using CLB or open CLB. Even when using V/S, descent or climb needs to he stopped manually by pusig the v/s knob. Very very annoying. This starting to become a deal breaker for me. 

Is there a way to roll back to 1.0.7?

 

[pijnackerpilot]

And 5 hours later it happened yet again! Sigh

[Galf]

I reported pretty much the same thing on Discord, the culprit changes but the crashes stay, and they're straight to CTD which never happens with anything else. I'll copy what I reported on Discord:
 

I just had another crash, conditions were on the ground as I alt tabbed to text on discord, but it followed the same behaviour as all other CTD's I had. I only have CTD's with the A350, no other plane (I tried default and Fenix) CTD's like this. it's a clean break to desktop, except Steam thinks the game is still running so I stop it on steam afterwards.

Hardware:

5800X3D - X570 Master motherboard - 64gb of 3600mhz C16 DDR4 memory - RTX 5080 on 576.02 drivers  - W11 24H2 - 2560x1440 360hz HDR10 enabled, full screen No overlays aside the Steam overlay Maxed out settings with some fps saving on the displays (medium refresh rate, 20fps in EFB options) running FG 2X and AutoFPS.

Crash report:

Quote

Faulting application name: FlightSimulator2024.exe, version: 1.3.25.0, time stamp: 0x00000000 Faulting module name: mimalloc.dll, version: 0.0.0.0, time stamp: 0x6703ed67 Exception code: 0xc0000005 Fault offset: 0x00000000000018f3 Faulting process id: 0x5278 Faulting application start time: 0x1DBB46B1453F0AA Faulting application path: H:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe Faulting module path: H:\SteamLibrary\steamapps\common\Limitless\mimalloc.dll Report Id: 7881fa7f-8635-49de-af51-bfa84b182a21 Faulting package full name: Faulting package-relative application ID:

Crash report 2 (This crash happened yesterday when I clicked the FO tray table click spot at cruise after about 1hr of flight time)

 

Quote

 

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: 0x3C0C Faulting application start time: 0x1DBB37024C47C8E Faulting application path: H:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe Faulting module path: H:\SteamLibrary\steamapps\common\Limitless\WTF.dll Report Id: 77a05882-8cbe-41b5-8df9-e74a26da45cb Faulting package full name: Faulting package-relative application ID:

Crash report 3 this time the flight lasted much more, like almost 1.5 hours I think. I performed a full safe mode DDU to be sure it wasn't unstability on Nvidia drivers to blame. gave it another go, another CTD this time 0xc0000005 I'd like to reiterate this is the only plane that creates CTD's, this time it happened when I tried drone cam.
 

Quote

Faulting application name: FlightSimulator2024.exe, version: 1.3.25.0, time stamp: 0x00000000 Faulting module name: FlightSimulator2024.exe, version: 1.3.25.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000002a86ca3 Faulting process id: 0x5730 Faulting application start time: 0x1DBB507ABB2C6AE Faulting application path: H:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe Faulting module path: H:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe Report Id: d1475e45-46ed-4696-996d-881e2cdb4589 Faulting package full name: Faulting package-relative application ID:

 

[Swaroop]

I had around 9 CTD’s after updating to 1.0.8.

Funny thing is all happened at last 1hr remaining to destination airport and all in vatsim.

Hardware: I9 14900HX and RTX4080

Edited Friday at 01:03 AM by Swaroop

[Eddie]

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

[Muffwin]

Hello,

I just had a crash with the A350 when trying to load it into KEWR.

Steps:
I just did a fresh reinstall (remove A350 from iniManager, cleared WASM folder, but kept all liveries), reinstalled the A350, rebooted PC and started MSFS 2024 via Steam.

I then loaded the A350-900 into LFPG, no issues, switched to default nav data + LIDO charts instead of Navigraph. I don't know why, I thought that when removing WASM folder, I had to redo throttle calibrations, but this time it was already done.

Then i went back to the main menu, planed a flight from KEWR to LFPO in simbrief, selected a new livery, choose a gate at KEWR, and then just after i clicked the button to start the flight, the sim CTD with the below error:

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: 0x6F20
Faulting application start time: 0x1DBB5BF5699E584
Faulting application path: S:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe
Faulting module path: S:\SteamLibrary\steamapps\common\Limitless\WTF.dll
Report Id: 120e8a2a-250a-44e2-b9e3-e8afb8dc2b33
Faulting package full name:
Faulting package-relative application ID:

So i am not sure if navdata is the problem here.

I also had this error yesterday when trying to do GCLA - EFKH in the a350-900, CTD with WTF.dll after 1h when I was cruising at FL380:

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: 0x6D60
Faulting application start time: 0x1DBB5141726C74F
Faulting application path: S:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe
Faulting module path: S:\SteamLibrary\steamapps\common\Limitless\WTF.dll
Report Id: b6679f12-9316-431b-a788-f55d867a6b59
Faulting package full name:
Faulting package-relative application ID:

[Galf]

3 hours ago, 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

This is not the case for me as I kept the plane to the default nav data always

[FelixM]

Hi,

I had the exact CTD crash as described by the OP (WTF.dll). Also sent a event crash log the other day here on the forum about this. v.1.0.8

Edited Friday at 12:08 PM by FelixM

[FelixM]

Hi,

before I had the WTF CTD same as the OP. Now I just had the other one, the CoherentUIGT.dll CTD:

As many others said  autosave recovery impossible. I also attached the last two autosaves.

1745683640.bin 1745683171.bin

[kobru79]

I too am experiencing a lot of sudden crashes (the simulator suddenly closes) with version 1.08 they are much more frequent.
Also often when I enter the flight plan the MCU freezes and I am forced to reboot. I don't understand why when I fill in the flight plan it doesn't recognize a lot of airways and points forcing me to fill in a lot of the flight plan point by point. The whole thing is very frustrating at the moment for me this plane is unusable....

[Manuel1989]

Same here, cruise crash with version 1.0.8

[Muffwin]

Ok so update on my previous comment:

I tried yesterday the A350-900 on FS2024, fresh install + Navigraph data, short flight from LFPO to LFMN, without any issues at all.

I thought everything was fixed, so i took the A350-900 again for the CTP today (LFPG - KIAD).
Loaded the plane at gate, did everything from cold & dark to pushback & start, no issues, then all of the sudden I had another CTD (WTF.dll, logs below).
The crash seems so random, because it happens to me 3 times: one just after departure (before 5000ft), another one at cruise FL380 after 1h25, and the last today just after engine start.

So i reloaded the sim, changed from Navigraph data to default data + LIDO charts, and was able to do the whole flight from gate to gate without any crash or issue. I will try do do more flights with the default navdata, but with the crashes happening at random times (and not on all flights), it is hard to tell if navdata is the real culprit here.

Anyways I hope you can find the issues of this crash and i wish you good luck 🍀


Crash report:
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: 0x278
Faulting application start time: 0x1DBB698482B181C
Faulting application path: S:\SteamLibrary\steamapps\common\Limitless\FlightSimulator2024.exe
Faulting module path: S:\SteamLibrary\steamapps\common\Limitless\WTF.dll
Report Id: 6822441c-a845-4638-b255-321926f01977
Faulting package full name:
Faulting package-relative application ID:

[Approach118]

I have been experiencing freezing issues since version 1.0.6.
The characteristics of the problem are as follows:
1.The knob in the cockpit is movable, but the number does not change accordingly. For example, when I cruise at 38000ft and adjust the knob to change the altitude, the number remains 38000ft.
2. The aircraft deviates from the route and does not fly according to the route.However, FS2024 is operating normally, and from an external perspective, the aircraft is flying normally.
4. (1) These problems occur every time at a distance of about 1 hour from the T/D point
    (2) The problem occurs on flights longer than 4 hours.
    (3) I start flying before bedtime every day and plan to land after waking up in the morning. Usually it's a 7-8 hour flight, but every FREEZE is incredibly disappointing and frustrating.

I have tried many methods to address these issues, but still have not been able to solve them.
So in version 1.0.7, I completely reinstalled my computer with Windows 11, Steam, FS2024, ini350, Fenix320, Navigragh, add-ons, and so on.

After everything was ready, I remained in version 1.0.7 without upgrading, and found that all the above issues were resolved! That is great! Whether it's a 5 hour or 10 hour long haul flight, it can arrive smoothly.

The good times didn't last long. Just this morning, ZBAA-WSSS (6 hours), I woke up on time at 6am and saw that the plane had deviated from its route and had already flown to Phuket.

I don't know what happened, why it has become so difficult to play games peacefully.
12600kf+48G 3600+5070ti

[kobru79]

After two crashes, I rebooted and moved the data to NAVDATA DEFAULT SIM as recommended. I was finally able to execute the flight from VIDP to RJTT the only problem is that although I had the updated airac during the flight plan entry it recognized 2 out of 10 aeroways and I had to enter the flight plan almost all by hand.

Gabriele

[pijnackerpilot]

On top of that, the default nav data does not work well with many GPS bases fixes. For instance in VHHH, an airport I like to fly from, I  cannot fly any sid or star because all TT*** and HH*** fixes refer to N00.000 and E000.000 making default nav data useless. I have the same issue with the Inibuilds default A330 and A321

[tesla]

It turns out that it's not just me who can't fly long distances after updating 1.0.8,The error code is consistent with yours one by one 0X8000003.I have no issues with the previous version, and I have not made any changes to my computer or simulation settings.If you're nlucky, start the englucky, you can fly for 6 hours. If you're uine and then exit to the desktop。