Thanks for zipping and posting the logs with Upload Attachment!
Your Hardening log ends with exit code 0, so you have no hardening issues.
Your "error message" was a Guru Meditation. It helps us if you tell us what the error message was.
The guru meditated over a Triple Fault, meaning something went very wrong and Virtualbox couldn't figure out what to do about it.
The guru meditated just after the system booted from the ISO.
There is one thing I found in the Vbox.log that might be the issue:
00:00:02.678308 Host RAM: 7989MB (7.8GB) total, 3785MB (3.6GB) available
00:00:02.873061 RamSize <integer> = 0x0000000135c00000 (5 196 742 656, 4 956 MB, 4.8 GB)
00:00:02.873429 VRamSize <integer> = 0x0000000010000000 (268 435 456, 256 MB)
You are asking 5GB RAM from 3.6GB available RAM. That ain't gonna fly. Try rebooting your host so memory is cleared, or reduce guest RAM to 2GB.
Though I don't think the following caused your problem, you also have a 2-core CPU with hyperthreading. Hyperthreads don't count, and you have two cores set in the guest, so the guest can ask for all CPU bandwidth, leaving the host with nothing. While this is against forum advice to give all the host cores to the guest, your host has too few cores to abide by forum advice. And Windows 10 just needs two cores to work well. So there's no way around your core-count setup. I also have a host with two hyperthreaded cores and I have run Windows 10 both as host and guest OS's on that computer. Things just get slow when the guest wants to churn the CPU. Be aware that W10 needs a couple days of being left on to stabilize itself, before it gets relatively usable in a guest, and the host will be sluggish too.