#15770 closed defect (fixed)
Anniversary update incompatibility / the instuction at ... referenced memory 0x0000000000000020. The memory could not be read
| Reported by: | Frank Bevers | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 5.1.2 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description
A quick way of REPLICATING this (for me) on my W10/64bit host with anniversay update & VB up to version 5.1.3 /build 109780 is to simply close a vm window & then select "power off the machine" in the popup window. I tested with W7 & W8.1 vm's , even with freshly created vm's.
Under normal working circumstances the error occurs USUALLY when I shutdown a vm from within the vm itself (orderly shutdown)
I tried reverting to an older build as well (5.0.26) and it has the same issue so it must be an incompatibility caused by the W10 anniversary update I guess.
Attachments (5)
Change History (18)
by , 8 years ago
| Attachment: | VB screenshots.pdf added |
|---|
comment:1 by , 8 years ago
I installed todays Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3176495) but it does not change things.
I'm attaching a few screenshots taken when the error occured after I selected shutdown in the VM itself.
After the error the vm's are in an "aborted" state.
The visual studio debugger does not launch (invalid license ? See screenshot)
comment:3 by , 8 years ago
I have almost same problem. Virtual Machine randomly crash but I haven't anniversary update.
VirtualBox 5.1.2r108956
Error message: The instruction at 0x00007FFB01CE278E referenced memory at 0x0000000000000010. The memory could not be read.
Host: Windows 10 Enterprise x64 10.0.10586 (without anniversary update)
Guest: Windows 10 Enterprise x64 10.0.10586 (without anniversary update)
comment:4 by , 8 years ago
I have the same problem. Virtual Machine randomly crash since i have update virtualBox to 5.1.2 and windows 10 to anniversary update.
VirtualBox 5.1.2 r108956
Error message: The instruction at 0x00007FFB01CE278E referenced memory at 0x0000000000000010. The memory could not be read.
Host: Windows 10 Pro x64 14393.51 (with anniversary update)
Guest: Crash with Win 7 Pro 64 bits et 32 bits
I have attach my log file.
by , 8 years ago
| Attachment: | Thomas C. 2016-08-16-17-48-37.log added |
|---|
comment:6 by , 8 years ago
I have updagre to 5.1.4 and i have the same issue. I have attach print screen and log. At next crash, i will try to give mini dump. I will also try with disable sound.
by , 8 years ago
| Attachment: | VirtualBox_Crash_log added |
|---|
comment:7 by , 8 years ago
After a crash, there is no mini dump generated. I think its normal because it's not VirtualBox which crash but the guest. Next test : i will disable sound.
comment:8 by , 8 years ago
Result with sound disable : One day past without crash.
I will continue testing with sound disable.
comment:9 by , 8 years ago
An other day without crash.
So it will appear that sound is the reason of this issue.
comment:12 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Thank you. I will close this ticket then. Please reopen if necessary.
comment:13 by , 8 years ago
I continue to see the problem on a vm that uses the host usb port with a RS232 to usb converter; if I start the application that reads the RS232 data via USB all works well. If I shutdown the guest it errors out. I use 5.1.6 on W10Pro v1607. This used to work perfect on older OS , with older virtualbox version.
screenshots