Prev: Installation failure of the DTM controller
Next: Bulkusb and Vista
From: Kinglemur on 13 Jun 2007 17:53
While testing USB device drivers on 32-bit Vista, we have repeatedly
encountered bug check 0xFE with an undocumented value for parameter 1.

This bug check is documented in the WinDbg help file, as well as here:
http://msdn2.microsoft.com/en-us/library/ms797153.aspx

Parameter 1 values from 1 to 5 are documented. 8 appears to new with Vista
and is apparently completely undocumented anywhere, although I have found a
handful of cases on the Web of people asking for help with it. This is
currently holding up our efforts to port our drivers, and therefore our
devices, to Vista.

What is the meaning of this bug check with parameter 1 equal to 8? The
crash occurs in the Microsoft USB hub driver, usbhub.sys, after what appears
to be an innoccuous power management IO request from our driver.

Thanks for any help,
David

From: Neo on 4 Jul 2007 07:36
Hi David,

i agree with u i got a bugcheck as follows with parameter1 = 6.

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000006, USB Bugcheck Code:
Arg2: 82e45000
Arg3: 48706950
Arg4: 00000000

Debugging Details:
------------------
MODULE_NAME: USBPORT

FAULTING_MODULE: 81800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4549b26d

DEFAULT_BUCKET_ID: VISTA_BETA2

BUGCHECK_STR: 0xFE

LAST_CONTROL_TRANSFER: from 818adbac to 81835688

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may
be wrong.
83c0388c 818adbac 00000003 83061cf0 82e45000 nt!DbgBreakPointWithStatus
+0x4
83c03c38 818acfcb 000000fe 00000006 82e45000 nt!KeBugCheckEx+0xbff
83c03c58 87c201f9 000000fe 00000006 82e45000 nt!KeBugCheckEx+0x1e
83c03c74 87c2bcca 82e45000 04060000 48706950 USBPORT+0x11f9
83c03cb8 87c2c693 82fd9028 83061cf0 832a3008 USBPORT+0xccca
83c03ce0 87c23d39 82fd9028 83061cf0 832a3008 USBPORT+0xd693
83c03d20 87c24215 83003028 82fd9028 82fc2828 USBPORT+0x4d39
83c03d4c 87c2281e 83003028 82fc2828 837ea138 USBPORT+0x5215
83c03d78 81867cc9 83003028 837ea138 82fc2828 USBPORT+0x381e
83c03d90 87f4be67 82fc2828 832c77b8 00000000 nt!IofCallDriver+0x64
83c03da4 87f4c13c 830740e0 832c7700 82fc2828 usbhub+0x1e67
83c03dc8 87f4bc92 832c7700 82fc2904 832c7700 usbhub+0x213c
83c03ddc 81867cc9 832c7700 82fc2828 83061cf0 usbhub+0x1c92
83c03df4 8538ccb3 82fc2828 83399010 833f6e88 nt!IofCallDriver+0x64
83c03e14 8538c2cb 8338c1d0 83325a70 83c03e33 hidusb+0x1cb3
83c03e34 84154a5d 8338c1d0 82fc2828 82fc2828 hidusb+0x12cb
83c03e48 84155dea 8338c1d0 82fc2828 82fc292b HIDCLASS+0x1a5d
83c03e64 84155d3c 8338c29c 833f6e88 83c03ea7 HIDCLASS+0x2dea
83c03e94 81834b79 00000000 82fc2828 0038c29c HIDCLASS+0x2d3c
83c03ec8 87c28f18 81838164 837d8ba0 00000000 nt!RtlFreeHeap+0x1010
83c03f04 87c29564 82fd9028 82fc2828 82da7070 USBPORT+0x9f18
83c03f34 87c23163 82fd9028 39585043 82fd9be8 USBPORT+0xa564
83c03f60 87c215b9 82fd9028 82fd9be8 82fd9002 USBPORT+0x4163
83c03f88 8186b17e 82fd9bf4 34776478 00000000 USBPORT+0x25b9
83c03ff4 8183759d 990a0c00 00905a4d 00000003 nt!ObfReferenceObject
+0xb2c
990a0c1c 81b9b474 818ec702 990a0c54 990a0c54 nt!KiDispatchInterrupt
+0x3d
990a0c38 81b9b63d 82e74418 990a0c54 8183726e hal!
KeRaiseIrqlToSynchLevel+0x70
990a0c44 8183726e 990a0c00 00000062 990a0d08 hal!HalEndSystemInterrupt
+0x73
990a0c98 972d865f ffffffff fee24410 990a0d40 nt!KeSynchronizeExecution
+0x30e
990a0d08 972c869d 990a0d34 990a0d40 00000004 win32k!EngStrokePath
+0x28ca
990a0d4c 818461fa c604097a ff48fbe0 8b04099d win32k!EngLpkInstalled
+0x3f0f
990a0d64 77920f34 badb0d00 0019efc4 00000000 nt!ZwQueryLicenseValue
+0xc02
990a0d68 badb0d00 0019efc4 00000000 00000000 ntdll!KiFastSystemCallRet
990a0d6c 0019efc4 00000000 00000000 00000000 0xbadb0d00
990a0d70 00000000 00000000 00000000 00000000 0x19efc4

