Troubleshoot Suspend, Resume and Hibernate Problems

This page is for suspend, resume and hibernate troubleshooting. If you are looking for Shutdown Problems, they are dealt with at this link.

	The Advanced Power Management (APM) Specification defines the following power states: Ready Stand-by Suspended Hibernation Off
	This article describes how to troubleshoot hibernation and standby issues in Microsoft Windows XP. You may experience abnormal behaviour when a computer enters or leaves hibernation or standby.

	After you attach a keyboard, a mouse or another USB-based input device to your computer, your computer may no longer shut down correctly. For example, your computer may stop responding (hang) after you click Turn off or Restart. This issue may occur when the selective suspend functionality is enabled on a device that does not support it. This situation may occur when two or more USB-based devices have the same vendor and product identification numbers, and when only one of the devices supports the selective suspend functionality.
	When you return your computer from standby or suspend, your Universal Serial Bus (USB) keyboard may not function. This problem may occur on computers that use the Intel ICH2 chipset for USB functionality.
	If you bridge an Institute of Electrical and Electronic Engineers (IEEE) 1394 network adapter with another network adapter, suspend or hibernate the computer, and then resume the computer, network connectivity on the IEEE 1394 adapter may not work.
	When you resume your computer from standby or hibernation, you may receive a "USB Device Not Recognized" error message. This error message occurs only if USB/PS2 combination devices are attached to the computer. One example of such a device is a keyboard that has both USB and PS2 connectors. You can use either connector for all of the keyboard functions.
	When a scheduled task commences while a computer is sleeping, or has been suspended by the operator, the monitor continues to run in Power Management mode.
	If you repeatedly suspend and resume the operating system of a portable computer, the multifunction Personal Computer Memory Card International Association (PCMCIA) card does not work as expected. For example, if you suspend and resume a second time, the PCMCIA card stays turned on. If you suspend and resume a third time, other unexpected behaviour may occur. This unexpected behaviour may include the following: Device-specific program software does not detect the PCMCIA card. The PCMCIA card is not listed in Device Manager.
	You resume a Microsoft Windows XP-based computer (such as a graphic order terminal) from Suspend mode, and you type the first character of text on the keyboard. The first keyboard character you type is not accepted. Additional keyboard characters you type are accepted.
	When you use a remote control to resume a Microsoft Windows XP Media Center Edition 2004-based computer from suspend mode, the following event message may be logged in the event log: Event Type: Warning Event Source: kbdhid Event Category: None Event ID: 1 Date: 4/5/2004 Time: 4:54:25 PM User: N/A Computer: MCE Description: The driver has detected that this HID keyboard has bad firmware. It is issuing redundant report packets.
	You are recording Live TV in Microsoft Windows XP Media Center Edition 2005. When you press the Suspend or Hibernate button on the remote, you receive a warning message that this action will stop the recording. If you cancel the warning message and then press the Suspend or Hibernate button again, the recording is stopped. Additionally, the computer goes on standby or into hibernation. You do not receive a second warning message.
	If you swap a CardBus card after your computer resumes from suspend, your computer may stop responding (hang). This problem occurs with any PC Card device that displays a Power Management tab in its properties. If the Allow this device to bring the computer out of standby check box in the device's properties is selected, your computer may hang when you swap PC Card devices after suspending and resuming your computer.
	When you play Pinball.exe in Full-Screen mode and suspend the laptop, when you resume, the video may be distorted. The video resolution may also change to 640x480.
	When you use a remote control to resume a system from Suspend on a computer that is running Microsoft Windows XP Media Center Edition 2004, the display may be black even though the system has fully resumed.
	When you either close the lid of your laptop computer or press the closure-detection button for the lid, the back-lit LCD display may not turn off on Windows XP-based computers. If you manually enter suspend mode by pressing FN-F4, the backlight for the LCD display turns off. This problem does not occur if the laptop is connected to a CRT monitor.
	When you try to put your computer into Hibernate or Suspend mode while the system is writing data to a compact disc (CD), the computer may not enter Hibernate or Suspend mode. You may receive the following error message (or a similar one): The device driver for the '%device name%' device is preventing the machine from entering hibernation/suspend. Please close all applications and try again. If the problem persists, you may need to update this driver. You receive neither an informational message that the system is writing to a CD nor an error message that offers you the choice of stopping the CD write process or waiting until the process is complete. This behaviour occurs because you cannot put a computer into Hibernate or Suspend mode while the system is writing to a CD. Note: DUH!
	Consider the following scenario: You change the batteries on a portable computer that is in hibernation or in a suspended state, and then you resume the computer. In this scenario, one or more of the following symptoms may occur: The information that is displayed on the Power Meter tab may be incorrect. Specifically, information in the following categories on the Power Meter tab may be incorrect: Chemistry Manufacturer Total battery power remaining The computer remains in low battery hibernation mode, even though the battery may be fully charged. The computer may then shut down because the operating system mistakenly interprets the battery power to be very low.
	After you suspending and resume your computer several times, hard disk performance may be reduced. If you use Device Manager to view the properties of the IDE channel to which the drive is connected, the Advanced Settings tab may show that the current transfer mode for the drive is "PIO Mode".
	When your portable computer is running Microsoft Windows XP and IBM Tivoli Endpoint client goes on standby or hibernates to save power, and you pull the network cable at the same time, the system time freezes until the computer is reactivated. If you pull the network cable after the computer is fully on standby or in hiberation [sic], the problem does not occur. When you close the computer's lid and open it again after several minutes, the wrong system time is written to CMOS. This situation only occurs when IBM Tivoli Endpoint is running and the network adapter is active. This does not occur when either the network adapter or IBM Tivoli Endpoint is disabled when you close the portable computer lid. This may occur on a Panasonic Toughbook portable computer or on a Fujitsu Siemens Computers (FSC) Lifebook portable computer. Note: This behaviour may also occur on a Windows Server 2003-based computer.
	When a Microsoft Windows XP-based computer tries to enter standby, the computer stops responding (hangs).
	When you resume the Microsoft Windows XP-based computer from the hibernation state, the background (wallpaper) may not show on the Windows desktop. If you press SPACEBAR with a mouse pointer when the screen changes to a black screen, the background may not show on your Windows desktop. However, if you press SPACEBAR when you log on to your Windows XP-based computer, the background (wallpaper) shows on the Windows desktop.
	After your computer resumes from hibernation, the Human Interface Device (HID) audio control keys on an attached Universal Serial Bus (USB) keyboard may not work. This problem does not occur if you move the mouse or press other keys on the keyboard after the computer resumes from hibernation before you press the audio control key (such as a volume control key).
	Before the Microsoft Windows XP-based computer enters hibernation or standby, you do not hear a battery alarm sound and you do not receive a battery alarm message. This symptom occurs if the following conditions are true: You have recently configured the battery alarm settings on the Windows XP-based computer. The Windows XP-based computer enters hibernation or standby for the first time since you configured the battery alarm settings.
	Scheduled recordings may not occur or may be truncated after Microsoft Windows XP Media Center resumes (awakens) your computer from standby. Scheduled recordings may not occur if your computer goes into standby while the FM Radio feature of Media Center is playing. Scheduled recordings may be truncated if you start using Media Center after it resumes the computer from standby to start a scheduled recording.
	After a Microsoft Windows XP-based computer returns (or "wakes up") from hibernation, it may enter hibernation again after five minutes of inactivity, regardless of the settings you have configured in the Power Options tool in Control Panel.
	You may not be able to use a biometric logon device (such as a fingerprint reader or retinal scanner) to log on to Windows XP after the computer resumes from standby or hibernation. This problem typically occurs after the computer enters standby or hibernation while at the Welcome (logon) screen. When this problem occurs, you typically can use a password to log on to the computer.
	Consider the following scenario. You configure the Power Options profile in Microsoft Windows XP so that the computer enters standby after a particular period has elapsed since the last significant system activity. For example, assume that the computer is running on AC power and that you configure the standby setting to 20 minutes. When you watch the computer for 20 minutes, it does not enter standby even though the system appears to be idle. Even though the system appears to be idle, the Windows XP System Idle Task Scheduler service may be running system maintenance tasks. These tasks may trigger a reset of the System Idle counter. In this scenario, the computer does not enter standby. Note: Third-party programs and services may also be running during system idle time. These programs and services may use more than 10 percent of the computer's CPU and disk resources. This level of CPU and disk utilization may reset the System Idle counter and therefore delay the system from entering standby.
	This article describes how to troubleshoot hibernation and standby issues in Microsoft Windows XP. You may experience abnormal behaviour when a computer enters or leaves hibernation or standby. This behaviour may be caused by one of the following issues: Outdated system firmware Peripheral firmware Incompatible drivers Hardware that does not correctly support hibernation and standby This article also discusses how to determine whether a Windows XP-based computer supports Advanced Power Management (APM) features, such as hibernation or standby. When you attempt to hibernate a computer that is running Windows XP, you may receive the following message: It is now safe to turn the machine off. When you install Windows XP on a computer that is not in Advanced Configuration and Power Interface (ACPI) mode (by using a standard Hardware Abstraction Layer [HAL]) and you enable the hibernate option, the computer does not turn off (enter an S4 sleep state) as expected.
	If you pause a DVD player before it enters standby, when the player resumes from standby, you may receive an "Overlay failed" error message. You may receive this error if the following sequence of events occurs: The computer is a laptop and is connected to an external monitor. You turn on the extended desktop function on the external monitor. You start the DVD player, and then you pause the player. The computer goes into a power-saving mode (such as standby). While the computer is suspended, you disconnect the external monitor. After the computer resumes, you start the DVD player. Depending on the player that you are using, you may receive an "Overlay failed" or similar error message.
	The flush cache command is not issued to a large hard disk that has a 48-bit logical block address (LBA) enabled. As a result, the hard disk may become corrupted when you enter either the Shutdown state or the Hibernate state.
	Under the following conditions, your CD-ROM may not work after you resume your computer, and your CD-ROM may have a Code 38 status in Device Manager: Your computer was hibernating when you swapped between two ATAPI device bay CD-ROM devices; You used a data CD in the original CD-ROM drive; You removed the data CD from the original CD-ROM drive before your computer entered hibernation.
	After you enter and resume from standby, hibernate, or both multiple times, you may receive a "Stop 0xEA" error message.
	When you plug a USB device into a Windows XP-based computer immediately after the computer comes out of standby (S3) or hibernate (S4), the computer may not recognize the USB device. When this issue occurs, the USB device may be listed in Device Manager as an unknown device, and you may receive the following warning message: Unrecognized device has been found.
	If you resume your computer from hibernation after you remove the computer from a docking station, the computer may seem to stop responding (hang), and Windows Task Manager may show 100 percent CPU usage until you reboot the computer.
	The NetBIOS "computer name <03>" name (as shown by the nbtstat -n command) may remain unregistered under the following conditions: After you first unplug the network cable (for a long enough period of time to detect a Plug and Play event, about 30 seconds), and then plug the cable back in, the NetBIOS "computer name <03>" remains unregistered. When you change the TCP/IP subnet (while the computer is hibernating, connect it to another subnet, and then wake up from hibernate on the new subnet) and run the ipconfig /release command followed by the ipconfig /renew command, ipconfig/release unregisters the NetBIOS "computer name <03>" name, but ipconfig/renew does not restore it.
	Consider the following scenario. You are using a Bluetooth radio that is connected to a Microsoft Windows XP-based computer. A Bluetooth keyboard or a Bluetooth mouse is connected or has been connected to this radio. Additionally, one or more of the following conditions are true: You connect the radio to the computer. You disconnect the radio from the computer. You use a feature on a portable computer to disable or to re-enable wireless devices. The computer resumes from hibernation. In this scenario, you receive a stop error message that resembles the following: DRIVER_IRQL_NOT_LESS_OR_EQUAL STOP: 0x000000D1 (0X00000410, 0x00000002, 0x00000000,0xF89D6DC7) HIDCLASS.SYS – Address F89D6DC7 base at F89D6000, DateStamp 41107d52 Additionally, you may receive this error message if the 6.02 or a later version of Microsoft IntelliType Pro or Microsoft IntelliPoint software is installed on this computer.
	When you are using a computer that is running Microsoft Windows XP, if you run Helpctr.exe, and then send a request for assistance to a valid e-mail address, when the expert opens the request, takes control of your computer, and then leaves the computer unattended for one hour, the Remote Assistance connection is closed. When the computers are brought out of the Sleep or Hibernate state, the tool on the expert's computer is displayed as a white screen and the expert cannot submit a new text message using the chat functionality. On your computer, the tool is displayed, but the Remote Assistance connection closes if you attempt to use it. If you enable the On resume, password protect option under the Screen saver options on the server, the following behaviour occurs: The Welcome screen is displayed on the server. A blank screen is displayed on the client. No events are fired. When you return to the active session, a blank screen is still displayed on the client.
	The Microsoft Windows XP Media Center Edition 2005-based computer cannot enter hibernation. This symptom occurs if you are recording Live TV in Windows XP Media Center Edition 2005. If you press the power button on the remote or on the computer, the Stand By option appears. However, a Hibernate option does not appear. If you click Stand By, the computer correctly enters Stand By mode, and the Live TV recording is stopped. This symptom occurs even though you configure the When I press the sleep button on my computer option to Hibernate. The When I press the sleep button on my computer option is located on the Advanced tab in the Power Management tool.
	Your IBM ThinkPad portable computer that is running Microsoft Windows XP may not hibernate when you close the lid of the computer, even though you have configured it to hibernate. This behaviour occurs in the following conditions scenario: You press and hold down the Fn key and then press F4. You close the lid before the computer enters hibernation. Additionally, you may receive the following error message when you raise the lid: System Hibernation Failed : The device driver for the 'WAN miniport(PPPOE) device' is preventing the machine from entering hibernation. Please close all applications and try again. If the problem persists, you may need to update this driver.
	The SHIFT key on the Tablet PC Input Panel tool does not respond after you resume from the Hibernate state. This behaviour occurs after you use the tablet pen to put the Tablet PC in the Hibernate state.
	After you click Turn off computer on the Start menu, you may only see the following buttons even though you have enabled hibernation: Stand by Turn Off Restart Note: Computers that are on a domain that are using the classic Shut Down menu, do not have these buttons.
	When a computer running Microsoft Windows XP Service Pack 1 (SP1) resumes from hibernation, certain USB 2.0 devices may appear to be removed, and therefore they no longer function.
	You may experience one or more of the following symptoms on your Microsoft Windows XP Service Pack 1 (SP1)-based computer or your Microsoft Windows 2000 Service Pack 3 (SP3)-based computer: Universal serial bus (USB) devices are not detected when you restart the computer. USB devices are not detected after you resume the computer from hibernation or standby. The computer uses 100 percent of CPU resources when you move the USB mouse. The computer stops responding (hangs) when you resume the computer from standby when a USB mouse is connected. The computer takes a long time to start or resume when a USB device is connected. A yellow exclamation point with "Code 28" or "Code 31" appears on a USB device in Device Manager. USB 2.0 Hi-Speed devices are detected as Full-Speed (USB 1.1) devices when your computer resumes from hibernation, even though they are plugged in to a USB 2.0-capable port.
	After you resume your Microsoft Windows XP-based computer from hibernation, your computer may indicate that your wireless network connection is unavailable. This problem does not occur every time that you resume your computer from hibernation.
	When you resume your laptop computer, Windows XP may stop unexpectedly (crash), and you may receive the following error message: Stop 0x0000008E
	If a Windows XP-based computer has a wireless network adapter connected through a universal serial bus (USB) connection, and the computer resumes from standby or hibernation, the wireless connection icon may appear in the notification area (at the far right of the taskbar) with a red X and the following message: Wireless Network Connection Wireless Connection Unavailable Even though you receive this message, the wireless network connection may still be active and functioning correctly, and therefore you may still be able to successfully connect to network resources over the wireless network connection.

	The icon in the notification area (at the far right of the taskbar) for a wireless connection may show the connection as "Unavailable" after you resume your computer from standby, even if wireless connectivity is available.
	Consider the following scenario. You are running a Microsoft Windows XP-based computer. You apply a USB-related hotfix to this computer. Then, you put the computer into either hibernation or standby. However, after you resume the computer from hibernation or from standby, the hotfix no longer works. Specifically, the USB-related problem that was resolved by the hotfix occurs again after you resume the computer from hibernation or from standby.
	When all the following conditions are true, you may not be able to resume your Microsoft Windows XP-based computer when you move your USB mouse or press a key on your USB keyboard: You have a universal serial bus (USB) mouse or a USB keyboard connected to your Windows XP-based computer. You put your Windows XP-based computer in standby. While your Windows XP-based computer is preparing to enter standby, you move your USB mouse or press a key on your USB keyboard. Note: Your USB mouse and USB keyboard are both connected to the same USB host controller. Additionally, after you resume the Windows XP-based computer by using the power button, your USB mouse and your USB keyboard may not work correctly.
	When you resume your Microsoft Windows XP-based computer from standby, your universal serial bus (USB) keyboard or your USB mouse may not work if you resume operations by using any one of the special function keys on the keyboard (such as Volume Control). When you view Device Manager, the icon that represents your USB keyboard or your USB mouse may have a yellow-highlighted exclamation point in the lower-right corner. In this scenario, you must restart your computer to regain USB keyboard or USB mouse functionality.
	On some portable computer systems, the system stops responding when resuming from standby. This problem occurs on portable computer systems whose installed audio/video (A/V) streaming devices use universal serial bus (USB) connectors.
	When you have a Microsoft Natural Keyboard Elite attached a Universal Serial Bus (USB) 2.0 port, you may not be able to resume your computer from hibernation.
	A Universal Serial Bus (USB) storage device may not work when you follow these steps: You plug the device into one USB port on the computer. You put the computer into standby (S3 power state). You unplug the device while the computer is in standby. You plug the device into a different USB port while the computer is still in standby. You resume from standby. You put the computer into standby (S3 power state). You unplug the device while the computer is in standby. You plug the device into a different USB port while the computer is still in standby. You resume from standby. You unplug the device while the computer is in standby. You plug the device into a different USB port while the computer is still in standby. You resume from standby. You plug the device into a different USB port while the computer is still in standby. You resume from standby. You resume from standby. In Device Manager, an exclamation point in a yellow circle, with a status of Code 42 (duplicate device), may appear next to the device.
	After your Microsoft Windows XP-based computer resumes from hibernation, and then you use the Safely Remove Hardware function to remove a USB floppy disk drive, the computer stops responding (hangs).
	When you press a key on your Universal Serial Bus (USB) keyboard, use a USB mouse, or use the computer's power button to resume your computer from standby (an S3 state), the first keystroke may be lost. Although subsequent key strokes wake the computer, these key strokes are passed along to the program that currently has focus.
	Fixes a problem that may occur if you have an "Incoming Connections" network connection defined. Provides a hotfix to resolve the problem. You must have Windows XP Service Pack 2 installed to apply the hotfix.
	A computer that is running Microsoft Windows XP or a later operating system stops responding during resume from standby, and you receive one of the following stop error messages: KERNEL_DATA_INPAGE_ERROR 0x0000007a (e163a3e4,c000000e,bf8e9313,0697f860) 0x000000F4 (0x00000003, Parameter2, Parameter3, Parameter4)
	Consider the following scenario: You use a USB camera on a Microsoft Windows XP-based computer to capture video. You put the computer on standby. You resume the computer from standby. In this scenario, the camera waits approximately 8 seconds before it restarts video capture.
	You may experience any one of the following symptoms: Your computer automatically restarts. After you log on, you receive the following error message: Microsoft Windows The system has recovered from a serious error. A log of this error has been created. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve Microsoft Windows. We will treat this report as confidential and anonymous. To see what data this error report contains, click here. You receive the following "Stop" error message on a blue screen: A problem has been detected and Windows has been shut down to prevent damage to your computer... Technical information: *** STOP: 0x000000A5 (0x00000011, 0x00000006, 0x00000000, 0x00000000) Bug Check Symbolic Name
	If your computer has an ATA Packet Interface (ATAPI) hard disk that is larger than 137 gigabytes (GB), you may experience any of the following symptoms: Your computer may restart instead of resuming from hibernation You may experience hard disk corruption when Windows XP writes a memory dump file as a result of an unrecoverable Windows error (or Stop error) You may experience hard disk corruption when your computer enters either standby or hibernation
	You may receive the following error: STOP 0x0000009F DRIVER_POWER_STATE_FAILURE This error occurs if drivers do not handle power state transition requests properly, usually during one of the following procedures: Shutting down Suspending or resuming from Standby mode Suspending or resuming from hibernation
	If you have multiple universal serial bus (USB) devices connected to an external USB hub, when you unplug a USB device during system hibernation and then plug another USB device into the same USB port, the new USB device may not function.
	If your Windows 2000-based or Windows XP-based computer with multiple ATA drives enters the S1 power state, you may experience one of the following symptoms: Windows does not recognize the ATA drives when you resume your computer from sleep or standby. You may receive the following error message: Unsafe Removal of Device: You have unplugged or ejected a device without stopping it. Unplugging or ejecting devices without first stopping them can frequently cause your computer to crash and loose valuable data. Windows may stop responding (hang).
	If you disconnect a Universal Serial Bus (USB) camera from your computer after you suspend and then resume the computer, the camera may remain in Device Manager. If Device Manager is running when you remove the camera, Device Manager may stop responding (hang) if you try to scan for new hardware. If Device Manager is not running when you remove the camera, Microsoft Management Console (MMC) may hang when you try to start Device Manager. This problem may occur under the following conditions: Your computer is compliant with the Advanced Configuration and Power Interface (ACPI) specification. Your computer supports USB. You connect a USB camera before you suspend the computer. This problem may occur if you connect the USB camera to a USB port on either a port replicator or a docking station.
	When you resume your Windows 2000-based or Windows XP-based computer from a Standby state, the keyboard and mouse do not work.
	You resume your Microsoft Windows XP-based computer from standby while your network is either disconnected or down. After network connectivity is restored, you lose access to your network resources. Additionally, if your Windows XP-based computer is moved to a different network while the computer is on standby, you lose access to network resources when you resume the computer.
	Computers that have removable disk device controllers, such as CardBus or Memory Stick, may take a long time to resume from standby if there is a disk in the controller.
	When your Microsoft Windows XP-based computer resumes from hibernation (S4), or attempts to Wake-on-LAN from standby (S3) you may experience one or more of the following symptoms: The screen is not displayed correctly, and garbled characters may appear. The screen appears blank. The computer stops responding. The symptoms may vary, depending on what video adaptor is installed in your computer.
	After you resume a Microsoft Windows XP-based computer from standby or from hibernation, some high performance PC Card (PCMCIA) devices may not work correctly. For example, a high-speed CardBus universal serial bus (USB) host controller may run slower.
	When you press the power button on the remote control to resume a Microsoft Windows XP Media Center-based computer from standby, the computer screen does not appear on your TV.
	After you install a new network device, you may receive either of the following messages when you first resume operation after the computer hibernates: You may need to run the Home Networking Wizard to continue sharing your Internet Connection. Click here to run the Home Networking Wizard. Windows has detected the installation of a new networking device. If you want to set up a network, click here to run the Network Setup Wizard.
	When you resume your Windows XP-based computer from standby, you may find that infrared communications no longer work. You cannot use the infrared port to transfer data. To restore the functionality of the infrared port, you must restart the computer after you resume the computer from standby.
	When your computer resumes from standby or hibernate, the notification balloons that appear over the notification area, at the far right of the taskbar, might be corrupted or overlapped. This issue may occur if several balloons are scheduled to be opened, and if the balloons appear at the same time instead of waiting for you to clear a previous balloon.
	If you have installed Crystal Sound Fusion 4281, MIDI file playback through the MPU-401 port unexpectedly changes tempo and continues to vary in tempo after your computer resumes from hibernation.
	When you resume your computer from hibernation, Windows Explorer may not resume from hibernation. No icons appear on the desktop, and the taskbar does not appear.
	When you resume your computer from standby or from hibernation after you switch user accounts, the Volume icon in the notification area may be displayed incorrectly. Specifically, the icon may have a thick black outline. This problem may also occur with other icons in the notification area, such as the Windows Product Activation icon. This problem occurs in a user session other than the current session.
	When you put your computer into an S4 sleep state (hibernation), and then resume it from hibernation many times, your computer may eventually stop responding (hang) before it enters hibernation. For example, the computer may stop responding after you put it into hibernation and then resume it from hibernation approximately 300 times.
	When you resume a Microsoft Windows XP-based computer from hibernation, the desktop wallpaper is redrawn slowly. This problem may be more pronounced if either of the following conditions is true: The wallpaper selection has a large file size. You have hibernated and resumed the computer several times since you last restarted it.
	When you resume your Microsoft Windows XP Media Center Edition 2005-based computer from standby or from hibernation, the Media Center window may remain black. In this scenario, the computer appears to stop responding (hang).
	After your computer resumes from hibernation, your PS/2 mouse may not work. The mouse pointer may not respond to the movement of your mouse.
	If you remove a 16-bit PC card from your computer and then insert a new 16-bit PC card, the new 16-bit PC card is not detected. This symptom occurs if the following conditions are true: You are using a Microsoft Windows XP-based computer. You change PC cards while your Windows XP-based computer is in hibernation. You resume your Windows XP-based computer from hibernation after you change PC cards.
	Consider the following scenario. You are using a computer that is running Update Rollup 2 for Windows XP Media Center Edition 2005. This computer has a dual-core processor and supports Away mode. However, when the computer resumes from Away mode, the operating system no longer throttles the CPU correctly.
	When you click Start and then click Undock, and then you remove your portable computer from your docking station or from your port replicator, your computer may not resume from standby.
	When you resume a computer that is running Microsoft Windows XP from standby while a Secure Digital (SD) media card is inserted, you receive the following error message: Unsafe Removal of Device
	When you hibernate your computer that is running Microsoft Windows XP Media Center Edition 2005, and then you resume your computer from hibernation, the Media Center window is black. If Media Center was running in full-screen mode when you put your computer into hibernation, the whole screen is black when you resume from hibernation.
	With some Dell models, when a laptop resumes from standby (S3 sleep state) after a warm undock, the video display is corrupt for a brief period of time (approximately 5 to 10 seconds). The video display returns to a normal state after the computer completes the undocking process.
	When you resume your Sony VAIO PCG-F520 computer from standby by using the USB IntelliMouse Optical, the display appears corrupted. To regain normal display, you have to restart the computer.
	Every time that you resume your computer from standby, the Handle Count value for the Winlogon.exe process may increase by one in Microsoft Windows Task Manager.
	When a portable computer that is running Microsoft Windows XP Media Center Edition 2004 resumes from hibernation, the Live TV window in Media Center may be blank and unresponsive.
	When you resume your Microsoft Windows XP Media Center Edition 2005-based computer from standby, the Windows Messenger session that was open in Media Center is not restored in the Media Center user interface (UI). You receive no additional communications in the Windows Messenger UI in Media Center.
	Under the following conditions, data that is written to a removable media storage device may be deleted from the device: Your Windows XP-based computer hibernates while a removable media storage device is inserted. Removable media storage devices may include Compact Flash, Memory Stick, SmartMedia, or Secure Digital memory devices. You remove the media, and then add data to it. You reinsert the media into the computer, and then resume from hibernation. The data that was written to the device while the computer was hibernating may be missing when you insert the media into another computer or device (such as a digital camera).
	A computer that is running Microsoft Windows XP or Microsoft Windows Server 2003 may stop responding when you select the Delete restoration data and proceed to system boot menu option while the computer is resuming from hibernation. For example, while the computer is resuming from hibernation, you receive the following message: For troubleshooting and advanced startup options for Windows, press F8. If you press F8, you receive the following message, which presents two options: Continue with Restart Delete restoration data and proceed to system boot menu. The problem occurs when you select the Delete restoration data and proceed to system boot menu option. Note: When you select the Delete restoration data and proceed to system boot menu option, the Hiberfil.sys file is deleted. Therefore, all information about the operating system state that is stored in the hibernation file is lost. This information includes any unsaved data.
	When you resume your computer from standby, your computer may stop responding (hang).
	After you install Windows XP, you may be notified that Windows has detected a new network device. This occurs the first time that the computer enters standby and then resumes.
	When you resume your computer that has two IDE drives connected to one cable from Standby, your computer may stop responding (hang).
	If the following conditions exist, your IBM ThinkPad laptop computer may stop responding (hang): You hot docked your IBM ThinkPad laptop computer to a docking station that has a UDMA-capable device (such as CD-ROM or DVD drive) in the ThinkPad Ultra bay. You placed your IBM ThinkPad laptop computer into Hibernation mode or Standby mode. You resumed your IBM ThinkPad laptop computer from hibernation or standby.
	The computer may unexpectedly resume from standby or hibernation and then automatically return to standby or hibernation after two minutes.
	Consider the following scenario: A computer has three or more processors. The computer is running an x64-based version of Microsoft Windows. The computer resumes from hibernation. In this scenario, the computer may stop responding on the Resuming Windows screen.
	If you remove a PC Card storage device while the computer is in standby or hibernation, the My Computer window may be displayed in a black or white window, and the computer may stop responding (hang) when it resumes. This problem can occur with PC Card storage devices such as CompactFlash, Flash ATA card, and Memory Stick devices.


	After your computer has been idle for a while, the Windows XP Welcome screen may appear. When this occurs, you may be prompted to select an account with which to log on.
	When you resume your Microsoft Windows XP Media Center Edition 2004-based computer from standby, you may receive the following error message: Media Center Tray Applet has encountered a problem and needs to close.
	After you specify the Standby option on a computer that has an ATiXpert 98 XL video adapter, the system appears to continue running. The system fan continues to operate, and the system appears to resume when there is input from the keyboard or the mouse.
	When your Microsoft Windows XP-based portable computer resumes from hibernation, and then you unplug the AC power from the computer, the battery may be drained more quickly than expected. Therefore, the operating system may shut down prematurely.
	After you use code to resume Microsoft Windows XP from a low-power state programmatically, you may have to return Windows to a low-power state manually. For example, after a program causes Windows to resume from Suspend or Hibernate mode, you may have to provide mouse or keyboard activity before Windows can return to Suspend or Hibernate mode. This problem may occur when you use any of the following methods: SetActivePwrScheme WriteGlobalPwrPolicy CallNtPowerInformation
	Although you can successfully double-click to maximize a video window, the video window appears completely black.
	In Microsoft Windows XP, you can configure Mouse Programming properties so that you can use the mouse to wake the computer from Standby mode. To do so, open the Mouse Programming properties, click Hardware, click Properties, click Power Management, and then click to select the Allow this device to bring the computer out of standby check box. However, in some cases, even if you have not selected this check box, you can still use the mouse to control the Standby function.
	Consider the following scenario: On a computer that is running Windows XP, you install a hotfix that includes an Ntoskrnl.exe file. The version of this Ntoskrnl.exe file is later than 5.1.2600.2773 and earlier than 5.1.2600.3239. You have only a small amount of random access memory (RAM) installed on the computer. For example, you have only 128 megabytes (MB) of RAM installed on the computer. You hibernate or resume the computer. In this scenario, hibernation and resume times may increase by about 30 percent.
	Consider the following scenario. A Microsoft Windows XP Professional x64 Edition-based computer is running a program that is performing intense floating-point calculations. You put this computer into standby. In this scenario, a calculation error may occur when you resume the computer from standby. Note Standby is also known as sleep mode or S3 mode. Typically, you can put a computer into standby by using one of the following methods: Click Start, click Shutdown, and then click Standby. Press the power button or the standby button on the computer.
	After you resume a Microsoft Windows XP-based computer from standby, the computer stays at the highest processor performance state, even though a lower performance state has been implemented by Windows XP before standby. This behaviour occurs on all Hewlett-Packard (HP) Pavilion computers that include the AMD K6-2 processor.
	When you wake the computer from hibernation or from standby, the display may not turn on.
	A Microsoft Windows XP-based computer that is using an Intel dual-core processor may stop responding when you try to resume the computer from standby.
	If you set the EnablePowerManagement registry value to 1 as specified in the following Microsoft Knowledge Base article, Serial.sys does not power on the attached device when you resume the computer from standby: (http://support.microsoft.com/kb/275042/EN-US/) Modem Powers Off When It Is Not in Use
	You use a computer that is running one of the x64-based versions of Microsoft Windows Server 2003 or Microsoft Windows XP Professional x64 Edition. When you resume the computer from hibernation, you may receive the following error message: MCA_WARNING_UNKNOWN_NO_CPU
	Your laptop computer that supports Intel SpeedStep Technology but that does not support RTC wake-up from S4 (Hibernate) may stop responding (hang) when it resumes from hibernation.
	A Microsoft Windows Server 2003-based computer that is using an Intel dual-core processor may stop responding when you try to resume the computer from standby. Note: This article also applies to Microsoft Windows XP Professional x64 Edition.
	When you press the STANDBY button on the Media Center remote one time, a computer that is running Microsoft Windows XP Media Center Edition 2005 does not go on standby. However, the computer goes on standby when you press the STANDBY button again. Note The STANDBY button may be unlabeled. Or, the STANDBY button may be labeled POWER. This problem occurs even though you have applied the update that is described in the following article in the Microsoft Knowledge Base: (http://support.microsoft.com/kb/888795/) Update Rollup 1 for eHome Infrared Receiver for Windows XP Media Center Edition 2005
	This problem occurs if the following conditions are true: The computer has multiple user accounts. The screen saver is active and is a three-dimensional (3-D) screen saver. The Prompt for password when computer resumes from standby check box is selected in the power options on the Screen Saver tab.
	Consider the following scenario. You access a shared folder that is located on a remote Microsoft Windows XP-based computer. You then rename a file in the shared folder, or you move a file into another shared folder. Then, you disconnect from the remote computer. Additionally, a System Standby or System Hibernate timer is specified in the remote computer's Power Options item in Control Panel. In this scenario, the remote computer no longer automatically enters standby or hibernation.
	After you remove and add a Trident Video Accelerator CyberBlade i1 driver, settings under Power Schemes for Sleep and Hibernation may not appear. Also, the Hibernation tab may be missing from the Power Option Properties dialog box.
	When you try to put your computer into standby or hibernate mode, you may receive the following error message: The device driver for com1 is preventing the system from entering hibernation. If you disable com1, and then try to put your computer into standby or hibernate mode, you may receive the following error message: The device driver for com2 is preventing the system from entering hibernation.
	When you use HyperTerminal to transfer a file from one computer to another, if one or both of the computers enter standby or hibernation, and pass the timeout period, the file transfer does not succeed and you must restart the transfer.
	If you try to put a computer that is running Microsoft Windows XP, Microsoft Windows XP Tablet PC Edition, or Microsoft Windows 2000 on standby or into hibernation, it may take 30 seconds for the computer to go on standby or to enter hibernation.
	When you try to put your Microsoft Windows XP-based computer on standby or in hibernation, the computer appears to change states, but then unexpectedly powers back up and starts Windows XP.
	If you burn one or more files to a DVD-RAM disk, and the computer enters hibernation during the burning process, the files are not completely burned to the DVD-RAM disk, although the burn process is completed with no errors.
	When your Microsoft Windows XP-based computer returns from standby or from hibernation, you may receive a "STOP 0xFE" error message. This problem may occur if all the following conditions are true: You are using Windows XP Professional with Service Pack 1. You installed the update that is described in the following Microsoft Knowledge Base article: (http://support.microsoft.com/kb/822603/) Availability of the Windows XP S822603 USB 1.1 and 2.0 update You removed the universal serial bus (USB) 2.0 Enhanced Host Controller (EHCI) controller from Device Manager. For example, you may have removed the controller because Device Manager displayed an exclamation point in a yellow circle next to the listing for the controller. The details report displayed "Code 10". Note: The name of your USB 2.0 EHCI controller may vary.
	You cannot put a Microsoft Windows Embedded for Point of Service-based computer into hibernation as expected. Additionally, when a SCSI or SATA storage device is installed, a dump file is not created when you receive a Stop error message or a fatal system error message.
	When you try to hibernate a Windows XP-based computer, you may receive a "Stop 0xA0" error message on a blue screen.
	Your Windows XP-based computer may not hibernate. This problem may occur if the following conditions are true: Your computer has one gigabyte (GB) or more of RAM. Your computer is running multiple processes that create a high-stress condition. For example, you may see this symptom if you run the dir command in 500 Cmd.exe processes.
	If you install Windows XP on a portable computer whose primary partition is formatted with the FAT16 file system, the computer may no longer hibernate after you increase the random access memory (RAM) and then restart the computer.
	After you return your computer from hibernation, if you attempt to disable a Logitech serial mouse, Device Manager may stop responding (hang). This behaviour occurs on a Windows XP-based computer that has the Lsermous.sys driver installed.
	After you upgrade your Sony computer from Microsoft Windows 2000 Professional to Windows XP Professional, devices that you disabled through Device Manager in Windows 2000 may not be fully disabled when you bring your computer out of hibernation in Windows XP. As a result, you may encounter resource conflicts. Note: The title of this article is for win2k, however the article applies to Microsoft Windows XP Professional upgrades from win2k.
	When you try to put a portable computer that is running Microsoft Windows XP into hibernation or on standby, the computer may stop responding.
	Consider the following scenario: You use a computer that is running Windows XP Tablet PC Edition 2005. You connect a USB digitizer device or a USB touchscreen device to the computer by using a standard Human Interface Devices (HID) configuration. In this scenario, Windows XP Tablet PC Edition 2005 unexpectedly changes the system state to standby (S3) or to hibernation (S4) when you operate the digitizer device or the touchscreen device.
	You cannot put a computer that is running Microsoft Windows XP or that is running Microsoft Windows Server 2003 into hibernation. Additionally, the Hibernate tab in the Power Options Properties dialog box is unavailable. Notes: This issue occurs if your computer has more than 4 gigabytes (GB) of random access memory (RAM). This issue occurs in both 32-bit and 64-bit versions of Windows.
	If the 3D Flowerbox, 3D Flying Objects, 3D Pipes, 3D Text, or another Direct3D-based screen saver is running in Windows XP, the computer may not be able to enter standby or hibernation by using the timer in Power Management properties. This issue is not video adapter-dependent.
	When you use the remote to switch between Live TV and a recorded program in Microsoft Windows XP Media Center Edition 2005, the Media Center window may go black. This problem may occur if you use an S-video connection or a composite video connection. The problem may also occur after you bring the computer out of standby or out of hibernation.
	You use a computer that is running Microsoft Windows XP with Service Pack 2 (SP2), Microsoft Windows XP Tablet PC Edition 2005, or Microsoft Windows XP Media Center Edition 2005. When you try to put the computer in hibernation, the computer occasionally does not hibernate. When this problem occurs, you receive an error message that is similar to the following: Insufficient System Resources Exist to Complete the API. When you experience this problem, the hibernate feature is not available on the computer until you restart the computer. This problem typically occurs when the computer uses 1 gigabyte (GB) or more of RAM.
	If you put your Microsoft Windows XP Media Center Edition 2005-based computer on standby while you are recording a TV program, you do not receive a warning message that the TV program will not be recorded.
	When you try to use power management features such as Standby or Hibernate, your computer may not enter the power management state that you choose, and you may experience one or more of the following symptoms: Your mouse may stop responding. You may be unable to open or use the Power Options tool in Control Panel. You may receive the following error message The device driver for the device name is preventing the machine from entering Standby or Hibernation. Please close all applications and try again. If the problem persists, you may need to update the driver.
	After you install Microsoft Windows XP on a computer that uses a Diamond Multimedia Stealth II G460 video adapter, the computer does not enter System Standby mode. If you try to use System Standby mode on a computer that uses this video adapter, you receive the following error message: The device driver for the Stealth II G460 device is preventing the machine from entering standby. Please close all applications and try again. If the problem persists you need to update the driver.
	On a Microsoft Windows XP- or Microsoft Windows 2000-based computer that uses Intel® HyperThreading Technology or Enhanced SpeedStep® Technology, you may experience any one or more of the following symptoms: When you play audio, the audio may not play continuously. When you play MIDI-based music, the music may play at a slow tempo. The computer may not correctly enter the C3 power-saving state. This may affect the duration of battery power.