Prev: MSVAD buffer size problem.
Next: Application can not receive WM_DEVICECHANGE
From: Owen Smith on 11 Jan 2008 07:16
Hi,

I'm writing a HID filter using KMDF (1.5) and get a BSOD with the PnPDTest
ReBalance resources test under driver verifier on XP. The problem is not
present on Vista.

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 00000006, IRP passed to IoCompleteRequest contains invalid status
Arg2: 00000103, the status
Arg3: 89f44d98, the IRP
Arg4: 00000000, 0

I have run the rebalance test without my driver and no problems are found.
I have stripped my driver back to bear minimum (just calling
WdfFdoInitSetFilter, WdfDeviceInitSetDeviceType and WdfDeviceCreate, not
even adding any IO queues) and the problem still occurs.
I have tried replacing my driver with the firefly sample driver, and the
problem still occurs.

Any suggestions to debugging this problem?


Owen


--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
From: Eliyas Yakub [MSFT] on 11 Jan 2008 10:13
The crash says that the IRP is being completed with STATUS_PENDING as the
completion status. The stack trace should show who completed the IRP.

-Eliyas

"Owen Smith" <nospam.osmith(a)saitek.com.nospam> wrote in message
news:op.t4rlp3sg39p9aw(a)oas-core2...
> Hi,
>
> I'm writing a HID filter using KMDF (1.5) and get a BSOD with the PnPDTest
> ReBalance resources test under driver verifier on XP. The problem is not
> present on Vista.
>
> DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
> The IO manager has caught a misbehaving driver.
> Arguments:
> Arg1: 00000006, IRP passed to IoCompleteRequest contains invalid status
> Arg2: 00000103, the status
> Arg3: 89f44d98, the IRP
> Arg4: 00000000, 0
>
> I have run the rebalance test without my driver and no problems are found.
> I have stripped my driver back to bear minimum (just calling
> WdfFdoInitSetFilter, WdfDeviceInitSetDeviceType and WdfDeviceCreate, not
> even adding any IO queues) and the problem still occurs.
> I have tried replacing my driver with the firefly sample driver, and the
> problem still occurs.
>
> Any suggestions to debugging this problem?
>
>
> Owen
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From: Maxim S. Shatskih on 11 Jan 2008 13:51
> Arg1: 00000006, IRP passed to IoCompleteRequest contains invalid status
> Arg2: 00000103, the status

== STATUS_PENDING

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim(a)storagecraft.com
http://www.storagecraft.com

From: Doron Holan [MSFT] on 11 Jan 2008 19:12
please send the entire output of !analyze -v

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Owen Smith" <nospam.osmith(a)saitek.com.nospam> wrote in message
news:op.t4rlp3sg39p9aw(a)oas-core2...
> Hi,
>
> I'm writing a HID filter using KMDF (1.5) and get a BSOD with the PnPDTest
> ReBalance resources test under driver verifier on XP. The problem is not
> present on Vista.
>
> DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
> The IO manager has caught a misbehaving driver.
> Arguments:
> Arg1: 00000006, IRP passed to IoCompleteRequest contains invalid status
> Arg2: 00000103, the status
> Arg3: 89f44d98, the IRP
> Arg4: 00000000, 0
>
> I have run the rebalance test without my driver and no problems are found.
> I have stripped my driver back to bear minimum (just calling
> WdfFdoInitSetFilter, WdfDeviceInitSetDeviceType and WdfDeviceCreate, not
> even adding any IO queues) and the problem still occurs.
> I have tried replacing my driver with the firefly sample driver, and the
> problem still occurs.
>
> Any suggestions to debugging this problem?
>
>
> Owen
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From: Owen Smith on 14 Jan 2008 06:09

1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 00000006, IRP passed to IoCompleteRequest contains invalid status
Arg2: 00000103, the status
Arg3: 89e5ed50, the IRP
Arg4: 00000000, 0

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*** No owner thread found for resource 8055a4e0
*** No owner thread found for resource 8055a4e0
*** No owner thread found for resource 8055a4e0
*** No owner thread found for resource 8055a4e0

BUGCHECK_STR: 0xc9_6

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 6

IRP_ADDRESS: 89e5ed50

DEVICE_OBJECT: 89a93ca8

DRIVER_OBJECT: 897b43c8

IMAGE_NAME: mouhid.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7d82fd

MODULE_NAME: mouhid

FAULTING_MODULE: b6170000 mouhid

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LOCK_ADDRESS: 8055a560 -- (!locks 8055a560)

Resource @ nt!IopDeviceTreeLock (0x8055a560) Shared 1 owning threads
Threads: 89bb2020-01<*>
1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0x8055a560
Thread Count : 1
Thread address: 0x89bb2020
Thread wait : 0x4bf8

LAST_CONTROL_TRANSFER: from 804f8cb1 to 8052a834

