Page 1 of 1
Win10 2004 Cannot enable 3D acceleration
Posted: 19. Aug 2020, 19:00
by Cartman
Hardware
intel i5-10400
MSI B460-A Pro
SAMSUNG PM861
Kingston 16G DDR4 2666
NVIDIA GTX 1050 TI
Software
Windows 10 2004 19041.450
Oracle VM VirtualBox 6.1.12 r139181
Problem
Enable 3D acceleration, shutdown memory error Unable to save configuration
Re: Win10 2004 Cannot enable 3D acceleration
Posted: 19. Aug 2020, 19:04
by Cartman
Pic2
Re: Win10 2004 Cannot enable 3D acceleration
Posted: 19. Aug 2020, 19:05
by Cartman
Pic3
Re: Win10 2004 Cannot enable 3D acceleration
Posted: 19. Aug 2020, 19:41
by scottgus1
I'm not entirely certain what criteria led you to post those particular screenshots, but a full vbox.log will help better.
Start the guest from full power off, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.
Please right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
Re: Win10 2004 Cannot enable 3D acceleration
Posted: 19. Aug 2020, 20:06
by Cartman
OK
Re: Win10 2004 Cannot enable 3D acceleration
Posted: 19. Aug 2020, 20:06
by Cartman
(mod edit - took out quote of complete previous post - Please use the Post Reply button at the bottom of the topic.)
Re: Win10 2004 Cannot enable 3D acceleration
Posted: 19. Aug 2020, 20:20
by scottgus1
the vbox.log wrote:00:00:03.035408 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_X509_CPV_NOT_VALID_AT_TIME fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume5\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\
nvldumdx.dll: Certificate is not valid
A new Nvidia driver version for your host video was put out with a file that has a portion of its security signature incompatible with Virtualbox's hardening. (The jury is still out on whether it is Nvidia or Virtualbox at fault, or both.). Get on with Nvidia's help or forums.
See fth0's suggestions:
viewtopic.php?f=6&t=99059&p=480386#p480336
https://www.nvidia.com/en-us/geforce/fo ... mentPage=1