You disable a Peripheral Component Interconnect (PCI) device on a computer that is running Windows Vista, Windows Server 2008, Windows 7 or Windows Server 2008 R2. However, the PCI device is enabled unexpectedly after you resume the system from hibernation.

Consider the following scenario:

• You have a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Vista Service Pack 2 (SP2).
• That computer uses internal eHome Infrared Receiver.
• You resume the computer from hibernation.

In this scenario, a Windows Media Center remote control does not work. Additionally, you cannot find the eHome Infrared Receiver item in Device Manager. Instead, you find an Unknown device under Universal Serial Bus controllers. This issue also occurs when a Windows Vista-based computer changes from standby to hibernation when the hybrid sleep feature is enabled.

On a computer that is running Windows Vista or Windows Server 2008, you receive the following Stop error message when you resume the system from sleep mode:

Stop 0×000000FE (00000008, 00000006, 00000001, parameter4)
BUGCODE_USB_DRIVER

Notes:

• The parameters in this Stop error message may vary, depending on the configuration of your computer. Typically, the first three parameters are 8, 6 and 1. However, the fourth parameter varies.
• The symptoms of the Stop error may vary, depending on your computer’s system failure options. For example, your computer may restart when the Stop error occurs.

After resuming a computer running Windows Vista from sleep (S3) or hibernation (S4), with the monitor powered off, you cannot see a logon screen and will not be able to logon.

Assume you connect a high-speed USB 2.0 device to a computer that is running Windows Vista or Windows Server 2008. After you put the computer into hibernation and then resume the computer, the USB 2.0 device is recognized incorrectly as a full-speed device instead of a high-speed device. Therefore, the transmission speed over the USB connection is significantly reduced.

This problem occurs occasionally.

In Windows Vista or Windows Server 2008, you create a task in Task Scheduler, and then you select the Wake the computer to run this task option. This option makes sure that the computer wakes up from sleep or from hibernation to run the task. In this scenario, the scheduled task wakes up the computer as scheduled. However, 120 seconds later, the operating system resumes sleep or hibernation even if the scheduled task is running. Therefore, the scheduled task is suspended unexpectedly.

Note: The issue does not occur if the scheduled task calls the SetThreadExecutionState() function.

You are using a Windows Vista-based or Windows Server 2008-based computer has multiple video cards installed. When the computer resumes from sleep (S3), the operating system may stop responding.

Note: If you are running an application that uses the DirectX kernel driver, a black screen may appear.

You may see a blank screen upon log-in if you have disconnected one of multiple monitors while the system was locked in screen saver mode

Consider the following scenario. You have a portable computer that runs Windows Vista or Windows Server 2008. You put the computer to sleep (S3) while the computer’s lid is open. Then, you close the lid while the computer is asleep. Later, you open the lid to wake up the computer.

In this scenario, the computer starts resuming. However, you only see a blank screen and a mouse pointer until you provide some user input. For example, this situation lasts until you press a key or click the mouse.

Note: This problem occurs only on certain computers.

You establish a dial-up connection on a Windows Vista-based computer by using USB modem device. Then, you put the computer into standby (the S3 power state). After you resume the computer from standby, you cannot establish a new connection, and you may receive the following error message:

Failed to connect to ConnectionName

Additionally, after you receive the error message, the following error may be logged in the Application log:

Log Name: Application
Source: RasClient
Event ID: 20227
Level: Error
Description:
CoID={XXXXXXXX-XXXX-XXXX-XXXXXXXXXXXXXXXXX}: The user UserName dialed a connection named ConnectionName which has failed. The error code returned on failure is 633.