Inibuilds A350 Master WASM Crash Thread v1.2.4 FS24

[IniJamir]

Inibuilds A350 Master WASM Crash Thread v1.2.4 FS2024

This thread will be the new location for all WASM Crashes relating to the Inibuilds A350-900/1000 for Microsoft Flight Simulator 2024

Below this message will be where users can upload their WASM Crashes pertaining to the current version of the A350.

NOTES: If you do not see orange expectations screens on your displays or "WASM exception in X gauge" in the developer console it is not a WASM crash. The "sim-freeze" is a separate event that is tied to something on the server side which we are investigating with Asobo.

All WASM Crashes existing in this thread will be removed following the release of a new update.

i.e. Any Crashes identified in Inibuilds A350 v1.2.4 will be removed from the post following the release of v1.x.x and so forth.

Please ensure that when posting WASM crashes you post the WASM log from the in-game console alongside any media (photo/video) and a brief description of what you were doing leading up to the crash. Instructions on what to do are located in this thread - 

Any posts not following this format are subject to deletion.

Thank you

[packman2002]

flight KDTW to KJFK, just on cruise FL310, entered arrival Star, Runway 22R, PUCKY1 , was just selecting VIA None,  and crash

1.24, deleted WASM files after update.   SU4 of course

KDTWKJFK_PDF_1773859607.de5f241d.pdf

KDTW/21R ZETTR4 KELTI DCT HANKK Q140 MEMMS PUCKY1 KJFK/22R1773864146.bin

.  1773864748.bin

 

KDTWKJFK_INA_1773859607.fpl

Edited March 19 by packman2002

[packman2002]

by the way, did shutdown msfs2024, re-opened, started aircraft with engines running on the runway.   loaded autosave status, a bit earlier on the flight.  did proceeed farer into the destination.  enterred STAR, Runway, via and transitioni.  was fine this time

