VMware Communities
rjf7r
Enthusiast
Enthusiast
Jump to solution

After system crash, Workstation 10 reports "Not enough physical memory is available"--how to fix?

On a Windows 8.1 Pro system with 32GB of main memory, I was running three virtual machines on Workstation 10.  Then we had a power failure and the system crashed.  Once the power was back and I had rebooted, every attempt to run a virtual machine failed with the following message (the numbers change):

Not enough physical memory is available to power on this virtual machine with its configured settings.

To fix this problem, decrease the memory size of this virtual machine to 988 MB, increase the amount of physical memory for all virtual machines to 1219 MB, or adjust the additional memory settings to allow more virtual machine memory to be swapped.

This happens whether the VM I try to start is one of the ones that was running or one that was not running at the time of the crash.  This happens whether I am running as administrator or not.

I checked Edit/Preferences/Memory and the reserved memory is set to 24480 MB--24 GB.  I can run a VM if I set its memory size to below the value given in the message (in this case, 988 MB).  Of course, I don't want to run that way!

The Windows system control panel reports (nearly) the full 32GB system memory. The Task Manager reports that only 7% of the nearly 32GB is in use.  "About VMware Workstation" reports 32640 MB.

How do I fix this?  I'm essentially dead in the water.

Bob

0 Kudos
1 Solution

Accepted Solutions
dariusd
VMware Employee
VMware Employee
Jump to solution

You're probably encountering the same problem others have reported in this other thread: Windows 8.1 October rollup KB2995388 and issue with Workstation 10

Try the workaround there and see if it helps.

--

Darius

View solution in original post

0 Kudos
1 Reply
dariusd
VMware Employee
VMware Employee
Jump to solution

You're probably encountering the same problem others have reported in this other thread: Windows 8.1 October rollup KB2995388 and issue with Workstation 10

Try the workaround there and see if it helps.

--

Darius

0 Kudos