none
BSOD in VolSnap.Sys During Sleep and PNP (disable and enable) with IO Before and After (Certification - Software Device) RRS feed

  • Question

  • Hi!

    I'm running into the following when I run the Sleep and PNP (disable and enable) with IO Before and After
    (Certification - Software Device) test on Windows 8:

    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: fffff88001a8f710, The address in the driver's code where the error was detected.
    Arg3: fffff98038534af0, IRP address.
    Arg4: fffffa80055058a0, Device object address.

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


    ADDITIONAL_DEBUG_TEXT:  Bugcheck data extracted fron VfErrorBugcheckData.

    OVERLAPPED_MODULE: Address regions for 'cdrom' and 'cdrom.sys' overlap

    BUGCHECK_STR:  0xc9_221

    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  221

    FAULTING_IP:
    volsnap!VolSnapPnp+0
    fffff880`01a8f710 48895c2408      mov     qword ptr [rsp+8],rbx

    At first I thought this may have something to do with my WFP callout driver. I then ran the same test and selected wfplwf.sys. I ran into the same BSOD.

    I also recreated/reformatted the partitions on the hard drive but this did not help. The hard drive has three partitions, with Win8 on one and Win7 on another. The third partition is not bootable and is used to save backup data from the other partitions.

    This is very reproducible but unfortunately, since this apparently not being caused by my driver, I'm stuck as to how to proceed. What is the reason for this crash and how can I work around it?

    The full stack trace from the DV assert follows:

    *******************************************************************************
    *                                                                             *
    *                        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: fffff88001a8f710, The address in the driver's code where the error was detected.
    Arg3: fffff98038534af0, IRP address.
    Arg4: fffffa80055058a0, Device object address.

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


    ADDITIONAL_DEBUG_TEXT:  Bugcheck data extracted fron VfErrorBugcheckData.

    OVERLAPPED_MODULE: Address regions for 'cdrom' and 'cdrom.sys' overlap

    BUGCHECK_STR:  0xc9_221

    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  221

    FAULTING_IP:
    volsnap!VolSnapPnp+0
    fffff880`01a8f710 48895c2408      mov     qword ptr [rsp+8],rbx

    FOLLOWUP_IP:
    volsnap!VolSnapPnp+0
    fffff880`01a8f710 48895c2408      mov     qword ptr [rsp+8],rbx

    IRP_ADDRESS:  fffff98038534af0

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff801876b9062 to fffff801876bb86a

    STACK_TEXT: 
    fffff880`02f40350 fffff801`876b9062 : fffffa80`04a0d6d0 fffff880`02f404a0 fffffa80`0421d0f0 fffffa80`055058a0 : nt!ViErrorFinishReport+0x72
    fffff880`02f403a0 fffff801`876b6ef2 : fffffa80`055059f0 fffff880`01a8f872 fffffa80`04a0d6d0 fffff980`38534fb0 : nt!IovpCallDriver2+0x18a
    fffff880`02f40770 fffff801`876add6d : fffff980`38534af0 fffffa80`055058a0 fffff980`38534af0 fffff801`876b6695 : nt!VfAfterCallDriver+0x296
    fffff880`02f40800 fffff801`87459bdf : fffffa80`055058a0 00000000`c00000bb 00000000`00000000 fffffa80`04a0d6d0 : nt!IovCallDriver+0x3fd
    fffff880`02f40850 fffff801`87574cfd : 00000000`00000002 fffff880`02f40919 fffffa80`05509d30 fffffa80`055058a0 : nt!IopSynchronousCall+0xc7
    fffff880`02f408c0 fffff801`871b5c28 : fffff8a0`026fdc20 00000000`00000000 fffffa80`05509d30 00000000`00000000 : nt!IopRemoveDevice+0xd9
    fffff880`02f40980 fffff801`875742c6 : fffffa80`055058a0 fffffa80`05509d30 00000000`00000000 fffff8a0`01d29101 : nt!PnpRemoveLockedDeviceNode+0x1b8
    fffff880`02f409d0 fffff801`875741f0 : 00000000`00000000 00000000`00000000 fffff8a0`01d29100 fffffa80`05509d30 : nt!PnpDeleteLockedDeviceNode+0x9a
    fffff880`02f40a10 fffff801`8765a375 : 00000000`00000000 fffff880`02f40b70 fffff8a0`024bc220 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0x98
    fffff880`02f40a70 fffff801`874044a5 : fffff880`00000000 00000000`00000000 fffff8a0`0056a500 fffff8a0`00000000 : nt! ?? ::NNGAKEGL::`string'+0x28ee0
    fffff880`02f40be0 fffff801`87467616 : fffff8a0`026fdc20 00000000`00000000 00000000`00000001 00000001`65d06f00 : nt!PnpProcessTargetDeviceEvent+0x9d
    fffff880`02f40c20 fffff801`871050d1 : fffffa80`036d27c0 fffff8a0`024bc220 fffff801`8746732c fffffa80`069de010 : nt!PnpDeviceEventWorker+0x2ea
    fffff880`02f40c80 fffff801`87099e45 : 00020000`00000000 00000000`00000080 fffff801`87104f90 fffffa80`036d27c0 : nt!ExpWorkerThread+0x142
    fffff880`02f40d10 fffff801`8714e676 : fffff880`009c7180 fffffa80`036d27c0 fffffa80`036a1700 fffffa80`036bc940 : nt!PspSystemThreadStartup+0x59
    fffff880`02f40d60 00000000`00000000 : fffff880`02f41000 fffff880`02f3b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND:  .bugcheck ; kb

    SYMBOL_NAME:  volsnap!VolSnapPnp+0

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: volsnap

    IMAGE_NAME:  volsnap.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  5010abc2

    BUCKET_ID_FUNC_OFFSET:  0

    FAILURE_BUCKET_ID:  0xc9_221_VRF_volsnap!VolSnapPnp

    BUCKET_ID:  0xc9_221_VRF_volsnap!VolSnapPnp

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

    Saturday, May 4, 2013 2:26 AM

All replies

  • You are seeing this due to a known bug in Windows 8. Please refer to errata #582 with your submission and submit the memory dump to have this failure manually waived by our submission reviewers.

    Note that errata #582 only applies when:

    1) This particular bug check (DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)) in volsnap.sys is seen, and

    2) Sleep and PNP (disable and enable) with IO Before and After (Certification - Software Device) is the failing test

    Thanks


    This posting is provided AS IS with no warranties, and confers no rights.

    Monday, May 6, 2013 7:55 PM
  • hey thanks for your information.

    how can i submit this package to Microsoft, if this test getting failed every time.

    your reply will help me a lot.

    Many thanks.

    Monday, August 24, 2015 6:31 AM