AVGA

I would, but as my problem was a complete system freeze, there was no ability to get back to the main menu to look up the error. Had to force quit the sim, and upon reopening the program and going straight to the dev console, nothing was logged. Nor was anything found in Event Viewer. So, there is no information to me to provide, other than: - The freeze happened while trying to manually adjust vertical speed - Just before this, I briefly activated WX, which I never usually do, since there had been prior reports of WX use causing WASM crashes, but thought perhaps this was now fixed - along with Navigraph use causing WASM crashes

Was happening to me all the time, then the latest Inibuiilds update appeared to solve it ... until yesterday, when 2 hours into a 4 hour flight, I went to change altitude and got a total system freeze. Nothing logged in Event Viewer, and since the sim froze, force quitting and then going back into MSFS24 resulted in nothing showing in the sim error log, either. Assuming it's yet another WASM crash, but can't verify. Totally agree about stress ... every flight with this plane is a nail biting "will it CTD" experience. Which is such a shame, as the plane itself is incredible. Judging by their recent replies, Inibuiilds seems to be getting fed up with the requests to fix this, but something needs to be done, as we aren't the only ones having a problem, and it's definitely not my PC.

Same issue here. Also en route to VHHH, oddly enough. And it happened just a minute after I stupidly activated the WX, thinking it might be safe to use now. So, wondering if this is the same WX WASM issue as before, or if it's just a coincidence.

Have had the same issue since two updates ago. Same type of freezing, and no errors reported in Windows or MSFS24. As much as I enjoy the A350, I’ve given up on this plane until this is fixed. And yeah, I’ve tried everything Inibuilds and others have suggested. It’s a software issue that needs to be addressed.

Hi, Thank you. I’ve tried not using Navigraph data in the OIS, not using the OIS map, not using WX, and not using terrain - all of which was suggested to me. I’ve also cleared the WASM folder. But every flight freezes at some point … only since the last update. Can happen any time, though so far not while on the ground. Cockpit just freezes while sound continues to play, along with SayIntentions, which isn’t affected. Also, the sim doesn’t CTD. It just seizes up, and I have to force quit it to return to desktop. But PC is fine, as in, clicking off the sim is fine. And there is nothing reported in event viewer. welcome your thoughts. Also, can you confirm how to resume an auto save? Tried to restore a frozen flight - from the ground by getting back into A350 and selecting the last save from the OIS menu - and I ended up back in the saved flight with a cold and dark airplane, leading to a flight crash that went on loop until I quit the sim.

All I get are freezes and CTDs since the last update. Did everything that everyone has suggested - including on this thread - and plane remains impossible to use since last update. And this is the only plane that does it. Fenix will go around the world without a single issue. Inibuilds can’t get to level cruise without crashing out, since the last update. Wtf.

Did everything you suggested and froze again - during the climb. Not sure what else to do, as this plane is now impossible for me to fly, and I honestly can’t figure out why. Not even an entry in event viewer … sim just freezes. And it doesn’t with any other aircraft.

Thanks very much. Am on SU2, but was using everything else you mentioned. Will try this asap and let you know. Thx again.

Hi, 4 hours into a 5 hour flight, during decent at 23,000 ft., all glass cockpit instruments froze -- speed, altitude, etc. -- and certain buttons stopped responding, along with all flight controls. Plane continued to fly, but proceeding was useless, so I was able to hit ESC to return to main menu. But the flight was ruined, also because when I restarted flight on the ground and hit autosave, I ended up back at cruise altitude, with a cold and dark aircraft plummeting to the ground. Followed by a "you crashed" MSFS loop. Has anyone experienced frozen instruments since the last update? This is a whole new one for me, and nothing is logged in the Event Viewer. Any advice on how to properly activate an autosave would also be greatly appreciated. Thank you. Len

Thanks. I didn’t see the larger thread about this at first, but will try the nav data change and see if that works as a stop gap.

Also got a coherentUIGT error my first time out with the latest update. Hadn’t happened with prior versions, so didn’t know about the nav data workaround. Will try it, but the bug is definitely not fixed with the update.

Checking the forum, we aren’t alone with these issues, though I’m most curious about others having the same error I posted here. Did you check to see if you could find any error codes specific to your problem?

Thanks for replying. So now am wondering if this is an issue with the new update? Wondering if anyone else can confirm as well.

Hi, First flight with the latest version and five minutes after takeoff, sim went into the dreaded "freeze/sound cuts out/sound comes back/sound cuts out" then crash to desktop. Error report appears to blame a file named CoherentUIGT.dll", which is a new one for me. Is this related to Inibuilds, or something else? Advice welcome, also because the A350 was rock solid stable before I tried the latest update. Error report is below. Thx. - Len Log Name: Application Source: Application Error Date: 5/11/2025 11:22:43 AM Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords: User: FLIGHTOPS\len Computer: FlightOps Description: Faulting application name: FlightSimulator2024.exe, version: 1.3.23.0, time stamp: 0x00000000 Faulting module name: CoherentUIGT.dll, version: 2.9.5.0, time stamp: 0x6749d3e5 Exception code: 0xc0000005 Fault offset: 0x000000000007877c Faulting process id: 0x5FAC Faulting application start time: 0x1DBC29798FF1CE6 Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll Report Id: b47eb5b3-cf07-4825-ae12-ed8b54c63934 Faulting package full name: Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2025-05-11T18:22:43.1628211Z" /> <EventRecordID>8816</EventRecordID> <Correlation /> <Execution ProcessID="6676" ThreadID="12432" /> <Channel>Application</Channel> <Computer>FlightOps</Computer> <Security UserID="S-1-5-21-129321138-3886899281-40719315-1004" /> </System> <EventData> <Data Name="AppName">FlightSimulator2024.exe</Data> <Data Name="AppVersion">1.3.23.0</Data> <Data Name="AppTimeStamp">00000000</Data> <Data Name="ModuleName">CoherentUIGT.dll</Data> <Data Name="ModuleVersion">2.9.5.0</Data> <Data Name="ModuleTimeStamp">6749d3e5</Data> <Data Name="ExceptionCode">c0000005</Data> <Data Name="FaultingOffset">000000000007877c</Data> <Data Name="ProcessId">0x5fac</Data> <Data Name="ProcessCreationTime">0x1dbc29798ff1ce6</Data> <Data Name="AppPath">C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe</Data> <Data Name="ModulePath">C:\Program Files\WindowsApps\Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll</Data> <Data Name="IntegratorReportId">b47eb5b3-cf07-4825-ae12-ed8b54c63934</Data> <Data Name="PackageFullName">Microsoft.Limitless_1.3.23.0_x64__8wekyb3d8bbwe</Data> <Data Name="PackageRelativeAppId">App</Data> </EventData> </Event>