Windows 7 forum: Windows 7 PROBLEM with USB 3.0 PART FOUR - Green Shoots

Windows 7 PROBLEM with USB 3.0 PART FOUR - Green Shoots Rev. 1.0
" PART of the PROBLEM, part of the solution "

SYMPTONS: Original application of change to Registry (Edit)
On a computer that is running Windows 7 or Vista with Service Pack 2 (SP2), you press any key on the keyboard to resume the computer from sleep or from hibernation. However, the keyboard and the mouse become unresponsive for a long time after the logon screen appears. It may take more than twenty seconds before you can use the keyboard and the mouse.

This issue occurs on some systems that use a wireless keyboard and mouse.
http://support.microsoft.com/kb/969711/
http://answers.microsoft.com/en-us/windows/forum/windows_vista-desktop/mouse/924b2360-ce21-4f32-8736-b2b801555109

SYMPTONS: Proposal to apply method to USB 3.0 Non-Start Issue
On a computer that is running Windows 7 / 8 , (Vista Not Tested here), having established that USB 3.0
connection issue is solved by Reinstalling Driver and maintained until ReStart/Boot (no Dropouts/Disconnection)

This issue occurs on some systems with PCI, PCIe, Onboard USB 3.0 Host Controllers
This 'WorkAround' does NOT Resolve the USB 3.0 ' non-start' Issue, but reduces by Appx. 50% the number [See Table at End] of
Re-Installation cycles required for connection **

SEE:

Windows 7 PROBLEM with USB 3.0 For Some (the Routine ** )
Windows 7 PROBLEM with USB 3.0 PART TWO - Continuing Quest
Windows 7 PROBLEM with USB 3.0 PART THREE - Interim Report
Windows 7 PROBLEM with USB 3.0 PART FOUR - Green Shoots (this)

Links: @ end, below


CAUSE:

USB 3.0 Host Controller (Hardware/Software) / Operating System (O/S) / CHIPSET Issues

RESOLUTION:

To resolve this issue, add the ForceHCResetOnResume registry entry for the USB universal host controllers. To do this, follow these steps:

:
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows
http://support.microsoft.com/kb/969711/
http://answers.microsoft.com/en-us/windows/forum/windows_vista-desktop/mouse/924b2360-ce21-4f32-8736-b2b801555109

(Here are the steps but they are also included in the KB article along with more details about this issue:)

[MODIFIED For USB 3.0 application]

*** 322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows ***
+
***AT YOUR OWN RISK - IF NOT COMFORTABLE WITH REGEDIT - BETTER TO NOT PROCEED ***

Step 1: Determine the specific USB universal host controller (Simpler - only One USB 3.0 Host Controller)
a. [Click Start, type device manager in the Start Search box, and then click Device Manager in the Programs list. ]

Click Control Panel / Hardware and Sound / Device Manager

b. (On the View menu, click Devices by Type)

Locate Universal Serial Bus Controllers & Expand (Click on left [node])
Locate 'manufacturer'USB 3.0 Host Controller

c. Right Click the USB 3.0 Host Controller entry, Click on Properties, then Details