0: kd> kb
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may
be wrong.
83c0388c 818adbac 00000003 83061cf0 82e45000 nt!DbgBreakPointWithStatus
+0x4
83c03c38 818acfcb 000000fe 00000006 82e45000 nt!KeBugCheckEx+0xbff
83c03c58 87c201f9 000000fe 00000006 82e45000 nt!KeBugCheckEx+0x1e
83c03c74 87c2bcca 82e45000 04060000 48706950 USBPORT+0x11f9
83c03cb8 87c2c693 82fd9028 83061cf0 832a3008 USBPORT+0xccca
83c03ce0 87c23d39 82fd9028 83061cf0 832a3008 USBPORT+0xd693
83c03d20 87c24215 83003028 82fd9028 82fc2828 USBPORT+0x4d39
83c03d4c 87c2281e 83003028 82fc2828 837ea138 USBPORT+0x5215
83c03d78 81867cc9 83003028 837ea138 82fc2828 USBPORT+0x381e
83c03d90 87f4be67 82fc2828 832c77b8 00000000 nt!IofCallDriver+0x64
83c03da4 87f4c13c 830740e0 832c7700 82fc2828 usbhub+0x1e67
83c03dc8 87f4bc92 832c7700 82fc2904 832c7700 usbhub+0x213c
83c03ddc 81867cc9 832c7700 82fc2828 83061cf0 usbhub+0x1c92
83c03df4 8538ccb3 82fc2828 83399010 833f6e88 nt!IofCallDriver+0x64
83c03e14 8538c2cb 8338c1d0 83325a70 83c03e33 hidusb+0x1cb3
83c03e34 84154a5d 8338c1d0 82fc2828 82fc2828 hidusb+0x12cb
83c03e48 84155dea 8338c1d0 82fc2828 82fc292b HIDCLASS+0x1a5d
83c03e64 84155d3c 8338c29c 833f6e88 83c03ea7 HIDCLASS+0x2dea
83c03e94 81834b79 00000000 82fc2828 0038c29c HIDCLASS+0x2d3c
83c03ec8 87c28f18 81838164 837d8ba0 00000000 nt!RtlFreeHeap+0x1010


There is no trace of my Driver in the Stack Trace.
May be my driver fault has caused it but what made it to cause.
can anyone helps us.

Regards,
Neo

From: Doron Holan [MSFT] on 4 Jul 2007 12:23
first, fix your symbols by using the public symbol server. that will give
you a better idea of what is going on

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.


