Jump to content

Recommended Posts

Posted

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

Posted

If you are using SU3 Beta, go back to SU2 in 2024. Avoid opening the Navigraph moving map in OIS. Avoid using WX radar and Terrain radar. Do a flight then report back if that works for you.

Posted
5 hours ago, ykeyre said:

If you are using SU3 Beta, go back to SU2 in 2024. Avoid opening the Navigraph moving map in OIS. Avoid using WX radar and Terrain radar. Do a flight then report back if that works for you.

 

Posted

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

Posted

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. 

Posted

I had the same problem in V1.0.11. About an hour after takeoff, adjusting the Range knob had no effect, and NAV could not fly according to the flight plan.

Posted

I have encountered this problem many, many times since version 106. Later, I had no choice but to format and reinstall the entire Win11, FS2024, and everything else to solve this problem. Afterwards, I was afraid of encountering the same problem again and have been stuck in version 107 until now. The issue of 350 is really scary. I really can't understand why such an expensive airplane has allowed such a problem to exist for so long!!!

Posted

Hello everyone,

I have the same problem with frozen display units: Since A350 version 1.0.10 this behaviour starts for me and I am not able to complete a longer flight with the A350 in FS2024. After approx. 1,5-2 hours flight time all displays are frozen (aircraft is still flying and sound and cockpit cameras are working). I am able to manupulate some switches and knobs, however there is no reaction on the respective display/functionality.

I am on FS2024 SU2 (version 1.4.20), Windows 11, 64-bit, 24H2, and an intel i9-12900K gaming PC with 64 GB DDR5-6000 RAM and an AMD Radeon RX7900 XTX graphics card.

I have had serveral emails with the inibuilds support, but nothing of their advices worked so far for me (reinstallation, clearing the WASM folder, etc). For the time beeing the A350 is unflyable in my FS2024. However, other planes such as the FlyByWire A380X or the Headwind A339X works fine, so that I assume, that it is a problem of the A350.

I try to reproduce if it is a WASM crash by reading out the failures and errormessages in the console of the FS2024 developer mode, but it seems, that I have to wait 1-2 hours until the next crash occurs. I will keep you informed.

PLEASE iniBuilds-Team: help me / us with this "freezing displays error" - your A350 is such a nice and advanced airplane !!!

Brgds from Berlin, Germany,

Jayberlin

 

  • Like 1
Posted (edited)

Hello everyone,

last weekend I made an BIOS update to my ASUS z690-F Gaming mainboard (to version 4301, which came out end of May) and since I did that update the freeze of displays is gone (for now). For the time being - I made just a short flight of about 2 hours - my problem of freezing displays is gone.

Before that BIOS update (coming from version 4101) I was not event able to use XMP1 with my G.Skill Z5 DDR5-6000 RAM; memtest86 and also the Intel XTU stresstest fails (especially with the AVX-tests). I found on an Intel website regarding failed AVX-tests, that it may help to set in the advanced BIOS settings -> AI tweaker -> SVID Behavior to "Intel fail safe".

I also avoid to use the weather radar in A350, as I read that in another post in this A350 forum.

However, I am not able to say wich action mentioned above solves my problem, but I hope the CTD/freeze-problems of the A350 are solved.

Next I will try a longhaul flight and keep you informed if A350 flys stable now.

Brgds,

Jayberlin

Edited by Jayberlin
Posted

Hello everyone,

too early to celebrate: last night and this morning I tried a longrange service (planned WSSS to FYWH, about 11:30 flighthours), but after 2h at first flight frozen displays (no error messages neither in Windows nor in the Fs2024 dev mode console) and after approx 35 minutes of the second flight a CTD with Windows error message (0xc00000050).

So the aircraft is still unflyable.   😞

Inibuild Support told me that they have contacted Asobo for their consultation. 

Brgds,

Jayberlin

 

  • Like 1
Posted
On 5/31/2025 at 2:30 PM, Jayberlin said:

 

PLEASE iniBuilds-Team: help me / us with this "freezing displays error" - your A350 is such a nice and advanced airplane !!!

 

 

+1 with you. I'm in the same case, I think I'll make a pause until the problem is resolved.

Posted
On 5/31/2025 at 2:30 PM, Jayberlin said:

PLEASE iniBuilds-Team: help me / us with this "freezing displays error" - your A350 is such a nice and advanced airplane !!!

+1 with you. I'm in the same case, I think I'll make a pause with the A350 until the problem is resolved.

Posted (edited)

Yes, this happened to me while i was on the ground in KSEA. Buttons press, but no actions, Knobs on FCU turn but diplayed numbers dont. No animations on the sticks or throttles. MS24, SU3 .  Back in the hanger...

 

Edited by Peter
Posted

Same for me after trying to open the airport map and configuring BTV. short freeze of the sim, then first only the left fms was freezed, some actions later the right fms, displays, and thereafter the whole cockpit was freezed.
 

a350freeze.png

Posted

same issue here give us rollback option!

LG-48GQ900-B 48"
AMD 9900X3D
ASUS TUF Gaming X870-PLUS Wi-Fi AMD AM5
AORUS GeForce RTX™ 5080 XTREME WATERFORCE
CORSAIR Vengeance DDR5 6000MHz CL30 AMD(2 x 32GB)
2X 2TB 970 EVO Gen 4 (FS 2024)
1X 1 TB 990 EVO Gen 5 (WIN 11)
3TB SSD (MOVIES/APP)
Marantz HD-DAC1
Beyerdynamic T1 Tesla (2nd Gen)
Thrustmeter TCA Captains Pack
Thrustmeter TFRP Rudder
MiniCockpit (miniFCU V2 + miniEFIS)
WinWing MCDU
FS2024 (FGX4) (120* FPS on ULTRA @4K) *locked

Posted

 

On 5/22/2025 at 8:58 PM, AVGA said:

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

Yes! Happened to me on a Los Angeles to Sydney Australia flight 😩😩😩

Posted
10 hours ago, patchadams502003 said:

 

Yes! Happened to me on a Los Angeles to Sydney Australia flight 😩😩😩

Sorry to hear this happened, was there anything presented in the log on WASM? 

 

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...