happening to me 2024 JustFlight 146, tried reloading multiple times, thus unusable, voted
i got this in a A330-300GE passenger career mission. the autopilot was completely put of order. even if in the screenshot shows that he is still active (he isnt), also the thrust is complete stuck which means i need to land with 38% of thrust (maybe add that as a challenge). it happened after i wanted to fly to the waypoint ratan after my descent was far to late thanks to the atc (improvements when?). the route was from vidp to vnkt.
if something like that would happen in reality the fleet would be grounded immediately
I never had this before but with the new year I suddenly get WASM crashes in pretty much every flight.
No changes to my system, no changes to the sim.
The last crash did not even give me the orange displays. It just had the whole cockpit freeze while the plane kept flying and eventually crashed to the sea.
I just had one in the Ini A350 (PC). It’s a sim thing. I’m collecting the whole set 
ps. it’s happening on many other devs airliners too. Although in PMDG’s case they patched their FS2024 737 in late December to try to mitigate it.
In their release announcements they say -
”We have also brought in some memory management techniques that had some success in the 777 program to reduce the rate of instance for WASM crashes that seem to plague MSFS 2024.”
It’s time MS/Asobo addressed these WASM issues. They are happening intemittently but too frequently for my liking, and across aircraft/developers/platforms.
The same issue. Also, at the final stage of the flight.
On PS5 also exists.
For me it happens nearly always at gate on initial setup, but always before taxi. Not good if it’s happening mid flight for others though. It was happening on my old PC before Christmas and now on my new PC, as well as across airliners and developers so I’m quite confident it’s a sim issue at this stage. It’s intermittent, and comes and goes so probably hard to tie down.
I just bought the A340 from the marketplace and I’m now experiencing these WASM crashing issues.
This never happens to me with the Fenix A320.
And how much longer are we going to have to wait to fix this problem?
@Microsoft/Asobo/Inibuild, do your job before selling us things that don’t work…!!!
I experienced the same while on vatsim, EGLL > EGPH. I put a left hold in at TARTN, which I then removed - so it must be related to this. Have flown this same route before (also EGKK > EGPH) with no hold and it was all OK.
Route:
EGLL/27R N0439F360 UMLA1F UMLAT T418 WELIN T420 TNT UN57 POL UN601 ABEVI N601 INPIP INPI1E EGPH/24
Image of “RSOD”:
I recently cleared my WASM folder for FS2020. Also in my BIOS, I’m on AMD 9800X3D, I had my Core Configurations for Gaming set to Legacy. Set it back to Auto and it’s working well now.
Saying only “I have a WASM crash” is not enough.
A report must include a list of all programs / addons running during the flight, for example:
- FSUIPC
- SPAD.neXt
- AxisAndOhs (AAO)
- MobiFlight
- ChasePlane
- GSX
- Active Sky
- etc.
Also, read the topic “How to – Verify and Report WASM Crashes?” before posting.
https://forum.inibuilds.com/topic/25287-how-to-verify-and-report-wasm-crashes
I have been flying Ini A350 for the last two days without a single WASM crash. I also had no WASM crashes when flying: Fenix A321, PMDG 777/738, or iFLY MAX 8.
The addons I have running during flight are: SPADneXt, GSX and of course I have various airports in the Community folder.
I’ve only ever had one WASM crash which was with the A330-300GE after a long haul flight from Paris to Madagascar. I was having problems getting the RNAV approach to work, and I had just tried to restore the flight plan from the secondary when it crashed. That was probably a 10+ hour flight.
exactly same happened with me now my every flight crashes wasm
Hi folks,
Please can I ask that reports in this thread be specific to 1st party products and not 3rd party products, and also related to WASM based 1st party (default) airlines such as the iniBuilds Airbus series.
If there are any particular details of your flights (such as the route and what caused the WASM crash) will be invaluable data for the testing team to try to replicate. For example if you proceeded direct to a particular waypoint in the MCDU and as soon as you pressed a particular button it WASM crashed, or something similar, this sort of information would be greatly appreciated.
Thanks
The MSFS Team
2 Likes
Had this last night after a 3 hour passenger mission, went to do a go around and boom wasm crash. Tried to land and aircraft just keep accelerating. 4m bill, could have been worse but very frustrating.
one thing after another with this game
Just an update from me (PC user) for wasm crashes. I’ve not tried a broad spectrum of airliners having mainly been flying the FSS E190 most, but I‘ve done about 10 flights with no wasm crashes so far. Previously I was seeing a wasm crash every 2-3 flights irrespectve of airliner type. What did I find? Disabling/uninstalling FSUIPC (I was using it for PACX) seems to have stopped the wasm crashes for me. I know this isn’t an xbox solution, but just another clue perhaps.
Same issue.
I press the “DIR” button from the MCDU and direct crash.
I use the default A320 neo (this plane is full of bugs, I think I will have to switch to FBW a32nx, but not available in career)
There’s a reason why FSUIPC was the first addon I brought up.
I highly doubt it’s the root cause of the problem itself. At most it seems to trigger or expose the issue. In any case, the WASM crash is already bug-logged, so at this point all we can really do is wait for a fix.
Yes thank you for that suggestion. It was one thing that I had recently added back in (which made me suspicious). Now removed. I do hope they get on top of the real reason for wasm crashes for the rest of users and especially on xbox. Good to see it’s bug logged. FSUIPC is maybe just a clue as it exacerbates wasm crash episides for me.