USB issues

  • Thread starter Thread starter Jim Ludwig
  • Start date Start date
J

Jim Ludwig

Hi all,
I have recently had some new usb problems that I can't explain. I have an
older Gateway P4 running
WinXP that has 2 front usb 1.0 ports and 2 rear usb 1.0 ports. I have also
installed a pci usb 2.0 card some time ago. Recently, the built in ports
have stopped working properly. If I plug my thumb drive into the front
port, it is recognized and shows up in My Computer or Windows Explorer.
However, I can't access the files on it. I get an error message about
input/output problems. Also, I have an HP Photosmart multifunction printer
plugged into the back. I keep getting balloon notifications down in the
system tray telling me that my HP Multifunction device has been
disconnected, but of course it hasn't. Furthermore, I can't print to this
printer at all. If I send a print job, the printer comes alive and I see
the status screen behaving as if it were taking in all the data prior to
printing. However, this goes on way longer than it should and finally, the
printer spits out a paper with maybe on line printed on it or if the type
was large, only half the line will be printed. So far, it appears that my
pci card is working fine. Also, there are no conflicts in Device Manager.
So evidentally, I'm having some sort of input/output issue. Any thoughts to
what is going on here?
Thanks,
Jim
 
Jim said:
Hi all,
I have recently had some new usb problems that I can't explain. I have
an older Gateway P4 running
WinXP that has 2 front usb 1.0 ports and 2 rear usb 1.0 ports. I have
also installed a pci usb 2.0 card some time ago. Recently, the built in
ports have stopped working properly. If I plug my thumb drive into the
front port, it is recognized and shows up in My Computer or Windows
Explorer. However, I can't access the files on it. I get an error
message about input/output problems. Also, I have an HP Photosmart
multifunction printer plugged into the back. I keep getting balloon
notifications down in the system tray telling me that my HP
Multifunction device has been disconnected, but of course it hasn't.
Furthermore, I can't print to this printer at all. If I send a print
job, the printer comes alive and I see the status screen behaving as if
it were taking in all the data prior to printing. However, this goes on
way longer than it should and finally, the printer spits out a paper
with maybe on line printed on it or if the type was large, only half the
line will be printed. So far, it appears that my pci card is working
fine. Also, there are no conflicts in Device Manager. So evidentally,
I'm having some sort of input/output issue. Any thoughts to what is
going on here?
Thanks,
Jim
Click to expand...

There have been a number of failures involving ICH5/ICH5R from Intel.
The USB ports blow. The logic blocks are fine, so the
USB section in Device Manager appears normal. But the physical
layer is damaged, and the ICH5/ICH5R ends up "deaf" to plugged
in USB devices.

In some cases, the chip burns. It looks like this. In cases
where the chip burns, the computer will no longer POST. So if
it happened to look like this, you'd no longer have a working
computer. This might happen right after a static discharge to
the USB port.

http://onfinite.com/libraries/179057/2ea.jpg

(Example of one that is not burned...)

http://img.tomshardware.com/de/2004...pteron_250_gegen_intel_xeon_3_6_ghz/ich5r.jpg

Your failure is likely the less fatal kind. The USB is still
damaged, but at least the computer can still boot.

Using a PCI USB card is the workaround. So you've implemented
the proper solution to fix it.

At least one Asus motherboard owner, got a new ICH5 soldered
to the motherboard, under warranty.

This is the only public warning about the problem. You will not
find this information on the Intel site, so they don't consider
you should know this. I don't know whether Intel has
provided warranty money to motherboard makers, to help
pay for the repairs.

http://tw2005.giga-byte.com/Motherboard/Support/FAQ/FAQ_456.htm

I have read one description, where the failure did not
seem to come from static discharge. One person claims the
chip burned, right after the computer was rebooted. So in
their case, the failure happened on reboot. But many others
correlate with static discharge or usage of a front USB port.

Paul
 
Paul said:
There have been a number of failures involving ICH5/ICH5R from Intel.
The USB ports blow. The logic blocks are fine, so the
USB section in Device Manager appears normal. But the physical
layer is damaged, and the ICH5/ICH5R ends up "deaf" to plugged
in USB devices.

In some cases, the chip burns. It looks like this. In cases
where the chip burns, the computer will no longer POST. So if
it happened to look like this, you'd no longer have a working
computer. This might happen right after a static discharge to
the USB port.

http://onfinite.com/libraries/179057/2ea.jpg

(Example of one that is not burned...)

http://img.tomshardware.com/de/2004...pteron_250_gegen_intel_xeon_3_6_ghz/ich5r.jpg


Your failure is likely the less fatal kind. The USB is still
damaged, but at least the computer can still boot.

Using a PCI USB card is the workaround. So you've implemented
the proper solution to fix it.

At least one Asus motherboard owner, got a new ICH5 soldered
to the motherboard, under warranty.

This is the only public warning about the problem. You will not
find this information on the Intel site, so they don't consider
you should know this. I don't know whether Intel has
provided warranty money to motherboard makers, to help
pay for the repairs.

http://tw2005.giga-byte.com/Motherboard/Support/FAQ/FAQ_456.htm

I have read one description, where the failure did not
seem to come from static discharge. One person claims the
chip burned, right after the computer was rebooted. So in
their case, the failure happened on reboot. But many others
correlate with static discharge or usage of a front USB port.

Paul
Click to expand...
I would recommend checking the event log using event viewer for more
information, from that you should be able to get a better idea of what's
actually going on.

As an administrator or an account with administrative privileges:
Start -> Run -> type eventvwr -> hit enter or click OK
 
Back
Top