Hi Team, I am hoping to get some help/clarity here. I routinely fly long hauls, and have done upwards of 16 hours in the a350. However, ever since I purchased the a380, I have not been able to complete a single long haul flight. The simulator will CTD every time after a few hours of flying. I would like to figure out whats happening but I do not know where to start. Any help is appreciated. The only clue I have so far is that on both occasions, the CTD happened around the same area (Eastern Europe)

Some more context - not sure if this is a red herring or not - I emptied my community folder and loaded into LTFM (Default) and the plane just hung and endlessly loaded until the sim crashed. I disabled City/World Update Eastern Europe, cleared scenery indexes, and was able to resume my flight from an auto-save.

So far the two flights I tried were OMDB-EGLL and OMDB-KJFK. Both crashes happened when flying near Turkey/Romania. I'm not entirely sure why, maybe this is a rolling cache thing? Is there anything Ini would like me to do to collect more data?

I’ve had the same issue as you twice, both around 3hrs in to the flight flying from Dubai to the UK, once was in a similar place to your crash, and the other was a more southerly routing flying over the Greek islands then crashing to desktop over the Greek mainland. I’ve actually never had msfs CTD, I’ve had long haul flight freeze a few hours in, I find clearing the cache before every flight solved that issue with the 777, but CTD is totally new. I am running ActiveSky and BeyondATC, and do have a handful of airports installed in Greece as well.

My error code was 0xc0000000002e5c278

Module name was FlightSimulator2024.exe

Nice to know I am not alone and its interesting how your crashes were the same as mine! When i was flying from Dubai to the UK, I had a CTD near Greece. Going to NYC, it was around Bucharest.

I cleared my rolling cache and disabled pretty much every addon I have and I will try another long haul tonight and see what happens. This is truly weird, as I also have not had any CTD's before, and I have flown the A350 ultra long haul many times in these same areas.

Happened again about 6 hours into the flight, this time over Alaska. The error was 0xC0000005. At this point, I have not been able to complete a single A380 flight without a crash, so I'm gonna go ahead and put this one into my hangar until i figure it out.

Also CTD here. Happend as I wanted to enter the approach performance data.

Yeh I reset my cache before every flight with every aircraft I fly and I’ve had no issues except this aircraft, I set it to 16gb. But yeah with the a380 I’ve done 5 flights, all around the 7h-8hr mark and two of them have crashed like this, both in a similar area to yours, I have tried turning the cabin off too. Will try a fresh installation when I’m off work in a few days. Also worth noting its done it when I’ve actually been away from the computer in cruise, so it’s not like I’ve been messing between camera views either.

Other than that the aircraft is great though, super cool aircraft with more than enough depth for realistic operations, I find it runs pretty well with lossless scaling on my 9700xtx even with max traffic!

3 hours ago, matthewb4375 said:

Yeh I reset my cache before every flight with every aircraft I fly and I’ve had no issues except this aircraft, I set it to 16gb. But yeah with the a380 I’ve done 5 flights, all around the 7h-8hr mark and two of them have crashed like this, both in a similar area to yours, I have tried turning the cabin off too. Will try a fresh installation when I’m off work in a few days. Also worth noting its done it when I’ve actually been away from the computer in cruise, so it’s not like I’ve been messing between camera views either.

Other than that the aircraft is great though, super cool aircraft with more than enough depth for realistic operations, I find it runs pretty well with lossless scaling on my 9700xtx even with max traffic!

Yeah ive only attempted three flights so far and every one resulted in a CTD after a couple of hours. I looked into the Asobo Crash Report file and saw the error 0xC0000005.

I agree with you though, the airplane is awesome and I genuinely love it. The performance has also been spectacular - it actually gets better frames on my system than the a350 if you believe that - which is why these mysterious CTDs are so weird to me. I'll keep you guys posted if I figure anything out. Im gonna try a clean install and reverting my graphics drivers. ini is also updating the plane this Tuesday so I think they're going to fix some art related and system things - maybe it'll help.

Edited Sunday at 08:28 PM4 days by zoomyboomy

Im my case it seems to be a VRAM overload. Before every CTD my VRAM of 16 GB is full. I reduced some settings in the sim but on some big airports as EDDF by Aerosoft it is nearly impossible.

7 hours ago, Neotron said:

Im my case it seems to be a VRAM overload. Before every CTD my VRAM of 16 GB is full. I reduced some settings in the sim but on some big airports as EDDF by Aerosoft it is nearly impossible.

That would make sense but when you are flying at night in the middle of no-where, and your graphics are intentionally reduced (Im talking about texture quality, TLOD, etc) then VRAM overload does not make sense. Unless, there is a memory leak somewhere.

Same here also CTD a couple of hours in flight.

It happened to me somewhere around Tanzania. Was doing a flight Capetown-Dubai....

Hope there will be a fix soon for the CTD`s

I’m at 24gb on my VRAM, and pretty much like everyone I’m still getting the warnings when switching views saying about exceeding GPU memory, I’ve never had it in cruise though, it’s just when changing views quickly from outside to inside or panning the spot view like a lunatic when at airports. Dose anyone know how far out installed airpots load in at cruise? I’ve only had this crash around Greece, and I’ve got quite a few airports installed in that part of the world, is it plausible that’s what’s tipping it over the edge?

32 minutes ago, matthewb4375 said:

I’m at 24gb on my VRAM, and pretty much like everyone I’m still getting the warnings when switching views saying about exceeding GPU memory, I’ve never had it in cruise though, it’s just when changing views quickly from outside to inside or panning the spot view like a lunatic when at airports. Dose anyone know how far out installed airpots load in at cruise? I’ve only had this crash around Greece, and I’ve got quite a few airports installed in that part of the world, is it plausible that’s what’s tipping it over the edge?

Hi,

This will depend entirely on your simulator settings. TLOD (Terrain Level of Detail) and OLOD (Object Level of Detail) are two settings that could affect the behaviour you're describing.

Thanks!

Same issue for me. Thought it might have been my VRAM on my 3070ti, I have since upgraded to 9070xt with 16gb vram and not been able to complete a full flight yet in the A380. Any other aircraft okay but just not this one. All drivers up to date and crashes randomly midway through a flight.

2 hours ago, iniKyle said:

Hi,

This will depend entirely on your simulator settings. TLOD (Terrain Level of Detail) and OLOD (Object Level of Detail) are two settings that could affect the behaviour you're describing.

Thanks!

Hi Kyle, I know some users here reported CTDs as well - but on the contrary, I intentionally run my sim with reduced settings and a nearly empty community folder (with the exception of a the origin and destination airports, a380 liveries, and a few mods such as GSX and Universal Cabin Announcer, and FSLTL)

I’m curious if anyone on the Inibuilds side is aware of or tracking any possible causes for a mysterious CTD happening during cruise? If you look at my earlier posts I mentioned the error that was in the asobo crash report.

I’m curious if there any adverse interactions between FSLTL or Spad.Next, or any specific graphics settings I should pay attention to.

So far, I’ve cleared my nvidia cache, deleted the wasm folder, reinstalled the airplane, verified MSFS game directory, and disabled FSLTL during cruise - still no avail.

1 minute ago, zoomyboomy said:

Hi Kyle, I know some users here reported CTDs as well - but on the contrary, I intentionally run my sim with reduced settings and a nearly empty community folder (with the exception of a the origin and destination airports, a380 liveries, and a few mods such as GSX and Universal Cabin Announcer, and FSLTL)

I’m curious if anyone on the Inibuilds side is aware of or tracking any possible causes for a mysterious CTD happening during cruise? If you look at my earlier posts I mentioned the error that was in the asobo crash report.

I’m curious if there any adverse interactions between FSLTL or Spad.Next, or any specific graphics settings I should pay attention to.

So far, I’ve cleared my nvidia cache, deleted the wasm folder, reinstalled the airplane, verified MSFS game directory, and disabled FSLTL during cruise - still no avail.

Hi,

The sim crashing is one of those particularly difficult issues to diagnose. It is very rare for a 3rd-party aircraft to cause the simulator to crash outright. More often, this type of behaviour can be related to the core simulator itself, hardware/driver issues, PC temperatures, or other system-level factors.

Other than the few reports in this thread, I have not seen any widespread reports of this particular issue, which makes it even more difficult to pinpoint.

There could be hundreds of reasons why your simulator is behaving this way, which unfortunately makes troubleshooting a very painstaking process.

You may have already tried some of these, but what I can personally suggest is the following:

• Make sure your motherboard BIOS is up to date.

• If you're running the simulator from an SSD or M.2 drive, make sure its firmware is up to date.

• Ensure Windows is fully up to date.

• Make sure your GPU drivers are up to date.

• Try lowering some of your in-sim settings, particularly Trees, Bushes, Rocks, and Fauna. Personally, I run all of these on LOW or OFF.

Hopefully one of these helps narrow down what may be causing the crashes.

Thanks!

Hi Kyle, I will have a look at these but i think most have already been completed. It just seems weird that its just in the A380, A350 working perfectly fine, aircraft from other developers also fine. Not sure.

I've done everything that they asked - Including BIOS and SSD firmware updates, cleared cache, cleared wasm, fresh installed the a380, reduced graphics settings significantly, and clean installed drivers. Also using the reduced texture pack, and accepted/allowed the new crash reporting tool. I've done some digging and found the MSFS crashes I encountered in Event Viewer. This might be helpful to the Ini Team:

Crash 1 (mimalloc.dll Access Violation)

• Faulting Module: mimalloc.dll (v0.0.0.0)

• Exception Code: 0xc0000005

• Fault Offset: 0x000000000000d254

Crash 2 (Core Game Access Violation)

• Faulting Module: FlightSimulator2024.exe (v1.8.16.0)

• Exception Code: 0xc0000005

• Fault Offset: 0x000000000054ef06

Crash 3 (GPU Device Loss / Execution Trap)

• Faulting Module: FlightSimulator2024.exe (v1.8.16.0)

• Exception Code: 0x80000003

• Fault Offset: 0x0000000003e1b2c1

Since these are happening only when i use the A380 (A350, A340, and PMDG aircraft are fine), and with what I've been reading in this discord post - I suspect this might be EFB related. (Maybe a red herring, who knows - but we'll see. I'll do some long flights over the weekend and see if this is still an issue in 1.01)

Edited 11 hours ago11 hr by zoomyboomy

Hello! I was resisting putting this up but this is happening more frequently then I'd like.

Firstly, I love this aircraft, I do...but so far i've only been able to complete 3 long haul flights since release. SFO - MUC, MUC-DXB (1 WASM Crash) then DXB to DFW (No errors!)

Since 1.0.1, not a single long haul flight can be completed. I'm waiting for the sim to load a 7th time but I tried going form DFW - DXB and on 3 separate occasions ...CTD just outside of St. Louis. On the 4th load after going through Autosave, I made it as far as Hamburg before it CTD'd again.

I've uninstalled the AC and liveries, and i'm now streaming it...but after a few minutes in the air, it CTD's again, and again, and again.

• Faulting Module: FlightSimulator2024.exe (v1.8.16.0)

• Exception Code: 0xc0000005

• Fault Offset: 0x00000000021ff89f

I know its not a VRAM issue, the resource message hasn't popped up since DXB (only once) Nvidia version 617.14, FPS is locked at 30, FG X3, RTX 5080 on a 14900K. This bird is smooth through and through with exception to this.

Not sure where to go from here.

3 more CTDs Inibuilds Livery, loaded from Autosave after starting on the ground, got up just over 10000ft then CTD.

Background apps were shut off (FSUIPC, Map Enhancement, BeyondATC) even Volanta, and the community folder was dumped...same faulting error code.

Faulting application name: FlightSimulator2024.exe, version: 1.8.16.0, time stamp: 0x00000000

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Thanks for the reports everyone. Will note all of the info and forward to the team for further review.

Hi everyone,

I'm going to leave this down below for you all to review. Hoping some, if not all are able to find the culprit.

Common Causes

1. Sim Updates- Conflicts with sim updates/patches (SU Beta changes often break add-ons temporarily)

2. Mod/Add-on Conflicts - Other liveries, mods, or third-party addons conflicting with iniBuilds aircraft

3. Corrupted Files

- Incomplete or corrupted installation

- Corrupted community folder files

- Damaged aircraft cache/config files

4. System/Hardware Issues

- Insufficient VRAM (these are typically high-detail, resource-intensive aircraft)

- Outdated GPU drivers

- RAM issues or insufficient RAM

- Overheating components

5. Software Conflicts

- Overlay software (Discord, MSI Afterburner, etc.)

- Antivirus interference

- Windows/OS-related issues

Possible Solutions

Quick Fixes

- Update the aircraft – Ensure you have the latest version via the iniManager or Marketplace

- Update MSFS2024 – Confirm the sim itself is fully updated

- Update GPU drivers

Installation-Related

- Reinstall the aircraft – Delete and do a clean reinstall

- Clear the Community folder – Remove other addons temporarily to isolate the conflict (test with only iniBuilds aircraft active)

- Check for corrupted cache – Clear MSFS shader cache and rolling cache

System-level

- Turn off overlays – Disable Discord overlay, Xbox Game Bar, MSI Afterburner, etc.

- Check Event Viewer logs (Windows) – Identify the specific module causing the crash (helps pinpoint if it's an .exe, .dll, or specific system file)

- Verify sufficient VRAM/RAM – These aircraft are demanding; ensure your system meets requirements

- Run sim as Administrator

- Disable antivirus/firewall temporarily to test

Thanks!

On 9/19/2026 at 1:11 PM, matthewb4375 said:

I’ve had the same issue as you twice, both around 3hrs in to the flight flying from Dubai to the UK, once was in a similar place to your crash, and the other was a more southerly routing flying over the Greek islands then crashing to desktop over the Greek mainland. I’ve actually never had msfs CTD, I’ve had long haul flight freeze a few hours in, I find clearing the cache before every flight solved that issue with the 777, but CTD is totally new. I am running ActiveSky and BeyondATC, and do have a handful of airports installed in Greece as well.

My error code was 0xc0000000002e5c278

Module name was FlightSimulator2024.exe

6 hours ago, Bassman7e7 said:

3 more CTDs Inibuilds Livery, loaded from Autosave after starting on the ground, got up just over 10000ft then CTD.

Background apps were shut off (FSUIPC, Map Enhancement, BeyondATC) even Volanta, and the community folder was dumped...same faulting error code.

Faulting application name: FlightSimulator2024.exe, version: 1.8.16.0, time stamp: 0x00000000

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

On 9/22/2026 at 3:42 PM, Adam892 said:

Hi Kyle, I will have a look at these but i think most have already been completed. It just seems weird that its just in the A380, A350 working perfectly fine, aircraft from other developers also fine. Not sure.

On 9/22/2026 at 6:01 AM, mrmike1979 said:

Same here also CTD a couple of hours in flight.

It happened to me somewhere around Tanzania. Was doing a flight Capetown-Dubai....

Hope there will be a fix soon for the CTD`s

Guys, what GPU's do you have and what driver versions are you on? Also, are you using things like DLSS Swapper or Frame Gen? - Ive been reading tons of discord posts and doing a bunch of testing, I think I might be onto something but I'm not sure yet.