Keyspan serial adapter - Model: USA-19HS - Blue screen of death

I have 2 systems crashing with the “blue screen of death” which appears to be related to the Keyspan USB serial adapter. Any advice on how to proceed would be greatly appreciated.

OS Windows XP SP3

I have tried a few different versions of the driver and get the same result. The system crashes 1 to 2 hours after startup. The mini dump follows:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [E:\Mini051810-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100216-1514
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue May 18 13:40:46.278 2010 (UTC - 4:00)
System Uptime: 1 days 6:02:57.927
Loading Kernel Symbols
...............................................................
...................................................
Loading User Symbols
Loading unloaded module list
........................................
*** WARNING: Unable to verify timestamp for USA19H2kp.SYS
*** ERROR: Module load completed but symbols could not be loaded for USA19H2kp.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {38, 2, 1, 80546ae8}
*** WARNING: Unable to verify timestamp for USA19H2k.sys
*** ERROR: Module load completed but symbols could not be loaded for USA19H2k.sys
Probably caused by : USA19H2kp.SYS ( USA19H2kp+b40 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000038, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80546ae8, address which referenced memory
Debugging Details:
------------------

WRITE_ADDRESS: 00000038
CURRENT_IRQL: 2
FAULTING_IP:
nt!Exfi386InterlockedExchangeUlong+0
80546ae8 8711 xchg edx,dword ptr [ecx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from b8400b40 to 80546ae8
STACK_TEXT:
b84d3b30 b8400b40 00000000 896bdc20 8969f100 nt!Exfi386InterlockedExchangeUlong
WARNING: Stack unwind information not available. Following frames may be wrong.
b84d3b44 b8400cdd 026bdc20 00000000 8969f102 USA19H2kp+0xb40
b84d3b5c b8401f10 896bdc20 b84d3b88 b46120b4 USA19H2kp+0xcdd
b84d3b68 b46120b4 8969f102 b462a9d0 8969f0ac USA19H2kp+0x1f10
b84d3b88 b460dd4d 8969f0ac 88fcdad7 00000000 USA19H2k+0x80b4
b84d3ba4 804f16c0 00000000 88fcd9f8 893faae0 USA19H2k+0x3d4d
b84d3bd4 b734a0d5 88fcd9f8 892d9008 89b53028 nt!IopfCompleteRequest+0xa2
b84d3c3c b734ad47 893faae0 00000000 89b537d8 USBPORT!USBPORT_CompleteTransfer+0x373
b84d3c6c b734b944 026e6f44 89b530e0 89b530e0 USBPORT!USBPORT_DoneTransfer+0x137
b84d3ca4 b734d13a 89b53028 80546afc 89b53230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
b84d3cd0 b735b24b 89b53028 80546afc 89b53028 USBPORT!USBPORT_DpcWorker+0x224
b84d3d0c b735b3c2 89b53028 00000001 8055c0c0 USBPORT!USBPORT_IsrDpcWorker+0x38f
b84d3d28 80545eaf 89b5364c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
b84d3d50 80545d94 00000000 0000000e ffffffff nt!KiRetireDpcList+0x61
b84d3d54 00000000 0000000e ffffffff ffffffff nt!KiIdleLoop+0x28

STACK_COMMAND: kb
FOLLOWUP_IP:
USA19H2kp+b40
b8400b40 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USA19H2kp+b40
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USA19H2kp
IMAGE_NAME: USA19H2kp.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 465cb828
FAILURE_BUCKET_ID: 0xA_USA19H2kp+b40
BUCKET_ID: 0xA_USA19H2kp+b40
Followup: MachineOwner
---------

Solution: Keyspan serial adapter - Model: USA-19HS - Blue screen of death

Hi jkavx,

This happens 'cause each users might be having a different resolution and also they might resize the forms and also their DPI settings might be differet.

At best what you can do is rather than hardcoding the position of the controls you can use layouting techniques - Anchoring, Docking, Container Panels etc.

Regards,
Chinmay

Keyspan serial adapter - Model: USA-19HS - Blue screen of death

Solution: Keyspan serial adapter - Model: USA-19HS - Blue screen of death

Popular Tags