Virtualbox VM crashes / virtual graphics card problems

[alex_ncfc]

Hi,

I use VirtualBox for my Windows 10 "Windows insider" virtual machine rather than installing the latest previews on my actual hardware.

Until recently this has been fine, even on 6.1.8, but it started acting up with regards to video driver problems. I installed 6.1.10 (as well as the new GAs) thinking it may solve it, but I am having exactly the same issues as follows:

I can't get the video driver working in the guest OS - it installs and it goes to initialise the VirtualBox driver, but then reverts to a smaller resolution (like it's using the Microsoft Basic Display adapter) and I have this issue in Device Manager of the VM:

vboxvga.jpg (105.82 KiB) Viewed 4669 times

Then the actual error that occurs outside of the VM - it sometimes happens at random, but always happens when I go to shut down the VM - I get this error dialog:

---------------------------
VirtualBoxVM.exe - Application Error
---------------------------
The instruction at 0x00007FFF7C75F43C referenced memory at 0x0000000000000000. The memory could not be read.


Click on OK to terminate the program
---------------------------
OK
---------------------------

Then the VM exits but the VirtualBox program itself doesn't crash. Just the instance of the Windows 10 VM.

Is there anything I can do to fix this? It only started happening very recently and not sure why.

Thanks

[scottgus1]

First, peruse the Windows Guests forum, as this is more of a guest problem than a host problem.

Second, official even-last-number releases of Virtualbox don't try to support the previews, as they are a moving target. The devs only try to develop for the final release. You could try the test builds.

[alex_ncfc]

First, peruse the Windows Guests forum, as this is more of a guest problem than a host problem.

Second, official even-last-number releases of Virtualbox don't try to support the previews, as they are a moving target. The devs only try to develop for the final release. You could try the test builds.

Thanks for the reply. I wasn't sure which sub-forum to post this in to be honest because I have been having troubles in the VM itself but also that error that occurs outside of it (with the instruction error dialog)

I've had a look around and it seems that turning off the 3D acceleration box in the VM settings brings things back to normal. It's a bit strange as it was working with that selected as "on" the other day and I hadn't changed my VirtualBox version nor updated to the latest Windows Insider Build.

[scottgus1]

turning off the 3D acceleration box in the VM settings brings things back to normal.

Do you have an Nvidia graphics card, and if so did you update drivers in the last couple days?

[alex_ncfc]

Actually yes I do, and yes I did update to version 451.48 the other day. Is this likely the cause of the problem?

[scottgus1]

Yes. Virtualbox 3D acceleration uses the host video drivers to calculate the guest's 3D commands. That version of Nvidia drivers has a file that was not security-signed properly, and Virtualbox hardening trips up on it, making the guest's video have trouble.

Roll back those Nvidia drivers, then get on the horn with Nvidia and let them know about the insecure file. If you want, you can post the guest's log file before rolling back the drivers and we can tell you which one it is. Right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

[alex_ncfc]

Thanks for the clarification and also for advising which steps to take regarding the log files.

I have attached the log to this post from my Windows 10 VM (with 3D acceleration ticked/on)

If you could advise about the file from Nvidia which is being problematic from my looking at the log, that'd be very useful (or indeed any other issues you may be able to spot that could be causing problems)

Many thanks

[scottgus1]

Here you go:

00:00:03.801443 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_X509_CPV_NOT_VALID_AT_TIME fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\
nv_dispi.inf_amd64_ccad5caddc3a3d35\nvldumdx.dll: Certificate is not valid (ValidTime=2020-06-21T21:27:51.000000000Z Validity=[2018-07-18T17:42:53.000000000Z...2019-07-18T17:42:53.000000000Z]): \Device\HarddiskVolume4\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ccad5caddc3a3d35\nvldumdx.dll

[alex_ncfc]

Sorry for the late reply on this, and thanks for showing me which file was involved.

Still no luck with this, and I have actually been in the process of back and forth e-mails with Nvidia support over the past week or 2, I have explained that 3D acceleration does not work in VMs at the moment due to the invalid certificates on the files involved but I just feel like I'm getting nowhere, I keep getting asked the same questions - the latest e-mail reply from last night is asking me what is the Host OS and Guest OS installed...! Things I clarified in my original e-mail to them! Also asks me which Nvidia drivers did 3D Acceleration work with, but it was so long ago, I can't remember. So it feels like it's not really getting anywhere, anyone else had any updates?

[scottgus1]

There's been a lot of discussion about this here and on Nvidia's forum. Details differ on where the problem lies in Nvidia's or Oracle's code or both.

See fth0's suggestion:
viewtopic.php?f=6&t=99059&p=480386#p480336
https://www.nvidia.com/en-us/geforce/fo ... mentPage=1

Workarounds:
Downgrade host video drivers to the drivers you had before or try more recent but not latest drivers.
Turn off 3D acceleration in the guests.