CTD loading in!

[jpallotta4]

I un-installed the plane, deleted and uninstalled the inibuilds manager, started the sim, loaded to an airport with the PMDG 777 just fine, shut down the sim, restarted my PC, installed inibuilds manager and then the a350. restarted computer, booted into MSFS, picked a350, picked a basic airport, CTD at 75%. I think the only fix is just to forget this plane and switch to PMDG, Fenix planes permanently and eat the $$ loss. 

Faulting application name: FlightSimulator.exe, version: 1.39.9.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.39.9.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000001e90802
Faulting process id: 0x5304
Faulting application start time: 0x1DC126A527D4BA4
Faulting application path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: f39a42e7-425d-4ba4-93c2-877c6d979d3d
Faulting package full name: 
Faulting package-relative application ID: 

[babybus]

You shouldn’t need to do any of this. ini used to be my one of my favourite developers. After the botched release of the A350 and the decision to not make products for 2020 they’re quickly falling down my list. 

[jpallotta4]

I found 3 wasm files in my Microsoft Flight Simulator\Community\inibuilds-aircraft-a350 folder. Deleted those. Now the plane loads into an airport but nothing works at all. I'm able to press and move switches but nothing comes on. This thing is truly broken. 

[pete_auau]

5 hours ago, jpallotta4 said:

I found 3 wasm files in my Microsoft Flight Simulator\Community\inibuilds-aircraft-a350 folder. Deleted those. Now the plane loads into an airport but nothing works at all. I'm able to press and move switches but nothing comes on. This thing is truly broken. 

have you submitted a ticket in is the only way fwd now since you have done everything possible who knows mite be some thing simple 

Edited August 21 by pete_auau

[babybus]

Weirdly the -900 works just not the -1000. Very strange! 

[richboy2307]

Hi all,

4 hours ago, jpallotta4 said:

I found 3 wasm files in my Microsoft Flight Simulator\Community\inibuilds-aircraft-a350 folder. Deleted those. Now the plane loads into an airport but nothing works at all. I'm able to press and move switches but nothing comes on. This thing is truly broken. 

Firstly, you should never delete the WASMs in the community folder. What you've done is essentially deleted all the code of the aircraft, so no wonder it doesn't work in that instance. Please DO NOT delete any files from the package in the community folder.

You should uninstall and reinstall the package fresh from iniManager to ensure there are no missing essential files at present.

When we ask you to clear your WASM folder, we only mean the sim-compiled WASMs that can be found on the AppData folder paths listed here:

4 hours ago, babybus said:

You shouldn’t need to do any of this. ini used to be my one of my favourite developers. After the botched release of the A350 and the decision to not make products for 2020 they’re quickly falling down my list. 

You are welcome to receive support but please refrain from making inflammatory statements. We apologize for your frustrating experiences but I assure you, as you said, "you shouldn't need to do any of this" as the product is working fine in this regard for majority of the customer base without CTDs.

Your experience so far is the exception, not the universal norm, so please have some patience as we work with you (and others here) to figure out the cause of such issues on your install.

6 hours ago, jpallotta4 said:

Here are the things I’ve tried:

• Un-install/Re-Install
• Cleared every folder associated with a350
• Cleared WASM
• Memory Page Filing
• Cleared Rolling Cache/ Turned off
• Remove all liveries
• Tried switching from DX12 to DX11 but when I did that I get CTD during initial sim loading

I was able to get into the plane when I loaded into an airport with the PMDG 777 and switched to the a350 with the Developer Menu Aircraft Selector, the plane loaded but not fully, landing gear wasn’t deployed and nothing worked. Tried loading from main menu again and sim crashed at 75% airport loading again.

5 hours ago, jpallotta4 said:

Faulting application name: FlightSimulator.exe, version: 1.39.9.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.39.9.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000001e90802
Faulting process id: 0x5304
Faulting application start time: 0x1DC126A527D4BA4
Faulting application path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: f39a42e7-425d-4ba4-93c2-877c6d979d3d
Faulting package full name: 
Faulting package-relative application ID: 

The Windows crashdumps are very limited in their ability to diagnose or provide useful data when it comes to MSFS. Going by the above though, it points to some kind of potential error or corruption in virtual memory (pagefile). I know you have tried, but just for completeness sake, please can you can try the following in the way listed below:

1. Uninstall A350 from iniManager then complete a fresh install of the latest (v1.1.4)
2. Delete your FS20 AppData WASM folders from the paths listed here: 
3. Adjust Virtual Memory behaviour as per this link: https://forums.flightsimulator.com/t/flightsimulator-exe-application-error-0x80000003-a-breakpoint-has-been-reached/334962/101
   
   If it was already on automatic, try manually setting a custom size that is 1.5x your physical memory (e.g. if you have 16GB RAM, try 24GB)
4. Load into MSFS with just the A350 package (inibuilds-aircraft-a350) in your community folder. 
5. Spawn directly onto a runway in any variant. Observe if you get a CTD or WASM loads on launch.
6. If you do have a CTD, please share the windows error log again as well as exactly where you tried.

Again, most users don't have to do any of this but we are just going off the limited metrics available to us from your submitted crash reports to help you find a solution.

On 8/18/2025 at 4:06 AM, babybus said:

The latest update seems to have broken the aircraft again for me. It was CTD'ing when loading in. I then removed everything from community folder apart from A350 and it worked. I then added everything in with no liveries and it works. I then add the ini liveries back in and I get the CTD again. 

This is very weird considering "broken" liveries will at best result in lack of selection for those liveries in the aircraft selection menu, not CTD the sim as a whole. The livery package, if unreadable, will normally just not load into the VFS.

What were the liveries you had installed so I can try exactly that set to see if we can reproduce the issue?

On 8/14/2025 at 4:16 AM, blueskies2k40 said:

can yall figure figure figure figuuuuuuuuuure out what liveries it has issues with on msfs2020 seems like it only loads on blank livery,updates n updates n still issues, this is a joke $70 spent on this with crashing n bug issues,the only aircraft that brings problem we can even enjoy.

For context, I run FS20 A350 in testing regularly across 2 different systems (one PC, one laptop) with the entire FS20 IniManager liveries library installed on one system; and all the marketplace livery packs installed on another and have yet to experience such CTDs across the iniManager or Marketplace builds. 

What were the liveries you had installed so I can try exactly that set to see if we can reproduce the issue?

If there is any action/fix required on our part, we're always eager to do it and push it via update, as we have throughout the life of this product. However, we can't fix an issue that we cannot reproduce, so we need your help to try these things and let us know so we can work together to find the cause (and also hopefully a solution).

Thanks!