Skip to content

A340-600 consistently freezing MSFS 2024

Featured Replies

Since the 1.0.3 update the A340-600 will cause my sim to freeze at seemingly random intervals but it always remains inevitable. Reloading an autosave will allow me to continue my flight but the simulator will still inevitably freeze up. The freeze is as follows: MSFS 2024 completely freezes, audio keeps playing, my desktop is still responding perfectly ok and the simulator shows up as not responding in the task manager. The only way to close the sim is to end task via task manager. I have not experienced this issue on any other 3rd party aircraft in MSFS 2024 and this issue was not present prior to the 1.0.3 update.

I have reinstalled the A340-600 twice with a fully cleared WASM folder, I have reinstalled my simulator and I am running the latest GPU drivers and windows 11 version. I have exhausted all the options I can think of by myself. 

I have the same problem, but it is random. But irritating if it happens after a flight of 2 hours just before landing.

I try to test more, but I have the idea that the freeze only appear if you used time compression inside the EFB (not the msfs2024 timecompression)

And maybe it is a memory problem.

The problem is that it take some time to get the freeze so it takes an eternety to test several flights.

Do you have a graphic card with 8 or more memory? Because I only have 8 and I want to know if the lack of memory is causing this.

On 6/27/2026 at 1:19 AM, peopleconsumer20 said:

I never touch compression and I am running a 7800x3d + 5070 and 32gb of RAM which is more than competent enough to run the sim.

No doubt, but I was wondering about the amount of videoram was sufficient.

I have a 3060Ti with 8 gb. I wanted to know if a 16 gb or 12 gb videoram card has the same problems

But I think the 7800 has 8Gb as well

  • 2 weeks later...

I am also having the same issue. In my case, long hauls only will cause a wasm crash. After 7 to 8 hours all my screens go orange with that terrible wasm message. Using RTX 5080 and 32GB DDR5 so it should be suficient. These crashes happened using the 1.0.3 version. I have downloaded the 1.0.4 which is the latest to this date, but haven't tried that yet.

  • Administrator

For the folks not in our Discord, here's a quick copy of our message regarding this:

We're aware some users are experiencing WASM crashes on 1.0.4. In order to try and gather more information regarding these crashes, we've created a dedicated crash report form on our helpdesk

If you are one of the users experiencing these crashes and are willing to assist us in tracking down these issues, please create a ticket using the dedicated form here. Please note that this form should only be used for A340 crash reports, as this is a crash submission form only, and general inquiries under it will not be responded to. For general A340 support, continue to use our usual Microsoft Flight Simulator support form.

If we require more information from you, we'll get back to you via the ticket. Further instructions on what we require can be found on the ticket form.

If you're having these issues consistently, please do fill out the above form.

  • 1 month later...

I used the dedicated form and told aerosoft what the freezing problem was. In a reaction Aerosoft gave me the solution to delete the wasmfolder before the flight.

And indeed if you delete the WASM folder you can finish a flight normal.

The problem is, with every new flight you have to delete the WASM folder before you fly. I know it is not a very big deal, but it would be more convenient if the plane doesn't freeze the game without deleting the WASM folder.

Other planes can manage this too, so I hope in version 1.5 they find a fix

Lets be clear, I don't get a WASM warning with red screens. The screen just freeze and the sound goes on. This can happen randomly 1 minute, 5, or 10 minutes even after an hour.

I have to use taskmanager to get out of the situation.

  • Author
On 8/30/2026 at 3:19 AM, BenBaron said:

We have identified a potential cause for this issue that will be available with the next build.

Good to hear but it has been way too long overdue at this point.

On 8/29/2026 at 9:19 PM, BenBaron said:

We have identified a potential cause for this issue that will be available with the next build.

Please push this ASAP rather than waiting for the other model updates etc. to be ready. Unflyable for me for two months now

  • Aerosoft
vor 14 Minuten schrieb Fluss:

Please push this ASAP rather than waiting for the other model updates etc. to be ready. Unflyable for me for two months now

