May i ask when you cleared your shader cache the last time AND if you did a DirectX Clear with windows also?
I use DLSS Frame Generation, so both dx12
1 Like
I previously tried this method, but it didn’t have any effect on the performance of my msfs2020 and msfs2024.
Been meaning to try adding a page file size to try and calm down the Virtual RAM settings, on the 1440p machine first and strangely, this really calmed down the VRAM too. Yellow on the ground and apart from a short Red section after about half an hour for 5 minutes, that more or less continued until landing when it went red and stuttery again but much better. Went to the 4k machine, allowed up to 40GB on C where MSFS 2024 is installed, still red on take off but quickly to orange then yellow and then had to give up as short of time.
Can’t think why this should work but it seems to and to be fair, why is it needing a swap file at all when I have 32GB of RAM anyway and I’ve never seen the machine RAM and virtual RAM reach that combined anyway. Note on the 1440p machine, I allowed up to 30GB on C and also on the MSFS 2024 drive.
Just thought I should mention this in case it works for others too if having these issues.
I have also tested this in 4k too and also seems to help. Not as much in 1440p, mainly into the Orange, but then shouldn’t be getting anwhere near VRAM issues with 16GB in 1440p and VRAM seemed little different between 4k and 1440p which was surely not how it should be.
Overall though seems like early SU3 where it seemed to me at least to be holding on to VRAM it no longer needs for far too long. Try going from inside to outside and back again, I was getting an extra GB used on each change and got nowhere near enough back and what I did get took far too long.
OK, found a youtube video I’ll link next post in case somebody thinks it breaks any rules but now the sim is much more stable.
Firstly Virtual RAM (pagefile/swapfile) should be minimum at 1.5x RAM installed and maximum 2xRAM installed. This had the biggest effect on VRAM control for some reason. Meant I could now get VRAM in yellow/orange most of the time instead of flashing pink/red or just red all the time!
The a couple more tweaks to RAM management in registry. Activate Large System Cache to reduce use of swap file and increase use of machine RAM. Create PreferExternalManifest to set VRAM excess to utilise RAM instead of swapfile. Finally stop Windows compressing Memory to remove delay in RAM access/use.
There were other things in there I did not use but the sum of these that I did use meant my flight from Innsbruck to Geneva using the EFB created route meant VRAM in red on the ground prior to take off, falling to yellow within a few minutes of takeoff with external view. Back to cockpit view saw VRAM rise to flashing pink/red and triggereing the over retail use warning. VRAM then fell to around 14GB and returning to external view again had little immediate effect but then fell to yellow and even for a short period, white but then needed to go back inside again for landing.
No stutters on landing but were some on the ground taxiing and turning at speed due the no brakes scenario with the longitude an when I did finally stop, VRAM recovered to around 14GB with medium traffic and able to look around freely with no stuttering and I don’t think I saw the FPS drop below high 50’s throughout save for the landing taxiiing which quickly recovered back to 60 again (2x30). Link to follow.
This is the video I found that told me how to do what I did to make it possible for me to stay with the beta with my 4080 which I don’t think should be suffering from any VRAM issues.
My machine now has less of an issue to start with and is better able to cope if it does occur.
For the moderators, I have no connection to the video and only found it this afternoon when looking for solutions to work around the VRAM issue with SU4.
1 Like
I do believe!
I would strongly urge everyone to first research the changes these types of videos suggest before actually making the change. They may not have the desired results. An example in the above mentioned video refers to adding a registry entry for PreferExternalManifest to resolve a VRAM issue. That registry entry has nothing to do with VRAM so you run the risk of causing more harm then good. The same is true for the entry largesystemcache which is meant primarily for file servers.
Bottom line, do your research before making these types of changes.
6 Likes
I completely agree with the sentiment and always at your own risk. However strange that the entries are nothing to do with VRAM given that for the first time pretty much ever in MSFS 2024 I have have VRAM figures that both rise and fall as they should rather than just rise as they did. They are still going too high and still slower to react than I’d like but at least they now recover in a couple of minutes after going from external view to internal and back again rather than more VRAM to go into the cockpit and yet more to come back out again and never get either back.
Just to repeat though, these are things to do with caution which I did with the necessary knowledge and backups to correct anything that could go wrong and can even rebuild completely with fresh installs of windows in far less time than I spend trying to get 2024 beta’s to work. Don’t go down any road you aren’t comfortable you can reverse out of. Same can be said for being in the Beta program in the first place.
1 Like
4 Likes
Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.
3 tags are required - add them in the tag section next to the title above:
-
One for aircraft if related (start typing in your aircraft name in the tag section and pick correct option)
Feel free to delete this quote section after adding your appropriate tags.
ISSUE DESCRIPTION
Simulator stops responding (freezes) 1 hour into the flight
FREQUENCY OF ISSUE
Everytime I fly over land
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue: For this issue, I will load exact flight:
-
Start the simulator
-
Once on the sim, select Free Flight
-
Select Boeing 737 MAX 8
-
Configure fuel and load
-
Select starting airport: San Francisco International (Flightbeam-KSFO) and departure gate
-
Select arrival airport: Tocumen International (vPilot-MPTO)
-
If flight plan was created in SIMBRIEF, Import it: TRUKN2 SYRAH Q130 REANA DCT KU48O DCT KD45Q DCT KA39U/N0468F350 DCT PNH J58 FUZ J33 DONIE DCT SBI A766 KEHLI UA766 SIGMA UM205 AMESI/N0464F370 UM205 SPP UN420 MORLI OSUP2B.
-
After finalizing boarding process, startup and taxi, we are cleared for take off
-
Climb to cruise altitude and monitor flight.
-
After 1 hour- 2 hours: note how simulator is locked (we can hear sounds, etc… but its not responding
-
Open Performance Monitor and event viewer and check logs to check for probable cause
-
note how increased virtual memory is very high: (Log: Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: FlightSimulator2024.exe (18296) consumed 448374923264 bytes, FSRealistic.exe (17260) consumed 1142018048 bytes, and msedge.exe (37376) consumed 773033984 bytes.
-
Then Many .NET Runtime errors are displayed of apps that are dependent on the simulator
-
after 30 minutes of sim freeze, the Video driver hangs with the following error: The Desktop Window Manager process has exited. (Process exit code: 0xc00001ad, Restart count: 1, Primary display device ID: NVIDIA GeForce RTX 4090)
-
Additional errors: Faulting application name: FlightSimulator2024.exe, version: 0.0.0.0, time stamp: 0x00000000 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00007ff7b2453627 Faulting process id: 0x40F0 Faulting application start time: 0x1DC3754932C68EF Faulting application path: D:\XboxGames\Microsoft Flight Simulator 2024\Content\FlightSimulator2024.exe Faulting module path: unknown Report Id: 38a557b2-abc9-4602-bb48-d12334dcefb2 Faulting package full name: Microsoft.Limitless_1.6.11.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
-
Thrustmaster Boeing Yoke, Quadrant, TPR Pendular Rudder, XBOX Controller. Razer Nommo v2 Pro for audio output, streamplify mic
-
Developer mode is active but no changes have been done
-
Asus RTX 4090 OC on custom water-cooled sistem
-
NVIDIA App version: 11.0.5.266
Operating system: Microsoft Windows 11 Pro, Version 10.0.26100
DirectX runtime version: DirectX 12
Driver: Game Ready Driver - 576.40 - Mon May 12, 2025
CPU: 14th Gen Intel(R) Core™ i9-19900KS
RAM: 64.0 GB
Storage (3): SSD - 1.8 TB, SSD - 1.8 TB, SSD - 476.9 GB,+1 moreGraphics card
GPU: NVIDIA GeForce RTX 4090
Direct3D feature level: 12_1
CUDA cores: 16384
Graphics clock: 2610 MHz
Resizable BAR: Yes
Memory data rate: 21.00 Gbps
Memory interface: 384-bit
Memory bandwidth: 1.01 TB/s
Total available graphics memory: 55637 MB
System video memory: N/A
Shared system memory: 32609 MB
Dedicated video memory: 23028 MB GDDR6X
Video BIOS version: 95.02.3c.00.60
Device ID: 10DE 2684 889C1043
Part number: G139 0330
IRQ: Not used
Bus: PCI Express x16 Gen4Display (1): Samsung LC49G95T
Resolution: 5120 x 1440 (native)
Refresh rate: 120 Hz
Desktop color depth: Highest (32-bit)
Display technology: G-SYNC Compatible
HDCP: Supported
MEDIA
Please add a screenshot or video of the issue occurring.
While incredibly thorough, I’m not sure this bug report applies to this thread which is specific to issues with GPU VRAM usage, not system virtual memory, unless I’m misunderstanding something…
@Zadma I do believe it applies because even though I do not use Ultra on all my settings, the VRAM is still at 91% usage and is add traffic from FSLTL or AIG, it goes up to 98% in cockpit. however, as this is my first bug report I might have placed it in the wrong thread… thank you for the assistance
Gotcha - I didn’t see any mention of VRAM in your post.
Is there a way for me to attach any Dump or HARV files that can assist? I have them
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•
I have the same problem with the same aircraft, only on the PC. I just purchased a top of the line PC: AMD Ryzen 9 9950X3D, NVidia GeForce RTX 5090, 64 GB RAM, Fast SSD, all scenery packs downloaded to the local disk.
For the first part of the flight, things are o.k., but after a few hours, screen updates slow significantly and by the end of the flight, they’ slow to less than one per second. Doesn’t matter what I’m doing and it affects the other parts of the UI as well.
I’ve tried adjusting graphics settings while in flight to the lowest setting and it doesn’t make a difference.
Very frustrating to have a REALLY expensive brand new PC and this game can’t use the resources effectively.
Seems like some kind of memory leak or filling of an array somewhere where eventually, the list of data gets so big that each tick of the sim takes forever to iterate the list.
What version of the SIM are you running SU3 or SU4 beta? It sounds like you are experiencing this issue..
With SU4 my fps actually increased and it even became smoother, but all the good stuff ends when run out of VRAM. It’s incredibly frustrating. 5080, r9 7950x3d, MSI MPG X670E Carbon wifi, 64 GB of RAM, and I feel like a loser. I don’t know of a single game that consumes more video memory than it has. 
1 Like
Yeah a chronic problem and I also bought a 5080… when they were very expensive. My home airport is SFO and I run VR with a dedicated 6G Access Point and I still have to cut way back on the detail at SFO. Was the same story with 2D. Add in a bunch of even stationary aircraft and things grind down…. it is what it is not what was advertised.
I find my performance is much better if I use FSTL and not the native aircraft traffic. I’m on 8GB VRAM and while I run out from time to time it’s a lot better than when I tried with the sim’s air traffic enbaled.