It looks like you made quite a lot of changes beyond disabling Hyper-v. It looks like you also upgraded to VirtualBox v7. I believe 3D acceleration works very differently in VirtualBox v7, but you neglected to install the v7 GAs (you still have 6.1.40 Guest Additions in there).
So, I would update the GAs. I would also reduce the VM CPU allocation to the guest to 2 cores.
Personally I would have let v7 go through a few more interactions before I jumped to it. But I have no concrete reason for that, so you may as well stick with it now.
Your log has a huge number of these lines:
00:01:14.255342 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0
00:01:19.285059 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0
00:01:24.300919 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0
00:01:29.328202 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0
00:01:34.371487 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0
00:01:39.391734 VMMDev: Guest Log: vboxIPCSessionThread: Session 0000000019840804: Unknown message: 0x1, 0x3, 0x0, 0x0
... which I don't recognize. Let's see if they go away when the GAs are updated.
Note: in fact you shouldn't
update the 6.1.40 GAs. Instead you uninstall the old ones, then install the new ones. I suspect that uninstalling the GAs causes it to restore any modified system DLLs, which will be necessary since the new 3D engine uses a different method.