x64 guests crash when restart the systems

[cyh19910216]

I'm using virtualbox 6.1.14, and the problem arose when I updated vbox from 6.1.10 to 6.1.12

My CPU: AMD 3700X
GPU: NVIDIA 2070S
System: WIN10 x64

I've 5 guests: Windows XP, Windows 7 x64, Debian x64, Fedora x64, Arch Linux x64
Only the XP run properly, I can use it as usual.
The last 4, I can start and power off the systems. But when I want to restart, the vbox crashes.

Crash

QQ截图20200907202900.png (12.63 KiB) Viewed 1021 times

And in WIN7, I can't open aero.

In my other PC, all of the 5 are good.
That CPU: Intel 6750HQ; GPU: NVIDIA 980M; System WIN10 x64

How can I upload the logs? It said the files are too big.

[mpack]

We don't need logs (plural). Just the latest log please. I charge for anything extra!

Zip the log, then add the zip as an attachment.

A translation of that error message would be useful too. Google Translate and DeepL can't translate images.

[cyh19910216]

We don't need logs (plural). Just the latest log please. I charge for anything extra!

Zip the log, then add the zip as an attachment.

A translation of that error message would be useful too. Google Translate and DeepL can't translate images.

I'm very sorry that I forget how to edit the question, and my English is not good.

The logs I don't know which one is useful:

VBox.zip

(27.69 KiB) Downloaded 7 times

VBoxHardening.zip

(25.83 KiB) Downloaded 3 times

The error message may means:
VirtualBoxVM.exe - Application Error
0x00007FF831AFF47C instruction referenced 0x0000000000000000 memory. The memory can't be read.
The last two words are "OK" and "Cancel"

Thank you!

[mpack]

00:27:48.777590 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 0000000000000fe0!!!
00:27:48.777590
00:27:48.777590 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=00007ff831aff47c
00:27:48.777591 ExceptionInformation[0]=0000000000000000
00:27:48.777592 ExceptionInformation[1]=0000000000000000

That looks like a typical hardening error, a memory access fault due to a module being missing, most likely having been rejected by VirtualBox process hardening. There has been a spate of similar problems with NVidia drivers recently.

00:00:02.944167 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_X509_CPV_NOT_VALID_AT_TIME fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvldumdx.dll: Certificate is not valid (ValidTime=2020-08-12T21:53:45.000000000Z Validity=[2018-07-18T17:42:53.000000000Z...2019-07-18T17:42:53.000000000Z]): \Device\HarddiskVolume2\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvldumdx.dll
00:00:02.944301 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvldumdx.dll' (C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvldumdx.dll): rcNt=0xc0000190

Quite a few people have had this problem. It is caused by NVidia using an invalid (expired) certificate, therefore the DLL fails security checks and is barred from running inside the VirtualBox process. Check for upgrades (or downgrades) of your host NVidia drivers. You can also disable 3D graphics acceleration in the VM if you prefer.

Incidentally, this doesn't seem to have anything to do with 32bit vs 64bit. The relevant setting is 3D acceleration - and of course that feature is not available for XP guests in VirtualBox 6.1.x.

FAQ: Diagnosing VirtualBox Hardening Issues.

[cyh19910216]

Thank you very much!
Maybe the only thing I can do is to wait for NVIDIA to update their certificate?

[mpack]

You can either downgrade to a version of the drivers that was created before the certificate expired, or yes, wait for NVidia to fix the problem.

[cyh19910216]

You can either downgrade to a version of the drivers that was created before the certificate expired, or yes, wait for NVidia to fix the problem.

Maybe I can feedback this to NVIDIA.
It may cause other problems of other softwares to downgrade the driver.