Opened 4 years ago
Last modified 4 years ago
#20145 new defect
BSOD when a VM is shut down — at Initial Version
| Reported by: | Rafcio | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.1.16 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description
This issue is not new, but finally I'm fed up. I thought that you get crash reports from Microsoft, but perhaps this is not the case. It's been perhaps a year that this been happening and no solution still. At least 4 out of 5 times when a particular Windows 7 VM is shut down (not when it's restarted only), it causes the BSOD (memory corruption) on the Windows 10 host. It's more likely to happen when the VM has been running at least several hours, but this is not a requirement. The below info is from the debugger, but I don't know how to debug that, only providing this as a proof it's VirtualBox (VBoxDrv.sys) that causes the crash.
BugCheck 1A, {1236, ffff8a871b92b000, ffff8a871b92b308, 242513}
- ERROR: Symbol file could not be found. Defaulted to export symbols for VBoxDrv.sys -
- ERROR: Symbol file could not be found. Defaulted to export symbols for VMMR0.r0 -
Probably caused by : memory_corruption
BUGCHECK_STR: 0x1a_1236
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: VirtualBoxVM.e
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80782747406 to fffff807827f5780
STACK_TEXT:
fffff98f33cdf518 fffff80782747406 : 000000000000001a 0000000000001236 ffff8a871b92b000 ffff8a871b92b308 : ntKeBugCheckEx
fffff98f33cdf520 fffff8078271fc5b : ffff8a871b92b000 ffff87f200000000 ffffed8006c6f390 ffff8a8700000001 : ntMiFreePagesFromMdl+0x4c2
fffff98f33cdf5b0 fffff807881be341 : ffff8a8719ae7010 ffff8a871b530aa0 ffff8a871b931010 0100000000100000 : ntMmFreePagesFromMdl+0xb
fffff98f33cdf5e0 fffff8078818347b : ffff8a871b92d010 ffff8a871b530aa0 ffff8a871b931010 000000000d846602 : VBoxDrv!g_abRTZero4K+0x12bf1
fffff98f33cdf610 fffff8077ebd5f15 : ffff8a8719ae7010 ffff8a8719ae7010 ffff8a8719ae7010 fffff8078270f2b9 : VBoxDrv!RTR0MemObjFree+0xfb
fffff98f33cdf640 fffff8077ebd6a8f : ffff8a871b931010 ffff8a8719ae7260 ffff8a8716625000 fffff8078818227c : VMMR0!GMMR0Term+0x645
fffff98f33cdf6c0 fffff8077ebd856a : 0000000000002000 ffff8a8719ae7018 ffff8a8719e02010 ffff8a8716625000 : VMMR0!GMMR0CleanupVM+0x25f
fffff98f33cdf720 fffff8077ebd8794 : ffff8a8719e02030 ffff8a8716625000 ffff8a8719e02010 ffff8a8719e02030 : VMMR0!GVMMR0DestroyVM+0x39a
fffff98f33cdf750 fffff80788161cc1 : ffff8a871100c8d0 0000000000000055 ffff8a8719e02030 ffff8a8709e02000 : VMMR0!GVMMR0DestroyVM+0x5c4
fffff98f33cdf7a0 fffff8077ebd8465 : ffff8a8716625000 0000000000000003 0000000000042000 fffff807826501c1 : VBoxDrv!SUPR0ObjRelease+0x171
fffff98f33cdf7d0 fffff8077ebfe2a1 : 0000000000000000 0000000000000000 ffff8a87171e07c0 0000000000000000 : VMMR0!GVMMR0DestroyVM+0x295
fffff98f33cdf840 fffff8077ebff4ff : 0000000000000021 0000000000000000 0000000000000000 fffff8078266119e : VMMR0ModuleInit+0x6e1
fffff98f33cdf8a0 fffff80788167bfb : ffff8a871d9e7010 ffff8a870f8331a0 0000000000000000 ffff8a87171e07c0 : VMMR0!VMMR0EntryEx+0x9f
fffff98f33cdf910 fffff807881760d4 : 0000000000000030 fffff98f33cdfcc0 0000000000000030 ffff8a8700000000 : VBoxDrv!SUPR0PageFree+0x296b
fffff98f33cdf980 fffff807829fcb82 : 000000000022821c fffff80788175df0 0000000009a3f848 ffff8a8700000030 : VBoxDrv!SUPR0IoCtlPerform+0x25a4
fffff98f33cdfa20 fffff807829fc7e6 : ffff8a87189897c0 0000000000000000 0000000000000000 0000000000000000 : ntIopXxxControlFile+0x382
fffff98f33cdfb60 fffff807828071b5 : ffff8a87178f9080 fffff98f33cdfcc0 0000000009a3e4f8 fffff98f33cdfbe8 : ntNtDeviceIoControlFile+0x56
fffff98f33cdfbd0 00007ffaad14c094 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntKiSystemServiceCopyEnd+0x25
0000000009a3f7a8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x7ffa`ad14c094
I can provide more info (just ask), perhaps even upload the memory dump for analysis, but I don't have the skills to analyze the crash dump myself.

