December 20, 2025Dec 20 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
December 28, 2025Dec 28 Author any idea what caused this? I'm always getting a WASM crash in cruise only there without me doing anything. It's quite frustrating.
December 30, 2025Dec 30 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.
January 1Jan 1 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.
January 4Jan 4 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 January 4Jan 4 by DrShadow
January 4Jan 4 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 January 4Jan 4 by IndiaAlpha
January 8Jan 8 After reinstalling the software, I flew four times. The first three flights went without a problem, so I thought it was stable. However, today I used it to fly from Beijing to Munich, and it crashed twice during the flight, requiring me to use the auto-save function to recover. It's too unstable.
January 8Jan 8 On 12/20/2025 at 12:16 PM, Skyrock said: 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 1.26 MB · 1 download 1766248844.bin 152.81 kB · 1 download Hi, we are aware of this issue (not a WASM crash but an issue where the sim and aircraft seem to lose connection with each other) - we are in discussion with Microsoft about the cause/remedies to the issue. We haven't been able to identify a fix yet but we are working on it 🙂 AMD 7800x3d - 64gb RAM - nVidia RTX 5080
January 8Jan 8 @iniSteven Thank you so much for providing a reply to this discussion. I already lost hope that iniBuilds still cares about the ongoing issues with the A350. It is great to see that you acknowledge the issue and are willing to provide a fix. Could you please confirm if my reported issue here has the same root cause (although it clearly says "WASM Crash" on the screen)? If yes it would be great if you could copy&paste your reply there as well so people get that feedback. FYI, by mistake I've created that linked bug report in the MSFS 2020 section, please feel free to move it into the MSFS 2024 section for the A350 to avoid any confusion (I can neither move not delete that thread anymore). Thank you!
January 8Jan 8 9 minutes ago, sirupflex said: @iniSteven Thank you so much for providing a reply to this discussion. I already lost hope that iniBuilds still cares about the ongoing issues with the A350. It is great to see that you acknowledge the issue and are willing to provide a fix. Could you please confirm if my reported issue here has the same root cause (although it clearly says "WASM Crash" on the screen)? If yes it would be great if you could copy&paste your reply there as well so people get that feedback. FYI, by mistake I've created that linked bug report in the MSFS 2020 section, please feel free to move it into the MSFS 2024 section for the A350 to avoid any confusion (I can neither move not delete that thread anymore). Thank you! Hi Sirup, your other issue is a traditional WASM crash - again we are working hard to reduce these but as we've mentioned it's not an easy thing to fix, most crashes are unique in the sense that there isn't one fix for all of them, so it's a game of trying to recreate each report to see if we can replicate it, and from there prevent that specific crash from happening. Your issue in this thread though is one we have identified a consistent issue, and are working with MS on a fix as we've been able to recreate this issue with other addons. Currently we are trying to identify exactly what it is about our implementation that seems to cause this to happen more frequently with our products. AMD 7800x3d - 64gb RAM - nVidia RTX 5080
January 8Jan 8 Thank you very much for these insights. They are really important and helpful for all your customers to understand where we are and that iniBuilds is taking care of issues, still. It is great to hear that you could reproduce "my" WASM crash, that gives us hope that it will be fixed in an upcoming update. Please continue communicating and responding to reported issues so the community can go though that journey together with you and so that you can build up some trust again. I was very interested in buying the A340 as well but given the issues with the A350 that currently do not allow me to use this model in any reasonable way, I decided not to buy any further iniBuilds airplanes. If issues with the A350 can be fixed and trust can be reestablished, you will have me back as an A340 customer.
February 1Feb 1 Not surprising, the release notes didn't mention any fixes of WASM issues or the sim connect issues, unfortunately.
February 5Feb 5 I had the same problem (at least I think) that shows no error except for VDGS. Lovely plane and I can't wait for iniBuilds to fix the sim/WASM connection!
March 28Mar 28 On 1/9/2026 at 12:52 AM, iniSteven said: Hi, we are aware of this issue (not a WASM crash but an issue where the sim and aircraft seem to lose connection with each other) - we are in discussion with Microsoft about the cause/remedies to the issue. We haven't been able to identify a fix yet but we are working on it 🙂 Any update on this, my last 3 flights in the A350 have all had my gauges freeze and my plane start doing sprials, This is a new issue for me, and its wearing thin.
April 7Apr 7 Same issue last about every second or third flight. Screens either crash orange WASM or freeze.
April 24Apr 24 Latest update 1.2.5, still getting crashes WASM: ERR_FATAL_FILE_ERROR (-239 / ffffff11) WASM: Error -239 / ffffff11 [SS_WMKK_Airport_Driver.wasm] SS_WMKK_Airport_Driver: Initializing Version [1.20.40] [SS_WMKK_Airport_Driver.wasm] SS_WMKK_Airport_Driver: Connected to FS2020 [SS_WMKK_Airport_Driver.wasm] SS_WMKK_Airport_Driver: The FS2020 subscriptions have been registered. [SS_WMKK_Airport_Driver.wasm] SS_WMKK_Airport_Driver: Airport data populated. [fsdt-msfs-bridge.wasm] fsdt-msfs-bridge: Simconnect Dispatch proc set. [noolaero-vdgs-lppt.wasm] [noolaero-vdgs-lppt] EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-essa.wasm] [noolaero-vdgs-essa] EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-eidw.wasm] [noolaero-vdgs-eidw] EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-lszh.wasm] [noolaero-vdgs-lszh] EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-bikf.wasm] [noolaero-vdgs-bikf] EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-ksea.wasm] Sim | EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-klga.wasm] [noolaero-vdgs-klga] EXCEPTION 25: The AI operation requested cannot be completed [SS_WMKK_Airport_Driver.wasm] AIRCRAFT_TITLE[0]: A350-900 (Default Cabin) [SS_WMKK_Airport_Driver.wasm] INIBUILDS: A350-900 (Default Cabin) [WASM][IO] ./data\Textures\RMP\RMP-Main.png not found [WASM][IO] ./data/Textures/FCU/FCUCompo1k.png not found [WASM][IO] ./data\Textures\ECAM\Wheel1000More.png not found [WASM][IO] /Data\Textures\PFD\PFDA350Elements.png is neither a vfs path ('.\') or work path ('\work\)' WASM: Error during EFIS_gauge_draw execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty
April 24Apr 24 1 hour ago, Brettsan said: Latest update 1.2.5, still getting crashes WASM: ERR_FATAL_FILE_ERROR (-239 / ffffff11) WASM: Error -239 / ffffff11 [SS_WMKK_Airport_Driver.wasm] SS_WMKK_Airport_Driver: Initializing Version [1.20.40] [SS_WMKK_Airport_Driver.wasm] SS_WMKK_Airport_Driver: Connected to FS2020 [SS_WMKK_Airport_Driver.wasm] SS_WMKK_Airport_Driver: The FS2020 subscriptions have been registered. [SS_WMKK_Airport_Driver.wasm] SS_WMKK_Airport_Driver: Airport data populated. [fsdt-msfs-bridge.wasm] fsdt-msfs-bridge: Simconnect Dispatch proc set. [noolaero-vdgs-lppt.wasm] [noolaero-vdgs-lppt] EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-essa.wasm] [noolaero-vdgs-essa] EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-eidw.wasm] [noolaero-vdgs-eidw] EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-lszh.wasm] [noolaero-vdgs-lszh] EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-bikf.wasm] [noolaero-vdgs-bikf] EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-ksea.wasm] Sim | EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-klga.wasm] [noolaero-vdgs-klga] EXCEPTION 25: The AI operation requested cannot be completed [SS_WMKK_Airport_Driver.wasm] AIRCRAFT_TITLE[0]: A350-900 (Default Cabin) [SS_WMKK_Airport_Driver.wasm] INIBUILDS: A350-900 (Default Cabin) [WASM][IO] ./data\Textures\RMP\RMP-Main.png not found [WASM][IO] ./data/Textures/FCU/FCUCompo1k.png not found [WASM][IO] ./data\Textures\ECAM\Wheel1000More.png not found [WASM][IO] /Data\Textures\PFD\PFDA350Elements.png is neither a vfs path ('.\') or work path ('\work\)' WASM: Error during EFIS_gauge_draw execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty You have conflict between WASM addons. Try to test only with A350.
Yesterday at 09:59 AM1 day can you see where and what is conflicting? i don't use a lot of mods other than scenery... well I thought
23 hours ago23 hr I fed your error log to the Gemini AI and got the following analysis back. I have no clue if it is of use but suggest to give it a try: WASM Crash Analysis: inibuilds A350-900 Conflict The provided error log points to a classic memory access violation (0xc0000005) occurring when multiple complex WASM modules compete for resources. While the inibuilds A350 is the "victim" here, the log reveals several other active modules that are likely triggering the instability. Identified Conflict Candidates Skyline Simulations (WMKK) - Primary Suspect: Log Entry: [SS_WMKK_Airport_Driver.wasm] SS_WMKK_Airport_Driver: Initializing... Reasoning: This driver belongs to the Kuala Lumpur (WMKK) scenery by Skyline Simulations. Interestingly, the log shows this driver actively reading the AIRCRAFT_TITLE of the A350 right before the crash. This interaction suggests a direct conflict between the airport's custom logic and the A350's WASM environment. Noolaero VDGS (Multiple Airports): Log Entry: [noolaero-vdgs-xxxx.wasm] EXCEPTION 25 Reasoning: These modules manage the Visual Docking Guidance Systems for various airports (LPPT, ESSA, EIDW, LSZH, etc.). The log shows a flood of "EXCEPTION 25" errors. While these might not always cause a CTD (Crash to Desktop) on their own, they clutter the SimConnect stream and increase instability. FSDreamTeam (FSDT): Log Entry: [fsdt-msfs-bridge.wasm] Reasoning: This is the bridge for GSX or FSDT sceneries. It is active but generally stable; however, it adds to the overall WASM load. The Fatal Sequence The crash occurs immediately after the SS_WMKK_Airport_Driver identifies the aircraft. Simultaneously, the A350 fails to locate several PNG texture assets: WASM: Error during EFIS_gauge_draw execution. Error code : 0xc0000005 This indicates that the memory address the A350 was trying to use for its gauges was likely "stepped on" or blocked by another module (most likely the WMKK driver). Recommended Troubleshooting Steps Isolate WMKK: Temporarily remove the Skyline Simulations WMKK folder from your Community folder. This is the most likely fix, as the crash occurs exactly during its initialization phase. Update/Disable VDGS: If you are using a standalone VDGS package or sceneries from Aerosoft/JustSim that use Noolaero, ensure they are up to date. Clear WASM Cache: Delete the contents of the WASM folder located in your LocalState directory (the path varies for Steam/Microsoft Store). The simulator will rebuild these files on the next launch. Use Addon Linker: Since the A350 is a resource-heavy aircraft, use an Addon Linker to disable unnecessary airport drivers (like the ones for Dublin or Stockholm) when you aren't flying to/from those specific locations.
22 hours ago22 hr <removed> Looks like a weird filter thing ... Edited 22 hours ago22 hr by sirupflex
Create an account or sign in to comment