Don't worry: so far we are confident to have found the culprit and the next update is not far out, so you will have your chance to try. Mind you though that as with everything software there is still slim chance that your issues are caused by something else. I'd invite you to come back in here after the next update to share your experience, be it a positive or negative one.

First flight after update. No freezing on the first flight UNTIL I tried to jump to next waypoint, then the simulator froze. So still not 100% fixed for me but an improvement over before, when I couldn't get to cruise at all.

However, now I have very bad stutters lasting ~one second every so often, that did not appear before.

12 hours ago, Fluss said:

First flight after update. No freezing on the first flight UNTIL I tried to jump to next waypoint, then the simulator froze. So still not 100% fixed for me but an improvement over before, when I couldn't get to cruise at all.

However, now I have very bad stutters lasting ~one second every so often, that did not appear before.

Can confirm the stuttering issue reported by @Fluss.

In my test flight with v1.0.5, I did not experience any freezing even when using the "Jump to next waypoint" feature. However, I am now seeing noticeably bad stutters occurring periodically roughly every 60 seconds.

Prior to v1.0.5, these regular stutters were not present at all. It causes so much disruption during flight that I almost feel like downgrading back to v1.0.4.

Hi all, first post here.
I actually created an account just for this thread, because the bug is still there and I really like the aircraft otherwise.

Just did my first flight with 1.0.5 and for me it froze again after about 20 minutes, so the issue is still present on my end.

Since 1.0.3 I get this freeze. It's not a CTD, MSFS's HangDetector terminates the sim (0xC0000194). A memory dump I analysed with 1.0.4 shows a deadlock: the sim's main thread and a thread running WASM code are both waiting on the same lock. I can't say for sure that the WASM module is the A340's, but the freeze only ever happens with this aircraft. Fenix A320, iniBuilds A350 and Synaptic A220 are all fine on the same setup.

I plan to repeat the analysis with 1.0.5.

  • Author

I just got two CTD's just at the gate setting up the aircraft and the same stuttering as reported above. Fresh install with cleared WASM folder. Thoroughly disappointed since this addon is 80 euros and has been in an unflyable state for months.

  • Aerosoft

Hi guys:

we are sorry to hear that obviously the last update has not fixed the issue for good for all of you. We can say that during limited testing of 1.0.5 before release the problems were resolved for everyone that participated, who had stutters or freezes.

In order to move further and isolate the problem for the rest of you as well we need more formal data, though. So I'd ask anyone that is still experiencing issues with 1.0.5 to attach a zip file to your next post containing all the log files found in the A340 work folder (most importantly ToLissLog.txt) in addition to a most detailed description as to what it is that you are experiencing. If it is constant stutters or freezes, please try to get a rough timely measurement, that is the interval between freezes. Do you use any hardware other than a simple joystick and rudder, e.g. stuff from WinCtrl? Also, if you have the ability to provide a video of what it is that you are seeing, it would be highly appreciated.

Thank you in advance for your help in trying to track this down for everyone who still experiences problems.

19 hours ago, BenBaron said:

Hi guys:

we are sorry to hear that obviously the last update has not fixed the issue for good for all of you. We can say that during limited testing of 1.0.5 before release the problems were resolved for everyone that participated, who had stutters or freezes.

In order to move further and isolate the problem for the rest of you as well we need more formal data, though. So I'd ask anyone that is still experiencing issues with 1.0.5 to attach a zip file to your next post containing all the log files found in the A340 work folder (most importantly ToLissLog.txt) in addition to a most detailed description as to what it is that you are experiencing. If it is constant stutters or freezes, please try to get a rough timely measurement, that is the interval between freezes. Also, if you have the ability to provide a video of what it is that you are seeing, it would be highly appreciated.

Thank you in advance for your help in trying to track this down for everyone who still experiences problems.

It freezes for me after i move the airplane using the teleport function in the advanced menu, using the LAT and LONG coordinates. IN 1.0.3 in was fine but it broke in 1.0.4/5. As soon as enter coordinates and the plane moves, it freezes after exiting Slew Mode.

  • Aerosoft
vor 48 Minuten schrieb nikita1234:

