Finally I have found someone with the same problem as me. I get the BSOD in
safe mode or normal now. I also get an item detected by my spyware called
YourSiteBar which Mcafee dictionary defines as now a virus but part of a
download that I can't identify. I also recently downloaded SP2. It has now
disabled my printer, I get a message about the printer spool not enabled I
believe. I am quite a novice at this so please explain any help on a basic
level. Thank you for any help anyone may be able to provide. Allan

"R. McCarty" wrote:

> First I would unplug all USB devices then I would disable the
> motherboard based USB from BIOS. Remove the new PCI
> USB2 card. Start Windows, Go to Device Manager, Click
> View, Check "Show Hidden Devices". Expand the Universal
> Serial Bus Controllers category - Uninstall Everything in it.
> Then go to each category and remove the USB hosted devices
> such as Imaging devices, Printers...and HID devices.Finally,
> uninstall any USB support drivers/apps from Add/Remove
> programs applet. Then install the latest chipset driver package
> for your motherboard. Install the new USB2.0 card in either
> PCI slot #2 or 5. Then start installing your devices . I would
> also make sure the Computer driver (HAL) is an ACPI type.
> I've seen issues with USB on PCs that are using a "Standard
> PC" HAL.
>
> "Kerry Brown" <kerry@kdbNOSPAMsys-tems.c*a*m> wrote in message
> news:eWrK2uArFHA.3016@TK2MSFTNGP12.phx.gbl...
> > "Bruce Chastain" <bachastain@XNOSPAMXsbcglobal.net> wrote in message
> > news:%> that mount as disk drives, and those both cause the BSOD.
> >>
> >> My conclusion is this. It's a Windows bug. By purchasing a USB PCI
> >> card, I believe I'm eliminated all hardware and driver issues (the card
> >> came with its own drivers). And by duplicating the BSOD in Safe Mode, I
> >> believe I've eliminated all optional software issues. All that's left is
> >> a Windows bug. Why more people aren't experiencing this is a mystery.
> >>
> >
> > Because it's not a Windows bug? I have seen this problem a few times.
> > Everytime so far it has been a bad driver. Unfortuantely the only way I've
> > been able to determine which driver was by doing a clean install then
> > installing thngs one at a time until it breaks. SP2 changed USB quite a
> > bit for security reasons. Many pre SP2 drivers now exhibit this behaviour.
> >
> > Kerry
> >
> >
>
>
>