VirtualBox

Opened 14 years ago

Closed 14 years ago

#6453 closed defect (fixed)

BSOD bug check 0xc9 on windows7(64bit) guest.

Reported by: benjaminkim Owned by:
Component: other Version: VirtualBox 3.1.6
Keywords: BSOD, vboxmouse Cc:
Guest type: Windows Host type: Linux

Description

When I enable driver verifier and do reboot, then always BSOD occurs. The host system is Ubuntu 10.04 Beta. I use Vbox 3.1.6

Here is Bugcheck Analysis.

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 0000000000000006, IRP passed to IoCompleteRequest contains invalid status Arg2: 0000000000000103, the status Arg3: fffff98002d66cf0, the IRP Arg4: 0000000000000000

Debugging Details:


BUGCHECK_STR: 0xc9_6

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 6

IRP_ADDRESS: fffff98002d66cf0

DEVICE_OBJECT: fffffa8002aa72f0

DRIVER_OBJECT: fffffa8002aa8080

IMAGE_NAME: VBoxMouse.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4babb08a

MODULE_NAME: VBoxMouse

FAULTING_MODULE: fffff880033ea000 VBoxMouse

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LOCK_ADDRESS: fffff80002c88400 -- (!locks fffff80002c88400)

Resource @ ntPiEngineLock (0xfffff80002c88400) Exclusively owned

Contention Count = 1 NumberOfExclusiveWaiters = 1

Threads: fffffa8000cfbb60-01<*> Threads Waiting On Exclusive Access:

fffffa8000cfb040

1 total locks, 1 locks currently held

PNP_TRIAGE:

Lock address : 0xfffff80002c88400 Thread Count : 1 Thread address: 0xfffffa8000cfbb60 Thread wait : 0x518

LAST_CONTROL_TRANSFER: from fffff80002f250c2 to fffff80002a85f00

STACK_TEXT: fffff8800370f4f8 fffff80002f250c2 : 00000000000000c9 0000000000000006 0000000000000103 fffff98002d66cf0 : ntKeBugCheckEx fffff8800370f500 fffff880033f413b : fffff98002d66c00 0000000000000000 fffff98002d66cf0 fffffa8002aa72f0 : ntIovCompleteRequest+0xc2 fffff8800370f5d0 fffff80002f2bc16 : fffffa8002aa72f0 fffff98002d66cf0 fffffa8002aa9d60 fffffa8002a7d940 : VBoxMouse!g_szRTAssertMsg2+0x24cb fffff8800370f670 fffff880032034eb : 0000000000000103 fffffa8002a7d940 fffffa8002aa9d60 fffffa8002b295a0 : ntIovCallDriver+0x566 fffff8800370f6d0 fffff80002f2bc16 : fffff98002d66cf0 0000000000000002 fffffa8002aa9c10 fffffa8002b312e0 : mouclass!MousePnP+0x337 fffff8800370f730 fffff80002e43bde : fffff98002d66cf0 fffffa8002c38170 fffffa8002aa9c10 fffffa8002b312e0 : ntIovCallDriver+0x566 fffff8800370f790 fffff80002b7e0ed : fffffa80026a9390 fffffa8002c38170 fffff80002b83cd0 0000000000000000 : ntPnpAsynchronousCall+0xce fffff8800370f7d0 fffff80002e4e926 : fffff80002c881c0 fffffa80026aa890 fffffa8002c38170 fffffa80026aaa38 : ntPnpStartDevice+0x11d fffff8800370f890 fffff80002e4ebc4 : fffffa80026aa890 fffffa8000cd0019 fffffa8000cd5520 0000000000000001 : ntPnpStartDeviceNode+0x156 fffff8800370f920 fffff80002e71ea6 : fffffa80026aa890 fffffa8000cd5520 0000000000000001 0000000000000000 : nt!PipProcessStartPhase1+0x74 fffff8800370f950 fffff80002e7235c : fffffa8002a65560 0000000000000000 0000000000000000 0000000000000000 : ntPipProcessDevNodeTree+0x296 fffff8800370fbc0 fffff80002b86322 : 0000000100000003 0000000000000000 0000000032706e50 0000000000000084 : ntPiProcessStartSystemDevices+0x7c fffff8800370fc10 fffff80002a93161 : fffff80002b86020 fffff80002d7f501 fffffa8000cfbb00 0000000000000000 : ntPnpDeviceActionWorker+0x302 fffff8800370fcb0 fffff80002d29166 : 0000000000000000 fffffa8000cfbb60 0000000000000080 fffffa8000c5ab30 : ntExpWorkerThread+0x111 fffff8800370fd40 fffff80002a64486 : fffff880009e4180 fffffa8000cfbb60 fffff880009eef40 0000000000000000 : ntPspSystemThreadStartup+0x5a fffff8800370fd80 0000000000000000 : fffff88003710000 fffff8800370a000 fffff8800370f320 0000000000000000 : ntKxStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP: VBoxMouse!g_szRTAssertMsg2+24cb fffff880033f413b e95d010000 jmp VBoxMouse!g_szRTAssertMsg2+0x262d (fffff880033f429d)

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: VBoxMouse!g_szRTAssertMsg2+24cb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xc9_6_VRF_VBoxMouse!g_szRTAssertMsg2+24cb

BUCKET_ID: X64_0xc9_6_VRF_VBoxMouse!g_szRTAssertMsg2+24cb

Followup: MachineOwner

Change History (1)

comment:1 by Frank Mehnert, 14 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use