Possible memory leak - performance issues

This note may be helpful to you:

Make sure that you have created a virtual memory storage for your computer, because this helps to run many games better, however releasing memory is probably an application software issue.

What is the recommended virtual memory size for 16GB RAM in Windows 11 ?
For a PC or laptop system with 16GB RAM, setting the virtual memory between 24GB to 32GB is a good starting point, but adjustments might be needed based on specific use cases.

How can you set the swap file in Windows 10 / 11? Enlarge, move, change:
For all manual settings, go to System settings > Advanced system settings > Advanced > Performance > Settings > Advanced > Virtual memory > Change.

Don't forget to reboot your computer.
 
Two questions:
1) how long have you had this installed?
2) when is the last time you updated the drivers for it?

I am asking because there may be a benefit to updating if not done in a while.
:geek:
1.) 3 years installed
2.) Updates are done everytime a New update comes out for the card and one just updated a couple days ago...
Update** Just updated my Page File size from 8GB to 32GB and it made loads difference! runs much more smoother now!
 
Last edited:
1.) 3 years installed
2.) Updates are done everytime a New update comes out for the card and one just updated a couple days ago...
Update** Just updated my Page File size from 8GB to 32GB and it made loads difference! runs much more smoother now!
I was under the impression the page file would not be that small in most systems with a lot of RAM. How was it set to 8GB?
 
I was under the impression the page file would not be that small in most systems with a lot of RAM. How was it set to 8GB?
That's the default size set by Windows with Windows allocating space as needed. The problem with allocating as needed is the disk becomes highly fragmented if using a platter type hard drive, or causes excessive wear on an SSD. This isn't always efficient because Windows doesn't appear to react fast enough for our needs.

The old formula used for Windows servers is 1.5 to 3 times the size of installed RAM. I found the 3x value to be a sweet spot for T: ANE and up.

What happened was I was importing content into T: ANE and ended up with a CTD. After repairing the database, I did it again and watched the system resources and noticed that the RAM completely filled up to the max before the crash. I then increased the page file and I was able to get further before it crashed again, and I increased the page file again up to 3x the size of installed RAM and never had an issue after that.

When setting the new page file up, I set the size to a fixed size by putting the same value in the min and max settings after clicking on the fixed-size radio button, and I placed the page file on another drive while leaving the small 8GB on the boot drive. While this isn't necessary, if Windows crashes, it uses this swap file to write the memory.dump file and will complain about no swap file available.
 
That's the default size set by Windows with Windows allocating space as needed. The problem with allocating as needed is the disk becomes highly fragmented if using a platter type hard drive, or causes excessive wear on an SSD. This isn't always efficient because Windows doesn't appear to react fast enough for our needs.

The old formula used for Windows servers is 1.5 to 3 times the size of installed RAM. I found the 3x value to be a sweet spot for T: ANE and up.

What happened was I was importing content into T: ANE and ended up with a CTD. After repairing the database, I did it again and watched the system resources and noticed that the RAM completely filled up to the max before the crash. I then increased the page file and I was able to get further before it crashed again, and I increased the page file again up to 3x the size of installed RAM and never had an issue after that.

When setting the new page file up, I set the size to a fixed size by putting the same value in the min and max settings after clicking on the fixed-size radio button, and I placed the page file on another drive while leaving the small 8GB on the boot drive. While this isn't necessary, if Windows crashes, it uses this swap file to write the memory.dump file and will complain about no swap file available.
So, 96GB page file for 32GB of RAM, interesting.
 
Back
Top