Hello,

 

Aircraft: A350-1000

Simulator: FS2024

Navdata: Navigraph

OFP: included

Specs: CPU: AMD Ryzen 9800X3D, RTX 4080 Super, 32gb RAM

Autosave: unfortunately already deleted. 

WASM: apparently none?

I'm currently enroute from SYD to SIN in the A35K and after about 2hrs, overhead Alice Springs (AS), my displays froze completely. Why did I not write "WASM crash"? Because apparently there was none. According to this screenshot:

I don't know whether this helps to trace down the issue or not. This was the only error shown. I was not doing anything, in fact, I was laying on my couch and realized that the time in the ECAM had stopped 30min prior and with it all other displays. The ND was showing me going offtrack though before it froze. I was cruising at FL380 using Sayintentions. I merely just realized because my FO kept checking in with new sectors despite CPDLC not showing any handoffs or messages apart from the usual "connected". 

At this point the A350 is just frustrating for me. Every 2nd flight I get a display freeze (WASM crash or not, idk) and despite the autosave feature, it kinda ruins the experience. Last time I got it enroute from EDDF to WSSS after 4hrs into the flight. Unfortunately I didn't check the log.

I attached the OFP just to be sure. 

VS119_SYD_SIN.pdf

I had the same problem 5 minutes ago after 6-hours in flight. I've had this problem several times in the past. Yesterday, I made a 10-hour flight without any Problems. I have no idea why the error occurs sometimes. The error only started occurring for me after the latest Updates. Before I haven't had a single WASM crash since the release of the aircraft. 

4 minutes ago, Ron311280 said:

I had the same problem 5 minutes ago after 6-hours in flight. I've had this problem several times in the past. Yesterday, I made a 10-hour flight without any Problems. I have no idea why the error occurs sometimes. The error only started occurring for me after the latest Updates. Before I haven't had a single WASM crash since the release of the aircraft. 

Same. Yesterday I did SIN-SYD without any issues so I was kinda hopeful that I could do SIN-JFK tonight. But nope, not under these conditions. 50% reliability is not enough...

And it happened again...this time (yes I said I wouldn't do it, but I did anyways) enroute from SIN to JFK, after 9hrs over the pacific. I was not doing anything (again) and everything froze. I forgot to check the console for the WASM crash, but at least this time I managed to save the last autosave. The WASM crash or display freeze happened about 10min after the autosave...

I'm done with this. Uninstalling the A350, will revisit next year or so. It's way too frustrating (despite the autosave feature) to always be waiting for the WASM crash to happen. But I'm not willing to deal with this anymore

1757833492.bin

I can understand that; it's really frustrating when this happens after hours into a flight. It would be nice to have the option to roll back to an older version. I've been experiencing this error since one of the last Updates. Never had this problem before. I prefer to fly the Headwind A330 for now until hopefully there's a solution.

On 9/13/2025 at 10:27 AM, Skyrock said:

Hello,

 

Aircraft: A350-1000

Simulator: FS2024

Navdata: Navigraph

OFP: included

Specs: CPU: AMD Ryzen 9800X3D, RTX 4080 Super, 32gb RAM

Autosave: unfortunately already deleted. 

WASM: apparently none?

I'm currently enroute from SYD to SIN in the A35K and after about 2hrs, overhead Alice Springs (AS), my displays froze completely. Why did I not write "WASM crash"? Because apparently there was none. According to this screenshot:

I don't know whether this helps to trace down the issue or not. This was the only error shown. I was not doing anything, in fact, I was laying on my couch and realized that the time in the ECAM had stopped 30min prior and with it all other displays. The ND was showing me going offtrack though before it froze. I was cruising at FL380 using Sayintentions. I merely just realized because my FO kept checking in with new sectors despite CPDLC not showing any handoffs or messages apart from the usual "connected". 

At this point the A350 is just frustrating for me. Every 2nd flight I get a display freeze (WASM crash or not, idk) and despite the autosave feature, it kinda ruins the experience. Last time I got it enroute from EDDF to WSSS after 4hrs into the flight. Unfortunately I didn't check the log.

I attached the OFP just to be sure. 

VS119_SYD_SIN.pdf 855.78 kB · 0 downloads

 

I am having the same issue. Its been going on with v1.1.5 and now with v1.1.6. Its not wasm error.

Aircraft: A350-900 

Simulator: FS2024

Navdata: Navigraph

OFP: included

Specs: CPU: Intel i5-13400, RTX 3060 Ti, 32gb RAM

Autosave:  Included

I have also included screenshot of the error in console window

 

 

1760055156.bin WSSSLTFM_PDF_1760041392.pdf