Agreed. Some folks suggest manually setting Min/Max page file size. That was a good idea back in the old days. These days, just let Windows manage it. With 64GB RAM I shouldn’t ever need it for my programs. (Windows does require a small page file for certain things, so you shouldn’t delete it either.)
3 Likes
The reason I still suggest a min and a max is because above a certain amount of RAM, let’s say 16 GB or 32 GB, if you set the Minimum to 1024 MB you will see that the “Currently Allocated” amount will never grow. If you leave it set to Auto, it will 100% grow, not much, but you will be writing unnecessarily to your SSD Drive multiple times a day. Windows has yet to master this.
Source: I have a Lab that studies this, other types of benchmarks for gaming and high end rigs, as well as extensive research in power consumption of computers, and their components when put under different situations.
2 Likes
99% of MSFS CTDs are caused by wrong memory allocation. Game exe is faulty and a new patch is the only solution to solve it. Save your money unless you really need additional assets for specific reasons other than just using MSFS and read the release notes from previous game patches. Everytime a particular release is reproducing CTDs there´s a fix afterwards that instantly solves it. That has been the pattern for the last 3 years.
Cheers
1 Like
Re: Paging file use.
Note that these are my personal observations and your mileage may vary.
On every system that has had sufficient memory to absorb the system memory load, (both Linux and Windows), swap/paging file use is either zero or some trivially small constant value.
If I see that beginning to climb, regardless of actual memory utilization, that’s my cue to shut down what I’m doing and reboot the machine.
I don’t exactly know why it’s doing that, but I do know it spells trouble ahead.