Dear all,
I am using the usbsamp driver for a custom device. When the device is connected to the pc and the pc is moved into a standby mode then the kernel crashes. Do i have to explicitly handle any condition? The device is not powered by the pc, it is self powered.
An !analyze -v would help, if you have it.
mm
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 47919015
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
FAULTING_IP:
nt+53848
8052a848 cc int 3
TRAP_FRAME: bab07034 – (.trap 0xffffffffbab07034)
ErrCode = 00000000
eax=89db82a0 ebx=00000000 ecx=8052a97c edx=00000001 esi=804fad7e edi=00000102
eip=8052a849 esp=bab070a8 ebp=bab070c4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000202
nt+0x53849:
8052a849 c3 ret
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from a86be183 to 8052a849
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bab070c4 a86be183 89903200 a86e4098 8990321c nt+0x53849
bab070e0 a86c00b3 00000000 a86e4ca8 89c16b28 wdf01000+0x44183
bab07100 a86c808d 00000001 89c16b28 a86c80aa wdf01000+0x460b3
bab07114 a86c850b 89c16b28 a86e4900 89c16b28 wdf01000+0x4e08d
bab0718c a86c9c97 0000031a 00000000 89c16b28 wdf01000+0x4e50b
bab071b4 a86ca047 bab071cc bab07224 89c16b28 wdf01000+0x4fc97
bab071d8 a86d1b2d 00000001 bab071f8 a86d1d2f wdf01000+0x50047
bab071e4 a86d1d2f bab07224 a86e47a0 899210e4 wdf01000+0x57b2d
bab071f8 a86d1d5d 899210e4 bab07228 a86c4bcf wdf01000+0x57d2f
bab07204 a86c4bcf 89c16b28 bab07224 89921008 wdf01000+0x57d5d
bab07228 a86ae665 89921008 bab07250 a86ae888 wdf01000+0x4abcf
bab07234 a86ae888 89dc8f00 89921008 80562248 wdf01000+0x34665
bab07250 804ef0b5 89dc8f00 89921008 899210e4 wdf01000+0x34888
bab07274 805262c3 899210e4 89921008 89921108 nt+0x180b5
bab07294 80526433 89dc8f00 89dc8fd0 a86d07db nt+0x4f2c3
bab072b0 a86d086a 89dc8f00 00000002 00000004 nt+0x4f433
bab072ec a86d0b95 00000004 00000001 00000004 wdf01000+0x5686a
bab07300 a86d0d8f 00000004 00000001 a86e616c wdf01000+0x56b95
bab07318 a86cf49a 89c16b28 a86e59e0 89c16b28 wdf01000+0x56d8f
bab07390 a86cfff3 00000526 00000000 89c16b28 wdf01000+0x5549a
bab073b8 a86d072f bab073d0 00000000 89b9de9b wdf01000+0x55ff3
bab073dc a86d1a14 00000001 bab07418 804f15d6 wdf01000+0x5672f
bab073e8 804f15d6 89dc8f00 89b9dde0 89c16b28 wdf01000+0x57a14
bab07418 ba9fd859 89b9dde0 00000000 bab07448 nt+0x1a5d6
bab07428 baa044c9 89e08d50 89b9dde0 00000000 usbhub+0x5859
bab07448 baa04727 8a1c0658 89b9dde0 89b9dde0 usbhub+0xc4c9
bab07468 ba9fc97b 89b9de98 89b9dde0 00000002 usbhub+0xc727
bab07488 ba9fa1d8 8a1c0658 89b9dde0 bab074bc usbhub+0x497b
bab07498 804ef0b5 8a1c05a0 89b9dde0 89b9de98 usbhub+0x21d8
bab074bc 805262c3 89b9de98 89b9dde0 89b9deb4 nt+0x180b5
bab074dc a86d1ac6 8a1c05a0 8a1c0788 89c16b28 nt+0x4f2c3
bab074fc a86d1d56 bab07528 bab0752c a86c4bcf wdf01000+0x57ac6
bab07508 a86c4bcf 89c16b28 bab07528 89b9dde0 wdf01000+0x57d56
bab0752c a86ae665 89b9dde0 bab07554 a86ae888 wdf01000+0x4abcf
bab07538 a86ae888 89dc8f00 89b9dde0 80562248 wdf01000+0x34665
bab07554 804ef0b5 89dc8f00 89b9dde0 89b9debc wdf01000+0x34888
bab07578 805262c3 89b9debc 89b9dde0 89d909e0 nt+0x180b5
bab07598 80651ffa 89dc8f00 89dc8fd0 89d90b74 nt+0x4f2c3
bab075b8 806520bb 8055a45c 89863d60 00000005 nt+0x17affa
bab075d4 806523bf 89d909e0 89d90b74 00000000 nt+0x17b0bb
bab075fc 8065124c 00000000 bab076e4 bab07768 nt+0x17b3bf
bab076d0 8054088c 00000002 00000002 20000003 nt+0x17a24c
bab076e4 80500559 badb0d00 bab0775c 0006f174 nt+0x6988c
bab07830 8054088c 00000002 00000002 20000003 nt+0x29559
bab07844 7c90e514 badb0d00 0006f168 00000001 nt+0x6988c
bab07848 badb0d00 0006f168 00000001 0000000a 0x7c90e514
bab0784c 0006f168 00000001 0000000a 00000045 0xbadb0d00
bab07850 00000000 0000000a 00000045 00000000 0x6f168
STACK_COMMAND: kb
FOLLOWUP_IP:
wdf01000+44183
a86be183 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: wdf01000+44183
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: wdf01000
IMAGE_NAME: wdf01000.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
The symbols are not fixed sorry…but the faulty module is said as wdf01000.sys.
The problem does not happen when the device is not connected to the pc and the pc is set to standby mode. So seems like there is some problem with usbsamp.sys but dont know what…
You need to fix your symbols:
.sympath srv*c:\sym*http://msdl.microsoft.com/download/symbols
.reload -f -n
lml
mm
xxxxx@gmail.com wrote:
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 47919015
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
That’s an assertion failure from KMDF. Fixing the symbols is a
mandatory first step, but you’ll need to examine the KMDF log to find
out the reason for the assert. Something similar to this.
!load wdfkd.dll
!wdftmffile \winddk\7600\tools\tracing\i386\wdf01009.tmf
!wdflogdump usbsamp
Have you modified usbsamp?
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.