Wednesday, July 3, 2019

Windows is keeping large files I opened once in physical memory, in standby. How can I stop this?

I'm using Windows 8.1 64-bit, have 16gb of physical memory, and I understand why Windows wants to do this, but my specific case is really odd and annoying.


For some reason, on occasion, when I open a several GB file once - even if it's only once in the lifetime of the file and only for a few minutes, even if it's just a video file - it puts that file into "Standby (Physical) memory", putting my physical memory usage over 80% - sometimes over 90%. The worst part is, is that the file never gets removed automatically - I have to either restart, or use RAMMap to clear it out.


I understand why Windows manages memory the way it does, and that memory is meant to be used - however this is a bit of a problem for me since it never seems to clear these files out of standby on its own - and my performance suffers a significant amount as a result. I have an adequate page file on my SSD, my ram doesn't have any errors - my issue is just that Windows is predicting the wrong files I need to keep in physical memory, and not removing them after I close the file.


Edit / Update:



  1. Superfetch is disabled and has been for months.

  2. The pagefile is on an SSD.

  3. Process Explorer, RamMap, and HWiNFO all point towards these one time short use meaningless files being in StandBy, not in active memory (As shown in RamMap).

  4. When these files are removed from Standby - the physical memory usage goes down according to the tools listed above.

  5. My system doesn't 'think' it needs ram, and that's the exact issue at hand - it does need ram, and it's not clearing out the files using Standby memory unless I do it manually. As I said above, my memory usage can get to over 90% and sluggish, and not remove files Windows only needed once in the entire life of the file - instead preferring to remove files still needed in memory.


In summary: Windows is keeping files it doesn't need in memory, and removing files it does need when it asks for more ram. Why is this happening, and how do I fix it?


I'm not sure who marked this as a duplicate question, but the linked "duplicate" has nothing to do with my issue.

No comments:

Post a Comment

hard drive - Leaving bad sectors in unformatted partition?

Laptop was acting really weird, and copy and seek times were really slow, so I decided to scan the hard drive surface. I have a couple hundr...