1

I have an ultrabook with windows 8. 8GB of physical ram. I run Win7 inside a vmware image, which is assigned 4gb. However I can't make the numbers for physical memory usage add up.

The Win8 machine is doing not very much other than running the VM. Windows itself should have slightly less than 4GB to play in. Yet physical memory usage in task manager is constantly at 75-85% (and occasionally I get dire warnings "you're out of memory" and bluescreens). I can't figure out how that much is being used -- the numbers in task manager don't add up to that much! (either commit charge or working set). How could physical usage be higher than virtual usage?

I've run RamMap and it doesn't really explain things much (and i have no idea if these numbers are normal or indicate a problem). I don't want to have to learn all the gory details of windows memory management; I just want to know why this machine, that should have more than adequate physical RAM, runs out of memory.

I suspect caches/buffers, but CPU usage is low, and this memory doesn't get freed up quickly when it's needed.

Improve this question
3
  • Everything you're describing is normal except the warnings and the bluescreens. So why don't you tell us precisely what warnings and what bluescreens you are getting?
    – David Schwartz
    Commented Feb 11, 2013 at 16:42
  • You can get your minidump? I'm on it I can try to tell you exactly what is defective. Take away from any free file hosting. thewindowsclub.com/automatic-memory-dump-settings-windows-8 need small memory dump.
    – STTR
    Commented Feb 11, 2013 at 16:56
  • Years later, but..., "commit charge" , and the "out of memory" warnings, are for virtual address space, not physical. The working set numbers don't "add up" because there is a lot of usage of physical memory that isn't counted there. Can you post a screen cap from RAMmap?
    – Jamie Hanrahan
    Commented Mar 8, 2019 at 22:33

1 Answer 1

Reset to default
6

How could physical usage be higher than virtual usage?

Windows, correctly in this case, assumes that using memory that isn't needed for any other purpose has zero cost. While seeing a large amount of free memory might make you happy, it shouldn't. Free memory is just memory that is wasted.

If you're thinking "I want lots of free memory now so I can use it later", forget it. You can use it now and use it later. You don't have to choose one or the other.

Free memory, essentially, represents a failure. The system couldn't find anything of any value at all to do with the memory and was forced to make it free. This is a pure loss -- if the memory isn't used later, making it free is wasted effort. If the memory is used later, making it free was wasted effort since now it just has to be made used again (transition the memory directly from one use to another is more efficient). Modern operating systems only make memory free if they have absolutely no other choice.

Now, the blue screens and warnings are not normal. You should tell us about them.

Improve this answer
3
  • 2
    The best analogy I ever heard to help explain this: Imagine you are touring a factory, during the tour you complain "Hey why are all the workers working! Some workers should not be working and go sit on that couch over there and do nothing while we pay them, just in case we get a really big order that comes in and we may need to use them then!"
    – Scott Chamberlain
    Commented Feb 11, 2013 at 19:57
  • machine is currently physically inaccessible. The warnings weren't written down by the person who first encountered them.
    – Snowbody
    Commented Feb 11, 2013 at 23:04
  • @Snowbody: The virtual machine you mean? More details on the problem would be helpful. (Does it always happen? When does it happen? Is it sudden or does it gradually get worse? And so on.)
    – David Schwartz
    Commented Feb 11, 2013 at 23:14

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .