It's back: "HI-SPEED USB Device Attached To non-HI-SPEED Hub"

WinXP with all patches, updates, etc in place.

Suddenly I've started getting the "HI-SPEED USB Device Attached To
non-HI-SPEED Hub" error again after about a half-year or so of absence.
Nothing on my system has changed with the possible exception of the recent
WinXP updates.

What to do? Rolling back to an earlier restore point is no longer an option.

--
Bob
http://www.kanyak.com

What Chipset are you running, system specs, custom?
Case type? Is your grounding good, are all ports affected?
Have you pulled the board & isolated it on the bench to eliminate grounding
issues?

--
Thx.
Y_not
"Opinicus" <gezgin@spamcop.net> wrote in message
news:esSou%23A3IHA.5024@TK2MSFTNGP03.phx.gbl...
> WinXP with all patches, updates, etc in place.
>
> Suddenly I've started getting the "HI-SPEED USB Device Attached To
> non-HI-SPEED Hub" error again after about a half-year or so of absence.
> Nothing on my system has changed with the possible exception of the recent
> WinXP updates.
>
> What to do? Rolling back to an earlier restore point is no longer an
> option.
>
> --
> Bob
> http://www.kanyak.com
>

How does this pertain to Windows Update, Bob?

Opinicus wrote:
> WinXP with all patches, updates, etc in place.
>
> Suddenly I've started getting the "HI-SPEED USB Device Attached To
> non-HI-SPEED Hub" error again after about a half-year or so of absence.
> Nothing on my system has changed with the possible exception of the recent
> WinXP updates.
>
> What to do? Rolling back to an earlier restore point is no longer an
> option.

"Opinicus" <gezgin@spamcop.net> wrote in message
news:esSou%23A3IHA.5024@TK2MSFTNGP03.phx.gbl...
> WinXP with all patches, updates, etc in place.
>
> Suddenly I've started getting the "HI-SPEED USB Device Attached To
> non-HI-SPEED Hub" error again after about a half-year or so of absence.
> Nothing on my system has changed with the possible exception of the recent
> WinXP updates.
>
> What to do? Rolling back to an earlier restore point is no longer an
> option.
>
> --
> Bob
> http://www.kanyak.com

This drove me crazy for a long time before I fixed it. (the advice I got
from the computer manufacturer was to wipe my hard disk and reinstall
windows). Useless.

First, uninstall your USB drivers and let windows reinstall them. (Control
panel - system - hardware - device manager). Expand Universal Serial Bus
Controller (last one?), right click on each and uninstall. Then reboot.

If that doesn't work, then you may need a power USB hub. Your computer may
just be getting tired.

Hi there,

A driver probably from MS update messed up your enhanced usb controller as
computers do not get tired (lol)

Good luck on your quest.

Best regards,
Michel Denie


"its_my_dime" <its_my_dime@yahoo.com.spam (hold the .spam)> wrote in message
news:uhYZKYK3IHA.2064@TK2MSFTNGP02.phx.gbl...
>
> "Opinicus" <gezgin@spamcop.net> wrote in message
> news:esSou%23A3IHA.5024@TK2MSFTNGP03.phx.gbl...
>> WinXP with all patches, updates, etc in place.
>>
>> Suddenly I've started getting the "HI-SPEED USB Device Attached To
>> non-HI-SPEED Hub" error again after about a half-year or so of absence.
>> Nothing on my system has changed with the possible exception of the
>> recent WinXP updates.
>>
>> What to do? Rolling back to an earlier restore point is no longer an
>> option.
>>
>> --
>> Bob
>> http://www.kanyak.com
>
> This drove me crazy for a long time before I fixed it. (the advice I got
> from the computer manufacturer was to wipe my hard disk and reinstall
> windows). Useless.
>
> First, uninstall your USB drivers and let windows reinstall them. (Control
> panel - system - hardware - device manager). Expand Universal Serial Bus
> Controller (last one?), right click on each and uninstall. Then reboot.
>
> If that doesn't work, then you may need a power USB hub. Your computer may
> just be getting tired.
>
>
>

realcestmoi wrote:

> A driver probably from MS update messed up your enhanced usb controller as
> computers do not get tired (lol)

I'm not sure it's quite that cut-and-dried. A power supply could in principle
fail slowly, i.e., be unable to produce as much power as the computer needs to
function properly but not be completely dead. I don't know how frequently this
happens in practice, maybe never.

I do have experience with two different computer models which exhibited a high
failure rate after reaching a certain age. In many cases, if you gave them a
"rest", i.e., physically disconnected them from the mains for a week or so,
they'd revive and function normally for several months. This amounts to the
computer "being tired". (The underlying issue in one case was related to
inadequate cooling, in the other to dodgy capacitors on the motherboards.)

(In this case, I'd agree that a driver issue is at least as likely as a hardware
issue, and should be investigated first.)

Harry.

"PA Bear [MS MVP]" <PABearMVP@gmail.com> wrote

>> Suddenly I've started getting the "HI-SPEED USB Device Attached To
>> non-HI-SPEED Hub" error again after about a half-year or so of absence.
>> Nothing on my system has changed with the possible exception of the
>> recent
>> WinXP updates.

> How does this pertain to Windows Update, Bob?

I was wondering if one of the recent updates might have undone something
that had been fixed on the USB front. For example the problem of system
restore being turned on every time a USB drive was attached seemed to have
been fixed--at least it went a way a few months ago. Now it's back too.

--
Bob
http://www.kanyak.com

Opinicus wrote:
> "PA Bear [MS MVP]" <PABearMVP@gmail.com> wrote
>
>>> Suddenly I've started getting the "HI-SPEED USB Device Attached To
>>> non-HI-SPEED Hub" error again after about a half-year or so of absence.
>>> Nothing on my system has changed with the possible exception of the
>>> recent
>>> WinXP updates.
>
>> How does this pertain to Windows Update, Bob?
>
> I was wondering if one of the recent updates might have undone something
> that had been fixed on the USB front. For example the problem of system
> restore being turned on every time a USB drive was attached seemed to have
> been fixed--at least it went a way a few months ago. Now it's back too.

Not that I'm aware of, no.