Custom Query (16363 matches)
Results (1162 - 1164 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #12582 | obsolete | BSOD: PnP (vboxusb.sys) | ||
| Description |
Hello, BugCheck C9, {22e, fffff80023af3a70, ffffcf80021b4b40, 0}
DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000022e, The caller has completed a successful IRP_MJ_PNP instead of passing it down.
Arg2: fffff80023af3a70, The address in the driver's code where the error was detected.
Arg3: ffffcf80021b4b40, IRP address.
Arg4: 0000000000000000
The problem is caused by incorrect handling of IRP_MN_CANCEL_REMOVE_DEVICE state. vboxUsbPnPMnCancelRemoveDevice function (src/VBox/HostDrivers/VBoxUSB/win/dev/VBoxUsbPnP.cpp) is called with IRP_MN_CANCEL_REMOVE_DEVICE, but enmState is already in ENMVBOXUSB_PNPSTATE_STARTED state. MSDN says, you should pass the request down: A driver might receive a spurious cancel-remove request when the device is started and active. This can occur, for example, if the driver (or a driver higher in the device stack) failed an IRP_MN_QUERY_REMOVE_DEVICE request. When a device is started and active, a driver simply succeeds a spurious cancel-remove request for the device. current code: static NTSTATUS vboxUsbPnPMnCancelRemoveDevice(PVBOXUSBDEV_EXT pDevExt, PIRP pIrp)
{
ENMVBOXUSB_PNPSTATE enmState = vboxUsbPnPStateGet(pDevExt);
NTSTATUS Status = STATUS_SUCCESS;
if (enmState == ENMVBOXUSB_PNPSTATE_REMOVE_PENDING)
{
IoCopyCurrentIrpStackLocationToNext(pIrp);
Status = VBoxDrvToolIoPostSync(pDevExt->pLowerDO, pIrp);
if (NT_SUCCESS(Status))
{
vboxUsbPnPStateRestore(pDevExt);
}
}
else
{
Assert(0);
Assert(enmState == ENMVBOXUSB_PNPSTATE_STARTED);
}
VBoxDrvToolIoComplete(pIrp, Status, 0);
vboxUsbDdiStateRelease(pDevExt);
return Status;
}
fixed code: static NTSTATUS vboxUsbPnPMnCancelRemoveDevice(PVBOXUSBDEV_EXT pDevExt, PIRP pIrp)
{
ENMVBOXUSB_PNPSTATE enmState = vboxUsbPnPStateGet(pDevExt);
NTSTATUS Status = STATUS_SUCCESS;
Assert(enmState == ENMVBOXUSB_PNPSTATE_REMOVE_PENDING);
IoCopyCurrentIrpStackLocationToNext(pIrp);
Status = VBoxDrvToolIoPostSync(pDevExt->pLowerDO, pIrp);
if (NT_SUCCESS(Status))
{
if (enmState == ENMVBOXUSB_PNPSTATE_REMOVE_PENDING)
{
vboxUsbPnPStateRestore(pDevExt);
}
}
VBoxDrvToolIoComplete(pIrp, Status, 0);
vboxUsbDdiStateRelease(pDevExt);
return Status;
}
The same problem is also with vboxUsbPnPMnCancelStopDevice function. callstack: nt!KeBugCheckEx nt!VerifierBugCheckIfAppropriate nt!ViErrorFinishReport nt!VfPnpVerifyIrpStackUpward nt!VfMajorVerifyIrpStackUpward nt!IovpCompleteRequest2 nt!IovpLocalCompletionRoutine nt!IopfCompleteRequest nt!IovCompleteRequest VBoxUSB!vboxUsbPnPMnCancelRemoveDevice VBoxUSB!vboxUsbDispatchPnP VerifierExt!xdv_IRP_MJ_PNP_wrapper nt!IovCallDriver nt!ViFilterDispatchPnp nt!IovCallDriver VerifierExt!IofCallDriver_internal_wrapper MSDMFilt!FilterPassIrpSynchronously MSDMFilt!FilterCancelRemove MSDMFilt!FilterDispatchPnp VerifierExt!xdv_IRP_MJ_PNP_wrapper nt!IovCallDriver nt!ViFilterDispatchPnp nt!IovCallDriver nt!IopSynchronousCall nt!IopRemoveDevice nt! ?? ::NNGAKEGL::`string' nt!PnpDeleteLockedDeviceNode nt!PnpDeleteLockedDeviceNodes nt!PnpProcessQueryRemoveAndEject nt!PnpProcessTargetDeviceEvent nt!PnpDeviceEventWorker nt!ExpWorkerThread nt!PspSystemThreadStartup nt!KiStartSystemThread}}} Regards, Petr |
|||
| #10704 | obsolete | BSOD: SPECIAL_POOL_CORRUPTION_TYPE: 23 | ||
| Description |
BSOD: VirtualBox 4.1.18 for Windows hosts, Win 7 Ultimate 64 Bit host Debugging Details:
------------------
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
BUGCHECK_STR: 0xC1_23
SPECIAL_POOL_CORRUPTION_TYPE: 23
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: VirtualBox.exe
CURRENT_IRQL: 1
IRP_ADDRESS: fffff980042eaf3b
LAST_CONTROL_TRANSFER: from fffff8000356934a to fffff800034e31c0
STACK_TEXT:
fffff880`27cbb368 fffff800`0356934a : 00000000`000000c1 fffff980`03802fd0 fffff980`03802367 00000000`00530030 : nt!KeBugCheckEx
fffff880`27cbb370 fffff800`035e1fa3 : 00000000`00000000 00000000`00000000 fffff980`042eafa0 fffffa80`21619270 : nt!MiCheckSpecialPoolSlop+0x9a
fffff880`27cbb3b0 fffff800`0360d93b : fffff800`03464000 00000000`20206f49 ffffffff`fff70afa fffffa80`1ffa0280 : nt!MmFreeSpecialPool+0x1d3
fffff880`27cbb4f0 fffff800`034f7ade : 00000000`00000000 fffff980`042eafb0 fffff980`012eaa10 fffff980`0ffeaee0 : nt!ExDeferredFreePool+0xf33
fffff880`27cbb5a0 fffff800`034e6eea : fffff980`042eafb3 00000000`00000001 00000000`00000001 fffff800`0359cdf3 : nt!IopCompleteRequest+0x5ce
fffff880`27cbb670 fffff800`0397f19f : fffff980`042eaee0 fffff980`042eaf00 fffff980`042eae00 00000000`00000000 : nt!IopfCompleteRequest+0x66a
fffff880`27cbb760 fffff880`01baf1f6 : fffff880`27cbb8e8 00000000`00000000 00000000`00000000 fffff980`042eaee0 : nt!IovCompleteRequest+0x19f
fffff880`27cbb830 fffff800`03985c16 : fffff980`042eaee0 00000000`00000002 fffffa80`1d7e8060 fffffa80`18efe398 : VBoxDrv+0x11f6
fffff880`27cbb870 fffff800`037f9717 : fffffa80`1ffa0280 fffff880`27cbbb60 fffffa80`1ffa0280 fffffa80`244d70a0 : nt!IovCallDriver+0x566
fffff880`27cbb8d0 fffff800`037f9f76 : fffff880`03765180 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`27cbba00 fffff800`034e2453 : fffffa80`21619270 00000000`04c3fa18 fffff880`27cbba88 fffff800`037e8000 : nt!NtDeviceIoControlFile+0x56
fffff880`27cbba70 00000000`7750138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`04c3fb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7750138a
STACK_COMMAND: kb
FOLLOWUP_IP:
VBoxDrv+11f6
fffff880`01baf1f6 488b6c2448 mov rbp,qword ptr [rsp+48h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: VBoxDrv+11f6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: VBoxDrv
IMAGE_NAME: VBoxDrv.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4fce116c
FAILURE_BUCKET_ID: X64_0xC1_23_VRF_VBoxDrv+11f6
BUCKET_ID: X64_0xC1_23_VRF_VBoxDrv+11f6
Followup: MachineOwner
---------
2: kd> lmvm VBoxDrv
start end module name
fffff880`01bae000 fffff880`01bea000 VBoxDrv (export symbols) VBoxDrv.sys
Loaded symbol image file: VBoxDrv.sys
Image path: \SystemRoot\system32\DRIVERS\VBoxDrv.sys
Image name: VBoxDrv.sys
Timestamp: Tue Jun 05 10:02:20 2012 (4FCE116C)
CheckSum: 00039627
ImageSize: 0003C000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
|
|||
| #1683 | fixed | BSOD: Using Visual Studio with projects on a shared folder: BAD_POOL_HEADER, RDR_FILE_SYSTEM | ||
| Description |
I am able to reliably cause Windows XP SP2 to bluescreen by trying to rebuild a Visual Studio project that is located on a shared folder. If I copy the VS project on to the virtual C drive then it rebuilds just fine... This happens with any VS project.. include a New Console App. Usually the bluescreen error code is BAD_POOL_HEADER, but at one other time it was RDR_FILE_SYSTEM. There isn't any other information that I can see... the system reboots after about 1 second. This is a fairly critical issue for me as I need to share my dev files between my Linux host and XP Guest. Host is Ubuntu Hardy 8.04 x86. VirtualBox 1.6.2 PUEL. |
|||

