USB 2.0 card causing BUGCODE_USB_DRIVER error

[SevenSamurai]

Recently got a Lexar 1GB USB 2.0 memory stick. Since my computer did
not have USB 2.0 ports (Asus TUV4X motherboard) I installed an Adaptec
USB 2 connect AUA-3100LP card that had previously been in another
system. Now then, after installing the card, Windows detected it as a
NEC PCI to USB Enhanced Host Controller (B1). Not really an issue
since this is indeed an NEC chip based card and the actual Adaptec
drivers are two years old. Using my 1GB USB 2.0 stick off of it works
flawlessly (and at the correct speed) and all of my other USB 1.1
joysticks, printer, and Palm cradle work just as they used to off of a
hub.

But the problem I am having is that under any heavy load (i.e. games)
I will randomly get a blue screen with a BUGCODE_USB_DRIVER error
after between five and twenty minutes. I have since tried the drivers
from Adaptec's site (which are much older than the generic ones in
SP2) but that actually caused a driver_irql_not_less_or_equal error
when copying files to a usb stick. So I moved it to another PCI slot
and went back to SP2's generic NEC drivers and am still having the
bugcode_usb_driver error under games even when I'm not touching or
doing anything.

For the life of me I can't seem to get rid of this problem with simply
having a USB 2.0 card added to my system. Anyone?

Stats:
Pentium III-S 1.40 GHz
Asus TUV4X Bios 1006.02
Seagate Barracuda 7200.7 200GB hdd
Plextor PX-320A
GeForce4 Ti4400
Sound Blaster Audigy 2
Intel Pro/100+

 

[SevenSamurai]

Small follow up:

Doesn't seem to really make a difference what is plugged into it. The
two things I've been plugging into it are an HP Deskjet 930C on one
port and a Belkin 7-port USB 2.0 hub on another. The other two ports
on the card are unused. I've tried all sorts of combinations of
nothing plugged into the card, just the printer, just the hub, just
the hub without anything on the hub, and it all seems to crash out at
some point. Heck, just plugging back in my printer once gave me a
blue screen saying only that "A thread tried to release a resource it
did not own." The only thing I have noticed is that with the hub
plugged in, it blue screens much faster than without it. But since
this is a self-powered and not a bus-powered hub, it isn't drawing any
current so it can't be a power issue. This one has me thoroughly
stumped.