“DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 00000004, Invalid Device object passed to IoCallDriver
Arg2: 81d710d0, the Device object , 3/4 - 0
Arg3: 00000000
Arg4: 00000000”
My file system filter driver works properly without verifier.
However, if I verify my driver using “Windows Verifier”, it got crashed.
Whenever it calls IoCallDriver, verifier complains that the device to be passed is invalid.
As following.
"
kd> !devobj ffffffff81d710d0 f
Device object (81d710d0) is for:
\FileSystem\sr DriverObject 81e9d5b8
Current Irp 00000000 RefCount -1 Type 00000008 Flags 00000000
DevExt 81d71188 DevObjExt 81d712d0
ExtensionFlags (0xc0000000) DOE_BOTTOM_OF_FDO_STACK, DOE_DESIGNATED_FDO
AttachedDevice (Upper) 81bb1a98 \Driver\swmsio
AttachedTo (Lower) 81db6020 \FileSystem\Ntfs
Device queue is not busy."
Why this device got invalid?
Thx in advance.
“God is Love!”
RefCount is -1 which is wrong…
-pk
wrote in message news:xxxxx@ntfsd…
> “DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
> The IO manager has caught a misbehaving driver.
> Arguments:
> Arg1: 00000004, Invalid Device object passed to IoCallDriver
> Arg2: 81d710d0, the Device object , 3/4 - 0
> Arg3: 00000000
> Arg4: 00000000”
>
> My file system filter driver works properly without verifier.
> However, if I verify my driver using “Windows Verifier”, it got crashed.
> Whenever it calls IoCallDriver, verifier complains that the device to be
> passed is invalid.
>
> As following.
> “
> kd> !devobj ffffffff81d710d0 f
> Device object (81d710d0) is for:
> \FileSystem\sr DriverObject 81e9d5b8
> Current Irp 00000000 RefCount -1 Type 00000008 Flags 00000000
> DevExt 81d71188 DevObjExt 81d712d0
> ExtensionFlags (0xc0000000) DOE_BOTTOM_OF_FDO_STACK, DOE_DESIGNATED_FDO
> AttachedDevice (Upper) 81bb1a98 \Driver\swmsio
> AttachedTo (Lower) 81db6020 \FileSystem\Ntfs
> Device queue is not busy.”
>
> Why this device got invalid?
> Thx in advance.
>
> —
> “God is Love!”
>
>
>