

So upon running two similar machines that you would expect to only take about 10GB total, they would instead be using 16GB+ total.and if you're like me with only 16GB to start with this quickly translated into an unusable system followed by a lockup or a random BSOD (with a different error each time) as two running machines plus windows could only function if you are using a huge pagefile.sys and even then it would get very very slow. So say you wanted to give a VM 4GB of normal RAM and told it to use 1GB of RAM to the GPU and would in turn only expect it to use just over a total of about 5GB (with slightly more overhead).it would instead be using 8GB (with slightly more overhead)! Though between 3-4 GB of this only shows up as "Shared Commit" or "System Commit" in Process Explorer and "Commited" in Task Manager It seems that regardless of what limit you place on 'Graphics Memory' for each VM the new mksSandbox.exe process will still commit 4GB. It's under Virtual Machine Settings > Hardware > Display

To start with I'd suggest you try disabling "Accelerate 3D graphics" for the two VMs you ran into this issue with and see if it still happens after you power them on.
