BSOD while testing "System - Sleep and PNP (disable and enable) with IO Before and After (Certification)" on Windows 8.1

Question

Hi Sir,

I met a system BSOD while testing "Sleep and PNP (disable and enable) with IO Before and After (Certification)" on Windows 8.1.

From the kernel debugger, I think this issue is similar with the issue described in following link.

http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/dfb8aca9-2e7b-4d7a-a221-aeb3cd5ca932/bsod-in-volsnapsys-during-sleep-and-pnp-disable-and-enable-with-io-before-and-after?forum=whck

Could you help me to check whether this is a known issue on Windows 8.1?

Is there a errata can cover this failure?

Following is the kernel dump when my system BSOD.

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000221, An IRP dispatch handler for a PDO has deleted its device object, but the
 hardware has not been reported as missing in a bus relations query.
Arg2: fffff801cd89da70, The address in the driver's code where the error was detected.
Arg3: ffffcf801c924ab0, IRP address.
Arg4: ffffe000023b10c0, Device object address.

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

ADDITIONAL_DEBUG_TEXT:  Bugcheck data extracted fron VfErrorBugcheckData.

BUGCHECK_STR:  0xc9_221

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  221

FAULTING_IP:
nt!ViGenericPnp+0
fffff801`cd89da70 4c8b056955c8ff  mov     r8,qword ptr [nt!pXdvIRP_MJ_PNP (fffff801`cd522fe0)]

FOLLOWUP_IP:
nt!ViGenericPnp+0
fffff801`cd89da70 4c8b056955c8ff  mov     r8,qword ptr [nt!pXdvIRP_MJ_PNP (fffff801`cd522fe0)]

IRP_ADDRESS: ffffcf801c924ab0

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff801cd8869e8 to fffff801cd8900ea

STACK_TEXT: 
ffffd000`26c20330 fffff801`cd8869e8 : ffffe000`03b47a70 ffffd000`26c20490 ffffe000`00c17520 00000000`00000000 : nt!ViErrorFinishReport+0x8e
ffffd000`26c20390 fffff801`cd88cbcd : 00000000`00000000 fffff800`00291db3 ffffe000`03b47a70 00000000`00000246 : nt!IovpCallDriver2+0x15c
ffffd000`26c20760 fffff801`cd881928 : ffffcf80`1c924ab0 00000000`00000002 ffffcf80`1c924ab0 fffff801`cd88d469 : nt!VfAfterCallDriver+0x289
ffffd000`26c207f0 fffff801`cd67d5ea : ffffe000`023b10c0 00000000`00000000 ffffd000`26c208f0 ffffe000`03b47a70 : nt!IovCallDriver+0x3e4
ffffd000`26c20840 fffff801`cd63d460 : 00000000`00000002 ffffd000`26c20909 ffffe000`023ba540 ffffe000`023b10c0 : nt!IopSynchronousCall+0xfe
ffffd000`26c208b0 fffff801`cd2d4667 : ffffc000`01c00a80 00000000`0000000a ffffe000`023ba540 00000000`0000000a : nt!IopRemoveDevice+0xe0
ffffd000`26c20970 fffff801`cd63c6b1 : ffffe000`023b10c0 ffffe000`023ba540 ffffc000`02833a80 fffff801`cd77f8fe : nt!PnpRemoveLockedDeviceNode+0x1a7
ffffd000`26c209d0 fffff801`cd63c62a : 00000000`00000000 ffffc000`02833a80 ffffe000`023ba540 00000000`3f051397 : nt!PnpDeleteLockedDeviceNode+0x4d
ffffd000`26c20a10 fffff801`cd63b9c7 : ffffe000`0228bca0 ffffd000`00000002 00000000`00000000 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0x9a
ffffd000`26c20a90 fffff801`cd635a15 : ffffc000`01c00a00 00000000`00000004 ffffc000`00000000 fffff801`ffffffff : nt!PnpProcessQueryRemoveAndEject+0x4ef
ffffd000`26c20bf0 fffff801`cd635d4f : ffffc000`01c00a80 00000000`00000000 00000000`00000000 fffff801`cd635a30 : nt!PnpProcessTargetDeviceEvent+0x9d
ffffd000`26c20c30 fffff801`cd25a3cd : fffff801`cd635a30 ffffc000`02832c70 ffffd000`26c20d10 ffffe000`0305f010 : nt!PnpDeviceEventWorker+0x31f
ffffd000`26c20c90 fffff801`cd305664 : ffffe000`00090040 ffffe000`0352f740 ffffe000`0352f740 ffffe000`00073040 : nt!ExpWorkerThread+0x2b5
ffffd000`26c20d40 fffff801`cd3746c6 : ffffd000`206aa180 ffffe000`0352f740 ffffe000`00090040 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`26c20da0 00000000`00000000 : ffffd000`26c21000 ffffd000`26c1b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  nt!ViGenericPnp+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5215d156

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  0xc9_221_VRF_nt!ViGenericPnp

BUCKET_ID:  0xc9_221_VRF_nt!ViGenericPnp

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xc9_221_vrf_nt!vigenericpnp

FAILURE_ID_HASH:  {9b03958c-18ab-732a-2c41-f92dcd519377}

Followup: MachineOwner

Thanks in advance.

HC

---

hchuang

Answer 1

Hi Haung,

It seems to be same kind of failure as mentioned in the link pasted by you. But that errata is only for VolSnap.sys, not for your driver under test. better you can contact MSFT for errata request if you are sure that it's not a problem in you driver.

Thanks,

Mudit

Answer 2

Hi,

Any news on this subject? I'm getting the same error.

Thanks

MS

Answer 3

Hi MS,

I solved this issue by disable the AHCI ports' Hot-Plug capability in BIOS.

Hope it helps.

Regards,

HC

---

hchuang