Re: [long] Win2k USBtoCOM driver crash at usbd.sys
- From: "Calvin Guan" <hguan@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Aug 2006 23:57:40 -0700
Doron, who in Microsoft decide what symbols to put on the public sym server
or make it available to the connect.Microsoft.com? I'm having huge problems
poking around the weekly winmain interim builds since they come with
absolutely no symbols, hence windbg became nearly useless. Ndis team may
help with the ndt.vbl but not winmain:(
--
Calvin Guan (DDK MVP)
Sr. Staff Engineer
NetXtreme NTX Miniport
Broadcom Corporation
Connecting Everything(r)
"Doron Holan [MS]" <doronh@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23VmptmLzGHA.2300@xxxxxxxxxxxxxxxxxxxxxxx
you need to fix your symbols (.symfix). most likely, you are freeing a
PIRP that is still pending in USBD. remember that just b/c you call
IoCancelIrp does not mean that the irp will be completed immediately
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.
"Maksymilian Dutka" <maxdutka@xxxxxxxxxxxxxxxxxx> wrote in message
news:ed3ge6$4kk$1@xxxxxxxxxxxxxxxxxxxxxxx
Hi, I have written a driver for USB to RS232 converter. In Win98/WinXP
all works fine, but in Win2k is not:
When I unplug device in the moment when virtual COM is open the system
crashes:
*** Fatal System Error: 0x000000d1
(0x2BC30006,0x00000002,0x00000001,0x81475309)
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 D1, {2bc30006, 2, 1, 81475309}
Probably caused by : USBD.SYS ( USBD!USBD_CompleteRequest+3d )
Followup: MachineOwner
---------
nt!PsChargeSharedPoolQuota+0x76:
80455558 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: 2bc30006, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 81475309, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 2bc30006 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
+ffffffff81475309
81475309 0009 add [ecx],cl
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 8042afda to 80455558
STACK_TEXT:
8046ad70 8042afda 00000003 2bc30006 81475309
nt!PsChargeSharedPoolQuota+0x76
8046b0fc 80467df7 00000000 2bc30006 00000002
nt!PnPCheckFixedIoOverrideDecodes+0x92
8046b138 f3d2319d 81429f68 81458a68 81420000 nt!Dr_kitd_a+0x1b
8046b1dc 8041dfa5 00000000 81458a68 8139728c
usbhub!USBH_FunctionPdoDispatch+0x1ef
8046b1f8 f3f39c81 00000000 00000000 8046b22c
nt!FsRtlRemoveAndCompleteWaitIrp+0x48
8046b210 f3f21534 81458a68 00000000 00000000
USBD!USBD_CompleteRequest+0x3d
81458a68 00000000 00000000 00000000 81458a78 uhcd!UHCD_CompleteIrp+0xba
STACK_COMMAND: kb
FOLLOWUP_IP:
USBD!USBD_CompleteRequest+3d
f3f39c81 5e pop esi
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 5
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: USBD!USBD_CompleteRequest+3d
MODULE_NAME: USBD
IMAGE_NAME: USBD.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 3e2ecf5d
FAILURE_BUCKET_ID: 0xD1_W_USBD!USBD_CompleteRequest+3d
BUCKET_ID: 0xD1_W_USBD!USBD_CompleteRequest+3d
Followup: MachineOwner
---------
Thanks,
Maksymilian Dutka
.
- References:
- [long] Win2k USBtoCOM driver crash at usbd.sys
- From: Maksymilian Dutka
- Re: [long] Win2k USBtoCOM driver crash at usbd.sys
- From: Doron Holan [MS]
- [long] Win2k USBtoCOM driver crash at usbd.sys
- Prev by Date: Re: TdiBuildReceive question
- Next by Date: Re: TdiBuildReceive question
- Previous by thread: Re: [long] Win2k USBtoCOM driver crash at usbd.sys
- Next by thread: BUGCODE_USB_DRIVER - Arg1=0x05
- Index(es):
Relevant Pages
|
