Well fixed it with a reinstall of msfs 2024 and canceling the cloud backup. Had to set all my controle scène but finnaly no ctd anymore.
This cloud backup is a pita. Why not localy backup..i guess with the installation there was a fault that trigged the ctds
I’m glad to hear you’ve found a solution. Now you can have some fun with DLSS4, but just a heads-up – there are no “holy grail” and there never will be. If anyone tells you otherwise, just ignore them.
Also, DLSS4 isn’t fully compatible yet - and no, Asobo can’t simply swap the files just like that.
Fly safe.
I noticed that my virtual memory load went in red 98% before a ctd. How can i change my virtual memory? Has this something to do with the vram leakage?
I have 64gb of ram…is it normal that my virtual memory is full with 64gb ram?
It standard windows 11.
I run my ram at 6000 expo. Orher option is 5400 xpo. Can this virtual memory overload be a ram issue? Seems wierd that with 64gb ram and a fresh windows 11 and 4 tb nvme i get an virtual memory overloaded?
I had an simple resources monitor running on the background. After the ctd there was one value in red
With my old Windows 10 system i flew hours wthout any issue.
While 100% virtual memory usage with 64GB RAM is unusual, it doesn’t necessarily mean your physical memory is faulty.
Virtual memory can reach 100%, but it’s usually not a good sign.
FYI, increasing the page file size (virtual memory) may help prevent CTDs. Also, setting a fixed size can reduce unnecessary writes, extending SSD lifespan.
Did made the pagefile larger. 96gb-192gb.
No more ctd after this.
Memory used during a normal flight low level was max 31gb…so 32gb is close.
I’m glad to hear that my suggestion regarding increasing the virtual memory helped.
You can also set a fixed value, for example, 144GB, to ensure more stability.
with fixed you mean both the initial size and maximum size: 144000 MB?
You don’t need to set 140/144 GB of virtual memory - that was just an example, not a recommendation.
For instance, if you have 64 GB of physical RAM and you intend to generate a full memory dump, then yes - your virtual memory needs to be larger than your installed RAM to capture the entire dump.
But I’m guessing you’re a gamer, not running server-grade debugging or kernel-level diagnostics - so a full memory dump is probably not something you need and therefore, 140 GB of virtual memory isn’t necessary either.
In your case, something like 32 GB (or at most 64 GB) of virtual memory is more than enough for system stability, without wasting space on your drive.