Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://flybywiresim.com/
So I have to jump to an alternate conclusion: it's not MSFS, because MSFS does from what I know take into account your add-ons, and when you are lowering your AI planes, it should compensate. Still, 50% traffic is a lot for me, I keep my air traffic at 10% at the most, or turn it off altogether. I guess you like hearing the ATC talk to itself.
My conclusion is that you have an issue with Windows. That seems more likely, since the problem you are reporting seems uncommon to me for MSFS, but very common for Win. So, try this, to automatically allocate virtual memory:
From the Windows Search Bar type Performance.
Choose the Adjust Appearance and Performance of Windows. This will pop a Performance Options window.
Click on the Advanced tab.
Click on the Change… button in the Virtual memory section.
Check the box Automatically manage paging file size for all drives
Click OK
Reboot your computer
I'm also going to throw this in, from the Windows Helpdesk, steps you can do to troubleshoot your onboard memory. No doubt you have a leak, but the cause of the leak can be any number of things. Best to diagnose your hardware and be certain that's not letting you down:
https://answers.microsoft.com/en-us/windows/forum/all/how-do-i-get-rid-of-the-error-exception-break/cb222a25-89c2-4b36-910e-9130bc686cba
A game should not crash if you max your settings out to the moon due to memory allocation. It just should not. It should account for it and / or gracefully recover. But an outright crash to desktop with an HR code is not acceptable behavior. I will report the bug to Asobo. It should not crash if I set traffic to 100% or 1%. It still should understand that it cannot use 50 models of all the aircraft I have available and try to put them on the ramp, memory size be damned. That is not what it should do.
It is not my fault it tried to allocate more RAM than was available. Nor is it my PC's fault. What it does mean is that regardless of how much RAM you do have, eventually FS 2020 will crash (such as at larger airports) because it does not properly account for how much memory is left or there is a bug with it.
I'm on a fresh install of Windows 11 and everything has checked out 100%. Nothing is wrong. The issue is FS 2020.
then do the following...
Be sure that all the MS Store apps are up to date....Xbox, Game services etc....then
Open a command prompt with admin rights…
Go through each of the following steps one at a time. Copy each line, one at a time , paste it into the Dos window (crtl + V) and press return
and it will then run. Wait until each runs and finishes before you move on to the next one.
When you are completely finished, Restart your computer and then try to see in MS2020 will start and run properly
Dism.exe /online /Cleanup-Image /checkhealth
Dism.exe /online /Cleanup-Image /scanhealth
Dism.exe /online /Cleanup-Image /Restorehealth
sfc /scannow
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
Dism.exe /Online /Cleanup-Image /StartComponentCleanup
RESTART your computer as the last step. Then go for a test flight.
Some problems actually require some knowledge and diagnostics as opposed to just regurgitating random crap from the internet.
If you don't like it, then you've said your piece and you can be on your way.
https://www.youtube.com/watch?v=mZH1XiqxuyI
The only other crashes in event viewer are from Car Manufacture, which is an Early Access game and to be expected and from Dead Island 2 which has known stability issues. Both myself and my friend frequently crash during coop sessions. Actually he crashes more than I. I see about 2 crashes for me in 2 months.
FlightSimulator.exe crashed 4 separate times with this exception code and since then it has not thrown that same code. I should not have to change settings to get it to stop crashing. What was interesting was if I went to an airport with a relatively decent size ramp it would crash. If I went to something way out west in the middle of nowhere that was relatively small, it ran just fine.
So either something in packages->official got borked other than just fs-core or FS 2020 is not managing memory correctly. Given what I've seen from this product during updates with regards to file corruption and/or getting stuck on a file, and with memory consumption during runtime I would say it could be either or both.
I also found posts about this on general MS forums (not flight simulator) and on the official forums. What was suggested was to increase the page file size. But the person did this and reported that eventually it still had the same issue. Increasing the page file only solved it until FS 2020 tried to allocate more and more and then it crashed again.
I was not getting this until recent updates and really not until I downloaded 2 new aircraft. Now all of a sudden it seem some point has been reached where the sim craps itself memory-wise and I have to babysit it and hold its hand b/c it is incapable of doing it correctly by itself.
I just boosted it to 8000 to 16000. It was at 5000. I just updgraded to 11, so perhaps I need more physical RAM for this hog. I hate this band-aid fix that will do nothing but cause performance issues. Guess I need to drop another 32Gb in the system so misbehaved programs don't get their hand slapped by the OS for being stupid with memory allocations.
https://www.guidingtech.com/best-ways-to-fix-taskbar-disappeared-or-missing-on-windows-11/
Absolute nonsense. You have no clue what you're talking about.