Blue screen on Windows 10 host

Discussions related to using VirtualBox on Windows hosts.
Post Reply
rsocol
Posts: 3
Joined: 15. Feb 2020, 17:46

Blue screen on Windows 10 host

Post by rsocol »

While restarting a Windows 10 guest, I got a blue screen on the Windows 10 host.

An WinDbg analysis of the minidump says:

Code: Select all

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffa208b17df388, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8003d8c5f7c, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on RAZVAN-DELL

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 6

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 70

    Key  : Analysis.System
    Value: CreateObject

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1

    Key  : Dump.Attributes.RequiredDumpfileSize
    Value: 0x734557C2


ADDITIONAL_XML: 1

DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

BUGCHECK_CODE:  d1

BUGCHECK_P1: ffffa208b17df388

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8003d8c5f7c

WRITE_ADDRESS: fffff80021b733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff80021a2a3d8: Unable to get Flags value from nt!KdVersionBlock
fffff80021a2a3d8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 ffffa208b17df388 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  VirtualBoxVM.e

TRAP_FRAME:  ffff800eca99f160 -- (.trap 0xffff800eca99f160)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000e3e00 rbx=0000000000000000 rcx=ffffa208b173b000
rdx=0000000000000467 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8003d8c5f7c rsp=ffff800eca99f2f0 rbp=ffffa208b17b1800
 r8=00000000e3e00000  r9=00000000e3e00000 r10=0000000000000003
r11=ffff800eca99f4d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
VBoxDDR0+0x5f7c:
fffff800`3d8c5f7c 0fab85c8130100  bts     dword ptr [rbp+113C8h],eax ss:0018:ffffa208`b17c2bc8=????????
Resetting default scope