"Neo" <rksandilya(a)gmail.com> wrote in message
news:1183548965.432243.250110(a)a26g2000pre.googlegroups.com...
> Hi David,
>
> i agree with u i got a bugcheck as follows with parameter1 = 6.
>
> BUGCODE_USB_DRIVER (fe)
> USB Driver bugcheck, first parameter is USB bugcheck code.
> Arguments:
> Arg1: 00000006, USB Bugcheck Code:
> Arg2: 82e45000
> Arg3: 48706950
> Arg4: 00000000
>
> Debugging Details:
> ------------------
> MODULE_NAME: USBPORT
>
> FAULTING_MODULE: 81800000 nt
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 4549b26d
>
> DEFAULT_BUCKET_ID: VISTA_BETA2
>
> BUGCHECK_STR: 0xFE
>
> LAST_CONTROL_TRANSFER: from 818adbac to 81835688
>
> STACK_TEXT:
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 83c0388c 818adbac 00000003 83061cf0 82e45000 nt!DbgBreakPointWithStatus
> +0x4
> 83c03c38 818acfcb 000000fe 00000006 82e45000 nt!KeBugCheckEx+0xbff
> 83c03c58 87c201f9 000000fe 00000006 82e45000 nt!KeBugCheckEx+0x1e
> 83c03c74 87c2bcca 82e45000 04060000 48706950 USBPORT+0x11f9
> 83c03cb8 87c2c693 82fd9028 83061cf0 832a3008 USBPORT+0xccca
> 83c03ce0 87c23d39 82fd9028 83061cf0 832a3008 USBPORT+0xd693
> 83c03d20 87c24215 83003028 82fd9028 82fc2828 USBPORT+0x4d39
> 83c03d4c 87c2281e 83003028 82fc2828 837ea138 USBPORT+0x5215
> 83c03d78 81867cc9 83003028 837ea138 82fc2828 USBPORT+0x381e
> 83c03d90 87f4be67 82fc2828 832c77b8 00000000 nt!IofCallDriver+0x64
> 83c03da4 87f4c13c 830740e0 832c7700 82fc2828 usbhub+0x1e67
> 83c03dc8 87f4bc92 832c7700 82fc2904 832c7700 usbhub+0x213c
> 83c03ddc 81867cc9 832c7700 82fc2828 83061cf0 usbhub+0x1c92
> 83c03df4 8538ccb3 82fc2828 83399010 833f6e88 nt!IofCallDriver+0x64
> 83c03e14 8538c2cb 8338c1d0 83325a70 83c03e33 hidusb+0x1cb3
> 83c03e34 84154a5d 8338c1d0 82fc2828 82fc2828 hidusb+0x12cb
> 83c03e48 84155dea 8338c1d0 82fc2828 82fc292b HIDCLASS+0x1a5d
> 83c03e64 84155d3c 8338c29c 833f6e88 83c03ea7 HIDCLASS+0x2dea
> 83c03e94 81834b79 00000000 82fc2828 0038c29c HIDCLASS+0x2d3c
> 83c03ec8 87c28f18 81838164 837d8ba0 00000000 nt!RtlFreeHeap+0x1010
> 83c03f04 87c29564 82fd9028 82fc2828 82da7070 USBPORT+0x9f18
> 83c03f34 87c23163 82fd9028 39585043 82fd9be8 USBPORT+0xa564
> 83c03f60 87c215b9 82fd9028 82fd9be8 82fd9002 USBPORT+0x4163
> 83c03f88 8186b17e 82fd9bf4 34776478 00000000 USBPORT+0x25b9
> 83c03ff4 8183759d 990a0c00 00905a4d 00000003 nt!ObfReferenceObject
> +0xb2c
> 990a0c1c 81b9b474 818ec702 990a0c54 990a0c54 nt!KiDispatchInterrupt
> +0x3d
> 990a0c38 81b9b63d 82e74418 990a0c54 8183726e hal!
> KeRaiseIrqlToSynchLevel+0x70
> 990a0c44 8183726e 990a0c00 00000062 990a0d08 hal!HalEndSystemInterrupt
> +0x73
> 990a0c98 972d865f ffffffff fee24410 990a0d40 nt!KeSynchronizeExecution
> +0x30e
> 990a0d08 972c869d 990a0d34 990a0d40 00000004 win32k!EngStrokePath
> +0x28ca
> 990a0d4c 818461fa c604097a ff48fbe0 8b04099d win32k!EngLpkInstalled
> +0x3f0f
> 990a0d64 77920f34 badb0d00 0019efc4 00000000 nt!ZwQueryLicenseValue
> +0xc02
> 990a0d68 badb0d00 0019efc4 00000000 00000000 ntdll!KiFastSystemCallRet
> 990a0d6c 0019efc4 00000000 00000000 00000000 0xbadb0d00
> 990a0d70 00000000 00000000 00000000 00000000 0x19efc4
>
> 0: kd> kb
> ChildEBP RetAddr Args to Child
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 83c0388c 818adbac 00000003 83061cf0 82e45000 nt!DbgBreakPointWithStatus
> +0x4
> 83c03c38 818acfcb 000000fe 00000006 82e45000 nt!KeBugCheckEx+0xbff
> 83c03c58 87c201f9 000000fe 00000006 82e45000 nt!KeBugCheckEx+0x1e
> 83c03c74 87c2bcca 82e45000 04060000 48706950 USBPORT+0x11f9
> 83c03cb8 87c2c693 82fd9028 83061cf0 832a3008 USBPORT+0xccca
> 83c03ce0 87c23d39 82fd9028 83061cf0 832a3008 USBPORT+0xd693
> 83c03d20 87c24215 83003028 82fd9028 82fc2828 USBPORT+0x4d39
> 83c03d4c 87c2281e 83003028 82fc2828 837ea138 USBPORT+0x5215
> 83c03d78 81867cc9 83003028 837ea138 82fc2828 USBPORT+0x381e
> 83c03d90 87f4be67 82fc2828 832c77b8 00000000 nt!IofCallDriver+0x64
> 83c03da4 87f4c13c 830740e0 832c7700 82fc2828 usbhub+0x1e67
> 83c03dc8 87f4bc92 832c7700 82fc2904 832c7700 usbhub+0x213c
> 83c03ddc 81867cc9 832c7700 82fc2828 83061cf0 usbhub+0x1c92
> 83c03df4 8538ccb3 82fc2828 83399010 833f6e88 nt!IofCallDriver+0x64
> 83c03e14 8538c2cb 8338c1d0 83325a70 83c03e33 hidusb+0x1cb3
> 83c03e34 84154a5d 8338c1d0 82fc2828 82fc2828 hidusb+0x12cb
> 83c03e48 84155dea 8338c1d0 82fc2828 82fc292b HIDCLASS+0x1a5d
> 83c03e64 84155d3c 8338c29c 833f6e88 83c03ea7 HIDCLASS+0x2dea
> 83c03e94 81834b79 00000000 82fc2828 0038c29c HIDCLASS+0x2d3c
> 83c03ec8 87c28f18 81838164 837d8ba0 00000000 nt!RtlFreeHeap+0x1010
>
>
> There is no trace of my Driver in the Stack Trace.
> May be my driver fault has caused it but what made it to cause.
> can anyone helps us.
>
> Regards,
> Neo
>

From: Tim Roberts on 5 Jul 2007 22:24
Neo <rksandilya(a)gmail.com> wrote:
>
>i agree with u i got a bugcheck as follows with parameter1 = 6.
>
>BUGCODE_USB_DRIVER (fe)
>USB Driver bugcheck, first parameter is USB bugcheck code.
>Arguments:
>Arg1: 00000006, USB Bugcheck Code:
>Arg2: 82e45000
>Arg3: 48706950
>Arg4: 00000000

Arg3 is the fourcc "PipH", suggesting it may be a pipe handle. Is it
possible you are trying to use a pipe handle that isn't valid because of an
unplug?
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
 | 
Pages: 1
Prev: Installation failure of the DTM controller
Next: Bulkusb and Vista