WinVista BSOD VBoxUSBMon.sys ( VBoxUSBMon+750 )

[szoppi]

Cannot successfully launch VirtualBox - vbox.log irrelevant for this bug.

Just installed 3.0.10 w/USB Support (w/o USB Support works fine)

BSOD fault 0x0000000A upon launch of VirtualBox

Same problem occurred when using USB support in 3.0.8.

Windbg information:

Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18082.x86fre.vistasp2_gdr.090803-2339
Machine Name:
Kernel base = 0x83e36000 PsLoadedModuleList = 0x83f4dc70
Debug session time: Wed Oct 28 22:33:39.432 2009 (GMT-7)

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {16, 1b, 0, 83e68f21}

Unable to load image \SystemRoot\system32\DRIVERS\VBoxUSBMon.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for VBoxUSBMon.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxUSBMon.sys
*** WARNING: Unable to verify timestamp for HSFHWCD2.sys
*** ERROR: Module load completed but symbols could not be loaded for HSFHWCD2.sys
*** WARNING: Unable to verify timestamp for HSF_DP.sys
*** ERROR: Module load completed but symbols could not be loaded for HSF_DP.sys
*** WARNING: Unable to verify timestamp for HSF_CNXT.sys
*** ERROR: Module load completed but symbols could not be loaded for HSF_CNXT.sys
Probably caused by : VBoxUSBMon.sys ( VBoxUSBMon+750 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000016, memory referenced
Arg2: 0000001b, IRQL
Arg3: 00000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 83e68f21, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 83f6d868
Unable to read MiSystemVaType memory at 83f4d420
 00000016 

CURRENT_IRQL:  1b

FAULTING_IP: 
nt!IoReleaseRemoveLockEx+111
83e68f21 80781601        cmp     byte ptr [eax+16h],1

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  VBoxSVC.exe

TRAP_FRAME:  8c81eefc -- (.trap 0xffffffff8c81eefc)
ErrCode = 00000000
eax=00000000 ebx=8b7bf7b0 ecx=83f6e3c0 edx=00000000 esi=8b7bf7c0 edi=00000000
eip=83e68f21 esp=8c81ef70 ebp=8c81ef8c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!IoReleaseRemoveLockEx+0x111:
83e68f21 80781601        cmp     byte ptr [eax+16h],1       ds:0023:00000016=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 83e68f21 to 83e83fb9

STACK_TEXT:  
8c81eefc 83e68f21 badb0d00 00000000 00000000 nt!KiTrap0E+0x2e1
8c81ef8c a0be4750 8b7bf7b0 8b7bf6f8 00000018 nt!IoReleaseRemoveLockEx+0x111
WARNING: Stack unwind information not available. Following frames may be wrong.
8c81efc8 83e7a976 8a131030 87afdb30 87afdb30 VBoxUSBMon+0x750
8c81efe0 9312d87e 87afdb30 00000000 9313b2e5 nt!IofCallDriver+0x63
8c81f020 9313a9f7 87afdb30 8a112a48 8a112030 HSFHWCD2+0x87e
8c81f040 9312d4ca 1bafdb30 83e7a976 8a112030 HSFHWCD2+0xd9f7
8c81f060 9480580e 87afdb30 00000000 9480bb08 HSFHWCD2+0x4ca
8c81f0a0 9480b21a 87afdb30 87afdc9c 8a102c98 HSF_DP+0x80e
8c81f0c0 9480544a 1bafdb30 83e7a976 8a102c98 HSF_DP+0x621a
8c81f0e0 9495b2bd 87afdb30 9499c9b6 8a0f10f8 HSF_DP+0x44a
8c81f114 83e7a976 8a0f1040 87afdb30 87afdb30 HSF_CNXT+0x572bd
8c81f12c 949ac1b8 8c81f158 949b000b 8a0f1040 nt!IofCallDriver+0x63
8c81f134 949b000b 8a0f1040 87afdb30 8c81f1d0 modem!ForwardIrp+0x18
8c81f158 83e7a976 8a0f1c58 87afdb30 00000000 modem!ModemPnP+0x11f
8c81f170 83f7dbfc 8c81f238 86fbb490 93151698 nt!IofCallDriver+0x63
8c81f1f8 9314aec4 8a131030 8c81f210 8c81f23c nt!IoGetDmaAdapter+0x110
00000000 00000000 00000000 00000000 00000000 HSFHWCD2+0x1dec4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
VBoxUSBMon+750
a0be4750 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  VBoxUSBMon+750

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VBoxUSBMon

IMAGE_NAME:  VBoxUSBMon.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ae887fb

FAILURE_BUCKET_ID:  0xA_VBoxUSBMon+750

BUCKET_ID:  0xA_VBoxUSBMon+750