USB 2.0 issues in Windows 8 on motherboards with Intel 6 Series Chipset
After the upgrade to Windows 8, I noticed a strange problem: after the sleep mode, and sometimes with a cold start, I could not log in to the system because neither the mouse nor the keyboard was functioning! I hasten to disappoint those who are faced with this problem, there is no intelligible solution yet.
So, the reason was found pretty quickly. It turns out that sometimes when you start the system, one or both USB 2.0 controllers simply do not function. If you watch the device manager, then one or both of the following devices are stopped (yellow exclamation mark):
Accordingly, none of the connected devices is functioning. Interestingly, the problem disappears by itself when rebooting.
')
At first, I thought that the problem was in the motherboard (ASUS P8P67 Pro), but google suggested that the problem arose not only from me . Remarkably, in Windows 7, this problem is not observed.
Scrolling through the topic, I found the following solutions to the problem.
I have an additional USB 3.0 controller on the motherboard. Accordingly, the simplest solution would be to flush critical devices onto its ports. I personally tried this method, everything works. Unfortunately, USB 3.0 ports are significantly smaller than 2.0.
It is advised to disable USB Legacy Mode in BIOS. Judging by the topic, it helps not everyone, the problem may come back. It did not help me.
Or not with everything manually, but with the help of the task scheduler for the activation event. To do this, use the devcon tool. The launch string will be approximately as follows:
Adjusted for device ID from Device Manager.
It is proposed to remove the “LowerFilters” and “UpperFilters” parameters in the registry at.
I have not checked.
Glitch is unpleasant, although you can live with it. I was already going to change the motherboard, but it turned out that the problem is still software. Unfortunately, it is not known whether we will wait for some kind of reaction from Intel or Microsoft, for already several revisions of the drivers have flown by, but things are still there.
Problem
So, the reason was found pretty quickly. It turns out that sometimes when you start the system, one or both USB 2.0 controllers simply do not function. If you watch the device manager, then one or both of the following devices are stopped (yellow exclamation mark):
- Intel® 6 Series / C200 Series Chipset Family USB Enhanced Host Controller - 1C2D
- Intel® 6 Series / C200 Series Chipset Family USB Enhanced Host Controller - 1C26
Accordingly, none of the connected devices is functioning. Interestingly, the problem disappears by itself when rebooting.
')
At first, I thought that the problem was in the motherboard (ASUS P8P67 Pro), but google suggested that the problem arose not only from me . Remarkably, in Windows 7, this problem is not observed.
Scrolling through the topic, I found the following solutions to the problem.
Use additional controller
I have an additional USB 3.0 controller on the motherboard. Accordingly, the simplest solution would be to flush critical devices onto its ports. I personally tried this method, everything works. Unfortunately, USB 3.0 ports are significantly smaller than 2.0.
Disable USB Legacy Mode
It is advised to disable USB Legacy Mode in BIOS. Judging by the topic, it helps not everyone, the problem may come back. It did not help me.
Manual restart
Or not with everything manually, but with the help of the task scheduler for the activation event. To do this, use the devcon tool. The launch string will be approximately as follows:
devcon.exe restart "@PCI\VEN_8086&DEV_1C26&SUBSYS_04A91028&REV_04\3&11583659&0&E8" Adjusted for device ID from Device Manager.
Registry hack
It is proposed to remove the “LowerFilters” and “UpperFilters” parameters in the registry at.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36FC9E60-C465-11CF-8056-444553540000} I have not checked.
Total
Glitch is unpleasant, although you can live with it. I was already going to change the motherboard, but it turned out that the problem is still software. Unfortunately, it is not known whether we will wait for some kind of reaction from Intel or Microsoft, for already several revisions of the drivers have flown by, but things are still there.
Source: https://habr.com/ru/post/174613/
All Articles