Latest Version - System Freeze

[AVGA]

Downloaded latest update. Set up a new flight. Got to 10000 feet and then sound cut out, came back, and MSFS2024 completely froze. Error log is attached. Please also note the lengthy amount of fuel system errors. Not sure if that's the reason for the freeze, but there sure is a lot of them. Thx.

[tkemp66]

Same!!! But I have no clue where to find my log file

[AVGA]

Go to Advanced Options in MSFS and choose developer mode. That will give you access to logs. 
 

This plane is always one step forward/two steps back for some reason. Works fine for a while, then there’s an update, then it fails again. So inconsistent. 

[LineDX]

That's right. I can't understand how testers miss some of the basic malfunctions before build release. Ini people are talented and dedicated to 350, getting rid of some basic errors will make a vast majority of simmers happy as they are mostly point a to b casual flyers.

Edited Sunday at 02:52 PM by LineDX

[Xenon341]

Sim freeze is not a "basic malfunction", and it's not because OP system is freezing that every system are freezing. A lot of people can use the plane without any sim crash.

A sim crash is not a WASM crash and a WASM crash is not a sim crash. I think people in this thread are not even talking about the same problems.

Now if OP want to do something that can help him find the root cause, open windows event observer, find the trace of the sim crash and check inside if there are any hint at what caused it.

Another thing you can do is try with only the A350 in your community folder to find if something else is causing the sim freeze.

Edited Sunday at 05:05 PM by Xenon341

[AVGA]

Yep. Did all of that, and still have a freeze issue, which is why I posted. I also never called it a WASM crash (on purpose), and posted the sim error log. Would also post the report from Event Viewer, and can do so on request, but to my eye, it’s not specific enough to be helpful. 
 

What I’m looking for is actionable insight and advice, not “empty your community folder” and other basic steps I’ve already done. Also did not post a rant, only a request for any help that can be offered, as while I really like the A350, the various crashes and conflicts I continue to experience make it a real pain in the neck - especially compared to Fenix and others who provide strong reliability out of the box. If Inibuilds wants to charge the same price, they’ve got to be more stable and consistent. 

Edited Sunday at 06:03 PM by AVGA

[Xenon341]

I don’t know what advice you are expecting from people that doesn’t experience your issue beside « basic steps » like you said.

This is a community forum not an engineering one.

Contact direct support if you want more.

https://inibuilds.com/pages/contact

Edited Sunday at 09:22 PM by Xenon341

[AVGA]

It’s a post to see if anyone else is having a similar issue since the last update, and if so, perhaps some additional info or insight on it. Also submitted a ticket, but no harm asking for … what’s this forum called? Oh yeah. Support. 
 

If you’re not having the issue, and nothing to say about it, then move on. Plenty of other posts to entertain you. 
 

[Xenon341]

I had some things to say but that was to basic for you sadly.

Have a great day.

[Matteo Spacca]

Aircraft + SIM froze (NO CTD) after clicking on "SEND TO FMC" in the OIS. Latest version

[AVGA]

Thx for posting this. 

[LineDX]

9 hours ago, Matteo Spacca said:

Aircraft + SIM froze (NO CTD) after clicking on "SEND TO FMC" in the OIS. Latest version

Same issue when sending the v speeds from the OIS. It happened only on CYHZ-OPLA ofp from simbreif 

[tkemp66]

On 8/17/2025 at 1:23 AM, tkemp66 said:

Same!!! But I have no clue where to find my log file

Issue Resolved! I believe I’ve finally sorted out the problem. I experienced two cockpit freezes with the A350 in MSFS 2024, and was also dealing with GPU crashes when flying aircraft from another respected developer—FENIX!

To get the A350 running smoothly again, here’s what worked for me:

1. Uninstalled the NVIDIA driver.

2. Reset MSFS 2024 via Settings > Apps > Installed Apps. (Resetting through the Xbox App didn’t work at all.) This reset will likely require you to reinstall or re-link content in your Community folder. Third-party apps may also need to be reinstalled. MSFS settings will revert to default, including your cache file location. Controller settings may remain intact. If you happen to have 12 drives like I do (not necessary, but helpful), this process is much easier to manage.

3. Disabled Shader Cache in the NVIDIA Control Panel. If the driver is already uninstalled, you won’t be able to do this step. But if you disabled it beforehand, run Disk Cleanup:

   • Select drive 😄

   • Check DirectX Shader Cache and Temporary Internet Files

   • Click OK

4. Before reinstalling the driver, I deleted:

   • MSFS 2024 Rolling Cache

   • Contents of the DXCache and GLCache folders located at: C:\Users\USERNAME\AppData\Local\NVIDIA (You may need to restart Windows to fully clear these.)

5. Reinstalled the NVIDIA driver, restarted the PC, and re-enabled Shader Cache. Then I verified that:

   • DXCache and GLCache folders were empty

   • Rolling Cache is deleted

   • RUN MSFS2024 to rebuild indexes, then exit

6. Reinstalled and re-linked all MSFS 2024 game files (if you opted to reset the sim). Resetting MSFS isn’t mandatory, but although it’s a hassle, it’s incredibly effective for resolving persistent issues.

7. Configured driver settings using:

   • NVIDIA Control Panel

   • NVIDIA Inspector

   • NVIDIA App (Yes, I use all three!)

Pro Tip: I always install NVIDIA drivers using nvcleanstall, located here - https://www.techpowerup.com/download/techpowerup-nvcleanstall/ for a cleaner and more customized setup.

After all that—my A350 flew flawlessly! 

 

Now for the strange part...

After completing a successful flight with the A350, I exited MSFS 2024 and launched a new flight using the A320 from FENIX at KJFK (via iniBuilds). Same settings, same setup—but the sim instantly crashed with a graphics error and gave me a BSOD. Yikes!

No panic though—I repeated just these steps:

• Deleted Rolling Cache

• Disabled Shader Cache

• Ran Disk Cleanup

• Cleared DXCache and GLCache

• Rebooted PC

• Re-enabled Shader Cache

And just like that—perfect flight.

 

Final Thoughts

I’m now convinced that whenever:

• MSFS 2024 receives a major update

• A new GPU driver is installed

• Microsoft pushes a system update

• Third party developer updates

…it’s almost always necessary to repeat those key cleanup steps to avoid crashes and instability.

Hope this helps fellow simmers keep their skies smooth and their flights flawless!

 

 

Edited Tuesday at 02:08 AM by tkemp66