unknown bugcheck un USBHACI.sys..

NTDEV
1

Hi alll,

i am using a filter driver for USB class Devices and whenever it works very fine but when i format USB drive then after 99% of completion i m getting a bugcheck.

i m sure that it is just because of my driver but stack trace did’nt show any sign of my driver.

my driver name is Filter.sys.

i will be grateful if u guys put some light on this scenario.

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 0, f866a509}

*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : usbuhci.sys ( usbuhci!UhciAbortAsyncTransfer+4f )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
804eab25 cc int 3
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (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: 00000008, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f866a509, address which referenced memory

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 ***
*** ***
*************************************************************************

READ_ADDRESS: 00000008

CURRENT_IRQL: 2

FAULTING_IP:
usbuhci!UhciAbortAsyncTransfer+4f
f866a509 8b4e08 mov ecx,dword ptr [esi+8]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: f8876be8 – (.trap 0xfffffffff8876be8)
ErrCode = 00000000
eax=00000000 ebx=10000001 ecx=819b56e0 edx=00000004 esi=00000000 edi=81987d60
eip=f866a509 esp=f8876c5c ebp=f8876c74 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
usbuhci!UhciAbortAsyncTransfer+0x4f:
f866a509 8b4e08 mov ecx,dword ptr [esi+8] ds:0023:00000008=???
Resetting default scope

LAST_CONTROL_TRANSFER: from 805398e7 to 804eab25

STACK_TEXT:
f887679c 805398e7 00000003 f8876af8 00000000 nt!RtlpBreakWithStatusInstruction
f88767e8 8053a3be 00000003 00000008 f866a509 nt!KiBugCheckDebugBreak+0x19
f8876bc8 804e9158 0000000a 00000008 00000002 nt!KeBugCheck2+0x574
f8876bc8 f866a509 0000000a 00000008 00000002 nt!KiTrap0E+0x233
f8876c74 f86681fb 819b99dc 81987d60 81a96288 usbuhci!UhciAbortAsyncTransfer+0x4f
f8876c98 bad0a29b 819b99dc 81987d60 81a96288 usbuhci!UhciAbortTransfer+0x3d
f8876ce4 bad0a563 819b9028 81987be8 804ea579 USBPORT!USBPORT_DmaEndpointPaused+0x263
f8876d10 bad0c98c 819b9028 804ea579 81987be8 USBPORT!USBPORT_DmaEndpointWorker+0x149
f8876d38 bad1041a 819b9028 00000002 819b9028 USBPORT!USBPORT_CoreEndpointWorker+0x6d2
f8876d7c bad08fc0 819b9028 00000000 819dd948 USBPORT!USBPORT_Worker+0x212
f8876dac 80584fed 819b9028 00000000 00000000 USBPORT!USBPORT_WorkerThread+0x12a
f8876ddc 80501477 bad08e96 819b9028 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
usbuhci!UhciAbortAsyncTransfer+4f
f866a509 8b4e08 mov ecx,dword ptr [esi+8]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: usbuhci!UhciAbortAsyncTransfer+4f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbuhci

IMAGE_NAME: usbuhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

FAILURE_BUCKET_ID: 0xD1_VRF_usbuhci!UhciAbortAsyncTransfer+4f

BUCKET_ID: 0xD1_VRF_usbuhci!UhciAbortAsyncTransfer+4f

Followup: MachineOwner

kd> .trap 0xfffffffff8876be8
ErrCode = 00000000
eax=00000000 ebx=10000001 ecx=819b56e0 edx=00000004 esi=00000000 edi=81987d60
eip=f866a509 esp=f8876c5c ebp=f8876c74 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
usbuhci!UhciAbortAsyncTransfer+0x4f:
f866a509 8b4e08 mov ecx,dword ptr [esi+8] ds:0023:00000008=???
kd> lmvm usbuhci
start end module name
f8667000 f866c000 usbuhci (pdb symbols) C:\WINDOWS\Symbolsxp\sys\usbuhci.pdb
Loaded symbol image file: usbuhci.sys
Image path: \SystemRoot\system32\DRIVERS\usbuhci.sys
Image name: usbuhci.sys
Timestamp: Wed Aug 04 11:38:34 2004 (41107D62)
CheckSum: 00013083
ImageSize: 00005000
File version: 5.1.2600.2180
Product version: 5.1.2600.2180
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft? Windows? Operating System
InternalName: USBUHCI.sys
OriginalFilename: USBUHCI.sys
ProductVersion: 5.1.2600.2180
FileVersion: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
FileDescription: UHCI USB Miniport Driver
LegalCopyright: ? Microsoft Corporation. All rights reserved.

2

Your driver isn’t at stack trace because bugcheck occured in usbport worker thread. That’s normal. Use !process 0 7 to see all threads in the system and there can be your driver somewhere. BTW, filter.sys is not very well chosen name.

One of possible causes is that you filter driver destroyed an URB which wasn’t completed, yet. As you can see, usbuhci tried to abort transfer in progress (probably) and accessed NULL pointer. It could be an OS bug as well but it is more probable your filter did something wrong.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Saturday, April 18, 2009 9:01 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] unknown bugcheck un USBHACI.sys…

