The primary reason behind this is that your machine doesn't have enough available memory for the VM to launch.
Here is a KB article that was recently posted to get around this by setting a registry key that limits the amount of memory available to the host machine.
http://support.microsoft.com/kb/2911380/en-us
I have used the above fix and it worked for me.