Code 43

I have Win. 7 64 bit Home Premium

I keep getting this error: One of the USB devices attached to this computer
has malfunctioned and Windows does not recognize it.

It is an Unknown Device - one of the USB Root Hub (8 ports)

It says: Windows has stopped this device because it has reported problems
(Code 43)

It also says: No driver files are required or have been loaded for this
device (I found this after I gave Windows the chance to replace the driver)

Recommendation: Try reconnecting the device. If Windows still does not
recognize it replace the device.

Is it best that I Disable or Uninstall this device?

"Emrys Davies" <> wrote in message
news:...
> I have Win. 7 64 bit Home Premium
>
> I keep getting this error: One of the USB devices attached to this
> computer has malfunctioned and Windows does not recognize it.
>
> It is an Unknown Device - one of the USB Root Hub (8 ports)
>
> It says: Windows has stopped this device because it has reported problems
> (Code 43)
>
> It also says: No driver files are required or have been loaded for this
> device (I found this after I gave Windows the chance to replace the
> driver)
>
> Recommendation: Try reconnecting the device. If Windows still does not
> recognize it replace the device.
>
> Is it best that I Disable or Uninstall this device?

What is the device that you're plugging in? Does it cause an error on any
other PC?
--
SC Tom

"SC Tom" <> wrote in message news:jea6bd$5ue$...
>
>
> "Emrys Davies" <> wrote in message
> news:...
>> I have Win. 7 64 bit Home Premium
>>
>> I keep getting this error: One of the USB devices attached to this
>> computer has malfunctioned and Windows does not recognize it.
>>
>> It is an Unknown Device - one of the USB Root Hub (8 ports)
>>
>> It says: Windows has stopped this device because it has reported
>> problems (Code 43)
>>
>> It also says: No driver files are required or have been loaded for this
>> device (I found this after I gave Windows the chance to replace the
>> driver)
>>
>> Recommendation: Try reconnecting the device. If Windows still does not
>> recognize it replace the device.
>>
>> Is it best that I Disable or Uninstall this device?
>
> What is the device that you're plugging in? Does it cause an error on any
> other PC?
> --
> SC Tom
>
>

I am not plugging anything in, the error just pops up from time to time
while I am using my pc.

http://answers.microsoft.com/en-us/w...6-ee2dcb705c7f

JS

In message <jea7rv$8l3$>, Peter Foldes
<> writes:
>http://answers.microsoft.com/en-us/w...-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!

"J. P. Gilliver (John)" <> wrote in message
news:...
> In message <jea7rv$8l3$>, Peter Foldes
> <> writes:
>>http://answers.microsoft.com/en-us/w...-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.

"Emrys Davies" <> wrote in message
news:...
>
> "J. P. Gilliver (John)" <> wrote in message
> news:...
>> In message <jea7rv$8l3$>, Peter Foldes
>> <> writes:
>>>http://answers.microsoft.com/en-us/w...-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.

"Emrys Davies" <> wrote in message news:...
>
> "Emrys Davies" <> wrote in message news:...
>>
>> "J. P. Gilliver (John)" <> wrote in message news:...
>>> In message <jea7rv$8l3$>, Peter Foldes <> writes:
>>>>http://answers.microsoft.com/en-us/w...-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.

If this is a PC, and you have a fairly decent level of mechanical/electrical expertise, you could check the socket where
it's soldered to the MB and see if maybe the connection has broken free (that happens occasionally over time from use).
I find a lighted magnifying glass very useful for this. If it's cracked, you'll see it easily enough with one. Or it may
be a cold solder joint, in which case the solder will be a dull silver or whitish color. If either situation seems to be
the problem, a small solder iron can fix that for you.
It's possible that the contact(s) in the socket itself may have come free. You should be able to see it if that's the
case. Not too much you can do to fix that thought, other than replacing the socket with a new one.

If it's one of the front sockets, check the cabling to the MB, and each of the sockets for bad solder connections or
loose contacts.

Check the inside of the case for dust bunnies, pet hair, etc. It's possible that there's an overheating problem that's
causing it to intermittently throw the error.

If this is a laptop, you can do the same checks and repairs, but they're a bit harder to take apart to get to the MB.
--
SC Tom

On Sat, 7 Jan 2012 21:02:15 -0000, "Emrys Davies" <>
wrote:

>
>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.

My XP PC was giving me random errors a few years back. Finally, it
wouldn't even boot up. I went on-line with my other PC and started
reading the cause for the error message. (I forget what it said).

Anyway, one cure I read was a bad IDE cable to my DVD-ROM. I actually
have master and slave DVDs, so I unplugged them both. And the PC
booted right up! I then replaced the ribbon cable and had no problems.

So, is it a USB port from your MB or an add-on card reader? It could
be a bad cable or a bad card reader.

Brian

Emrys Davies wrote:
>
> "Emrys Davies" <> wrote in message
> news:...
>>
>> "J. P. Gilliver (John)" <> wrote in message
>> news:...
>>> In message <jea7rv$8l3$>, Peter Foldes
>>> <> writes:
>>>> http://answers.microsoft.com/en-us/w...-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