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.

Assume that a Secure Digital (SD) memory card slot is enabled on a Windows Vista-based or Windows Server 2008-based computer. When you try to put the computer into either standby or hibernation, the system stops responding (hangs).

This problem occurs randomly.

Consider the following scenario:

• You are running Windows Server 2003, Windows Vista, or Windows Server 2008 on a computer that has a multi-core processor installed.
• You put the computer to standby, and then you resume the computer.
• You put the computer to standby again, and then you try to resume the computer.

In this scenario, the computer stops responding (hangs), and the monitor never turns on again.

This problem occurs after you apply hotfix 951126 on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

951126 A multiprocessor computer that is running a Microsoft Windows operating system stops responding on a black screen after you resume the computer from hibernation

When you have a Windows Vista-based computer that is connected to a USB optical disc drive, and you resume the computer from Standby, you may receive a error message that resembles one of the following error messages:

STOP: 0×000000E4 (parameter1, parameter2, parameter3, parameter4)
STOP: 0×0000000A (parameter1, parameter2, parameter3, parameter4)

Notes

• The parameters in the error message vary, depending on the configuration of the computer.
• This issue may occur on a computer that is running Windows Vista, Windows Vista Service Pack 1 (SP1), or Windows Server 2008.
• Not all “0×000000E4″ or “0×0000000A” Stop errors are caused by this problem.

Consider the following scenario:

• You are running a Windows Vista-based computer that has a Blu-ray optical device and an AMD SB700 reference board installed.
• You use an application such as Pwrtest.exe or Sleeper.exe to set an RTC wake-up time on the computer.

In this scenario, you cannot resume the computer from hibernation (S4) or from standby (S3). However, if you press any key or the power button, the system resumes correctly.

Consider the following scenario:

• You are running a Windows Vista-based computer.
• This computer has a USB device, such as a USB fingerprint reader, attached.
• You resume the computer from standby or from hibernation,

In this scenario, you may receive the following Stop error message:

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

Note: In this error, the value of the Parameter4 placeholder may vary.

• An investigation of GUI changes found in Windows Vista SP1
  This article takes a look at a few of the visible changes in SP1 and explores some of the advantages and disadvantage of these changes.
  (tags: Review SP1 )
• The Road to Know Where: Microsoft Releases System Update Readiness Tool for Windows Vista
  System Update Readiness Tool checks for inconsistencies in the Windows system resources which may prevent the successful installation of future updates, service packs, and software (i.e. file data, registry data, and in-memory data)
  (tags: Updates )

Keep reading →

This article is intended to describe the steps that are used to troubleshoot performance-related issues with standby, resume, or hibernation, which vary depending on the point at which the issue occurs. Keep reading →

Consider the following scenario:

• You install a Bluetooth device on a Windows Vista-based computer, and then you turn the device on.
• You put the computer into standby (the S3 power state) or into hibernation (the S4 power state).
• You resume the computer from standby or from hibernation.

In this scenario, the Bluetooth device no longer works . Additionally, a yellow exclamation mark (!) appears next to the device in Device Manager. When you view the device properties, the device status is reported as code 43.

Consider the following scenario:

• You are running a Windows Vista-based computer.
• You resume the computer from standby (S3).

In this scenario, a bus driver that manages a Network Driver Interface Specification (NDIS) miniport is not loaded as expected. Therefore, a yellow exclamation mark (!) appears in Device Manager next to the device that is driven by the miniport. The driver also displays error code 38 (CM_PROB_DRIVER_FAILED_PRIOR_UNLOAD).

For example, this problem may occur on a bus driver that manages a USB composite device that includes a network adapter.