A hotfix is available for Windows Vista that addresses excessive power use during sleep or hibernation. This problem presents the following symptoms.

Symptom 1
If you put the computer to sleep or into hibernation when it is running on AC power, the high definition (HD) audio controller continues to use power. Additionally, even after the computer transitions to DC power while the computer is asleep or in hibernation, the HD audio controller still uses power. This behavior persists even though you disable the “Allow this device to wake the computer” option in the HD audio controller properties.

Symptom 2
After you disable the “Allow this device to wake the computer” option in the HD audio controller properties, the Wake on Ring feature still wakes the computer from sleep or hibernation.

Even after you apply hotfix 949514 on the computer, you still experience this problem.

Consider the following scenario:

• You run Windows Vista or Windows Server 2008 on a portable computer that has multiple hybrid graphics processing units (GPUs).
• A GPU mode transition occurs. This usually occurs when you unplug the AC power cord and the computer switches to power saving mode.
• You try to put the computer to sleep or into hibernation.

In this scenario, the computer crashes.

On Windows Vista with the Swedish Language Pack installed, Sleep is incorrectly labeled under the Power Options in the Control Panel. It shows as Vilollage instead of Vila.

Consider the following scenario:

• You have a computer that runs Windows Vista or Windows Server 2008.
• The computer has multiple SATA ports, and the disk controller is configured in the BIOS to operate in IDE mode.
• You have a hard disk attached to a SATA port that is exposed as the device 1 (secondary) port.
• There is no hard disk attached to the device 0 (primary) port of the same channel as the hard drive.

In this scenario, you may experience a delay of several seconds when the computer resumes from sleep. This behavior causes the computer to fail Windows Logo Program requirements for standby resume times.

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.

On a Windows Vista SP1-based computer, you have the Feature Pack for Wireless (update 942567) installed. On this computer, after you scan for about 25 Bluetooth devices, you try to put the computer into Sleep (S3) mode. In this scenario, you receive a Stop error message that resembles the following:

STOP: 0x0000007F (0×00000008, parameter2, parameter3, parameter4)
UNEXPECTED_KERNEL_MODE_TRAP

After you put a Windows Vista-based computer to sleep (S3), you may be unable to use a remote control to wake up the computer. However, you can use the mouse or the keyboard to wake up the computer.

This problem occurs if you install a TV tuner that has an integrated infrared (IR) remote control in a specific Peripheral Component Interconnect Express (PCIe) slot.

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.

On a Microsoft Windows-based computer, you perform a surprise removal of a universal serial bus (USB) device. When you try to put the operating system into S3 sleep (standby), the operating system may stop responding. When this problem occurs, the Plug and Play (PnP) manager may be unable to process any device removal actions or any device enumeration actions.

This problem occurs if the USB device is implemented by a Kernel-Mode Driver Framework driver that reads data from a bulk endpoint on the USB device. To do this, the Kernel-Mode Driver Framework driver uses a continuous reader. A continuous reader is a framework-supplied mechanism.

You experience the following issues on a computer that is running Windows Vista or Windows Server 2008.

Issue 1
Consider the following scenario:

• The computer supports hot-plugging of Peripheral Component Interconnect (PCI) Express graphics devices.
• On the computer, you install the driver for an external PCI Express hot-pluggable graphics device.
• You hot-plug the graphics device into the computer through a PCI Express cable or by using another method.

In this scenario, the external graphics device is not recognized the first time that it is hot-plugged. Or, the driver for the external graphics device is not loaded as expected, and you receive the following error message:

Incompatible Display Adapter is being disabled

Issue 2
Consider the following scenario:

• The computer supports hot-plugging of PCI Express graphics devices.
• The computer has an external PCI Express hot-pluggable graphics device.
• You connect multiple monitors to the computer.
• You configure a monitor on the external PCI Express graphics device as the primary monitor.
• You put the computer to sleep (S3) or into hibernation (S4).
• While the computer is asleep or in hibernation, you hot-unplug the PCI Express graphics device.
• You resume the computer from sleep or from hibernation.

In this scenario, you see a black screen. However, on a monitor that is connected to the internal graphics device, you expect to see either a logon dialog box or the desktop.

Note: These issues occur even after you apply hotfix 956756 on the computer.