Inibuilds A350 Master WASM Crash Thread v1.2.3 FS24

[IniJamir]

Inibuilds A350 Master WASM Crash Thread v1.2.3 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.3 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

[Johnnyyang]

• Aircraft: A350-1000
• Simulator: FS2024
• Version: iniManager
• Navdata Method: NAVIGRAPH
• WASM Error: WASM: Error during Wasm network callback execution. Error code : 0xc0000005
• Specs: R7 9800X3D + RX9070XT + 64GB RAM

Sim & Environment:

• Simulator: Microsoft Flight Simulator 2024

• Weather/Time: Real weather via ASFS + REX Atmos Core

External Applications Running:

• BeyondATC (BATC)

• Cabby

• Active Sky FS (ASFS)

• REX Atmos Core

• GSX Pro

Steps / Context leading to the crash:

1. Initialized the aircraft at iniBuilds VHHH.

2. Started GSX Pro services: Catering and Refueling were in progress.

3. The crash (WASM/CTD) did not trigger immediately upon pressing any GSX request buttons.

4. After several minutes of normal ground operations while services were running, the sim encountered a sudden WASM crash.

VHHHEDDF_CX289.pdf

[ksp100]

{UPDATE : A full deinstall not just a wasm folder delete, and then reinstall has now enabled me to complete a full flight - So the remaining problem may not be a wasm issue but something to do with how update is applied?}

• Aircraft: A350
• Simulator: FS2024
• Version: v1.2.3 (iniManager)
• Navdata Method: NAVIGRAPH
• OFP: Include a PDF of your Operational Flightplan (OFP) if related to FMS/Route Procedures crashes
• WASM Error: WASM: Error during MFD_gauge_draw execution. Error code : 0xc0000005
• Specs: 7800x3d + 7900xtx + 64GB DDR5.
• Autosave File:  No autosave - only been running < 1 minute. 

Sim & Environment:

• Simulator: Microsoft Flight Simulator 2024

• Weather/Time: Real weather

External Applications Running:

• GSX Pro

Steps / Context leading to the crash:

1. Initialized the aircraft at iniBuilds EGLL - Cold and Dark - Select external power A&B and turn on batteries - Start IRS alignment

2. Operated GSX Pro services: Jetway

3. Using EFB load Simbrief Plan. Load aircraft weight and fuel.

4. Load plan in MCDU on INIT page. Selected and loaded SID and STAR.

5. The sim then suddenly WASM crashes.

 

Quit sim and repeated with same effect.

 

 

Edited Saturday at 06:34 PM by ksp100
Updated experience.

[Tofo]

I just had the same Wasm crach after a fresh reinstall with new update... With GSX Pro, during boarding sequence, while using the OFP page of the EFB.

Regards

[Crosswind]

Wasm crach during change the flight plan STAR

[Tofo]

New flight, after a complete new install following yesteraday's experiment.

NTAA-KLAX. 
While crusing, I prepared my arrival to KLAX : chose the RWY, the STAR.. And...WASM again.

Flight made with GSX PRO, Active Sky and FSHUD

[Tommius84]

• Aircraft: A350
• Simulator: FS2024
• Version: v1.2.3 (iniManager)
• Navdata Method: NAVIGRAPH
• WASM Error: WASM: Error while selecting the 'VIA' on the Arrival page
• Specs: 7800x3d + 5070TI + 64GB DDR5.

Sim & Environment:

• Simulator: Microsoft Flight Simulator 2024

• Weather/Time: Real weather

• Took off from Istanbul, for a flight to Amsterdam, at cruise level (+- 80 NM into the flight) I wanted to change the arrival runway. Selecting the runway was no issue, however trying to select a new 'VIA' waypoint, the WASM error occured (orange screens).

Edited 20 hours ago by Tommius84

[Transair]

Another WASM (sorry no pics/logs)

On the grnd VHHH, inserted RWY07C, SID DALOL 1C...all OK

Then ,still in VHHH, Inserted RCTP RWY23L and then TONGA 1B with immediate WASM. (No transition inputted)

Restarted flight, did the same inputs in the same order and this time - all OK.

V1.2.3 A35K, Ini livery,MSFS24, VHHH scenery, Navigraph used, Simbrief used.

RTX 5080 Gaming PC, AMD Ryzen 7 9800X3D 8 Core, AMD X870 Chipset, GeForce RTX
5080 16GB, 64GB 6000MHz RAM, 4TB M.2 NVMe SSD, Fractal Design North XL TG Case, 1000W PSU.

Edited 9 hours ago by Transair

[neo john]

Aircraft: A350-900
Simulator: FS2024
Version: v1.2.3 (iniManager)
Navdata Method: NAVIGRAPH
WASM Error: WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005
Specs: i9-13980HX + 4060laptop + 32GB DDR5.

Autosave File:

Sim & Environment:

Simulator: Microsoft Flight Simulator 2024

Weather/Time: Real weather

Steps / Context leading to the crash:

After landing at RJTT runway 16L, the speed was reduced to 30 knots.

 

1773751486.bin

[TololoEZS]

• Aircraft: A350-900
• Simulator: FS2024
• Navdata Method: NAVIGRAPH
• OFP: Happened on oceanic routes
• WASM Error: WASM: Error during EFIS_gauge_update execution. Error code : 0xc0000005
• Specs: RTX4090 - I7-14700KF - 64GB RAM
• Autosave File: /
  

1773754170.bin

Edited 2 hours ago by TololoEZS