Athrusb.sys wireless adapter causing BSOD

I am running Vista 32 bit home premium SP2. AMD Phenom 9500 quad-core processor, 3 gb ram, nvidia geforce 8500 gt

BSOD's started a while after installing the 2Wire adapter. The connection itself is really poor and drops out pretty regularly, so that may have something to do with it.

I have updated all drivers, uninstalled unused drivers and programs, virus scan, all kinds of stuff. But I still get BSOD and the cause is athrsb.sys
I uninstalled the device and removed drivers for it, and no surprise, no BSOD since. I even left the comp on overnight for a few days.

Any help would be great. Here is the WinDBG from the dump.


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


Loading Dump File [C:\Users\Andrew\Desktop\Mini050210-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\windows\symbols\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18209.x86fre.vistasp2_gdr.100218-0019
Machine Name:
Kernel base = 0x82610000 PsLoadedModuleList = 0x82727c70
Debug session time: Sun May 2 22:04:13.306 2010 (GMT-7)
System Uptime: 0 days 10:55:31.850
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
...........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {5132c0, 2, 0, a3952a86}

Unable to load image \SystemRoot\system32\DRIVERS\athrusb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrusb.sys
*** ERROR: Module load completed but symbols could not be loaded for athrusb.sys
Probably caused by : athrusb.sys ( athrusb+5da86 )

Followup: MachineOwner
---------

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: 005132c0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: a3952a86, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from 82747868
Unable to read MiSystemVaType memory at 82727420
005132c0

CURRENT_IRQL: 2

FAULTING_IP:
athrusb+5da86
a3952a86 ?? ???

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: 85d56a70 -- (.trap 0xffffffff85d56a70)
ErrCode = 00000000
eax=0051329c ebx=c5270fd8 ecx=0051329c edx=8a5131f5 esi=8a3a2020 edi=c5270ed8
eip=a3952a86 esp=85d56ae4 ebp=85d56b04 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
athrusb+0x5da86:
a3952a86 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from a3952a86 to 8265dfd9

STACK_TEXT:
85d56a70 a3952a86 badb0d00 8a5131f5 a01a8035 nt!KiTrap0E+0x2e1
WARNING: Stack unwind information not available. Following frames may be wrong.
85d56ae0 85d56bf0 00000000 8a3a2020 8a3a2020 athrusb+0x5da86
85d56b04 a394b546 8a3a2020 8a1ee000 a2de91a8 0x85d56bf0
85d56b2c a394b652 8a1eb020 85d56b4c a394e4b2 athrusb+0x56546
85d56b38 a394e4b2 a2de9008 a2de90bc a2de9008 athrusb+0x56652
85d56b4c 828f2d4d 00000000 c5270ed8 a2de90bc athrusb+0x594b2
85d56b84 826b71fb 00000000 c5270ed8 85d56bf0 nt!IovpLocalCompletionRoutine+0x16e
85d56bb8 828f2b95 8a5ec028 a6b413a8 8a3229c0 nt!IopfCompleteRequest+0x11d
85d56c28 84d60e0a 82657724 8a3229c0 00000000 nt!IovCompleteRequest+0x11c
85d56c64 84d5f132 8a5ec028 c5270ed8 93b1a5f0 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6cb
85d56c94 84d6195f 8a5ec028 39585043 8a5ecbf8 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x4f5
85d56cc0 84d5b24f 8a5ec028 8a5ecbf8 8a5ec002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x122
85d56ce8 826ba6c2 8a5ecc04 34776478 00000000 USBPORT!USBPORT_Xdpc_Worker+0x274
85d56d50 826b889d 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
85d56d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND: kb

FOLLOWUP_IP:
athrusb+5da86
a3952a86 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: athrusb+5da86

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: athrusb

IMAGE_NAME: athrusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4608ec87

FAILURE_BUCKET_ID: 0xD1_VRF_athrusb+5da86

BUCKET_ID: 0xD1_VRF_athrusb+5da86

Followup: MachineOwner
---------

 

Thanks for the tips Halo,
here is the adapter I am using
http://www.2wire.com/index.php?p=117

Now that I think about it the adapter was plugged into one of my monitor's usb ports... That may be the problem. I also downloaded CPUZ to determine what chipset drier I need to install.

I'll post again if I need to change chipset river.

 

Forgot to mention, when the adapter is in use (connected to internet) and I restart the computer, it will sometimes hang and give a BSOD DRIVER_POWER_STATE_FAILURE. This never happens when the drivers and device are uninstalled.

Also, when I reinstall the adapter, it increments the device name. No other device does this.

example - Atheros AR5007UG Wireless Network Adapter #23

 

Oddly enough when I plug the adapter into the ports marked usb 2.0 it says "this device could be running faster" or whatever. But when its plugged into the monitor it doesn't. Not sure why?

When I plug it in elsewhere it tries to reinstall the driver software and fails, or refuses to let the device work until i replug it into the monitor. Really odd

 

Here is the newest minidump. Now it is mentioning sptd.sys in WinDbg