kmoberg

Example WASM Crash Report Flying on the most recent AIRAC (2505) when flying LAX > BNA I had already reloaded the flight for a CTD early (about an hour and a half) into the flight. The flight recovered fine so I continued. However, some issues did creep up: * I was no longer able to load any fixes on the FIX INFO page. I could enter info into there, but nothing would appear on the ND nor the MCDU. Prior to the sim crashing, I had utilized all 4 FIX pages with pilot defined waypoints. About 8 hours later, I was loading my approach data into BNE, and I realized that even though the runways popped up on the data page, no approaches nor STARS were available. When I selected RWY 19L, it did allow me to move on to the next box, but nothing was actually entered in the MCDU approach page, it kept just giving me blank data. I did get the option to INSERT, so I did, clicked YBBN again, selected rwy 19L again, then WASM crashed. To reproduce Load autosave Select any approach runway into BNE. Select any approach type (i only had 1 available, just said 19L) Insert with no STAR Go back to select any approach type Select rwy 19L Information Aircraft: A350-900 Simulator: FS24 Navdata Method: NAVIGRAPH - 2505 OFP: Attached Specs: Ryzen 9800X3D, RTX 5080, 64GB RAM Autosave: Last two autosaves attached - pretty sure the newest saved after the crash WASM: Error during BAT_gauge_update execution. Error code : 0xc000001d KLAXYBBN_PDF_1746957875.pdf 1747004102.bin 1747004344.bin

To be clear, it crashed at around the same physical location flying LAX-SYD as well. I don't have any records of that flight though, I deleted the Volanta track and don't have any error report either. Sorry.

WASM Crash Report Ok, I've managed to crash this flight 4 times, at the basically exact same place - 5 times if you include my LAX-SYD flight as well, but that one I just trashed and forgot about. However, I managed to fly LAX-SYD again, but on a different route, then on the return flight SYD->LAX it crashes. I load up the autosave, it crashed shortly after. I loaded the oldest autosave, it crashes on the same location again. To reproduce Fly on the specific route, it crashes close to the waypoint 30S164E. Information Aircraft: A350-900 Simulator: FS24 Navdata Method: NAVIGRAPH OFP: Attached Specs: Ryzen 9800X3D, RTX 5080, 64GB RAM Autosave: Attached latest .BIN file before crash - attached all 5 autosaves, it crashed on the same location for all 5. WASM: Error during EFIS_gauge_update execution. Error code : 0xc000001d YSSYKLAX_PDF_1746604192.pdf 1746613974.bin 1746628650.bin 1746628846.bin 1746629043.bin 1746629239.bin

Happened once again, but this time I think I located the problem. The WASM plugin crashed after I was messing around in the native tablet - the sim froze while using the Navigraph plugin to import the route to the tablet/EFB, froze for a good 10-15 seconds or so. When it resumed, the plugin was crashed and everything was frozen and dead. FS2024, Steam, SU1 installed.

Mine crashed too after messing around with the lower display. WASM seems to have crashed.