STACK_TEXT:  
ffff800e`ca99f018 fffff800`217d33e9 : 00000000`0000000a ffffa208`b17df388 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff800e`ca99f020 fffff800`217cf72b : 00000000`00000000 00000000`00000000 ffffa208`00000000 ffffa208`cf166c40 : nt!KiBugCheckDispatch+0x69
ffff800e`ca99f160 fffff800`3d8c5f7c : ffffcd76`b4a09cc0 ffffa208`b173b000 ffffa208`b17b0000 ffffa208`b173b000 : nt!KiPageFault+0x46b
ffff800e`ca99f2f0 ffffcd76`b4a09cc0 : ffffa208`b173b000 ffffa208`b17b0000 ffffa208`b173b000 ffffa208`b174b000 : VBoxDDR0+0x5f7c
ffff800e`ca99f2f8 ffffa208`b173b000 : ffffa208`b17b0000 ffffa208`b173b000 ffffa208`b174b000 ffffcd76`b4a1ed70 : 0xffffcd76`b4a09cc0
ffff800e`ca99f300 ffffa208`b17b0000 : ffffa208`b173b000 ffffa208`b174b000 ffffcd76`b4a1ed70 00000000`00000003 : 0xffffa208`b173b000
ffff800e`ca99f308 ffffa208`b173b000 : ffffa208`b174b000 ffffcd76`b4a1ed70 00000000`00000003 fffff800`3d8c6041 : 0xffffa208`b17b0000
ffff800e`ca99f310 ffffa208`b174b000 : ffffcd76`b4a1ed70 00000000`00000003 fffff800`3d8c6041 ffffcd76`b4a09cc0 : 0xffffa208`b173b000
ffff800e`ca99f318 ffffcd76`b4a1ed70 : 00000000`00000003 fffff800`3d8c6041 ffffcd76`b4a09cc0 00000000`e3e00000 : 0xffffa208`b174b000
ffff800e`ca99f320 00000000`00000003 : fffff800`3d8c6041 ffffcd76`b4a09cc0 00000000`e3e00000 ffffa208`b173b000 : 0xffffcd76`b4a1ed70
ffff800e`ca99f328 fffff800`3d8c6041 : ffffcd76`b4a09cc0 00000000`e3e00000 ffffa208`b173b000 ffffa208`b173b000 : 0x3
ffff800e`ca99f330 ffffcd76`b4a09cc0 : 00000000`e3e00000 ffffa208`b173b000 ffffa208`b173b000 00000000`e3e00000 : VBoxDDR0+0x6041
ffff800e`ca99f338 00000000`e3e00000 : ffffa208`b173b000 ffffa208`b173b000 00000000`e3e00000 ffffa208`b173b000 : 0xffffcd76`b4a09cc0
ffff800e`ca99f340 ffffa208`b173b000 : ffffa208`b173b000 00000000`e3e00000 ffffa208`b173b000 00000000`00000003 : 0xe3e00000
ffff800e`ca99f348 ffffa208`b173b000 : 00000000`e3e00000 ffffa208`b173b000 00000000`00000003 fffff800`3d80708e : 0xffffa208`b173b000
ffff800e`ca99f350 00000000`e3e00000 : ffffa208`b173b000 00000000`00000003 fffff800`3d80708e ffffcd76`b4a09cc0 : 0xffffa208`b173b000
ffff800e`ca99f358 ffffa208`b173b000 : 00000000`00000003 fffff800`3d80708e ffffcd76`b4a09cc0 fffff800`3d7ee800 : 0xe3e00000
ffff800e`ca99f360 00000000`00000003 : fffff800`3d80708e ffffcd76`b4a09cc0 fffff800`3d7ee800 00000000`00000000 : 0xffffa208`b173b000
ffff800e`ca99f368 fffff800`3d80708e : ffffcd76`b4a09cc0 fffff800`3d7ee800 00000000`00000000 00000000`00000000 : 0x3
ffff800e`ca99f370 ffffcd76`b4a09cc0 : fffff800`3d7ee800 00000000`00000000 00000000`00000000 00000000`e3e00000 : VMMR0+0xe708e
ffff800e`ca99f378 fffff800`3d7ee800 : 00000000`00000000 00000000`00000000 00000000`e3e00000 00000000`e3e00000 : 0xffffcd76`b4a09cc0
ffff800e`ca99f380 00000000`00000000 : 00000000`00000000 00000000`e3e00000 00000000`e3e00000 ffffa208`b17b0000 : VMMR0+0xce800


SYMBOL_NAME:  VBoxDDR0+5f7c

MODULE_NAME: VBoxDDR0

IMAGE_NAME:  VBoxDDR0.r0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  5f7c

FAILURE_BUCKET_ID:  AV_VBoxDDR0!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {adfe888d-54bd-f62d-b430-1c3609d15304}

Followup:     MachineOwner
---------

The VHD was created with disk2vhd (about a month ago) from the same Dell Inspiron laptop.
For a while, I was downgrading to VirtualBox 6.0.12-133076 (because I was suspecting other crashes), but yesterday I upgraded again to 6.1.2-135663.
Today I installed the updated Virtual Machine Additions in the guest (after uninstalling VirtualBox itself from the guest), but I had already restarted the guest after installing them (this was another restart of the guest).
Top
rsocol
Posts: 3
Joined: 15. Feb 2020, 17:46

Re: Blue screen on Windows 10 host

Post by rsocol »

After another restart of the guest, I got a "Guru Meditation" message: "A critical error has occurred while running the virtual machine and the machine execution stopped". I am attaching the VBox.log and the VBox.png files, as instructed.
Attachments
VBox.png
VBox.png (13.3 KiB) Viewed 4878 times
VBoxLog.zip
(72.96 KiB) Downloaded 53 times
Top
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: Blue screen on Windows 10 host

Post by scottgus1 »

rsocol wrote:The VHD was created with disk2vhd (about a month ago) from the same Dell Inspiron laptop.
Dell locks their installed OS's to the hardware it's installed on, and you technically, and possibly in reality, can't run it on other hardware. Virtualbox is other 'hardware'.

The guest was save-stated: 
00:00:02.002959 Console: Machine state changed to 'Restoring'
There's unusual things in the log:
00:23:04.175730 AssertLogRel F:\tinderbox\win-rel\src\VBox\Devices\Graphics\DevVGA.cpp(5645) int __cdecl vgaR3PciIORegionVRamMapUnmap(struct PDMDEVINSR3 *,struct PDMPCIDEV *,unsigned int,unsigned __int64,unsigned __int64,enum PCIADDRESSSPACE): RT_SUCCESS_NP(rc)
00:23:04.175874 VERR_PGM_HANDLER_PHYSICAL_CONFLICT (-1603) - Attempt to register an access handler for a physical range of which a part was already handled.
Try running the guest with full shutdowns instead of save-state.

And to confirm that Virtualbox is still working, try a fresh Windows 10 guest with Microsoft's Media Creation Tool.
Top
fth0
Volunteer
Posts: 5690
Joined: 14. Feb 2019, 03:06
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Linux, Windows 10, ...
Location: Germany

Re: Blue screen on Windows 10 host

Post by fth0 »

The VBox.log file shows a known and yet unsolved issue, see https://www.virtualbox.org/ticket/19007 and viewtopic.php?f=6&t=94381&start=30#p461317.

Additionally, saving the state of a VM under VirtualBox version X and resuming the same VM under VirtualBox version Y can be compared to changing the hardware of a running PC. The larger the differences between X and Y, the higher the probability of a crash.
Top
scottcopus
Posts: 4
Joined: 31. Oct 2015, 18:04
Primary OS: MS Windows 10
VBox Version: OSE other
Guest OSses: Windows, Linux, DOS, bootable ISO/flash

Re: Blue screen on Windows 10 host

Post by scottcopus »

I wanted to chime in a "me too" for Win10 blue screens. I had VirtualBox 6.1.2 installed for several days and experienced several blue screens... sometimes while not even having VirtualBox running. The blue screen would always point to "vboxddr0.r0". Ever since uninstalling VirtualBox a couple weeks ago I've had no issues.

My setup:
Win10 Enterprise 10.0.18362 (aka 1903)
Dell XPS 13 9380 (Intel i7-8565U, 16GB), latest BIOS & drivers
Typically connected to a thunderbolt dock utilizing dock's connection to two UHD monitors, USB keyboard, USB mouse, audio, network, and occasionally USB flash drives.
Hyper-V not installed
VMware Workstation 15.5.1 installed (no issues)

cheers,
Scott
Top
rsocol
Posts: 3
Joined: 15. Feb 2020, 17:46

Re: Blue screen on Windows 10 host

Post by rsocol »

The Guru Meditation error still appears in VirtualBox 6.1.4, see attached files.
The VM state was saved in the same version of VirtualBox. VM Guest Additions were up to date. I was trying to restart after installing KB4537572.
About 40 seconds before the VERR_PGM_HANDLER_NOT_FOUND error, the same errors as before appeared in the log:
00:59:33.309989 AssertLogRel F:\tinderbox\win-rel\src\VBox\Devices\Graphics\DevVGA.cpp(5648) int __cdecl vgaR3PciIORegionVRamMapUnmap(struct PDMDEVINSR3 *,struct PDMPCIDEV *,unsigned int,unsigned __int64,unsigned __int64,enum PCIADDRESSSPACE): RT_SUCCESS_NP(rc)
00:59:33.310010 VERR_PGM_HANDLER_PHYSICAL_CONFLICT (-1603) - Attempt to register an access handler for a physical range of which a part was already handled.
Fortunately, no Blue Screen on the host this time.
Attachments
VBoxLog (29 feb 2020).zip
(75.38 KiB) Downloaded 54 times
Top
Post Reply

Return to “VirtualBox on Windows Hosts”