VirtualBox

Opened 4 years ago

Last modified 2 years ago

#19588 assigned defect

Crash - referenced memory at 0x0000000000000000

Reported by: Mark Filipak Owned by: gombara
Component: other Version: VirtualBox 6.1.6
Keywords: Cc:
Guest type: Linux Host type: Windows

Description

Host: Windows 10, 1803

Guest: Linux Mint, 18.3 Cinnamon 64-bit, 3.6.7

Guest Browser: Pale Moon, 28.9.3 (64-bit)

Web Site: 'https://coronavirus.jhu.edu/map.html'

Crash: "VirtualBoxVM.exe - Application Error"

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

Status: Hard, reproducible.

Attached: C:\VMs\Mint18\Mint18-2020-05-15-12-12-36.log

Attachments (4)

Mint18-2020-05-15-12-12-36.log (109.8 KB ) - added by Mark Filipak 4 years ago.
virtualbox_error.png (21.1 KB ) - added by josergc 4 years ago.
virtualbox_error1.png (51.8 KB ) - added by josergc 4 years ago.
Before the image is painted yellow, it was a floor map. That floor map gets corrupted then crashes the virtual machine.
VBox.log.2 (204.6 KB ) - added by Mark Filipak 4 years ago.

Download all attachments as: .zip

Change History (26)

by Mark Filipak, 4 years ago

comment:1 by Ben_P, 4 years ago

I've been running into a similar (maybe the same) issue for several versions of VirtualBox (months). I am using a Windows 10 x64 host and FreeBSD x64 guest. The instruction address is different but the memory address referenced (0x0000000000000000) is always the same.

The crash sometimes happens when I'm at the system but often happens when I'm away so the systems is as idle as it can be (not much running in the background). It will at times stay up and running for days and at times crash every couple hours.

in reply to:  1 ; comment:2 by Mark Filipak, 4 years ago

Replying to Ben_P:

I've been running into a similar (maybe the same) issue for several versions of VirtualBox (months)...

The problem appears to be with the Guest Additions. I regressed to VBox 6.1.6. Hopefully my report and yours will prompt the fix, eh?

in reply to:  2 comment:3 by Ben_P, 4 years ago

The problem appears to be with the Guest Additions.

Thank you, that is good to know. I just uninstalled the Extension Pack from my host system. Hopefully that will help it be more stable.

You're right about hoping the reports will result in a fix.

comment:4 by gombara, 4 years ago

Owner: set to gombara
Status: newassigned

This has been fixed quite recently and the fix wil be included in the next release. Do please change the vm settings and switch to vmsvga graphics adapter. If this does not solve the problem then please comment here. Thanks

in reply to:  4 comment:5 by Mark Filipak, 4 years ago

Replying to gombara:

... Do please change the vm settings and switch to vmsvga ...

I am using vmsvga.

in reply to:  4 ; comment:6 by Mark Filipak, 4 years ago

Replying to gombara:

This has been fixed quite recently and the fix wil be included in the next release...

Thank you!

in reply to:  6 ; comment:7 by gombara, 4 years ago

Replying to MarkFilipak:

Replying to gombara:

This has been fixed quite recently and the fix wil be included in the next release...

Thank you!

No. I was wrong to say that. The bug I referred occurs when a graphics adapter other than vmsvga is used. Meaning your bug is still out there lurking.

in reply to:  7 comment:8 by Mark Filipak, 4 years ago

Replying to gombara:

Replying to MarkFilipak:

Replying to gombara:

This has been fixed quite recently and the fix wil be included in the next release...

Thank you!

No. I was wrong to say that. The bug I referred occurs when a graphics adapter other than vmsvga is used. Meaning your bug is still out there lurking.

Hmmm... What can I do to help you? I'm a retired hardware designer and I know how to use Windows Sysinternals.

comment:9 by gombara, 4 years ago

I tried this on a Linux host with and could not reproduce. If you can give us step by step reproduction scenario that would be ideal.

in reply to:  9 comment:10 by Ben_P, 4 years ago

Replying to gombara:

