Pihkin

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.