It freezes for me after i move the airplane using the teleport function in the advanced menu, using the LAT and LONG coordinates. IN 1.0.3 in was fine but it broke in 1.0.4/5. As soon as enter coordinates and the plane moves, it freezes after exiting Slew Mode.

Hi Nikita:

but just to be clear: if you do not teleport the aircraft, you don't have anu issues at all? No stutters and no freezes? After the freeze there is no way to continue the flight, correct? Do you use any additional hardware other than a joystick and rudder? Like stuff from WinCtrl? Please also, if you can, provide the log files that I requested in my post above after you have teleported and the aircraft frooze.

Regarding the stutters introduced after the v1.0.5 update, you can see them occurring roughly every minute in this video: https://youtu.be/DA8Pfs0RJ-U?si=h324_Ok9hla7QA_2

Although the video starts from the descent phase, the stutter was already present before takeoff and even during the Cold & Dark state at EDDF. Furthermore, this is not isolated to this single flight—it occurs consistently on every flight I take since updating to v1.0.5. I have never experienced this issue since v1.0.0.

  • Aerosoft
vor 8 Stunden schrieb Ryusuke:

Regarding the stutters introduced after the v1.0.5 update, you can see them occurring roughly every minute in this video: https://youtu.be/DA8Pfs0RJ-U?si=h324_Ok9hla7QA_2

Although the video starts from the descent phase, the stutter was already present before takeoff and even during the Cold & Dark state at EDDF. Furthermore, this is not isolated to this single flight—it occurs consistently on every flight I take since updating to v1.0.5. I have never experienced this issue since v1.0.0.

Thank you for the video: did you personally encounter any issues before 1.0.5? Any crashes, freezes or stutters? Do you use any additional hardware than joystick, pedals and thrustlevers? Like stuff from WinCtrl?

8 hours ago, BenBaron said:

Thank you for the video: did you personally encounter any issues before 1.0.5? Any crashes, freezes or stutters? Do you use any additional hardware than joystick, pedals and thrustlevers? Like stuff from WinCtrl?

I didn't encounter the stutter before ver1.0.5.

9 hours ago, BenBaron said:

Thank you for the video: did you personally encounter any issues before 1.0.5? Any crashes, freezes or stutters? Do you use any additional hardware than joystick, pedals and thrustlevers? Like stuff from WinCtrl?

Prior to v1.0.5, I experienced almost no crashes or freezes during standard flights. The only rare exceptions were:

  • Very infrequent WASM crashes/freezes when using the Jump feature while on SIM RATE 4x. (Once I learned to reset SIM RATE to 1x before jumping, this issue disappeared.)

  • Crashes when loading a saved flight state, which occurred very rarely (perhaps about 3 times in total).

Other than these specific cases, the aircraft was practically faultless in terms of stability.

Regarding periodical every minute stutters, I experienced absolutely zero stutters up to v1.0.4, they only began after updating to v1.0.5.

For reference, here is my hardware setup:

Used since v1.0.0:

  • WINCTRL URSA MINOR Airline Joystick L

  • WINCTRL URSA MINOR 32 Throttle / 32 PAC Metal

  • Elgato Stream Deck XL

  • Elgato Stream Deck Plus

Added after v1.0.3 update (worked completely fine without stutters on v1.0.4 as well):

  • WINCTRL FCU / EFIS

  • WINCTRL MCDU

Am 18.9.2026 um 09:08 schrieb Ryusuke:

Regarding the stutters introduced after the v1.0.5 update, you can see them occurring roughly every minute in this video: https://youtu.be/DA8Pfs0RJ-U?si=h324_Ok9hla7QA_2

Although the video starts from the descent phase, the stutter was already present before takeoff and even during the Cold & Dark state at EDDF. Furthermore, this is not isolated to this single flight—it occurs consistently on every flight I take since updating to v1.0.5. I have never experienced this issue since v1.0.0.

Just want to join as I have the exact same issue!

Don't know if its the same reason as others have with complete freezing?
If so, I also would open a new thread about it.

Otherwise per formance is very good and fluid. Just these stutters you see ecaxtly in the video

Create an account or sign in to comment

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.