Hi alll,

i am using a filter driver for USB class Devices and whenever
it works very fine but when i format USB drive then after 99%
of completion i m getting a bugcheck.

i m sure that it is just because of my driver but stack trace
did’nt show any sign of my driver.

my driver name is Filter.sys.

i will be grateful if u guys put some light on this scenario.

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 0, f866a509}

**************************************************************
***********
***
***
***
***
*** 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
***
***
***
**************************************************************
***********
Probably caused by : usbuhci.sys ( usbuhci!UhciAbortAsyncTransfer+4f )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
804eab25 cc int 3
kd> !analyze -v
**************************************************************
*****************
*
*
* Bugcheck Analysis
*
*
*
**************************************************************
*****************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (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: 00000008, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f866a509, address which referenced memory

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
***
***
***
**************************************************************
***********

READ_ADDRESS: 00000008

CURRENT_IRQL: 2

FAULTING_IP:
usbuhci!UhciAbortAsyncTransfer+4f
f866a509 8b4e08 mov ecx,dword ptr [esi+8]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: f8876be8 – (.trap 0xfffffffff8876be8)
ErrCode = 00000000
eax=00000000 ebx=10000001 ecx=819b56e0 edx=00000004
esi=00000000 edi=81987d60
eip=f866a509 esp=f8876c5c ebp=f8876c74 iopl=0 nv up
ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010246
usbuhci!UhciAbortAsyncTransfer+0x4f:
f866a509 8b4e08 mov ecx,dword ptr [esi+8]
ds:0023:00000008=???
Resetting default scope

LAST_CONTROL_TRANSFER: from 805398e7 to 804eab25

STACK_TEXT:
f887679c 805398e7 00000003 f8876af8 00000000
nt!RtlpBreakWithStatusInstruction
f88767e8 8053a3be 00000003 00000008 f866a509
nt!KiBugCheckDebugBreak+0x19
f8876bc8 804e9158 0000000a 00000008 00000002 nt!KeBugCheck2+0x574
f8876bc8 f866a509 0000000a 00000008 00000002 nt!KiTrap0E+0x233
f8876c74 f86681fb 819b99dc 81987d60 81a96288
usbuhci!UhciAbortAsyncTransfer+0x4f
f8876c98 bad0a29b 819b99dc 81987d60 81a96288
usbuhci!UhciAbortTransfer+0x3d
f8876ce4 bad0a563 819b9028 81987be8 804ea579
USBPORT!USBPORT_DmaEndpointPaused+0x263
f8876d10 bad0c98c 819b9028 804ea579 81987be8
USBPORT!USBPORT_DmaEndpointWorker+0x149
f8876d38 bad1041a 819b9028 00000002 819b9028
USBPORT!USBPORT_CoreEndpointWorker+0x6d2
f8876d7c bad08fc0 819b9028 00000000 819dd948
USBPORT!USBPORT_Worker+0x212
f8876dac 80584fed 819b9028 00000000 00000000
USBPORT!USBPORT_WorkerThread+0x12a
f8876ddc 80501477 bad08e96 819b9028 00000000
nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
usbuhci!UhciAbortAsyncTransfer+4f
f866a509 8b4e08 mov ecx,dword ptr [esi+8]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: usbuhci!UhciAbortAsyncTransfer+4f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbuhci

IMAGE_NAME: usbuhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

FAILURE_BUCKET_ID: 0xD1_VRF_usbuhci!UhciAbortAsyncTransfer+4f

BUCKET_ID: 0xD1_VRF_usbuhci!UhciAbortAsyncTransfer+4f

Followup: MachineOwner

kd> .trap 0xfffffffff8876be8
ErrCode = 00000000
eax=00000000 ebx=10000001 ecx=819b56e0 edx=00000004
esi=00000000 edi=81987d60
eip=f866a509 esp=f8876c5c ebp=f8876c74 iopl=0 nv up
ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010246
usbuhci!UhciAbortAsyncTransfer+0x4f:
f866a509 8b4e08 mov ecx,dword ptr [esi+8]
ds:0023:00000008=???
kd> lmvm usbuhci
start end module name
f8667000 f866c000 usbuhci (pdb symbols)
C:\WINDOWS\Symbolsxp\sys\usbuhci.pdb
Loaded symbol image file: usbuhci.sys
Image path: \SystemRoot\system32\DRIVERS\usbuhci.sys
Image name: usbuhci.sys
Timestamp: Wed Aug 04 11:38:34 2004 (41107D62)
CheckSum: 00013083
ImageSize: 00005000
File version: 5.1.2600.2180
Product version: 5.1.2600.2180
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft? Windows? Operating System
InternalName: USBUHCI.sys
OriginalFilename: USBUHCI.sys
ProductVersion: 5.1.2600.2180
FileVersion: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
FileDescription: UHCI USB Miniport Driver
LegalCopyright: ? Microsoft Corporation. All rights reserved.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online
at http://www.osronline.com/page.cfm?name=ListServer

3

Have you tried this with verifier enabled for the stack?

Mark Roddy

On Sat, Apr 18, 2009 at 3:01 AM, wrote:
> Hi alll,
>
> i am using a filter driver for USB class Devices and whenever it works very fine but when i format USB drive then after 99% of completion i m getting a bugcheck.
>
> i m sure that it is just because of my driver but stack trace did’nt show any sign of my driver.
>
> my driver name is Filter.sys.
>
> i will be grateful if u guys put some light on this scenario.
>
>
>
>
>
>
>
>
>
> *
> * ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
> * ? ? ? ? ? ? ? ? ? ? ? ?Bugcheck Analysis ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
> * ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
>
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck D1, {8, 2, 0, f866a509}
>
>
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
>? ?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 ? ? ? ? ? ? ? ? ?
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
>
> Probably caused by : usbuhci.sys ( usbuhci!UhciAbortAsyncTransfer+4f )
>
> Followup: MachineOwner
> ---------
>
> nt!RtlpBreakWithStatusInstruction:
> 804eab25 cc ? ? ? ? ? ? ?int ? ? 3
> kd> !analyze -v
> *
> * ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
> * ? ? ? ? ? ? ? ? ? ? ? ?Bugcheck Analysis ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
> * ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
>
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
> An attempt was made to access a pageable (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: 00000008, memory referenced
> Arg2: 00000002, IRQL
> Arg3: 00000000, value 0 = read operation, 1 = write operation
> Arg4: f866a509, address which referenced memory
>
> 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 ? ? ? ? ? ? ? ? ?
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
>
>
> READ_ADDRESS: ?00000008
>
> CURRENT_IRQL: ?2
>
> FAULTING_IP:
> usbuhci!UhciAbortAsyncTransfer+4f
> f866a509 8b4e08 ? ? ? ? ?mov ? ? ecx,dword ptr [esi+8]
>
> DEFAULT_BUCKET_ID: ?DRIVER_FAULT
>
> BUGCHECK_STR: ?0xD1
>
> PROCESS_NAME: ?System
>
> TRAP_FRAME: ?f8876be8 – (.trap 0xfffffffff8876be8)
> ErrCode = 00000000
> eax=00000000 ebx=10000001 ecx=819b56e0 edx=00000004 esi=00000000 edi=81987d60
> eip=f866a509 esp=f8876c5c ebp=f8876c74 iopl=0 ? ? ? ? nv up ei pl zr na pe nc
> cs=0008 ?ss=0010 ?ds=0023 ?es=0023 ?fs=0030 ?gs=0000 ? ? ? ? ? ? efl=00010246
> usbuhci!UhciAbortAsyncTransfer+0x4f:
> f866a509 8b4e08 ? ? ? ? ?mov ? ? ecx,dword ptr [esi+8] ds:0023:00000008=???
> Resetting default scope
>
> LAST_CONTROL_TRANSFER: ?from 805398e7 to 804eab25
>
> STACK_TEXT:
> f887679c 805398e7 00000003 f8876af8 00000000 nt!RtlpBreakWithStatusInstruction
> f88767e8 8053a3be 00000003 00000008 f866a509 nt!KiBugCheckDebugBreak+0x19
> f8876bc8 804e9158 0000000a 00000008 00000002 nt!KeBugCheck2+0x574
> f8876bc8 f866a509 0000000a 00000008 00000002 nt!KiTrap0E+0x233
> f8876c74 f86681fb 819b99dc 81987d60 81a96288 usbuhci!UhciAbortAsyncTransfer+0x4f
> f8876c98 bad0a29b 819b99dc 81987d60 81a96288 usbuhci!UhciAbortTransfer+0x3d
> f8876ce4 bad0a563 819b9028 81987be8 804ea579 USBPORT!USBPORT_DmaEndpointPaused+0x263
> f8876d10 bad0c98c 819b9028 804ea579 81987be8 USBPORT!USBPORT_DmaEndpointWorker+0x149
> f8876d38 bad1041a 819b9028 00000002 819b9028 USBPORT!USBPORT_CoreEndpointWorker+0x6d2
> f8876d7c bad08fc0 819b9028 00000000 819dd948 USBPORT!USBPORT_Worker+0x212
> f8876dac 80584fed 819b9028 00000000 00000000 USBPORT!USBPORT_WorkerThread+0x12a
> f8876ddc 80501477 bad08e96 819b9028 00000000 nt!PspSystemThreadStartup+0x34
> 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
>
>
> STACK_COMMAND: ?kb
>
> FOLLOWUP_IP:
> usbuhci!UhciAbortAsyncTransfer+4f
> f866a509 8b4e08 ? ? ? ? ?mov ? ? ecx,dword ptr [esi+8]
>
> SYMBOL_STACK_INDEX: ?4
>
> SYMBOL_NAME: ?usbuhci!UhciAbortAsyncTransfer+4f
>
> FOLLOWUP_NAME: ?MachineOwner
>
> MODULE_NAME: usbuhci
>
> IMAGE_NAME: ?usbuhci.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: ?41107d62
>
> FAILURE_BUCKET_ID: ?0xD1_VRF_usbuhci!UhciAbortAsyncTransfer+4f
>
> BUCKET_ID: ?0xD1_VRF_usbuhci!UhciAbortAsyncTransfer+4f
>
> Followup: MachineOwner
> ---------
>
> kd> .trap 0xfffffffff8876be8
> ErrCode = 00000000
> eax=00000000 ebx=10000001 ecx=819b56e0 edx=00000004 esi=00000000 edi=81987d60
> eip=f866a509 esp=f8876c5c ebp=f8876c74 iopl=0 ? ? ? ? nv up ei pl zr na pe nc
> cs=0008 ?ss=0010 ?ds=0023 ?es=0023 ?fs=0030 ?gs=0000 ? ? ? ? ? ? efl=00010246
> usbuhci!UhciAbortAsyncTransfer+0x4f:
> f866a509 8b4e08 ? ? ? ? ?mov ? ? ecx,dword ptr [esi+8] ds:0023:00000008=???
> kd> lmvm usbuhci
> start ? ?end ? ? ? ?module name
> f8667000 f866c000 ? usbuhci ? ?(pdb symbols) ? ? ? ? ?C:\WINDOWS\Symbolsxp\sys\usbuhci.pdb
> ? ?Loaded symbol image file: usbuhci.sys
> ? ?Image path: \SystemRoot\system32\DRIVERS\usbuhci.sys
> ? ?Image name: usbuhci.sys
> ? ?Timestamp: ? ? ? ?Wed Aug 04 11:38:34 2004 (41107D62)
> ? ?CheckSum: ? ? ? ? 00013083
> ? ?ImageSize: ? ? ? ?00005000
> ? ?File version: ? ? 5.1.2600.2180
> ? ?Product version: ?5.1.2600.2180
> ? ?File flags: ? ? ? 0 (Mask 3F)
> ? ?File OS: ? ? ? ? ?40004 NT Win32
> ? ?File type: ? ? ? ?2.0 Dll
> ? ?File date: ? ? ? ?00000000.00000000
> ? ?Translations: ? ? 0409.04b0
> ? ?CompanyName: ? ? ?Microsoft Corporation
> ? ?ProductName: ? ? ?Microsoft? Windows? Operating System
> ? ?InternalName: ? ? USBUHCI.sys
> ? ?OriginalFilename: USBUHCI.sys
> ? ?ProductVersion: ? 5.1.2600.2180
> ? ?FileVersion: ? ? ?5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
> ? ?FileDescription: ?UHCI USB Miniport Driver
> ? ?LegalCopyright: ? ? Microsoft Corporation. All rights reserved.
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>

4

no…

i did’t try that…

but i will

5

i have enabled verifier for the driver…

but still it is showing the same… Error in USBHUHCI.SYS

i m not able to rectify it…

Boilerplate code is been taken from filter driver of ONEY’s book… and i have changed it for my need…

i m average in driver development… so help me…

thank you alll

6

I’m not sure what do you expect from us. It is your driver and it is you
who has to debug it.

When I need to solve such a problem (and I had several oportunities with
exactly this part), I list all threads in the system (!process 0 7) and
find threads which contain my driver code. Then I examine my own data
structures (device extension) and with both info together I try to find
what happenned just before the crash. It may or may not be enough. If it
isn’t and the problem is reproducible, I turn on tracing in relevant
part of my driver, start DebugView and reproduce problem. From dump it
is possible to extract DebugView buffer with traces so I can see what my
driver did just before crash. It is usually enough to find out to decide
if the problem is in my code (and where) or somewhere else.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Monday, April 20, 2009 3:24 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] unknown bugcheck un USBHACI.sys…

i have enabled verifier for the driver…

but still it is showing the same… Error in USBHUHCI.SYS

i m not able to rectify it…

Boilerplate code is been taken from filter driver of ONEY’s
book… and i have changed it for my need…

i m average in driver development… so help me…

thank you alll

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online
at http://www.osronline.com/page.cfm?name=ListServer

7

harish bisht wrote:

but still it is showing the same… Error in USBHUHCI.SYS

In addition to what Michal said (all excellent hints), have you tried reproducing this under different scenarios? i.e. formatting a different memory stick, using a hub versus not using a hub, using EHCI or OHCI, using Win2k/Vista/Win7, etc.?

If it reproduces on many or all of the above, then you probably have something fundamentally wrong in your driver. If it only occurs in one or two situations, you probably have a more subtle problem (that may not even be yours).

Debugging USB port issues can be tough. You may have to bite the bullet and open a support incident to get help. Be forewarned, however, that if the bug actually ends up to be on the MS side, the odds of you getting a hotfix are probably slim…

8

> -----Original Message-----

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: Tuesday, April 21, 2009 4:35 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] unknown bugcheck un USBHACI.sys…

Debugging USB port issues can be tough. You may have to bite
the bullet and open a support incident to get help. Be
forewarned, however, that if the bug actually ends up to be
on the MS side, the odds of you getting a hotfix are probably slim…

Opening a support incident is the last resort for me when I’m sure the
bug is at MS side (and the last time it was eventually mine…). It can
take months before somebody starts examining it. It is possible to get a
QFE or even hotfix if there is enough “business justification”,
otherwise it can be planned to next SP or even next OS version.

Anyway, if somebody “average in driver development” encounters a
bugcheck, it is very probable the problem is at his side.

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]