I tried this on a Linux host with and could not reproduce. If you can give us step by step reproduction scenario that would be ideal.

I'm not exactly sure how to give you the steps to reproduce.

  1. Install VirtualBox on a fully patched Windows 10 host.
  2. Install a FreeBSD 12.1-RELEASE-p6 as a host
  3. Run the FreeBSD host and wait for a crash

When there's a crash again I'll post it somewhere and provide a link. It looks like a log was provided in the original report too.

by josergc, 4 years ago

Attachment: virtualbox_error.png added

comment:11 by josergc, 4 years ago

I got the same but "The memory could not be written." instead. I'm using VirtualBox 6.1.10 with the extension pack on a Windows 10 64bit host, running LUbuntu with the proprietary drivers in use. The graphics controller is VMSVGA, with 3D acceleration enabled. I notice before each crash, a corruption on the same JPG image in the web browser occurred.

by josergc, 4 years ago

Attachment: virtualbox_error1.png added

Before the image is painted yellow, it was a floor map. That floor map gets corrupted then crashes the virtual machine.

comment:12 by josergc, 4 years ago

Hmmm.... I don't know if it'd work for you, but I switched the video driver to VBoxVGA and 3D acceleration disabled, and I don't get the VM crashing anymore.

comment:13 by Mark Filipak, 4 years ago

Thanks Ben_P, josergc,

Let's see if there's any graphics commonality, eh?

My laptop has 2 GPUs, Intel HD Graphics 530 (8 cores) and NVIDIA GeForce GTX 980M (1536 cores). The Intel GPU is physically connected to the built-in UHD display. The NVIDIA GPU is physically connected to the display port -- HDMI on steroids -- that feeds a home theater.

The graphics driver uses a techology called 'Optimus' that controls both GPUs. For the built-in display, Optimus uses the NVIDIA's 1536 cores as coprocessors to do the rendering and then feeds the results to the Intel GPU for display.

The Windows Host and VBox with Linux Guest always go to the built-in display.

Is this at all similar what your computer does?

comment:14 by Mark Filipak, 4 years ago

Based on josergc's post, I installed 6.1.10 and the extension pack. The symptoms have not changed. Browing to 'https://coronavirus.jhu.edu/map.html' still causes the same error: "The instruction at 0x................ referenced memory at 0x0000000000000000. The memory could not be read."

by Mark Filipak, 4 years ago

Attachment: VBox.log.2 added

in reply to:  12 comment:15 by K3n20, 4 years ago

Replying to josergc:

Hmmm.... I don't know if it'd work for you, but I switched the video driver to VBoxVGA and 3D acceleration disabled, and I don't get the VM crashing anymore.

In my case the issue was that - the Virtual Box application crashed whenever i rebooted the guest machines, be it linux or windows the Vbox just crashed!! I changed the graphics controller to VBoxVGA and disabled the 3D acceleration just as you did and voila!! the Vbox application doesn't crashes anymore. Is is a problem due to the new windows 10 update (my Host is windows 10). Reason being everything was fine with the old settings until the latest windows update. Fill me in if i'm missing something here. Thanks

Edit: It also works fine with graphics adapter - VBoxSVGA and 3D acceleration disabled.

Last edited 4 years ago by K3n20 (previous) (diff)

in reply to:  13 ; comment:16 by Ben_P, 4 years ago

Replying to MarkFilipak:

Thanks Ben_P, josergc,

Let's see if there's any graphics commonality, eh?

My laptop has 2 GPUs, Intel HD Graphics 530 (8 cores) and NVIDIA GeForce GTX 980M (1536 cores). The Intel GPU is physically connected to the built-in UHD display. The NVIDIA GPU is physically connected to the display port -- HDMI on steroids -- that feeds a home theater.

The graphics driver uses a techology called 'Optimus' that controls both GPUs. For the built-in display, Optimus uses the NVIDIA's 1536 cores as coprocessors to do the rendering and then feeds the results to the Intel GPU for display.

The Windows Host and VBox with Linux Guest always go to the built-in display.

Is this at all similar what your computer does?

