VBox crash when running Linux guests; graphics acceleration not working in Linux Mint

[WhatHaveYou]

I have two problems with VirtualBox 6.1.10 running on Windows 10 1909.

Problem 1: various Linux guests - namely: Mint 20 Cinnamon; a recent version of Kubuntu; a recent version of MX Linux - suffer from VirtualBox errors to do with being unable to read a memory location. These errors crash VirtualBox and occur when I try to restart (and shutdown?) the guest.

Problem 2: Mint is refusing to run with hardware graphics acceleration. I have set the graphics RAM - in VirtualBox - to the maximum and I am using the default graphics acceleration options, with (if this is not the default) such acceleration enabled. Mint 19 did use to run with hardware acceleration. Given that problem 1 affects multiple distros, I am disinclined to blame Mint.

Things I have tried to no avail:

• removing the 'WSL' from my Windows machine, and the 'Virtual Machine Platform';
  deleting and recreating VMs;
  reinstalling VirtualBox;
  reinstalling the Guest Additions;
  removing my WIndows anti-malware program;
  reinstalling my Windows Nvidia drivers;
  telling Mint's 'Driver Manager' to look for suitable drivers (it found none).

I would appreciate help.


Also, and about this board: I cannot work out how to change the e-mail address registered to my account. Also, having 'Logout [ <your username> ] will encourage people to click the username, hoping to do account administration. Instead the user will get logged out. That irritates. Also, the 'list' function on this forum seems not to work - or at least not in 'preview' mode.

[scottgus1]

Do the following for the Linux Mint guest. Its log should clear up both problems if the problems are what I think they are.

Start the guest from full normal shutdown, 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.

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.

Re 'Logout' ?= 'Manage Account':

having 'Logout [ <your username> ] will encourage people to click the username, hoping to do account administration. Instead the user will get logged out. That irritates.

Tabbing through the links at the top of the page reveals that 'logout username' is all one link. I don't know if it is possible to change it, though. Now that you know what it does, it won't be irritating anymore. There is a 'User Control Panel' link on the other side of the forum that handles forum-specific account settings. (It does make sense to me that the username should be with the Control Panel, though.)

Email and password are handled by Oracle Single Sign-On, not this forum. To change email:

Go to: profile.oracle.com
Sign in on the single-sign-on page.
Your Oracle profile information should come up. At the top should be your email and a link to edit it.

Here is how to use 'List" (click 'quote' to see how it looks in the editor):

1. item A
2. Item B
3. Item C

[WhatHaveYou]

Changing credentials: thank you; I got that working.

Using the list function on this forum: ah, OK, thanks. One expects though that it would suffice to press the toolbar button when the text to be listed is selected.

VirtualBox problems

You write: 'Run until you see the problem happen'. Yet, one of the two problems occurs immediately. That is the lack of graphics acceleration. The other problem occurs only when I restart - as against shutdown - the VM. But still I had some logs already. I attach them, with high hopes! I hope the compression format is alright. For, for boring reasons, it was easier to compress them on a Linux computer.

[fth0]

00:00:03.340493 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_X509_CPV_NOT_VALID_AT_TIME fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume6\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\HarddiskVolume6\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ccad5caddc3a3d35\nvldumdx.dll
00:00:03.340577 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ccad5caddc3a3d35\nvldumdx.dll' (C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ccad5caddc3a3d35\nvldumdx.dll): rcNt=0xc0000190
00:00:03.340928 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: cached rc=VERR_CR_X509_CPV_NOT_VALID_AT_TIME fImage=1 fProtect=0x2 fAccess=0x5 cHits=1 \Device\HarddiskVolume6\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ccad5caddc3a3d35\nvldumdx.dll
00:00:03.341199 supR3HardenedErrorV: supR3HardenedScreenImage/NtCreateSection: cached rc=VERR_CR_X509_CPV_NOT_VALID_AT_TIME fImage=1 fProtect=0x2 fAccess=0x5 cHits=2 \Device\HarddiskVolume6\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ccad5caddc3a3d35\nvldumdx.dll

On your host, you seem to have installed Nvidia drivers with expired certificates, and VirtualBox crashes later on during the graphics initialization.

[WhatHaveYou]

Thanks. At least now we know the cause. However: my Nvidia driver is recent (indeed I still have the problem after installing just now the latest driver) and according to this thread on the Nvidia forum well . . I don't know, it is hard to tell whose fault it is or what the fix is.

[WhatHaveYou]

