No, it won´t solve the CTDs because problem is not on your system nor in the addons. No existing addon will use 20 GB, unless it has a massive CGL extending over 20km or something crazy like that. If you open developer console you will see that memory allocation caused by loaded assets in game is not extreme indeed, nor even close to be high.
I have 64 GB and game still crashes and has been crashing during the whole 2023, when it didn´t crash before. However some extra RAM can for sure help as it prevents frequent swapping and FPS drops during that process. Regarding pagefile it´s not relevant. I have tried even with 64 GB and it will use 99% of it before crashing. When the random bug comes no setting will prevent it.
As I said the problem is the memory handling and until Asobo acknowledges it and puts real efforts to solve it we will continue suffering it for many more months, in both platforms and with any kind of systems.
FWIW, I’m sitting on the RW at EGLL, with LNM and Task Manager and Firefox running. Total RAM usage is 17.9GB. VRAM usage is 7.3GB. Normally while flying my system ram stays at about this level. VRAM can get close to my max of 12GB over large cities etc…
Someone may have already mentioned this, but keep in mind if your VRAM maxes out it will begin using RAM to top itself up.
After booting, my memory usage is about 20% or 6 GB. MSFS is about 8 to 9 GB and it fluctuates during flights. I don’t see a memory spike starting a 737 at KMIA, only staying about 9 GB.
The only unusual thing I see is with your paging setup. Virtual memory is significantly over allocated. Try checking the “Automatically …” box at the top. Here is what mine looks like:
. Many years ago (Windows 95) the paging recommendation was 1.2 to 1.5 times RAM. Today, Windows needs a lot less.
Adding MSFS memory to Windows (9 GB + 7 GB) is about 16 GB or about 50% of 32 GB. If everything else drives utilization to 75%, you are using a lot. Since paging doesn’t seem to be working for you right now, you might want to leave it off because once Windows starts paging, the system starts slowing down.
I think your choices are 1) don’t use Windows paging and have occasional BSODs, 2) use Windows paging and accept potential system slowing, 3) Use Windows paging and eliminate some additional programs, 4) install additional RAM. None are optimal.
There may be other things going on (virus scan?, other services?) that wake-up and gobble memory at random times. This is difficult to detect without deeper investigation.
Windows shouldn’t really blue screen simply because of ram exhaustion if the ram exhaustion is caused by 3rd party programs and not the core windows system itself. It activates the OOM killer (Out of memory killer) and kills processes to free up memory. I suspect the blue screens are caused by something else. On the other hand, you mentioned that you have 16-20 GB of memory usage on boot without any programs running? That seems like an issue to me. Maybe it would be good to investigate why it’s so high?
Also one time I had a failing disk that would cause blue screens because it would corrupt data in the page file and cause issues when it was read back into the memory. Maybe try turning off all of your (arguably too many) page files and see if the situation improves?
Not sure it goes that far that soon but since the rumor that mr Gates quoted ( long time ago,) that 640k is sufficient for ever it’s not impossible demands on RAM, VRAM etc. will grow over time.
