n3ilb wrote:
Basically the available memory in Windows was dropping at times to below 100MB free (which Microsoft say indicates a lack of RAM). The conflict we had though was the team looking at the VM side of things were saying the Active Memory usage by the VM was sitting around the 4GB mark and therefore the VM had adequate memory and Windows was just reporting it wrong.
There are lots of possibilities for confusion regarding the memory handling and the reporting.
Windows will "know best" about what it has actually loaded into its RAM and if it reports that it only has a certain number (100 MB here) of free/available memory then that will very likely be true.
The counters your VMware administrators was looking at is called "active" and is only a rough estimate of how much memory has recently been touched by the VM, but not how much it actually consumes.