Windows 10 freeze completely.

[Wozap]

hello, have a problem with starting in virtualbox windows 10. first time I install virtualbox version [VirtualBox-5.1.14-112924-OSX] it working fine dont have any problem RAM will be 1500mb after some time i pick up it to 1800 but after updating it to 5.1.18 r114002 (Qt5.6.2) version it completely freeze and want start up!
Now RAM 2000! installed Guest Additions version 5.1.18. and nothing!

[socratis]

Wozap,
I already answered your concerns in another thread, where I suggested you open a new one, because your problem was with Win10, not with Win8.1. And you did open this one, nice.

However, you did not fix most of the issues that I pointed in that answer, except that you installed the GAs. I'll repeat the remaining here briefly, so that you can address them:

• You are assigning memory to your guest, that you do not have available. Either close some applications on the host, buy more RAM for the host, or reduce the amount of RAM assigned to the guest.
  
  In the best case scenario from the logs, you have 2214 MB available. You assign 2000 MB to your VM, 128 to the vRAM, add some virtualization overhead and you're left with nothing on your host. That's going to cause you some serious problems. As I said, your host with 4096 MB of RAM is too weak to run Windows 10 correctly and you will have problems, unless you buy some more RAM.
• 2D/3D video acceleration is disabled in some configurations. Enable them in the VM Settings » Display, while the VM is completely shut down. And keep them enabled.
• Try not to run at full screen. And if you do go into normal mode (window), select a "nice" computer size for the display, like 1024x768 or 1280x1024 or something that Win10 proposes, without you resizing the window manually. Computers don't really like that.

Finally, we do not need to see the same information 3 times. It takes serve space and our time. Next time, please post one log only. Thanks.

[mpack]

00:00:16.390136 Host RAM: 4096MB (4.0GB) total, 1781MB available
...
00:00:16.939725 RamSize <integer> = 0x000000007d000000 (2 097 152 000, 2 000 MB)
...
00:00:16.940107 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

Host RAM grossly over committed. Only a dual core host. I rather doubt you'll ever get Win10 running usably as a VM on this host.

[Wozap]

but win10 working fine before updating on new version! how its can be posible? I have macbook pro i5.

[Wozap]

How to Downgrade it to 5.1.14???

[socratis]

Make the changes I suggested: 2D/3D enabled, run it and change it from full screen to 1024x768. Shut it down. Reboot your Mac. Run NOTHING except that Win10 VM. If it doesn't abort, shut it down. Post the log.

[Wozap]

when 2d/3d enabled it freeze on firs log.

[Martin]

You still don't have enough free RAM to run a 2GB guest.

[Wozap]

Thank you for you time! I fink best way to delete it and istall again.

[mpack]

I'm not sure how that will fix your RAM problem. You seem to think that addressing the unsufficient RAM problem is optional - it isn't. As long as you have that problem then the question is not how did your VM fail, the question is how did your VM ever work.