previously i put via as last item (selected none  and crash happened.  no idea if relataed to entering the arrival data late or the order enteirng the arrival date. 

 

[CaptainSlow747]

I was just setting up a flight and had a WASM crash when I clicked on ATC COM, prior to that I entered 4 Fixes in the FIX page.

• Aircraft: A350-900 (no cabin)
• Simulator: FS2024
• Version: 1.24 (INImanager
• Navdata Method: NAVIGRAPH
• SPECS: Ryzen 9800X3D, RX7800XT, 32GB RAM

 

[MD82]

Sorry if I did not post as stated above. So, it might be of little help. I came here to this site afterwards:

Flight TPE-LHR

WASM #1 was when entering arrival STAR during ground preparation on active F-PLN
Flight Restart
WASM #2 was when entering destination (RCTP) into SEC 2 to build a quick return

[JeffreyJ91]

MUC-EWR

A350-900 (no cabin) D-AIXY

During the cruise, out of nowhere. Was not active in the cockpit.

Latest version of A350

Navigraph

 

[Lukasz Krajnik]

On 3/18/2026 at 9:31 PM, packman2002 said:

flight KDTW to KJFK, just on cruise FL310, entered arrival Star, Runway 22R, PUCKY1 , was just selecting VIA None,  and crash

1.24, deleted WASM files after update.   SU4 of course

KDTWKJFK_PDF_1773859607.de5f241d.pdf 784.82 kB · 4 downloads

KDTW/21R ZETTR4 KELTI DCT HANKK Q140 MEMMS PUCKY1 KJFK/22R1773864146.bin

.  1773864748.bin

 

KDTWKJFK_INA_1773859607.fpl 641 B · 0 downloads

Exactly same situation on same approach to KJFK. The only difference was 16 hours haul from WSSS. WASM deleted before clean install to 1.2.4. First run on runway, and so on. FS2024 SU4. Will try next night same haul after again deleting WASM.

[QY_Nebula]

Flight ZSPD-RCTP. This happened far away from Top of Descend point. I was selecting Arrival procedures. It's normal when I entered STAR RWY ILSZ and on the PFD the route was drawn successfully. However when I enetered VIA it crashed.

To reproduce:
Select Arrival like this: RWY 05L ILS05L BAKER-1A then choose VIA JAMMY

Information:
Aircraft: A350-900
Simulator: FS2024 SU5 BETA
Version: v1.2.4(latest)
Navdata Method: NAVIGRAPH
WASM Error: 
WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005
WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty
Specs: 
CPU:13th Gen Intel(R) Core(TM) i9-13900HX (2.20 GHz)
RAM:32.0 GB
GPU: NVIDIA RTX4080 LAPTOP

OFP included, flight route: ZSPD16R HSN-82D PONAB W13 OKATO R596 BERBA B576 BAKER (BAKER-1A VIA JAMMY RCTP05L)

1774184245.bin OFP.pdf

[ksp100]

v1.2.4 is no better than previous versions. WASM crash whilst sitting at the terminal programming the MCDU. Was just entering the arrival SID for VNKT and it orange screened.

• Aircraft: A350-900 (cabin)
• Simulator: FS2024
• Version: 1.24 (INImanager)
• Navdata Method: NAVIGRAPH
• SPECS: Ryzen 7800X3D, 7900XTX, 64GB RAM
• Other Apps : GSX

OFP: VHHH/07R PECAN3X PECAN V10 SIKOU R339 BSE A599 LXI W148 XSJ W146 GULOT A599 LSO A201 RAJ G463 ROMEO ROMEO3R VNKT/02

[Theooo]

Aircraft : A350-900

Simulator : FS2024

Version : 1.2.4 (Lasted Version)
Microsoft Flight Simulator 2024 version : SU4

NavData Method : SIM DEFAULT
OFP : Available (PDF attached / FLP reference)

WASM Error : 

WASM: Error during HUD_gauge_update execution. Error code: 0xc0000005

WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty

System Specs

• CPU: AMD Ryzen 7 5800X3D
• GPU: Gigabyte Radeon RX 9070 XT
• Motherboard: Gigabyte B550 Gaming X V2
• RAM: 32GB DDR4 3200 MHz
• Storage: 2TB + 1TB NVMe (Crucial P3)

Issue Description

I am experiencing very frequent WASM crashes with the A350-900, across multiple flight phases and different routes.

Out of approximately 10 flights, 6 resulted in a WASM crash, making the aircraft unreliable to operate.

This significantly degrades the experience. At this stage, flying the A350 feels unstable and unpredictable, as crashes occur regularly without a single consistent trigger.

Because of this, I am currently reconsidering using this aircraft, as most flights do not complete successfully.

Attached, you will find a compressed file containing the requested files. If you require any further information, please do not hesitate to ask.

 

Reproducible Scenario (Confirmed)

Taxi after landing (reproduced twice)

• Normal landing
• Vacating the runway
• Taxiing after runway exit
  → WASM crash occurs

This scenario has been reproduced 2 times under similar conditions.

 

Other Observed Scenarios

FMS / Approach Entry (3 occurrences)

• While entering approach procedures in the FMS
• Example: Seoul → Tokyo (OFP available)
  → WASM crash

At Gate

• During IRS alignment
  → WASM crash

In-flight Failures

• Sudden loss of navigation
• Full WASM failure without orange screen indication

 

Reproducibility Summary

• Approx. 60% crash rate
• Occurs across:
  • Taxi phase
  • FMS programming
  • Gate operations
  • In-flight
• Not route-specific

 

Additional Files Available

• Console screenshots
• WASM error screenshots
• OFP (PDF)
• Autosave (.bin prior to crash)

Impact

These repeated WASM crashes severely impact usability and prevent normal operation of the aircraft.

At the moment, the experience is highly inconsistent and unreliable, making it difficult to complete flights.

 

Final Notes

Given the frequency and variety of triggers, this appears to be a broader stability issue rather than a single isolated bug.

I am happy to provide additional logs, files, or test scenarios if needed.





 

WASM.7z