睡眠期间的VolSnap.Sys中的BSOD和使用IO之前和之后的PNP（禁用和启用）（认证 - 软件设备） [英] BSOD in VolSnap.Sys During Sleep and PNP (disable and enable) with IO Before and After (Certification - Software Device)
问题描述
嗨！
当我运行 睡眠和PNP（禁用并启用）时，我遇到了以下情况在Windows 8之前和之后的
（认证 - 软件设备）测试：
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）
$
IO管理员遇到行为不端的司机。
参数：
Arg1：0000000000000221，一个IRP调度处理程序对于PDO已删除其设备对象，但在总线关系查询中尚未报告该
硬件。
Arg2：fffff88001a8f710，地址在检测到错误的驱动程序代码。
Arg3：fffff98038534af0，IRP地址。
Arg4：fffffa80055058a0，设备对象地址。
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：  从VfErrorBugcheckData提取的错误检查数据。
ADDITIONAL_DEBUG_TEXT: Bugcheck data extracted fron VfErrorBugcheckData.
OVERLAPPED_MODULE：'cdrom'和'cdrom.sys'重叠的地址区域
OVERLAPPED_MODULE: Address regions for 'cdrom' and 'cdrom.sys' overlap
BUGCHECK_STR： 0xc9_221
BUGCHECK_STR: 0xc9_221
DRIVER_VERIFIER_IO_VIOLATION_TYPE： 221
DRIVER_VERIFIER_IO_VIOLATION_TYPE: 221
FAULTING_IP：
volsnap！VolSnapPnp + 0
fffff880`01a8f710 48895c2408 ;   MOV     qword ptr [rsp + 8]，rbx
FAULTING_IP:
volsnap!VolSnapPnp+0
fffff880`01a8f710 48895c2408 mov qword ptr [rsp+8],rbx
起初我认为这可能与我的WFP标注驱动程序有关。然后我运行相同的测试并选择了wfplwf.sys。我遇到了同样的BSOD。
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.
我还重新创建/重新格式化了硬盘上的分区，但这没有帮助。硬盘有三个分区，一个是Win8，另一个是Win7。第三个分区不可启动，用于保存其他分区的备份数据。
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?
来自DV断言的完整堆栈跟踪如下：
The full stack trace from the DV assert follows:
*** ************************************************** **************************
$
* ;                        &NBSP ;                        &NBSP ;                  
*
*      检测错误分析                        &NBSP ;          
*
*                                                             
*
************************************* ******************************************
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
DRIVER_VERIFIER_IOMANAGER_VIOLATION（c9）
$
IO管理员遇到行为不端的司机。
参数：
Arg1：0000000000000221，一个IRP调度处理程序对于PDO已删除其设备对象，但在总线关系查询中尚未报告该
硬件。
Arg2：fffff88001a8f710，地址在检测到错误的驱动程序代码。
Arg3：fffff98038534af0，IRP地址。
Arg4：fffffa80055058a0，设备对象地址。
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：  从VfErrorBugcheckData提取的错误检查数据。
ADDITIONAL_DEBUG_TEXT: Bugcheck data extracted fron VfErrorBugcheckData.
OVERLAPPED_MODULE：'cdrom'和'cdrom.sys'重叠的地址区域
OVERLAPPED_MODULE: Address regions for 'cdrom' and 'cdrom.sys' overlap
BUGCHECK_STR： 0xc9_221
BUGCHECK_STR: 0xc9_221
DRIVER_VERIFIER_IO_VIOLATION_TYPE： 221
DRIVER_VERIFIER_IO_VIOLATION_TYPE: 221
FAULTING_IP：
volsnap！VolSnapPnp + 0
fffff880`01a8f710 48895c2408 MOV    个qword的ptr [RSP + 8]，RBX
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
FOLLOWUP_IP:
volsnap!VolSnapPnp+0
fffff880`01a8f710 48895c2408 mov qword ptr [rsp+8],rbx
IRP_ADDRESS： fffff98038534af0
IRP_ADDRESS: fffff98038534af0
DEFAULT_BUCKET_ID： WIN8_DRIVER_FAULT
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME： 系统
PROCESS_NAME: System
CURRENT_IRQL： 2
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER： 从fffff801876b9062到fffff801876bb86a
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`01 d29101：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 ：恩！ ?? :: NNGAKEGL ::'串'+ 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_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
STACK_COMMAND: .bugcheck ; kb
SYMBOL_NAME： volsnap！VolSnapPnp + 0
SYMBOL_NAME: volsnap!VolSnapPnp+0
FOLLOWUP_NAME： MachineOwner
FOLLOWUP_NAME: MachineOwner
MODULE_NAME：volsnap
MODULE_NAME: volsnap
IMAGE_NAME： volsnap.sys
IMAGE_NAME: volsnap.sys
DEBUG_FLR_IMAGE_TIMESTAMP： 5010abc2
DEBUG_FLR_IMAGE_TIMESTAMP: 5010abc2
BUCKET_ID_FUNC_OFFSET： 0
BUCKET_ID_FUNC_OFFSET: 0
FAILURE_BUCKET_ID： 0xc9_221_VRF_volsnap！VolSnapPnp
FAILURE_BUCKET_ID: 0xc9_221_VRF_volsnap!VolSnapPnp
BUCKET_ID： 0xc9_221_VRF_volsnap！VolSnapPnp
BUCKET_ID: 0xc9_221_VRF_volsnap!VolSnapPnp
跟进：MachineOwner
---------
Followup: MachineOwner
---------
推荐答案
由于Windows 8中存在已知错误，您会看到此问题。请参阅勘误表＃582并提交内存转储以解决此问题由我们的提交审核人手动放弃。
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.
请注意，勘误表＃582 仅适用于：
Note that errata #582 only applies when:
1）此特定错误检查（ DRIVER_VERIFIER_IOMANAGER_VIOLATION（c9） ） in
volsnap看到.sys ，
1) This particular bug check (DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)) in volsnap.sys is seen, and
2）睡眠和PNP（禁用和启用）IO前后（认证 - 软件设备）是失败的测试
谢谢
这篇关于睡眠期间的VolSnap.Sys中的BSOD和使用IO之前和之后的PNP（禁用和启用）（认证 - 软件设备）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
