Ошибка virtualbox память не может быть read

Hi all.

So I’ve had this installation of Kali Linux that I haven’t used in a while, but just tried to launch.
Now when I launch my virtual machine I get the error message that you see below every time I try to restart the VM.

There are no issues or error messages popping up while the VM boots, while it’s running or if I shut it down.
It only happens if I try to restart it.

I thought this was just an issue with the VM itself, so I just deleted the VM and created a fresh install. Same error.
I tested on a Windows VM that I have, no error message.
Is anyone familiar with this issue? Log attached.

The instruction at 0x00007FFE50F9F43C referenced memory at
0x0000000000000000. The memory could not be read.

Click on OK to terminate the program

Nvidia just released a driver with a file that is not signed. If Linux hosts act like Windows hosts by requiring driver files to be signed before they can be used by Virtualbox, then this driver is causing the trouble. Disabling 3D is a workaround to this problem, since 3D uses host video drivers to accelerate the guest video.

Try downgrading the Nvidia drivers.

Hello, disable 3d its just a half solve of problem.

In my case problem are coming after i had moved to ltsc before all worked more or less fine.

host win 10 Ltsc 1809
notebook dell g5 5590
cpu: intel 9750h (disabled hyper thread)
gpu1: intel uhd 630
gpu2: nvidia rtx 2060

guest
win 10 pro (1909)

1. First: set core count on guest to 2 or 4 (on 6 cores it hanging a lot some vbox bug)
2. i had tryed to install different versions of virtual box from 6.1.4 to 6.19 (testing) nothing help.
and versions of drivers for nvidia gpu only also different version of intel uhd.
drivers from dell official site will not solve problem at all.

after some time i have found setup to work well:
nvidia driver:
452.06 game ready with geeforce experience (don’t know why?)
intel udh driver: 27.21.14.5206
virtual box: 6.1.16

Thanks for your info, Maravan4. Yes, disabling 3D is only a workaround. With 3D off the host drivers are not used so the hardening/security-sign problem does not happen. However, the VM OS has to then drop back to software-ish rendering and harder running.

If Nvidia gets their drivers signed, then 3D acceleration can start being used again.

scottgus1 wrote:Thanks for your info, Maravan4. Yes, disabling 3D is only a workaround. With 3D off the host drivers are not used so the hardening/security-sign problem does not happen. However, the VM OS has to then drop back to software-ish rendering and harder running.

If Nvidia gets their drivers signed, then 3D acceleration can start being used again.

Which drivers? All files are signed, when I click on my GPU in device manager. Have same issue on latest nvidia drivers update (old drivers from dec, 20 works fine). Vbox 5 latest

NeedHelp1, please start a new topic.

Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM’s OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window’s VM list, choose Show Log. Save the far left tab’s log (and the hardening log next to it if you have a Windows host) zip them, and post the zip file, using the forum’s Upload Attachment tab.

13 июн. 2023, в 18:02

5000 руб./за проект

13 июн. 2023, в 17:53

3000 руб./за проект

13 июн. 2023, в 17:47

10000 руб./за проект