Opened 8 years ago
Last modified 8 years ago
#16066 new defect
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 (7)
Change History (16)
by , 8 years ago
comment:1 by , 8 years ago
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.
comment:2 by , 8 years ago
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.
follow-up: 4 comment:3 by , 8 years ago
I think this might be a duplicate of "Immediate crash when pressing Alt+Num1", ticket #15719.
comment:4 by , 8 years ago
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 by , 8 years ago
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 by , 8 years ago
I would still like to know if the most recent VBox 5.1 test build for Windows make a difference.
comment:9 by , 8 years ago
@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.
Main log file