WASM module crashed

[jan_aviation]

Helllo guys,

I took off from Athens today with the 340 and shortly after takeoff I had this bug in the cockpit with the screens etc turning orange and saying WASM module crashed, what do I have to do to solve this?

 

Jan

[STEVEBOB87]

Hi,

Count me in. The orange screens are still present even after restarting the sim (as shown in the screenshot). The WASM crash occurred mid-flight, about three hours in, while I was working in the MCDU on the STEP ALTS page.

I’ve given this aircraft multiple chances since its release, but I’m honestly quite disappointed. I experience a WASM crash every second or third flight, even after five updates. The first time it happened, I didn’t even realise it was a WASM crash - I haven’t encountered anything like this in years, it "only" happens with this product.

It’s particularly frustrating because the aircraft is excellent when it works. I deliberately stayed away from the 350 due to the WASM reports, despite really wanting it. I couldn’t resist the 340, unfortunately - lesson learned.

Please, fix this product.

Sandro

[Beurreesale]

11 hours ago, STEVEBOB87 said:

Hi,

Count me in. The orange screens are still present even after restarting the sim (as shown in the screenshot). The WASM crash occurred mid-flight, about three hours in, while I was working in the MCDU on the STEP ALTS page.

I’ve given this aircraft multiple chances since its release, but I’m honestly quite disappointed. I experience a WASM crash every second or third flight, even after five updates. The first time it happened, I didn’t even realise it was a WASM crash - I haven’t encountered anything like this in years, it "only" happens with this product.

It’s particularly frustrating because the aircraft is excellent when it works. I deliberately stayed away from the 350 due to the WASM reports, despite really wanting it. I couldn’t resist the 340, unfortunately - lesson learned.

Please, fix this product.

Sandro

Got the exact same problems

[jan_aviation]

And there are not any solutions? 😪

[_Double]

Same issue. I hadn't flown the A340 for a few updates, but I updated to 1.0.6 last week. I did not attempt a full flight until today. As of now, I get the error every time I attempt to enter custom waypoints for ETOPS in the stored waypoints data page. I have yet to make it past that point. I've uninstalled, cleared WASM, and removed all lingering ini A340 directories as well as loaded other aircraft in between attempts for both streamed and installed modes. 

Edited December 27, 2025 by _Double

[Airbumps2501]

Would be nice to get some kind of comment from @IniSteve, @iniBuilds Team @iniBuilds Pablo or anybody else from inibuilds on this. It is effecting so many of us and there really has been ZERO communications or support offered. There are multiple forum threads abou the issue which has been very well reported for months (since SU4 Beta arrvied).

Is this just going to be one of those issues thats easier to ignore than address?

[andreabarbuto]

@IniSteve  @Team iniBuilds @iniBuilds Pablo

Un caro saluto a Tutti Amici. Successo Ieri, dopo 5h e 30' di volo con MSFS2024.... Si è verificato autonomamente, senza alcuna azione da parte mia, in crociera a FL410.  Non ho provato con MSFS2020 quindi non saprei se il problema si manifesti anche con il 2020.

IniBuilds A350 v1.2.0 update 18 dicembre 2025 per MSFS2024.

Terze parti utilizzate durante il volo: Little Navmap v3.0.18 64-bitMSFS2024 AIRAC 2513;  FSLTL Traffic per MSFS2024 v1.8.0; A Pilot's Life Chapter 2 v2.2.1.181; FSUIPC v7.5.5; Pianificazione volo con Simbrief AIRAC 2513.

Cieli Sereni.