Emrys said:
Emrys Davies said:
J. P. Gilliver (John) said:
In message <
[email protected]>, Peter Foldes
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/erro
r-code-43-when-usb-not-recognised/6a2a5531-8b80-4798-9aa6-ee2dcb705c7f
JS
To save others the tedium of working through the above very terse
reply: the suggestion (when you eventually get to it) is to shut
down, then disconnect the power, including the battery if a laptop,
for a few minutes. There are several very grateful replies (these are
from people for whom assorted USB devices don't work, including in
one case all USB devices, rather than just people getting the error
occasionally), saying this solution worked, and at least one who said
it didn't.
It sounds to me as if one of your USB devices - probably one of the
hubs on the motherboard - is occasionally saying it has a fault; why,
I have no idea, though loose connection [possibly inside an IC,
though )-:] which comes to light at a certain connection seems to me
the most likely.
If you can reliably cause it to repeat, that might pin it down. It
might also help to find out which device it is, and which device(s)
are connected to it (through it if it's an internal hub). Things that
can be connected via an internal USB hub include the webcam and the
wifi, especially on laptops. (I say useful as if it gets worse it'd
be useful to know how important it is.)
--
J. P. Gilliver. UMRA: 1960/<1985
MB++G.5AL-IS-P--Ch++(p)Ar@T0H+Sh0!:`)DNAf
If vegetarians eat vegetables,..beware of humanitarians!
Thanks for that. I am going to try and determine what I am doing when
this error occurs and then we will have something to work on. It is
no problem other than being an occasional pop-up at the moment.
I went to backup my PC to my external drive and found that it was greyed
out with a big red X. I changed its USB port and it worked fine. So
hopefully that is the problem.
Depending on the motherboard, if it's an enthusiast type, you can
try bumping up Vsb (southbridge, home of USB ports) by one notch.
Vsb is the low voltage fed to the Southbridge core logic (while
+5VSB powers the USB pad logic and I/O, comes straight from the
ATX supply, and is not adjustable).
I had to bump up Vnb (northbridge) on my current motherboard,
after a "sudden attack" out of the blue, of RAM errors. The machine
has remained stable after the adjustment. And I don't know why that
happened, or if it will happen again.
Normally, chipset voltage adjustments are not required, and
things like Dell/HP/Acer/Gateway systems may not have adjustable
chipset voltages or a BIOS entry for such adjustments. In which case,
you have one fewer option at your disposal.
Since the OP is experiencing an intermittent problem, I don't
think some logic is necessarily stuck in an illegal state. It
sounds like a malfunction, like some logic receiving weak power
and not being able to hold state info properly.
Problems like this can also be causes by overheating of
the Southbridge. If the SB goes to 110C for example, I'd expect
the USB ports to get a little feisty.
*******
Good hardware design, includes a check for "resetability". We would
not release a design to manufacturing, unless it passed an "X check",
meaning hardware nodes in the chip were all reset in simulation to
a known value. That's a defense against insane hardware states by
undefined logic values.
Now, in their defense, things like the Southbridge, keep portions
of hardware powered during sleep or hibernate, and some of the
logic is in the "CMOS well". Perhaps it just isn't possible to
meet the reset criterion, and that is a place some "insane" hardware
could live. And then, the suggestion to unplug the PC and pull
the CMOS battery is in order. But releasing such designs to
manufacturing, is irresponsible - I've heard whiny excuses from
designers before, when I catch them releasing designs with that
flaw in them, and I'm not buying their excuses
*******
Note that, on modern computers, the SATA drive is not guaranteed
to be resettable. If you're having problems getting a computer
to boot or to recover after a crash, the root cause is insanity
on the SATA drive. And the solution is to power off the ATX supply
for a moment, to give the hard drive reset cct a chance to work
at the next powerup. That will clear it. That is an example of
bad architecture - on IDE drives, the cable has a reset facility,
while on SATA, it does not. (I don't know how it's supposed to work,
but it didn't work for me.) I wouldn't say this, without having
experienced an insane SATA drive here, where pressing the reset
button multiple times, yielded no change. But powering off helped.
That kind of fault doesn't require pulling the CMOS battery, because
it's the reset circuit on the SATA drive that we're after. And
killing +5 and +12 to the drive is enough to fix it, and cause
it to go through the startup sequence again.
Paul
