VirtualBox Critical Error Upon Booting

[Noor]

Hey there,
My issue is; once I try booting into my virtual-machine (Mint; XFCE Distro) It brings up a critical error then it crashes.
Small background
I had VirtualBox working totally fine for few months, but I lately enabled (Windows SandBox Feature & Virtual Machine Platform feature) @ Windows features, what happened is I noticed that the machine won't boot without disabling the 3D Acceleration, however, I disabled both features, and still, machine won't boot with 3D Acceleration being enabled.
But today, I tried opening my virtual machine, it won't boot by any means bringing that critical error.
I'll upload my logs zip.file
Notes:
1- I tried un-installing VirtualBox, and installing it again, it didn't work.
2 - Tried making a new virtual machine, didn't work.
3 - Opened the BIOS Settings it shows me that Virtualization services are enabled (Task Manager shows that too).
Anyways, I'll be waiting for your help and suggestions!
Thanks!

[scottgus1]

I had VirtualBox working totally fine for few months, but I lately enabled (Windows SandBox Feature & Virtual Machine Platform feature) @ Windows features, what happened is I noticed that the machine won't boot

If you turn these other Windows features off, does your guest start working again?

The vbox.log shows the guest guru-meditating right after the CD-rom starts to boot, and the guest display setting up:

00:00:08.225777 VMMDev: Guest Log: BIOS: Booting from CD-ROM...
00:00:08.387947 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=000000000cd40000 w=640 h=480 bpp=24 cbLine=0x780 flags=0x0 origin=0,0
00:00:08.389243 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:08.389262 Console: Machine state changed to 'GuruMeditation'
00:00:08.389419 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:08.389420 !!
00:00:08.389420 !!         VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

A file in your graphics driver is unsigned, which probably causes your guest OS's attempt to display to crash:

00:00:03.281474 [/Devices/vga/0/Config/] (level 4)
00:00:03.281476   3DEnabled          <integer> = 0x0000000000000001 (1)
.........

00:00:05.644863 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\amdihk64.dll: Not signed.
00:00:05.645057 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\WINDOWS\System32\amdihk64.dll': rcNt=0xc0000190

Google shows this file not being signed a problem for gaming too: google "amdihk64.dll" first thing up is it's not signed.

Try a host PC graphics driver update.

[Noor]

@scottgus1
Thank you for your reply!
I updated discrete AMD Graphics card, and my Intel Integrated graphics card is up to date.
And yes, I have the windows related virtualization features disabled, they have always been disabled but I wanted to try the windows sandbox, but since then things haven't been stable.
(They are disabled at the moment)
However, I tried making a new guest OS (different distro), the issue still exists
here are the new logs, (I tried searching for the amdihk64.dll in the logs, it seems to no longer exist)

[scottgus1]

Things look cleaner in the log, but still the guru meditates right after starting the CD boot.

Try turning off 3D acceleration. Also try reducing the guest CPU count to 2.

[Noor]

@scottgus1
I think I managed to solve the issue;
The issue was in Video Memory Size, When I changed it back to 128MBs it worked fine, I tried exceeding that limit by few MBs, it would bring an error.
It's kind of strange that this was the issue, I remember having the video memory @ 256MBs and it was no issue,
3D Acceleration works fine though.
However, I really appreciate your replies, thanks for helping me!
Have a nice day!

[scottgus1]

That's weird. 128MB is supposed to be the limit for non-3D-acceleration, 256MB with 3D on. Wonder if the devs should know? Try a post on the Bugtracker.