Blue screen when installing CATALYST drivers (5.2 and 5.3 ..

Archived from groups: alt.comp.periphs.videocards.ati (More info?)

Hello.

I seem to have notice a pattern related to blue screens of death after installing CATALYST drivers (5.2 and 5.3 so far), rebooting, and logging into Windows XP Professional SP2 (all updates). It seems like my wireless USB adapter software/driver does not like ATI driver setup program or something. I ran WinDebug (http://www.microsoft.com/whdc/devtools/debugging/default.mspx) to analyze the memory.dmp file (Kernel type):

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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*i:\winstuff\symbols\*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Fri Mar 11 23:48:56.421 2005 (GMT-8)
System Uptime: 0 days 0:01:37.968
Loading Kernel Symbols
.............................................................................................................................................................................
Loading unloaded module list
......
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck CE, {f78d890e, 8, f78d890e, 0}

Probably caused by : ECCL100.sys ( <Unloaded_ECCL100.sys>+90e )

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

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (ce)
A driver unloaded without cancelling timers, DPCs, worker threads, etc.
The broken driver's name is displayed on the screen.
Arguments:
Arg1: f78d890e, memory referenced
Arg2: 00000008, value 0 = read operation, 1 = write operation
Arg3: f78d890e, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, Mm internal code.

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


WRITE_ADDRESS: f78d890e Nonpaged pool

FAULTING_IP:
<Unloaded_ECCL100.sys>+90e
f78d890e ?? ???

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xCE

TRAP_FRAME: b84bdca0 -- (.trap ffffffffb84bdca0)
ErrCode = 00000010
eax=b84bdd2c ebx=00000000 ecx=00000000 edx=83df4d08 esi=83e72148 edi=804f97fc
eip=f78d890e esp=b84bdd14 ebp=b84bdd98 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
<Unloaded_ECCL100.sys>+0x90e:
f78d890e ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from f7313cd6 to f78d890e

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b84bdd10 f7313cd6 00000000 b84bdd2c f7312464 <Unloaded_ECCL100.sys>+0x90e
b84bdd98 f7312baa 83e72148 00000000 83df4da8 NDIS!ndisCheckProtocolBindings+0x183
b84bddac 805c4a28 83e721c8 00000000 00000000 NDIS!ndisWorkerThread+0x75
b84bdddc 80540fa2 f7312b85 83e721c8 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
<Unloaded_ECCL100.sys>+90e
f78d890e ?? ???

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: <Unloaded_ECCL100.sys>+90e

MODULE_NAME:

IMAGE_NAME: ECCL100.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .trap ffffffffb84bdca0 ; kb

BUCKET_ID: 0xCE_W__Unloaded_ECCL100.sys_+90e

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

After rebooting from the blue screen, I can safely enter XP again without any more crashes. It is a just weird glitch that I noticed with the last two versions. The first one (5.2) was overinstall from 5.1 driver. Second one was after removing MMC and 5.2 driver, and rebooting.

ECCL100.sys is owned by Envara -- http://www.envara.com. I believe I am using the latest driver and software utility for my for my Hawking Technology's Hi-Gain USB Wireless-G Adapter (Model: HWU54D)? I am currently using v2.5.1 (3/18/2004) for this software from http://www.hawkingtech.com/images/drivers/HWU54D.zip ...
bn
The utility says:
Device Name: ENVARA WiND 802.11g
Regulatory Domain: FCC (US)
Driver Version: v1.4.46.23.
Firmware Version: 0002 - 0166 / 0045 - 00B0
NVM Version: 2040010 - 26

I manually disabled the network adapter during reboots and before shutting down. Does anyone have this type of problem? I will report this to ATI as a possible bug report since I can reproduce this.

Thank you in advance.
--
"The men of experiment are like the ant; they only collect and use. But the bee...gathers its materials from the flowers of the garden and of the field, but transforms and digests it by a power of its own." --Leonardo da Vinci
/\___/\
/ /\ /\ \ Ant @ The Ant Farm: http://antfarm.ma.cx
| |o o| | Ant's Quality Foraged Links: http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )i
skankinlee@adelphia.net