usbver2k.sys

Hi,

I am currently doing HCT 11.1a testing for my USB device. When i execute
USB manual interoperability tests, usb verifier is loaded for every
connected device including my USB device. When USB verifier is loaded for
my device, the system crashes immediately with bug check
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) in usbver2k.sys. I have searched all
documentation about this driver usbver2k.sys in vain.

Basically, when the driver tries to submit URBs on the interrupt pipe
(IoCallDriver ()) this bug check occurs. If USB manual interoperability
test is not executed then there are no problems. Has anyone faced such a
problem before? Can somebody give ideas about what exactly is happenning?

Hari.

Windbg trace:

USB Verifier loaded on USB Video device

*** Fatal System Error: 0x000000d1
(0x0000005C,0x00000002,0x00000000,0xF082A973)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {5c, 2, 0, f082a973}

*** ERROR: Module load completed but symbols could not be loaded for
usbver2k.sys
Probably caused by : usbver2k.sys ( usbver2k+3973 )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
805103fa cc int 3
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pagable (or completely invalid) address at
an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000005c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f082a973, address which referenced memory

Debugging Details:

READ_ADDRESS: 0000005c

CURRENT_IRQL: 2

FAULTING_IP:
usbver2k+3973
f082a973 3b480c cmp ecx,[eax+0xc]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 805258ca to 805103fa

STACK_TEXT:
f0a612b0 805258ca 00000003 f0a615e0 0000005c
nt!RtlpBreakWithStatusInstruction
f0a612fc 80526160 00000003 0000005c f082a973 nt!KiBugCheckDebugBreak+0x19
f0a616c8 805266db 0000000a 0000005c 00000002 nt!KeBugCheck2+0x46d
f0a616e8 804dce53 0000000a 0000005c 00000002 nt!KeBugCheckEx+0x19
f0a616e8 f082a973 0000000a 0000005c 00000002 nt!KiTrap0E+0x2ad
WARNING: Stack unwind information not available. Following frames may be
wrong.
f0a6178c f08280fa 81715ab0 81140a84 8117b778 usbver2k+0x3973
f0a617a8 f0828a83 81715ab0 8119c460 815e3300 usbver2k+0x10fa
f0a617e8 f08279e7 817159f8 8119c460 00220003 usbver2k+0x1a83
f0a61814 804eca36 817159f8 8119c460 f0a6196c usbver2k+0x9e7
f0a61824 f06edadd 00000001 8119c584 81186980 nt!IopfCallDriver+0x31
f0a61844 f06f8b67 81186a40 8119c460 f0a618f0
videodev!SubmitInterruptUrb+0x169
f0a6191c 8056402b f06f8e34 f0a61948 811dbc38 nt!PiNotifyDriverCallback+0x6d
f0a6197c f06f58d2 00000002 00000001 e1300a98
nt!IoRegisterPlugPlayNotification+0x32a
f0a619fc f977571c 811dbc38 8108ebf8 00000000 videodev!DeviceStart+0x391
f0a61a24 f976fcad 8108ebf8 8108ed64 815f09e0 ks!CKsDevice::PnpStart+0x39
f0a61a38 804eca36 810fb3e8 8108ebf8 f0a61ab4 ks!CKsDevice::DispatchPnp+0x1b6
f0a61a48 8056b1ed f0a61ab4 8107e300 00000000 nt!IopfCallDriver+0x31
815f09e0 810fb3e8 00000010 f06ec000 00015a80 nt!IopSynchronousCall+0xb8
00a80004 00000000 00000000 00000000 00000000 0x810fb3e8

FOLLOWUP_IP:
usbver2k+3973
f082a973 3b480c cmp ecx,[eax+0xc]

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: usbver2k+3973

MODULE_NAME: usbver2k

IMAGE_NAME: usbver2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3dd1c55b

STACK_COMMAND: kb

BUCKET_ID: 0xD1_usbver2k+3973

Followup: MachineOwner


Beat the heat. Chill out in Himalayas.
http://server1.msn.co.in/sp03/summerfun/index.asp Mercury Rising contest.

Hallo,

Basically, when the driver tries to submit URBs on the interrupt pipe
(IoCallDriver ()) this bug check occurs. If USB manual interoperability
test is not executed then there are no problems. Has anyone faced such a
problem before? Can somebody give ideas about what exactly is happenning?

are your shure you have the rigth IRQL for your request ?
Your are using a IRP completion call ? or a blocked operation ? …
You cannot make sync calls at IRQL 0.

elli

I don’t believe that USBVER2K.SYS is a Microsoft driver. Since the driver verifier shows this driver attempted to deref NULL+5c, it’s almost definitely a driver bug. You should find the company which provided this driver, and report this as a bug.

Hth,
.

