HID device communication problem after resume.

[Svetlana]

[img]i/expressions/face-icon-small-confused.gif[/img]
We have a problem with the compound device : HUB + HID Device, connected to the
VIA Usb Hub Controller.
The problem is the following:
We have service that is running all the time and communicating with the HID device.
If during going to suspend mode the HID device constantly sends report packets to the
Host (like pressing buttons in the keyboard), after the resume the service can not communicate
with the HID device, until we don't reinstall its drivers or make hard reset to the device.
It seems that the Operation System , after sending packets while going to suspend state,
wants to unload the USB or HID driver in order to fix the situation. However , the handle to the HID
device is open in the service, so the driver is not unloaded until we make reset or reinstall the drivers.
The problem occurs only in Windows 2000. Service Pack 4 is installed.
We reproduce the same in Windows XP and the problem does not happen.
Has somebody encountered the same problem?
May be there is some patch that solves the problem described above.
Will be grateful for any input.
Regards,
Svetlana.

[Access1]

The USB Host Controller driver (UHCD.SYS) has a timing problem that may cause the USB device not to enumerate under certain conditions. You can download an update to UHCD.SYS from Microsoft. Complete the following steps to determine if you need to update UHCD.SYS:

Click Start, Find, and then click Files or Folders.
In Named, type UHCD.SYS
Verify that " Look in " has the C: drive listed and that Include Subfolders is checked.
Click Find Now.
When the search is complete, right-click and then click Properties.
Click the Version tab and check the version number. If the version number is not 4.10.2223 or later, download the update from Microsoft.

[Svetlana]

Thanks a lot for the answer.
I've checked the uhcd.sys version and it is 5.0.2195,
so it is later than the version that you've specified.
May be somebody knows another possible cause
to the problem.
Thanks in advance.
Regards,
Svetlana.

[SPotter]

I have two Win 2000 systems with identical platform and devices; both running Windows 2000 Version 5.00.2195.
One of them has these random BSOD issues, with Windbg pointing to USBD.SYS.
A binary compare of the two system's WINNT\system32\drivers directory reveals that the HSBD.SYS files are binarily identical; but UHCD.SYS is different.
The 'good' system has a UHCD.SYS file Version 5.0.2195.16205
The 'rogue' system has a UHCD.SYS file Version 5.0.2195.6555
Hmmmm
How do I get the 'rogue' system to accept the UHCD.SYS file from the 'good' system? - without introducing other problems in the process!

[SPotter]

I shall try regsvr32 and report back later.