Windows running out of memory: Difference between revisions
From Leo's Notes
This page was last edited on 30 December 2021, at 01:52.
Created page with "After running a few VMs on my Windows 10 computer that totals to around 24GB out of the 32GB that's installed, I have had Windows begin running out of memory. Symptoms include..." |
m Added categories and navbox |
||
| Line 9: | Line 9: | ||
Why doesn't the system automatically clear these standby lists when memory is running low? Shouldn't a low virtual memory condition be a good time to clear these standby lists? What is Windows doing? | Why doesn't the system automatically clear these standby lists when memory is running low? Shouldn't a low virtual memory condition be a good time to clear these standby lists? What is Windows doing? | ||
{{Navbox Windows}} | |||
[[Category:Windows]] | |||
Revision as of 01:52, 30 December 2021
After running a few VMs on my Windows 10 computer that totals to around 24GB out of the 32GB that's installed, I have had Windows begin running out of memory. Symptoms include the screens going blank temporarily and programs hanging and possibly stopping. Task manager shows the usage no where close to being full.
The event viewer does report system warnings similar to:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: mksSandbox.exe (10812) consumed 1422979072 bytes, msedge.exe (11464) consumed 757063680 bytes, and mksSandbox.exe (2336) consumed 692133888 bytes.
It turns out, a big chunk of the memory is stuck in standby lists. This can only be cleared using the RamMap (a Sysinternals, now Microsoft-owned) tool.
Why doesn't the system automatically clear these standby lists when memory is running low? Shouldn't a low virtual memory condition be a good time to clear these standby lists? What is Windows doing?