Ticket #20145 (new defect)

Opened 9 months ago

Last modified 9 months ago

BSOD when a VM is shut down

Reported by: Rafcio Owned by:
Component: other Version: VirtualBox 6.1.16
Keywords: Cc:
Guest type: Windows Host type: Windows

Description (last modified by ramshankar) (diff)

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




LAST_CONTROL_TRANSFER:  from fffff80782747406 to fffff807827f5780

fffff98f`33cdf518 fffff807`82747406 : 00000000`0000001a 00000000`00001236 ffff8a87`1b92b000 ffff8a87`1b92b308 : nt!KeBugCheckEx
fffff98f`33cdf520 fffff807`8271fc5b : ffff8a87`1b92b000 ffff87f2`00000000 ffffed80`06c6f390 ffff8a87`00000001 : nt!MiFreePagesFromMdl+0x4c2
fffff98f`33cdf5b0 fffff807`881be341 : ffff8a87`19ae7010 ffff8a87`1b530aa0 ffff8a87`1b931010 01000000`00100000 : nt!MmFreePagesFromMdl+0xb
fffff98f`33cdf5e0 fffff807`8818347b : ffff8a87`1b92d010 ffff8a87`1b530aa0 ffff8a87`1b931010 00000000`0d846602 : VBoxDrv!g_abRTZero4K+0x12bf1
fffff98f`33cdf610 fffff807`7ebd5f15 : ffff8a87`19ae7010 ffff8a87`19ae7010 ffff8a87`19ae7010 fffff807`8270f2b9 : VBoxDrv!RTR0MemObjFree+0xfb
fffff98f`33cdf640 fffff807`7ebd6a8f : ffff8a87`1b931010 ffff8a87`19ae7260 ffff8a87`16625000 fffff807`8818227c : VMMR0!GMMR0Term+0x645
fffff98f`33cdf6c0 fffff807`7ebd856a : 00000000`00002000 ffff8a87`19ae7018 ffff8a87`19e02010 ffff8a87`16625000 : VMMR0!GMMR0CleanupVM+0x25f
fffff98f`33cdf720 fffff807`7ebd8794 : ffff8a87`19e02030 ffff8a87`16625000 ffff8a87`19e02010 ffff8a87`19e02030 : VMMR0!GVMMR0DestroyVM+0x39a
fffff98f`33cdf750 fffff807`88161cc1 : ffff8a87`1100c8d0 00000000`00000055 ffff8a87`19e02030 ffff8a87`09e02000 : VMMR0!GVMMR0DestroyVM+0x5c4
fffff98f`33cdf7a0 fffff807`7ebd8465 : ffff8a87`16625000 00000000`00000003 00000000`00042000 fffff807`826501c1 : VBoxDrv!SUPR0ObjRelease+0x171
fffff98f`33cdf7d0 fffff807`7ebfe2a1 : 00000000`00000000 00000000`00000000 ffff8a87`171e07c0 00000000`00000000 : VMMR0!GVMMR0DestroyVM+0x295
fffff98f`33cdf840 fffff807`7ebff4ff : 00000000`00000021 00000000`00000000 00000000`00000000 fffff807`8266119e : VMMR0!ModuleInit+0x6e1
fffff98f`33cdf8a0 fffff807`88167bfb : ffff8a87`1d9e7010 ffff8a87`0f8331a0 00000000`00000000 ffff8a87`171e07c0 : VMMR0!VMMR0EntryEx+0x9f
fffff98f`33cdf910 fffff807`881760d4 : 00000000`00000030 fffff98f`33cdfcc0 00000000`00000030 ffff8a87`00000000 : VBoxDrv!SUPR0PageFree+0x296b
fffff98f`33cdf980 fffff807`829fcb82 : 00000000`0022821c fffff807`88175df0 00000000`09a3f848 ffff8a87`00000030 : VBoxDrv!SUPR0IoCtlPerform+0x25a4
fffff98f`33cdfa20 fffff807`829fc7e6 : ffff8a87`189897c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x382
fffff98f`33cdfb60 fffff807`828071b5 : ffff8a87`178f9080 fffff98f`33cdfcc0 00000000`09a3e4f8 fffff98f`33cdfbe8 : nt!NtDeviceIoControlFile+0x56
fffff98f`33cdfbd0 00007ffa`ad14c094 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`09a3f7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 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.


VBox.log.3 Download (167.0 KB) - added by Rafcio 9 months ago.
Log file when the machine was shut down successfully
VBox.log.2 Download (95.6 KB) - added by Rafcio 9 months ago.
Log file of a crashed session

Change History

comment:1 Changed 9 months ago by ramshankar

  • Description modified (diff)

comment:2 Changed 9 months ago by ramshankar

Please upload VBox.log of the VM in question.

comment:3 Changed 9 months ago by ramshankar

  • Description modified (diff)

Changed 9 months ago by Rafcio

Log file when the machine was shut down successfully

Changed 9 months ago by Rafcio

Log file of a crashed session

comment:4 Changed 9 months ago by Rafcio

Regarding the log of a crashed session. Sometimes I don't shut down the guest outright before rebooting the host (which typically ends with BSOD), but reboot the guest and pause the client VM right after the BIOS splash screen is displayed in the guest window. Then I try rebooting the host. Sometimes that helps, but it didn't at that time which is indicated by a bunch of NUL characters at the end of the log file.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use