My machine is a Windows desktop, fairly old. It's a MSI video card with an AMD Radeon HD 7700 Series GPU and 1GB of memory. My host is running the current release version of the driver. My guest is CLI only so nothing special installed or enabled.

One other note is I updated to the version of VirtualBox that was just released (6.1.12) and just had a crash.

in reply to:  16 ; comment:17 by Mark Filipak, 4 years ago

Replying to Ben_P:

Replying to MarkFilipak:

Thanks Ben_P, josergc,

Let's see if there's any graphics commonality, eh?

Well, the Optimus thing was a long shot.

One other note is I updated to the version of VirtualBox that was just released (6.1.12) and just had a crash.

6.1.10 seems to have fixed the problem for me (from the changelog):

VirtualBox 6.1.10 (released June 05 2020)

Guest Additions: Fixed VBoxClient error: The parent session seems to be non-X11. (bug #19590)

I don't know whether the non-X11 bug (which I had also experienced), is related to your problem, but I suspect the Guest Additions. I suggest you post a post-crash log that should be found here: <your_VM_location>\Logs\VBox.log.1

in reply to:  17 ; comment:18 by Ben_P, 4 years ago

Replying to MarkFilipak:

I don't know whether the non-X11 bug (which I had also experienced), is related to your problem, but I suspect the Guest Additions. I suggest you post a post-crash log that should be found here: <your_VM_location>\Logs\VBox.log.1

It may be Guest Additions but I did uninstall them at one point and continued to have crashes.

Here is my VBox.log.1 file: https://pastebin.com/tXtDgZRe

in reply to:  18 ; comment:19 by Mark Filipak, 4 years ago

Replying to Ben_P:

It may be Guest Additions but I did uninstall them at one point and continued to have crashes.

That's not a good idea. You should start from scratch.

in reply to:  19 ; comment:20 by Ben_P, 4 years ago

This morning I uninstalled, deleted the VirtualBox folder in Program Files and re-installed. I'll keep an eye on things to see if I have any crashes in the next couple days.

Replying to MarkFilipak:

Replying to Ben_P:

It may be Guest Additions but I did uninstall them at one point and continued to have crashes.

That's not a good idea. You should start from scratch.

in reply to:  20 comment:21 by Mark Filipak, 4 years ago

Replying to Ben_P:

This morning I uninstalled, deleted the VirtualBox folder in Program Files and re-installed. I'll keep an eye on things to see if I have any crashes in the next couple days.

Thanks for staying in touch, Ben. Do us both a favor? Monitor keyboard state, also. I've found that I sometimes lose the Shift/Caps Lock state so that I can't control certain keys. For example, if I try to type ', I get ", instead and it can't be fixed except via one method: Go back to the Host, type something there, then return to the Guest and try again.

By the way, I doubt the problem is with the VBox application. So in the future, if you want to start from scratch, just delete the Guest and build a new one. That should take only a few minutes.

Tip: Whenever I update the VBox application, I save a copy of the current Guest, first. That way, if the new VBox malfunctions, I can regress by simply regressing to a previous version of VBox and copying the backed-up Guest, overwriting the one that the update may have compromised.

Good Luck, and Stay Healthy, eh?

comment:22 by Ben_P, 2 years ago

The crash persisted and would happen if I was at the computer, or away from the computer, if I had other applications open, or if VirtualBox was the only application open.

For anyone else searching this I got sick of it so I just wrote the following PowerShell script that I've got constantly running:

cls do {

if ( test-netconnection -ComputerName "192.168.0.252" -Port 22 -InformationLevel Quiet ) {

# Write-Output "FreeBSD-Server is online"

} else {

# Write-Output "FreeBSD-Server is down" Stop-Process -Name "VirtualBoxVM" $command = "c:\Program Files\Oracle\VirtualBox\VBoxManage.exe" $args = "startvm FreeBSD-Server" $prms = $args.Split(" ") & "$command" $prms

} Write-Output "Sleeping" Start-Sleep -Seconds 300

} until($infinity)

If I ever don't want the VM running I simply stop the script. It's pretty basic but basically pings the server every 5 minutes and if there are no replies it kills the hung process and starts the VM again.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use