d. In the Property list {Device Description (DropDown Menu) select Driver key.

e. The driver key will resemble the following: {36fc9e60-c465-11cf-8056-444553540000}\0002
Note the last four digits of this driver key.

Step 2: Add the ForceHCResetOnResume registry entry for the USB 3.0 host controller
[Not USB 3.0 Root Hub] with RegEdit


a. Click Start , type regedit in the Start Search box, and then click regedit.exe in the Programs list.

b. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\Four-digit_number
(
Notes

o In this step, Four-digit_number is a placeholder for the USB devices in the system.

o In this step, you must locate the registry subkey by using the value that you noted in Step 1e. For example, if the driver key from Step 1e. is {36fc9e60-c465-11cf-8056-444553540000}\0002, then you must look for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000}\0002

c. On the Edit menu, point to New, and then click DWORD Value.

d. Type ForceHCResetOnResume, and then press ENTER.

e. Right-click ForceHCResetOnResume for the name of the DWORD, and then click Modify.

f. In the Value data box, type 1, and then click OK.

g. Exit Registry Editor.

h. Restart the computer.

Let me know if this he;ps resolve your issue.

TABLE:


Low statiscal base, but on 10 consecutive ReStart/Boot on each system, the results were as follows:

WIN 8 - vol SAFE Average RE-I 3.0 Before
REGEDIT/ForceHCResetOnResume

WIN 8 - vol SAFE Average RE-I 1.4 After REGEDIT/ForceHCResetOnResume


WIN 7 - vol WIN_7 Average RE-I 4.0 After REGEDIT/ForceHCResetOnResume

WIN 8 - vol TESTBED Average RE-I 1.6 After
REGEDIT/ForceHCResetOnResume [DRIVE present]

WIN 8 - vol TESTBED Average RE-I 0.7 After
REGEDIT/ForceHCResetOnResume

RE-I = Re-Installing of driver (Low is better) - Flash Drive plugged in, reduces chance of connect
HDD not advisable, until after RE-I

No Solution, but an eminently Practical Work Around AND yet more evidence that something can be done
at Software Level

Links: http://support.microsoft.com/kb/969711/
http://answers.microsoft.com/en-us/windows/forum/windows_vista-desktop/mouse/924b2360-ce21-4f32-8736-b2b801555109

Example: (Before & After) RE-I = RE-Installation of USB 3.0 Host Controller driver CON = Connection on BOOT

WIN 7 (Before RegEdit)
Not Measured - poor - for Comparison, see WIN 8

WIN 7 (After RegEdit)

1 FAIL (Connect on Boot). 2 x RE_I
2. FAIL (Connect on Boot). 4 x RE_I
3. FAIL (Connect on Boot). 1 x RE_I
4. FAIL (Connect on Boot). 3 x RE_I
5. FAIL (Connect on Boot). 2 x RE_I
6. FAIL (Connect on Boot). 6 x RE_I
7.FAIL (Connect on Boot). 8 x RE_I
8.FAIL (Connect on Boot). 3 x RE_I
9.FAIL (Connect on Boot). 7 x RE_I
0.FAIL (Connect on Boot). 4 x RE_I
________
RE-I s (Average 4.0) 40 For Windows 7 after ForceHCResetOnResume registry entry RegEdit

WIN 8 (Before RegEdit)

1 CON (Connect on Boot). 0 x RE_I
2. FAIL (Connect on Boot). 4 x RE_I
3. FAIL (Connect on Boot). 4 x RE_I
4. CON (Connect on Boot). 0 x RE_I
5. FAIL (Connect on Boot). 2 x RE_I
6. FAIL (Connect on Boot). 6 x RE_I
7.FAIL (Connect on Boot). 8 x RE_I
8.FAIL (Connect on Boot). 1 x RE_I
9.FAIL (Connect on Boot). 5 x RE_I
0.CON (Connect on Boot). 0 x RE_I
________
RE-I s (Average 3.0) 30 For Windows 8 Before ForceHCResetOnResume registry entry RegEdit


WIN 8 (After RegEdit)

1 FAIL (Connect on Boot). 1 x RE_I
2. CON (Connect on Boot). 0 x RE_I
3. FAIL (Connect on Boot). 3 x RE_I
4. CON (Connect on Boot). 0 x RE_I
5. FAIL (Connect on Boot). 3 x RE_I
6. FAIL (Connect on Boot). 1 x RE_I
7.FAIL (Connect on Boot). 1 x RE_I
8.FAIL (Connect on Boot). 3 x RE_I
9.FAIL (Connect on Boot). 1 x RE_I
0.FAIL (Connect on Boot). 1 x RE_I
________
RE-I s (Average 1.4) 14 For Windows 8 after ForceHCResetOnResume registry entry RegEdit

Links:

http://communities.intel.com/docs/DOC-19413
http://rog.asus.com/forum/forumdisplay.php?39-General-Hardware-Overclocking-amp-Tweaking&s=c23edb8c7f4b0e14aaa15814700c56c2
http://windowssecrets.com/forums/forumdisplay.php/52-Windows-7
http://forums.cnet.com/windows-7-forum/?tag=contentMain;posts
http://forums.tweaktown/windows/





MAY 17, 2012