You have a computer that is running Windows 7 or Windows Server 2008 R2. When the computer enters or resumes from sleep (S3) or from hibernation (S4), the computer may crash. Additionally, you receive a Stop error message that resembles the following:
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
There are no prerequisites for applying this hotfix.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Collapse this tableExpand this table
Version
Product
Milestone
Service branch
6.1.760 0 . 16 xxx
Windows 7 and Windows Server 2008 R2
RTM
GDR
6.1.760 0 . 20 xxx
Windows 7 and Windows Server 2008 R2
RTM
LDR
GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Usbccgp.sys
6.1.7600.16669
75,776
06-Sep-2010
03:06
x86
Usbhub.sys
6.1.7600.16669
258,560
06-Sep-2010
03:07
x86
Usbccgp.sys
6.1.7600.20794
75,776
04-Sep-2010
04:06
x86
Usbhub.sys
6.1.7600.20794
258,560
04-Sep-2010
04:06
x86
Usbd.sys
6.1.7600.16385
11,880
02-Apr-2010
03:12
Not applicable
Usbehci.sys
6.1.7600.16669
42,496
06-Sep-2010
03:06
x86
Usbhub.sys
6.1.7600.16669
258,560
06-Sep-2010
03:07
x86
Usbohci.sys
6.1.7600.16385
20,480
13-Jul-2009
23:51
x86
Usbport.sys
6.1.7600.16669
284,160
06-Sep-2010
03:06
x86
Usbuhci.sys
6.1.7600.16385
24,064
13-Jul-2009
23:51
x86
Usbd.sys
6.1.7600.16385
11,880
02-Apr-2010
03:12
Not applicable
Usbehci.sys
6.1.7600.20794
42,496
04-Sep-2010
04:06
x86
Usbhub.sys
6.1.7600.20794
258,560
04-Sep-2010
04:06
x86
Usbohci.sys
6.1.7600.16385
20,480
13-Jul-2009
23:51
x86
Usbport.sys
6.1.7600.20794
284,160
04-Sep-2010
04:06
x86
Usbuhci.sys
6.1.7600.16385
24,064
13-Jul-2009
23:51
x86
Usbccgp.sys
6.1.7600.16669
75,776
06-Sep-2010
03:06
x86
Usbhub.sys
6.1.7600.16669
258,560
06-Sep-2010
03:07
x86
Usbccgp.sys
6.1.7600.20794
75,776
04-Sep-2010
04:06
x86
Usbhub.sys
6.1.7600.20794
258,560
04-Sep-2010
04:06
x86
Usbd.sys
6.1.7600.16385
5,888
13-Jul-2009
23:51
Not applicable
Usbehci.sys
6.1.7600.16669
42,496
06-Sep-2010
03:06
x86
Usbhub.sys
6.1.7600.16669
258,560
06-Sep-2010
03:07
x86
Usbohci.sys
6.1.7600.16385
20,480
13-Jul-2009
23:51
x86
Usbport.sys
6.1.7600.16669
284,160
06-Sep-2010
03:06
x86
Usbuhci.sys
6.1.7600.16385
24,064
13-Jul-2009
23:51
x86
Usbd.sys
6.1.7600.16385
5,888
13-Jul-2009
23:51
Not applicable
Usbehci.sys
6.1.7600.20794
42,496
04-Sep-2010
04:06
x86
Usbhub.sys
6.1.7600.20794
258,560
04-Sep-2010
04:06
x86
Usbohci.sys
6.1.7600.16385
20,480
13-Jul-2009
23:51
x86
Usbport.sys
6.1.7600.20794
284,160
04-Sep-2010
04:06
x86
Usbuhci.sys
6.1.7600.16385
24,064
13-Jul-2009
23:51
x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Workaround for Windows 7 and for Windows Server 2008 R2
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:
“VID&PID” is the Vendor ID and Product ID of the USB device.
“InstanceID” is an instance of the USB device.
Set the value of the UsbccgpCapabilities registry entry to 10, and then click OK.
Restart the computer to apply the change.
Note This setting prevents the USB composite (also known as "parent") device from going idle. When the device does idle, the device issues a USB Idle Notification IRP. This setting disables the timer and worker routine that checks for idle child functions. Additionally, the setting idles the parent device if all child functions are idle.