STACK_TEXT:
bad03378 804f8cb1 00000003 bad036d4 00000000
nt!RtlpBreakWithStatusInstruction
bad033c4 804f989c 00000003 00000000 89a93d60 nt!KiBugCheckDebugBreak+0x19
bad037a4 804f9deb 000000c9 00000006 00000103 nt!KeBugCheck2+0x574
bad037c4 8065685c 000000c9 00000006 00000103 nt!KeBugCheckEx+0x1b
bad03840 b6171b52 89a93ca8 897b43c8 89817800 nt!IovCompleteRequest+0x13e
bad03860 804ef095 89a93ca8 00000000 806e4428 mouhid!MouHid_PnP+0x1c3
bad03870 80656128 89e5ef8c 89e5efb0 898178e0 nt!IopfCallDriver+0x31
bad03894 80660c0b 898178e0 89b2d520 89e5ed00 nt!IovCallDriver+0xa0
bad038a8 804ef095 89a93ca8 89e5ed50 806e4428 nt!ViDriverDispatchPnp+0xd7
bad038b8 80656128 898e1548 804f7d4e 89e5ed50 nt!IopfCallDriver+0x31
bad038dc baca239f 898e1548 898e1548 89e5efb8 nt!IovCallDriver+0xa0
WARNING: Stack unwind information not available. Following frames may be
wrong.
bad03918 baca2611 898e1548 00000000 89e5ed50 pnpfiltr+0x239f
bad03940 baca2549 898e1490 89e5ed50 898e1490 pnpfiltr+0x2611
bad03958 804ef095 898e1490 89e5ed50 806e4428 pnpfiltr+0x2549
bad03968 80656128 89e5efdc 00000000 89e5ed50 nt!IopfCallDriver+0x31
bad0398c babba541 89e5ed50 8992ff00 ff04ff01 nt!IovCallDriver+0xa0
bad039ac babb9777 898e1490 89e5ed50 00000001
mouclass!MouseSendIrpSynchronously+0x59
bad03a18 804ef095 8992fe48 89e5ed50 806e4428 mouclass!MousePnP+0x229
bad03a28 80656128 89e5f000 bad03ab8 89e5ed50 nt!IopfCallDriver+0x31
bad03a4c 805918d3 bad03ab8 89a48180 89a2bad8 nt!IovCallDriver+0xa0
bad03a78 80591951 8992fe48 bad03a94 00000000 nt!IopSynchronousCall+0xb7
bad03abc 804f61b4 89a48180 00000001 bad03d24 nt!IopStartDevice+0x4d
bad03acc 805910e7 89a2bad8 bad03d00 89b284c8
nt!PipProcessRestartPhase1+0x14
bad03d24 8059140b 89bd8dd8 00000001 00000000 nt!PipProcessDevNodeTree+0x2b7
bad03d54 804f6837 00000003 8055a5c0 8056375c
nt!PiProcessResourceRequirementsChanged+0x89
bad03d7c 805379bd 00000000 00000000 89bb2020 nt!PipDeviceActionWorker+0x12f
bad03dac 805ce84c 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
bad03ddc 8054532e 805378ce 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
mouhid!MouHid_PnP+1c3
b6171b52 eb2e jmp mouhid!MouHid_PnP+0x1f3 (b6171b82)

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: mouhid!MouHid_PnP+1c3

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xc9_6_VRF_mouhid!MouHid_PnP+1c3

BUCKET_ID: 0xc9_6_VRF_mouhid!MouHid_PnP+1c3

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


1: kd> !irp 89e5ed50
Irp is active with 16 stacks 13 is current (= 0x89e5ef70)
No Mdl: No System Buffer: Thread 89bb2020: Irp stack trace. Pending has
been returned
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 10 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[ 1b, 0] 0 10 89a48180 00000000 80660a56-00000000
\Driver\HidUsb nt!ViDriverStartCompletionRoutine
Args: 00000000 00000000 00000000 00000000
[ 1b, 0] 0 10 89b225a8 00000000 b611afb3-89a1e9f0

\DRIVER\VERIFIER Wdf01000!FxPkgFdo::_PnpStartDeviceCompletionRoutine
Args: 00000000 00000000 00000000 00000000
[ 1b, 0] 0 10 89b24738 00000000 80660a56-00000000
*** ERROR: Module load completed but symbols could not be loaded
for SaiK0CEA.sys
\Driver\SaiK0CEA nt!ViDriverStartCompletionRoutine
Args: 00000000 00000000 00000000 00000000
[ 1b, 0] 0 10 89ab9480 00000000 b617075a-89a93d60
\DRIVER\VERIFIER mouhid!MouHid_PnPComplete
Args: 00000000 00000000 00000000 00000000
> [ 1b, 0] 0 e1 89a93ca8 00000000 80660a56-00000000 Success Error Cancel
> pending
\Driver\mouhid nt!ViDriverStartCompletionRoutine
Args: 00000000 00000000 00000000 00000000
[ 1b, 0] 0 e0 898178e0 00000000 baca05c4-bad038f0 Success Error Cancel
\DRIVER\VERIFIER pnpfiltr
Args: 00000000 00000000 00000000 00000000
[ 1b, 0] 0 e0 898e1490 00000000 babb836e-bad0399c Success Error Cancel
\Driver\pnpstress mouclass!MouSyncComplete
Args: 00000000 00000000 00000000 00000000
[ 1b, 0] 0 0 8992fe48 00000000 00000000-00000000
\Driver\Mouclass
Args: e253f9d0 e25c0290 00000000 00000000



On Sat, 12 Jan 2008 00:12:34 -0000, Doron Holan [MSFT]
<doronh(a)online.microsoft.com> wrote:

> please send the entire output of !analyze -v
>
> d
>



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
 |  Next  |  Last
Pages: 1 2
Prev: MSVAD buffer size problem.
Next: Application can not receive WM_DEVICECHANGE