I removed the dll that the log (not the hardening log, though the problem was about . . hardening) complained off. No dice. So I removed my Nvidia drivers using the Display Driver Uninstaller tool, in safe mode as the tool advised. Upon reboot I had a very low screen resolution. I told Windows to scan for new hardware - nothing. I started to install the drivers that Nvidia supplies. That install aborted but seemingly the Windows default Nvidia driver had installer. (So, something of an omnishambles here.) I ran Vbox. My VM ran with no problems. I installed the driver provided by Nvidia. The VM problem returned.

Do I even need the drivers provided by Nvidia, since Microsoft is providing a driver? I need the Nvidia Control Panel, but this is now a Store App and it seems to work irrespective of everything else. Dare I dream then that the horrible Nvidia drivers, that I have been installing all these years, can simply be dispensed with?

On the other hand: VBox never had a problem with my Nvidia drivers until recently. So what's going on?

[tamm0r]

Same problem here: invalid driver certificate and the VM crashes while trying to read from memory during guest system shutdown/restart. I have the latest Nvidia driver installed, not sure what else I can do besides disabling the 3D acceleration

[WhatHaveYou]

tamm0r

I wonder whether the problem has something to do with particular graphics cards (or Nvidia not signing them properly). What card do you have? A have a GeForce GT 1030.

[scottgus1]

Nvidia not signing them properly

This is the problem, as pointed out by fth0. Specifically 'nvldumdx.dll':

00:00:03.340493 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_CR_X509_CPV_NOT_VALID_AT_TIME fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume6\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\HarddiskVolume6\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ccad5caddc3a3d35\nvldumdx.dll

[WhatHaveYou]

scottgus1

Right; but I was wondering whether it was only certain (older?) graphics cards that are lacking the signature.

Either way: I bet reporting a bug to Nvidia - closed source, huge, writes bad UIs and bloated software, if perhaps good core graphics drivers - is . . fun. How does one attempt to do it?

[scottgus1]

It's actually the file that is missing the signature. The age of the video card being driven is probably not part of the equation.

Only thing I can suggest to contact Nvidia is a web-search. There's probably a 'Contact Us' link on their websites. Or a forum.

[WhatHaveYou]

I found, only, a chat form. It told me I'd be connected to an agent in about four minutes. When the counter got to 3 seconds, it reset to two minutes. I'll see what happens. If I actually get connected, my previous experience of the self-defeating, asinine nature of these things tells me that getting anything to an engineer will be impossible. (Still, at least I'm not using Linux. That makes dealing with support really, really fun. 'We do not support Linus' (sic) is something I was once told - by a company that did support Linux.)

EDIT: The form timed out and would not re-launch. I am now trying in a different browser. This is exactly the sort of utter nonsense that I expected. And guess who writes the chat software? It's . . Oracle.

EDIT: I found an email address, but it for corporations only. I used it anyway. I got an automatic reply that suggests that no-one will actually respond to the email. The autoreply did include a phone number. If and when I have the strength, I will ring it. I am unsure the number is in my country. My country is the UK. The number is: '+1 (408) 486-2000'.

EDIT: I got through to someone in the chat. That person thought I was running Linux because . . in short, she or he had no idea what VirtualBox was. But I managed to get my report escalated.

[tamm0r]

I found this thread in the Nvidia forum: bit.ly / 3fs8nQm (sry, had to use a link shortener, I'm not yet allowed to posts links)-

I've just rolled back to the version 446.14 of GeForce Game Ready driver and enabling again the 3D Acceleration it works like a charm, just like before upgrading to the 451.48.

A lot of people in various other forums recommend that driver version, too, so I just rolled back. Warning: do not install the Geforce Experience application from that version as it has security issues (it's not needed for proper functioning of the driver).

[WhatHaveYou]

tamm0r,

That version of the driver works for me. Thank you very much. Between us, I think we'll help people. For, you've supplied the work-around and I reported the bug.

EDIT: Actually, no. Sometimes - more often than not - when I boot my VM, I get a blank screen.

[WhatHaveYou]

I add the following - about Nvidia's lamentable support. For, I'd like this to be public.

The second tier of Nvidia support contacted me. I was asked, in broken English, for data I had provided already. I do not blame people who have English as their second language from taking up these jobs. Yet: garbled prose, together with asking for stuff supplied already, wastes the time and energy of the person who reported the problem. And just now I've been sent an e-mail by Nvidia support telling me I need to create a password for a support account and that I am to do so by clicking a link that reads 'reset [sic] password' and tells me that I have successfully changed my password when I have set it for the first time.