Originally posted by HPgeno
I found some info for your question. You can probably find a driver for the FWH on Intel's web site. Ive included some info for you that might help familiarize yourself with it also. Good luck!

What is the FWH?
The Intel® 82802 Firmware Hub (FWH) uses flash technology to store and manage system and video BIOS, eliminating a redundant nonvolatile memory component, and enabling new security capabilities.
This also apllies to Casper's post:

Finding 'firmware hub'-problems can't be solved by typing 'firmware hub' in Google, and quoting the first reference that shows up...

Firmware apllies to either the Bios, or either a USB device.
The solution? Update the drivers

Firmware HUB definitely refers to a USB device : the USB device's firmware contains all of the information about the device - meaning that if your firmware isn't up-to-date, you have a problem.
I had the same problem with WinXP: my USB-modem (I know, forgive me) was giving problems (again). Here's the technical explanation (from the Microsoft Knowledge Base:

The symptoms of malfunctioning or incorrectly configured firmware might be unusual. Typically, when you remove and then re-add a USB device, the device simply becomes available again. However, the device may appear as a second instance of that device, and load itself as such in Device Manager. If you see duplicates of a device, verify that you have the most up-to-date firmware for that device. This issue is common with USB printers and modems. A similar issue that has the same cause occurs when a device loads a device driver and then adds a second device for which there appears to be no driver. The second device is displayed with an exclamation point in a yellow circle in Device Manager. The device may work correctly, but you cannot remove the "ghost" device until you unplug the parent device that seems to have generated the ghost device. Also, you may be able to resolve this issue by updating the firmware or the device driver for that device.
If your problem is not in the Knowledge Base, you can call it a feature, not a bug