Lucstra Posted April 5 Posted April 5 WASM Crash Report – iniBuilds A350 (FS2024) I encountered a WASM crash after vacating runway 25 at EDDS following a diversion caused by a dual engine shutdown. Flight Details: Route: LFPG 26R BUBLI6A BUBLI DCT LUVAL DCT MIRGU DCT BEGAR DCT TRA DCT GAMSA DCT UMVEG DCT DIMLO/N0485F350 DCT INVED DCT DINRO DCT UDROS UM859 KARDE UN644 ROLIN DCT TETRO DCT BARAD M747 SUBUT T916 LEYLA/N0499F370 N161 GASBI/K0919F370 N161 SARIN/K0889S1130 A368 SALMO/K0885S1190 A368 FKG W188 LIKMI W270 DKO W69 HUR B339 LADIX W34 VAPGU W100 ORAVA W201 UNSEK A326 SANKO/K0906S1250 A326 DONVO G597 AGAVO/N0487F410 Y644 EGOBA G597 LANAT Y71 XAC XACL RJTT16L Aircraft: iniBuilds A350-900 v1.2.4 (with cabin) Simulator: FS2024 Navdata: Navigraph Issue Description: A dual engine shutdown occurred unexpectedly between LUVAL and BEGAR. I initiated a diversion to EDDS via REUTL5A arrival for runway 25. After landing, I disconnected the autothrottle at approximately 50 knots to vacate the runway via taxiway I. The WASM crash occurred during runway vacating. Error Message: WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty WASM: Error during MFD_gauge_update execution. Error code: 0xc0000005 System Specs: Ryzen 7 9800X3D, RTX 5070 Ti, 64GB RAM 1775397464.bin 1
Thyra7 Posted April 7 Posted April 7 On the ground at LHR. MSFS SU4, latest A35K version. During cockpit preparation, adding the TRANS / VIA for KLAX crashed it immediately, turning all displays orange. 1
Thyra7 Posted April 7 Posted April 7 10 hours ago, Thyra7 said: On the ground at LHR. MSFS SU4, latest A35K version. During cockpit preparation, adding the TRANS / VIA for KLAX crashed it immediately, turning all displays orange. During flight adding a complex arrival no issue. Seems to be an issue during pre-flight heavy loads. 1
Sirraj Posted April 8 Posted April 8 WASM error occurred when I attempted to change the arrival runway during cruise. Thank you. Aircraft: A350-900 Simulator: FS24 Navdata Method: NAVIGRAPH Specs: Ryzen 7 9800X3D, AMD RX7900XT, 64Gb DDR5 6000 RAM KSFOKLAX_PDF_1775657462.d434bc26.pdf 1775656981.bin 1
lucianoo__ Posted April 9 Posted April 9 (edited) Aircraft: A350-900 (no cabin) Simulator: FS2024 Version: 1.24 Navdata Method: NAVIGRAPH SPECS: i9-9900k, RTX3070ti, 32GB RAM WASM crash after switching frequencies. Last thing I did was dial in / type in the frequency and then switch to it on the RMP. the RMP WASM gauge also failed. If this is any relevant to the case, I was connected on VATSIM. As I now found out the location of the autosave files, this time I attatched two autosave files (each 10 minutes apart, one of those should be just before the crash I hope.). 1775694645.bin 1775694041.bin Edited April 9 by lucianoo__ 1
Kirkus Posted Friday at 08:02 AM Posted Friday at 08:02 AM Ghost WASM crash RKSI - VHHH, frezze was just south of Taiwan. PC specs as per othe posts. Prior to the update on 18 March, my first and last Ghost WASM crash was on the 20-07-2025. I have also never had an Orange screen WASM crash in the A350 (has plenty in the A340 but thats another story) Basiclly since the update on march 18, I have completed 3 out of 10 flights with out a "Ghost WASM" crash. Between 20-07-2025 and 18-03-2026 I had completed 21 fligths with a total of 1 "Ghost WASM" Crash. What have I done to mitigate it, reinstalled ini manager and the A350, disabled add-ons that I usuaally use to fly with like auto FPS and any2GSX. 1
flor4s Posted Friday at 03:31 PM Posted Friday at 03:31 PM (edited) WASM crash after changing arrival information - it happened exactly when changing transition point. I was changing it to: 24l, rockt3, tibos Aircraft: A350-900 Simulator: FS2024 Version: 1.2.4 inimanager Navdata Method: NAVIGRAPH OFP: Attached WASM Error: WASM: Error during MFD_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 Specs: 9800x3d, rtx 4090, 64GB RAM EDDMCYUL_PDF_1775803945.5f688ee2.pdf Edited Friday at 04:26 PM by flor4s 1
Silent Shark Posted Sunday at 01:59 PM Posted Sunday at 01:59 PM (edited) Aircraft: A350-1000 default cabin Simulator: FS2024 Version: iniManager 1.2.4 Navdata Method: NAVIGRAPH (using LIDO charts in OIS though) Specs: R7 9800X3D, 5090, 64GB DDR5, Win 11 Other notes: Was flying in VR, had some weird GSX issues on the ground but doubt they did much. SGES-SAEZ Crash happened not long after take-off, again when I was inputting the arrival procedure, RNAV17 and PAGO7V. When I selected the VIA for ARSOT, crash happened then. 99% of my WASM crashes happen when doing this. Thought I'd get my approach settings in early this time, it didn't help ☹️ UPDATE: Further notes to add - Did the flight again, waited until stating descent before setting the arrival, and it crashed again (not captured error that time, sorry). But as I was most of the way through this time, I reloaded from save states and tried once again. When picking the arrival this time I was sim-paused still from the reloading, and I also accidentally mis-clicked on NONE when setting the VIA, and then selected ARSOT and it accepted it. Don't know if this made a difference, but it's something I'll try in the future... Edited Sunday at 03:49 PM by Silent Shark 1
A330MRTT Posted Sunday at 02:38 PM Posted Sunday at 02:38 PM (edited) Aircraft: A350-900 Simulator: FS2024 SU4 Version: 1.2.4 / iniManager Navdata Method:NAVIGRAPH OFP: No OFP WASM Error: Specs: 13700K RTX4090 32gb RAM 6000Mhz, Windows 11 Autosave File: Autosave not activated During insertion of APPCH and VIA the above posted WASM Crash occured. Edited Sunday at 02:39 PM by A330MRTT 1
Pilota459 Posted Sunday at 03:43 PM Posted Sunday at 03:43 PM Aircraft A350-1000 Simulator MSFS 2024 - SU4 Navdata NAVIGRAPH System Specs CPU: 7800x3D GPU: RTX4070 super RAM: 64GB DDR5 6000 MHz WASM ErrorWASM crashed Module: aircraft-a350 Package: inibuilds-aircraft-a350 Objects/Airplanes/iniBuilds_A350/attachments/iniBuilds_Function_Interior_A350/panel/inibuilds-A350.wasm Scenario Description Crash occurred on ground during cockpit preparation, specifically, during entering the STAR Steps to Reproduce Aircraft powered, cockpit setup in progress, APU started Flight plan inserted into FMS departure enter STAR → Immediate WASM crash Observed Behavior All cockpit displays turned orange after inserting the arrival (WASM crash state) 1
richinspirit Posted Monday at 08:47 AM Posted Monday at 08:47 AM Aircraft: A350-900 Simulator: FS2024 SU4 Version: 1.2.4 / iniManager Navdata Method:NAVIGRAPH CPU: Ryzen 7 9800X3D (8 cores) GPU: NVIDIA GeForce RTX 5080 (16GB) RAM: 64GB DDR5 I wasn't sure how to get the wasm details from the dev mode but will have a look through on the forum for the future. First ever WASM crash but not flown the 350 that much yet - was on the ground at Doha and doing my cold and dark start, WASM crash occurred as I clicked request company flight plan in the INIT page and there was a message in the orange screens saying it was an EFIS gauge WASM...not sure if that helps, but not seen anyone get one at this particular part of a flight so thought worth reporting. Do tend to agree, the 1.2.4 version seems less stable than the 1.2.1 1
LePillowLord Posted Monday at 02:49 PM Posted Monday at 02:49 PM Was cruising peacefully FL360 VHHH-WSSS and decided to turn on 4x time acceleration, not sure if it was because of that but i come back to a red screen Routing: PECA2B PECAN V12 EPDOS L642 EPKAL/K0935F360 L642 ESPOB/N0505F360 Q801 ESBUM Q802 ELALO ELAL1B Position: 10NM before EPKAL
Pihkin Posted Monday at 04:03 PM Posted Monday at 04:03 PM Over the past 2–3 days I’ve been flying the A350. The first WASM crash happened at LIMC right after landing, just after exiting the runway. I thought it was just bad luck and cleared the WASM. My second flight to EDDM was completely fine with no issues. For my third flight (EDDM–LTFM), during the approach I realized that I had entered the wrong STAR. Following ATC instructions, I updated the STAR from RIXE1A to RILE1A. The moment I entered "via IMREN", I experienced a WASM crash and, out of frustration, I closed the flight. Today I started the simulator again to try the same flight. This time, before even taking off, while still at the gate, I entered the STAR (RILE1A via IMREN) and again got a WASM crash. During all of these flights, autosave was disabled, so I didn’t have a file available. I restarted the simulator to try to reproduce the scenario with autosave enabled, but this time the issue did not occur. Before the last WASM crash occurred, I deleted the WASM folder, removed the aircraft and its livery, then reinstalled them through inimanager. I also updated Navigraph, installed the terrain data, and restarted the simulator. Aircraft: A350-900 / TC-LGS Simulator: FS2024 Navdata Method: Navigraph OFP: I don’t think the flight plan is related to this issue, as the crash can happen at any time and anywhere. WASM Error; WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty WASM: Error during MFD_gauge_draw execution. Error code : 0xc0000005 Specs: Windows 11 Pro 24H2. CPU: Ryzen 7 7800X3D GPU: NVIDIA GeForce RTX 4080 Super RAM: 32GB DDR5 6000Mhz Autosave File: I followed the specified file path, but there were no files there, so I do not have an autosave file.
Fiorentoni Posted Monday at 04:53 PM Posted Monday at 04:53 PM (edited) Had several WASM crashes over the last week, each time entering (IIRC) approach (only approach, no arrival, no transition, just ILS xxx) in the SEC F-PLN. All different airports. It's not 100% reproducible, but it happens often enough in SEC F-PLN while doing that to have a pattern. Edited Monday at 09:20 PM by Fiorentoni
Simon R Posted 6 hours ago Posted 6 hours ago Dear Ini Team, The crash happens when pressing "Insert" after a flight plan request (INIT page) 2 mins after spawnning at gate K58 LFPG Aircraft: A350 / Default Cabin / Simulator: FS2024 Version: 1.2.4 Navdata Method: NAVIGRAPH OFP: LFPG-CYVR WASM Error: WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005 WASM Error: WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty Specs: Ryzen 7 5800X3d / RTX 4070 / 32gb Ram Autosave File: No .bin due to previous WASM Crach so WASM Folder was clean using your method. Autosave Folder is not available. (see screenshot in attachment) You will find in attachment the file "Description" for the console error and the file for the Flight Plan. I hope you have all the information you need. Please let me know if you need any additional details. Thank you in advance for your help. Best regards,Description.txtLFPGCYVR_PDF_1776192970.f64d8a57.pdf
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now