Windows 10: [Question] Clearing Standby memory when free memory reaches some level

Since i'm a PC Gamer, i'm having a lot of troubles with the Standby memory 'stealing' my free memory numbers. So, i have a question:

Is there any software for Win 10 that automatically clears the standby memory when Free memory reaches, for example, 100mb ?

I know the task scheduler solution with the 'EmptyStandbyList.exe - wj32' that is all around the Win 10 forums, but that solution is not the most 'smart' since when i forget it turned ON it will constantly clear my standby memory every 5 minutes, even if i have tons of free memory, when i'm browsing for example..

I tried RamMap but it's not automatic, so i would have to alt+tab any game to clear the memory.

Memory Cleaner by Koshy John has a 'Clear Cache' function, but not the 'Clear Standby' one.

So, is there any software that does that?

:)

 

Windows 10 not releasing standby memory when required.

My system has 16GB of RAM and a max pagefile of 1000MB.

The standby memory cache stays around 7GB even when my commit limit is reached causing either a low memory warning or a program which crashes because it couldn't allocate memory.

I understand that free memory = wasted memory so have no problem that standby uses 7GB normally, but why isn't it releasing the memory when it is needed?

I know the pagefile is small, but it is for two reasons - limited SSD space and a windows controlled pagefile was causing performance issues from swapping too often.

Any help would be appreciated.

 

Windows 10 not releasing standby memory when required.

A restart does indeed free the standby memory. It quickly climbs to about 2.5GB (most being mapped files) when I open my standard programs.

So I did 3 tests..

1. While running Overwatch, loaded as many programs/webrowser tabs as I could to get Zero + Free close to 0 MBytes. The standby memory stayed very close to the same size (checked this by refreshing RAMMap a number of times during the testing period). Opened
one more small memory footprint program to see if the standby memory would free but instead had errors with programs not being able to allocate memory. Taskmgr showed that is was only using 9.7GB at the time.

Restarted.

2. Ran Overwatch for a bit, closed it down. According to Taskmgr->Details Overwatch was no longer running. RAMMap showed the large overwatch files in standby memory which at the time I would expect it to as I still had over 6GB Free (according to RAMMap). Again
opened programs to get to close to 0 Free/Zero MBytes, refreshed RAMMap but standby memory stayed. Opened the last program and same error.

Restarted

3. Same as other tests but DIDN'T run Overwatch. Standby memory (2.5GB) Same problem again.

I didn't get to see in the first test but did in the last two was that when windows gives the low/no memory error it then starts to release the standby memory, but it's too slow and memory allocation fails. So it's not that the standby memory won't release,
just that it's too slow to be useful. This seems like Windows isn't managing the memory properly.