-----Original Message-----
From: Hari K [mailto:xxxxx@hotmail.com]
Sent: Monday, May 19, 2003 9:12 PM
Subject: usbver2k.sys

Hi,

I am currently doing HCT 11.1a testing for my USB device. When i execute
USB manual interoperability tests, usb verifier is loaded for every
connected device including my USB device. When USB verifier is loaded for
my device, the system crashes immediately with bug check
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) in usbver2k.sys. I have searched all
documentation about this driver usbver2k.sys in vain.

Basically, when the driver tries to submit URBs on the interrupt pipe
(IoCallDriver ()) this bug check occurs. If USB manual interoperability
test is not executed then there are no problems. Has anyone faced such a
problem before? Can somebody give ideas about what exactly is happenning?

Hari.

Windbg trace:

USB Verifier loaded on USB Video device

*** Fatal System Error: 0x000000d1
(0x0000005C,0x00000002,0x00000000,0xF082A973)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {5c, 2, 0, f082a973}

*** ERROR: Module load completed but symbols could not be loaded for
usbver2k.sys
Probably caused by : usbver2k.sys ( usbver2k+3973 )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
805103fa cc int 3
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pagable (or completely invalid) address at
an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000005c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f082a973, address which referenced memory

Debugging Details:

READ_ADDRESS: 0000005c

CURRENT_IRQL: 2

FAULTING_IP:
usbver2k+3973
f082a973 3b480c cmp ecx,[eax+0xc]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 805258ca to 805103fa

STACK_TEXT:
f0a612b0 805258ca 00000003 f0a615e0 0000005c
nt!RtlpBreakWithStatusInstruction
f0a612fc 80526160 00000003 0000005c f082a973 nt!KiBugCheckDebugBreak+0x19
f0a616c8 805266db 0000000a 0000005c 00000002 nt!KeBugCheck2+0x46d
f0a616e8 804dce53 0000000a 0000005c 00000002 nt!KeBugCheckEx+0x19
f0a616e8 f082a973 0000000a 0000005c 00000002 nt!KiTrap0E+0x2ad
WARNING: Stack unwind information not available. Following frames may be
wrong.
f0a6178c f08280fa 81715ab0 81140a84 8117b778 usbver2k+0x3973
f0a617a8 f0828a83 81715ab0 8119c460 815e3300 usbver2k+0x10fa
f0a617e8 f08279e7 817159f8 8119c460 00220003 usbver2k+0x1a83
f0a61814 804eca36 817159f8 8119c460 f0a6196c usbver2k+0x9e7
f0a61824 f06edadd 00000001 8119c584 81186980 nt!IopfCallDriver+0x31
f0a61844 f06f8b67 81186a40 8119c460 f0a618f0
videodev!SubmitInterruptUrb+0x169
f0a6191c 8056402b f06f8e34 f0a61948 811dbc38 nt!PiNotifyDriverCallback+0x6d
f0a6197c f06f58d2 00000002 00000001 e1300a98
nt!IoRegisterPlugPlayNotification+0x32a
f0a619fc f977571c 811dbc38 8108ebf8 00000000 videodev!DeviceStart+0x391
f0a61a24 f976fcad 8108ebf8 8108ed64 815f09e0 ks!CKsDevice::PnpStart+0x39
f0a61a38 804eca36 810fb3e8 8108ebf8 f0a61ab4 ks!CKsDevice::DispatchPnp+0x1b6
f0a61a48 8056b1ed f0a61ab4 8107e300 00000000 nt!IopfCallDriver+0x31
815f09e0 810fb3e8 00000010 f06ec000 00015a80 nt!IopSynchronousCall+0xb8
00a80004 00000000 00000000 00000000 00000000 0x810fb3e8

FOLLOWUP_IP:
usbver2k+3973
f082a973 3b480c cmp ecx,[eax+0xc]

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: usbver2k+3973

MODULE_NAME: usbver2k

IMAGE_NAME: usbver2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3dd1c55b

STACK_COMMAND: kb

BUCKET_ID: 0xD1_usbver2k+3973

Followup: MachineOwner


Beat the heat. Chill out in Himalayas.
http://server1.msn.co.in/sp03/summerfun/index.asp Mercury Rising contest.

actually, usbver2k.sys is a Microsoft driver; in fact I believe it’s the USB
driver verifier driver (you can tell for sure by looking at the file version
properties when the system is running again).

The stack you included in your original looks highly bogus to me - are you
sure you are using the right symbols? Are you setup to use the Microsoft
symbol server? If not, do so and post the stack again… you might even find
symbols for this driver…

/simgr

-----Original Message-----
From: Henry Gabryjelski [mailto:xxxxx@windows.microsoft.com]
Sent: Thursday, May 22, 2003 11:55 AM
To: NT Developers Interest List

