Windows 10 guru boot and install crashing

[Rhyan]

I'm not able to install my windows 10 or start it when sometimes I can, it always crashes with an error message or a guru problem appears or something, I'll leave my log attached below.

[mpack]

Your PC doesn't have enough RAM to run a big VM. In fact, to be blunt, the RAM is barely adequate to run the host OS.

00:00:17.780916 Host RAM: 3909MB (3.8GB) total, 1512MB available
...
00:00:19.383985 RamSize <integer> = 0x0000000077200000 (1 998 585 856, 1.8 GiB)
00:00:19.384714 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128.0 MiB)

I'm resorting to bluntness because you already asked this question, getting virtually the same answer, which you said you understood. See the link below. The name of the guest OS doesn't affect this answer, the only thing that would change the answer is a different host PC or a VM with dramatically reduced resource requirements.

viewtopic.php?p=539167#p539167

Speaking of resource requirements, you have a separate problem that 1.8GB is below the 2GB minimum recommended for Win10(64bit). I.e. you do not have complete freedom to shrink the VM either.

[Rhyan]

Yes I really understand, but the thing is, I don't understand everything about VMs and it's Windows and not Linux, I didn't think it would be the same problem because they gave different errors in both. And I already managed to use windows 11 on the same host and there was never a problem, now because win 11 can run and win 10 cannot, I have no idea.

[scottgus1]

I don't understand everything about VMs and it's Windows and not Linux

There is a bit of difference between Windows and Linux VMs, because of the way Virtualbox handles RAM: it uses "lazy allocation": it asks for the VM's RAM as the VM's OS asks for it.

Linux asks for RAM as it needs it. Windows asks for all the RAM at once at boot-up. So a Linux VM can run for some time on an overloaded-RAM host, but a Windows VM might keel over rather quickly.

If by chance you happen to have 1.8GB available when the VM is started, then the limited RAM won't be a problem.

Try starting your VM right after logging in on the host.

Or you can try getting more RAM. 8GB would really open things up on the RAM front.

*******************************

The CPU is simply going to be too tight:

Host CPU status:
00:00:24.388794 CPUM: Logical host processors: 2 present, 2 max, 2 online, online mask: 0000000000000003
00:00:24.388797 CPUM: Physical host cores: 2
00:00:24.389542 Full Name: " Intel(R) Celeron(R) CPU B830 @ 1.80GHz"
Guest CPU settings:
00:00:19.383978 NumCPUs <integer> = 0x0000000000000002 (2)

But as long as you don't push both host and VM at the same time, you might be OK.

A VM uses threads and processes on the host. It doesn't "take away" the cores from the host. That's why two-processor VMs can run on a two-core host and still have the host stay running. But if the VM's threads and processes want to take up too much processor time on the host, then either the host or the VM or both will starve.

If by chance you can change the processor too, then you'd have more processor room.