WASM crash report

[Skyrock]

Just cruising along at FL410, no inputs or anything. Screenshots attached.

• Aircraft: A350-900
• Simulator: FS2024
• Navdata Method: NAVIGRAPH
• OFP: Include a PDF of your Operational Flightplan (OFP) if related to FMS/Route Procedures crashes
• WASM Error: It for some reason only shows vdgs related items? But clearly the displays are frozen and my A/C is flying to the northeast instead of east. 
• Specs: Ryzen 9800X3D, RTX 4080 Super, 32GB of RAM
• Autosave File:  Included

 

JX119_YWG_FRA.pdf 1766248844.bin

[Skyrock]

any idea what caused this? I'm always getting a WASM crash in cruise only there without me doing anything. It's quite frustrating.

[vahe312]

I had the same problem this morning, and my screens turned red

[BazAir]

I was in a 7 hour flight and exactly the same thing happened to me as well. Nothing I could do to fix it other than end my flight. Agree with you about it being frustrating. Have you logged a ticket direct with inibuild? This is obviously a continuing issue.

[sk0941]

Happened to me to when over the Atlantic a couple of hours into my flight

[sirupflex]

I can confirm that this happens to me as well quite regularly. During flight at cruise altitude, without any input or activity from my side, some functionality of the A350 stops working and/or modules freeze and you have to abort the flight. It is hardly possible for me to have a 3-4 hours flight without the A350 crashing rather sooner or later.

It is then also a bit frustrating when iniBuilds celebates the A350 in their 2025 review but in fact for me the very expensive airplane is actually useless. A long-range model that crashes on nearly all long-range flights. For me, stability of the A350 has not improved. All other airplane models in MSFS 2024 are stable and I hardly have any issues with anything else than the A350.

Today I logged a WASM crash report in the forum (in the MSFS2020 section of the forum by mistake), hoping it helps resolving issues.

iniBuilds says they are seeing less A350 WASM crash reports than in previous months and conclude that the A350 is much more stable now. My perception is rather that many customers gave up on the A350 at all or stopped reporting bugs out of frustration because not a lot changed in all those months. I cannot confirm that the A350 is even close to stable.

[DrShadow]

Hi all

I am happy to share my experiences on this topic.
Until the last update, I was able to fly without any problems. I flew to Australia with the A350 and 350 ULR and never had any issues. There were no errors in the systems or in the EFB. At least not any that made flying impossible. Now, since the last major update, that has changed. I was confronted with the orange screens for the first time and had to figure out from A to Z what had happened. I didn't even know there was a WASM crash.

Today, I fly mostly with the A340, as the crashes with this aircraft are “within limits.” I don't fly the A350 as often anymore, as I am confronted with the WASM crash at any time and then have to end the flight.

I think this is an important issue that should be addressed. Something has changed in the latest update, which sad because the aircraft is really fun to fly.

I have already created links in Explorer so that I can find the FASM folders more quickly and delete them so that I can fly again. 
Keeping an eye on the WASM issue and paying special attention to it would be a blessing for the bird and for us 🙂

 

Edited Sunday at 10:12 AM by DrShadow

[IndiaAlpha]

Yes, the WASM crashes are occurring quite regularly. Nearly every flight I take has one, where everything just freezes up without me doing anything at all. I’m currently not able to provide screenshots from the console, but I will do so when I encounter another crash.

I’m very frustrated with this because the airplane has great potential and is quite good if it were stable. I’ve never experienced so many problems with other products and I have a good selection.

Edited Sunday at 07:01 PM by IndiaAlpha