I don’t believe that USBVER2K.SYS is a Microsoft driver. Since the driver
verifier shows this driver attempted to deref NULL+5c, it’s almost
definitely a driver bug. You should find the company which provided this
driver, and report this as a bug.

Hth,
.

-----Original Message-----
From: Hari K [mailto:xxxxx@hotmail.com]
Sent: Monday, May 19, 2003 9:12 PM
Subject: usbver2k.sys

Hi,

I am currently doing HCT 11.1a testing for my USB device. When i execute
USB manual interoperability tests, usb verifier is loaded for every
connected device including my USB device. When USB verifier is loaded for
my device, the system crashes immediately with bug check
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) in usbver2k.sys. I have searched all
documentation about this driver usbver2k.sys in vain.

Basically, when the driver tries to submit URBs on the interrupt pipe
(IoCallDriver ()) this bug check occurs. If USB manual interoperability
test is not executed then there are no problems. Has anyone faced such a
problem before? Can somebody give ideas about what exactly is happenning?

Hari.

Windbg trace:

USB Verifier loaded on USB Video device

*** Fatal System Error: 0x000000d1
(0x0000005C,0x00000002,0x00000000,0xF082A973)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

****************************************************************************
***
*

*
* Bugcheck Analysis

*
*

*
****************************************************************************
***

Use !analyze -v to get detailed debugging information.

BugCheck D1, {5c, 2, 0, f082a973}

*** ERROR: Module load completed but symbols could not be loaded for
usbver2k.sys
Probably caused by : usbver2k.sys ( usbver2k+3973 )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
805103fa cc int 3
kd> !analyze -v
****************************************************************************
***
*

*
* Bugcheck Analysis

*
*

*
****************************************************************************
***

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pagable (or completely invalid) address at
an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000005c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f082a973, address which referenced memory

Debugging Details:

READ_ADDRESS: 0000005c

CURRENT_IRQL: 2

FAULTING_IP:
usbver2k+3973
f082a973 3b480c cmp ecx,[eax+0xc]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 805258ca to 805103fa

STACK_TEXT:
f0a612b0 805258ca 00000003 f0a615e0 0000005c
nt!RtlpBreakWithStatusInstruction
f0a612fc 80526160 00000003 0000005c f082a973 nt!KiBugCheckDebugBreak+0x19
f0a616c8 805266db 0000000a 0000005c 00000002 nt!KeBugCheck2+0x46d
f0a616e8 804dce53 0000000a 0000005c 00000002 nt!KeBugCheckEx+0x19
f0a616e8 f082a973 0000000a 0000005c 00000002 nt!KiTrap0E+0x2ad
WARNING: Stack unwind information not available. Following frames may be
wrong.
f0a6178c f08280fa 81715ab0 81140a84 8117b778 usbver2k+0x3973
f0a617a8 f0828a83 81715ab0 8119c460 815e3300 usbver2k+0x10fa
f0a617e8 f08279e7 817159f8 8119c460 00220003 usbver2k+0x1a83
f0a61814 804eca36 817159f8 8119c460 f0a6196c usbver2k+0x9e7
f0a61824 f06edadd 00000001 8119c584 81186980 nt!IopfCallDriver+0x31
f0a61844 f06f8b67 81186a40 8119c460 f0a618f0
videodev!SubmitInterruptUrb+0x169
f0a6191c 8056402b f06f8e34 f0a61948 811dbc38 nt!PiNotifyDriverCallback+0x6d
f0a6197c f06f58d2 00000002 00000001 e1300a98
nt!IoRegisterPlugPlayNotification+0x32a
f0a619fc f977571c 811dbc38 8108ebf8 00000000 videodev!DeviceStart+0x391
f0a61a24 f976fcad 8108ebf8 8108ed64 815f09e0 ks!CKsDevice::PnpStart+0x39
f0a61a38 804eca36 810fb3e8 8108ebf8 f0a61ab4 ks!CKsDevice::DispatchPnp+0x1b6
f0a61a48 8056b1ed f0a61ab4 8107e300 00000000 nt!IopfCallDriver+0x31
815f09e0 810fb3e8 00000010 f06ec000 00015a80 nt!IopSynchronousCall+0xb8
00a80004 00000000 00000000 00000000 00000000 0x810fb3e8

FOLLOWUP_IP:
usbver2k+3973
f082a973 3b480c cmp ecx,[eax+0xc]

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: usbver2k+3973

MODULE_NAME: usbver2k

IMAGE_NAME: usbver2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3dd1c55b

STACK_COMMAND: kb

BUCKET_ID: 0xD1_usbver2k+3973

Followup: MachineOwner


Beat the heat. Chill out in Himalayas.
http://server1.msn.co.in/sp03/summerfun/index.asp Mercury Rising contest.


You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com