Opened 3 years ago
Last modified 3 years ago
#20313 new defect
CentOS7 poweroff BUG, Couldn't be written — at Version 2
| Reported by: | Justin-Young | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.1.18 |
| Keywords: | CentOS7 poweroff BUG | Cc: | |
| Guest type: | Linux | Host type: | Windows |
Description (last modified by )
- Windows: Win10 family Chinese version 20H2 19042.928 Mem 16GB
- CentOS: CentOS Linux release 7.9.2009 (Core)
- Kernel: 3.10.0-1160.el7.x86_64
- Configuration
- CPU:1cores
- Mem: 1GB
- Network Cards: 1 NAT
- Reproduce:
Actually, every centos7 VM has the same problem, and it seems to have nothing to do with the virtual machine configuration. This problem occurs regardless of poweroff, shutdown, init 0 or ACPI shutdown commands. In addition, win10 1909 also has this problem. I wanna know is that a BUG, thank you!
- Error Message
VirtualBoxVM.exe - Application Error: The instruction at 0x00007FFED15D9B2C referenced memory at 0x00007FFED15D9B2C. The memory could not be written. Click on OK to terminate the program.
Change History (7)
by , 3 years ago
| Attachment: | ct.vbox-prev added |
|---|
by , 3 years ago
by , 3 years ago
| Attachment: | VBox.2.log added |
|---|
by , 3 years ago
| Attachment: | VBox.log.1 added |
|---|
by , 3 years ago
| Attachment: | VBox.3.log added |
|---|
comment:2 by , 3 years ago
| Description: | modified (diff) |
|---|
This does look like a bug. As you noticed, VirtualBoxVM detects this crash and saves some diagnostic information in the corresponding log file. However, it isn't giving a lot of hints.
The best way to help some developer work on this issue would be to enable MiniDumps as described on https://www.virtualbox.org/wiki/Core_dump#WindowsMiniDumps and provide it (usually doesn't work as an attachment due to its size).
You could try upgrading to VirtualBox 6.1.20, because that has some fixes for the audio functionality. I don't remember that it resolves this symptom, but you could narrow it down yourself before upgrading: try disabling audio for your VM and see if the crash still happens.


I noticed the same exception information in Vbox.3.log and Vbox.log.1 as follows: