Page 1 of 1

VirtualBoxVM.exe Application Error - The memory could not be read

Posted: 2. Sep 2022, 08:51
by Mirmuse
I recently updated my virutalbox, and it is no longer able to open ubuntu without the error below:
The instruction at 0x00007FFC7B2AA6D4 referenced memory at
0x0000000000000000. The memory could not be read.

Click on OK to terminate the program
It then closes and says it failed to open a session of the virutal machine.

I tried uninstalling and reinstalling virtualbox, no change. I created a fresh VM of ubuntu to see if that specific VM was somehow the issue, but the new one has the same issue. I also updated my Nvidia drivers in case that was the problem; no change.

I saw that people previously had this issue and solved it by disabling 3d acceleration, but I had never had that enabled in the first place. Attached is the log.

Re: VirtualBoxVM.exe Application Error - The memory could not be read

Posted: 2. Sep 2022, 09:58
by mpack
Your extension pack version is wrong. It is supposed to match the host software version.
00:00:02.279520 VirtualBox VM 6.1.36 r152435 win.amd64 (Jul 19 2022 21:51:27) release log
...
00:00:02.381283 Installed Extension Packs:
00:00:02.381317 Oracle VM VirtualBox Extension Pack (Version: 6.1.32 r149290; VRDE Module: VBoxVRDP)
Also, you are allocating RAM that doesn't exist. I suggest you reduce to 4096MB.
00:00:02.380321 Host RAM: 15731MB (15.3GB) total, 6103MB (5.9GB) available
...
00:00:02.548004 RamSize <integer> = 0x0000000275800000 (10 561 257 472, 10 072 MB, 9.8 GB)
On the other hand you didn't give it enough graphics RAM: max this parameter out.
00:00:02.548426 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)
While you are in there, reduce CPU cores to 2, since I very much doubt you have 7 cores free. In any case wasted cores do not make a VM go faster.
00:00:02.548000 NumCPUs <integer> = 0x0000000000000007 (7)
I couldn't tell how many cores you actually have free because the VM log was truncated. Please make sure the VM is full closed down before copying logs, and zip logs before attaching them.

Finally: this is not a Linux Guests question. These problems would affect any guest. Topic moved to "Windows Hosts".