VirtualBox

Ticket #16066 (new defect)

Opened 5 years ago

Last modified 5 years ago

The instruction at 0x... referenced memory at 0x.... The memory could not be read.

Reported by: Paul B. Owned by:
Component: other Version: VirtualBox 5.1.6
Keywords: crash, instruction, memory, read Cc:
Guest type: Windows Host type: Windows

Description

Hello, after some weeks ago my virtual machine start crashing many times per day with error:

The instruction at 0x00007FFCCB3949F9 referenced memory at 0x0000000001C9196C. The memory could not be read.

It happened in old and new version too. As host I use Windows 10 with Anniversary update. Probably problems come after this update. Guest operating system is Windows Server 2012 R2.

I tried to create mini dump via instructions on link https://www.virtualbox.org/wiki/Core_dump but it is not working in Windows 10 Anniversary update. I did it via Process Explorer.

Attached Dumps.zip file contains mini dumps from all processes in process tree of problematic VirtualBox.exe process:

- VBoxSVC.exe (VBoxSVC_Mini.dmp)
  - VirtualBox.exe (VirtualBox1_Mini.dmp)
    - VirtualBox.exe (VirtualBox2_Mini.dmp)
      - VirtualBox.exe (VirtualBox3_Mini.dmp - VM process)

Thanks for any suggestion/help.

Attachments

VBox.log Download (74.5 KB) - added by Paul B. 5 years ago.
Main log file
VBoxHardening.log Download (282.3 KB) - added by Paul B. 5 years ago.
Second log file
SPS2013 Develop - EUIS.vbox Download (9.8 KB) - added by Paul B. 5 years ago.
VirtualBox settings file
Error.png Download (9.3 KB) - added by Paul B. 5 years ago.
Error message
VirtualBoxProcesses.png Download (16.7 KB) - added by Paul B. 5 years ago.
Process tree
Dumps.zip Download (420.8 KB) - added by Paul B. 5 years ago.
Mini dumps of VirtualBox processes
vbox.jpg Download (204.1 KB) - added by Robert Fernando 5 years ago.
Picture of memory error

Change History

Changed 5 years ago by Paul B.

Main log file

Changed 5 years ago by Paul B.

Second log file

Changed 5 years ago by Paul B.

VirtualBox settings file

Changed 5 years ago by Paul B.

Error message

Changed 5 years ago by Paul B.

Process tree

Changed 5 years ago by Paul B.

Mini dumps of VirtualBox processes

comment:1 Changed 5 years ago by Paul B.

Crash happens when I switch between processes with shortcut Alt+Tab inside guest OS.
Not in all cases, but only once a time.
When i switch between running applications by mouse, crash never happened.

Last edited 5 years ago by Paul B. (previous) (diff)

comment:2 Changed 5 years ago by Paul B.

When I try shutdown my host OS, process VBoxSVC.exe jammed and only one option to shutdown is force kill this process. All virtual machines are closed.

Last edited 5 years ago by Paul B. (previous) (diff)

comment:3 follow-up: ↓ 4 Changed 5 years ago by socratis

I think this might be a duplicate of "Immediate crash when pressing Alt+Num1", ticket #15719.

comment:4 in reply to: ↑ 3 Changed 5 years ago by Paul B.

Replying to socratis:

I think this might be a duplicate of "Immediate crash when pressing Alt+Num1", ticket #15719.

It is possible, but ticket #15719 didn't contains solution :-(

comment:5 Changed 5 years ago by Exie

I get this all day long running VirtualBox on Windows 10.14393

It used to happen with Virtualbox 5.1.6 and continues to happen with 5.1.8

I can reproduce this on-demand. If I lock my workstation and walk away, come back after an hour, my running VM's will crash with this message.

It seems most prevalent on VM's with a UI such as Centos/Ubuntu guests running X

comment:6 Changed 5 years ago by frank

I would still like to know if the most recent VBox 5.1 test build for Windows make a difference.

comment:7 Changed 5 years ago by Paul B.

Solved in latest version 5.1.9. Thank you for your effort.

Changed 5 years ago by Robert Fernando

Picture of memory error

comment:8 Changed 5 years ago by Robert Fernando

Same error see picture for details

occurs in 5.1.14

comment:9 Changed 5 years ago by socratis

@Rovert Fernando
You don't seem to have the same problem. Your VM isn't even running when you're getting the crash. It's most probably a completely different problem. Invalid memory referencing has a lot of reasons that can trigger it.

So, if you can, please open a new thread in the  VirtualBox on Windows Hosts section and let's see if we can solve your problem there.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use