See
Diagnosing VirtualBox Hardening Issues for help with this sort of error.
Your hardening log ends with:
2204.2f8c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005
Post #5 in the above link deals with this exit code. What specific program interfered with Virtualbox is not blatantly visible, so you're going to have to experiment. The 5th post gives one suggestion to try with your guest, try it and report back what happens.
Also the log says you have Cylance Protect and Zonealarm Firewall installed. If the suggestion in the 5th post does not allow your guest to run, then temporarily uninstall (not just disable, uninstall) these two programs to see if Virtualbox runs.
You mention this in your guest setup:
Arunan wrote:adding all the ram and secondary memory for the VM
If this really means how it sounds, that you set the guest RAM to be all of your host RAM, then this is not good. Although this will not cause a hardening problem, your guest may not be able to start completely due to asking for more RAM than the host can give. You will have two computers running off the physical hardware available, and you need to share. Same for guest processors, you have to split the supplies. Ignore AMD threads & Intel hyperthreads: Virtualbox only uses cores. So if you theoretically have a 4-core 8-thread AMD or Intel CPU, it only has 4 CPUs for Virtualbox purposes, and you need to share out of that 4 for your guest.