Windows 7 - Windows 7 Seems Slower to Sleep and Wake Up

Hi everyone. I'm new to the forum. Just bought a Windows 7 PC today. After setting it up, it looks as if Windows 7 takes longer to sleep and wake up than Vista. Here's how I compared the two:

1) We have a recently purchased HP running Vista, 8GB DDR3 RAM, 1 TB hard drive, and an AMD Phenom II X4 910 processor. With just Windows and Firefox running, the computer takes 6 seconds to sleep. Wake-up takes just under 5 seconds.

2) Today, we purchased the latest version of the same HP computer -- so the same processor, RAM, etc., but running Windows 7 (by the way, it's a long story why we have two of the same in our house). With just Windows and Firefox running, the computer takes more than 3 times as long to sleep -- 20 seconds. Wake up takes just over 10 seconds.

Any ideas what might account for this? Certainly, the operating system is different, but I guess I was expecting basic Windows functions to be faster, or at least as fast. Would anyone with Windows 7 mind timing their sleep and wake-up modes? I'd be curious to know if your sleep/wake times are similar. Thanks.

This has had several threads. You might want to use the search at the top of the page and read through some of them. I don't kknow you'll find what your looking for but it's a start. Fabe

Fabe, thanks for the suggestion. I did an advanced search and found a number of threads about sleep mode, but so far they all seem to be about freezes, ports that don't work after wake up, etc. -- haven't seen anything yet about any relative slowness in sleep/wake-up.

I am in the exact same situation. Some have suggested that Google Talk / Google Toolbar is the culprit, but after disabling these, my computer still wakes up FAR slower than Vista did.

I've disabled hybrid sleep as well. Still no luck.

Does anyone have any further insight into this?

Have you tried to defrag your hard disk? I recomend DiskTrix.

My Windows 7 sleep/wakeup is quick, a few seconds each, so it's possible. I bet your problem is either drivers or some USB hardware still plugged in that isn't co-operating with this new fangled operating system.

Thanks for the responses guys. I have defragged recently (using defraggler), so I guess the next step is to unplug my USB HDD and see if that helps. I suppose it could also be my keyboard? I'll just try process of elimination on all my USB devices first and see if anything changes.

If it were possibly a driver issue, is there a recommended way I should go about trying to fix this?

As for drivers, often you have the choice of using either Microsoft's built in one or the OEM one downloaded from the manufacturer's website. One may give a faster shutdown than the other.

It may be worth running powercfg to get a report, my energy report showed there were USB issues. Get Detailed Power Management Report Using “Powercfg -ENERGY” Command in Windows 7 - Tweaking with Vishal

This is what I got...

Power Efficiency Diagnostics Report

Scan Time 2010-01-30T16:29:46Z
Scan Duration 60 seconds
System Manufacturer Gigabyte Technology Co., Ltd.
System Product Name EP45-DS3L
BIOS Date 11/07/2008
BIOS Version F10
OS Build 7600
Platform Role PlatformRoleDesktop
Plugged In true
Process Count 53
Thread Count 677
Report GUID {2defbd4f-2927-4d7d-bc4f-0f4c5947f2e4}
Analysis Results

Errors

Power Policy:Sleep timeout is disabled (Plugged In)
The computer is not configured to automatically sleep after a period of inactivity.

USB Suspend:USB Device not Entering Suspend

The USB device did not enter the Suspend state. Processor power management may be prevented if a USB device does not enter the Suspend state when not in use.
Device Name USB Composite Device
Host Controller ID PCI\VEN_8086&DEV_3A37
Host Controller Location PCI bus 0, device 26, function 0
Device ID USB\VID_06A3&PID_8021
Port Path 2

USB Suspend:USB Device not Entering Suspend
The USB device did not enter the Suspend state. Processor power management may be prevented if a USB device does not enter the Suspend state when not in use.
Device Name USB Composite Device
Host Controller ID PCI\VEN_8086&DEV_3A38
Host Controller Location PCI bus 0, device 26, function 1
Device ID USB\VID_046D&PID_C517
Port Path 1

USB Suspend:USB Device not Entering Suspend
The USB device did not enter the Suspend state. Processor power management may be prevented if a USB device does not enter the Suspend state when not in use.
Device Name USB Root Hub
Host Controller ID PCI\VEN_8086&DEV_3A38
Host Controller Location PCI bus 0, device 26, function 1
Device ID USB\VID_8086&PID_3A38
Port Path

USB Suspend:USB Device not Entering Suspend
The USB device did not enter the Suspend state. Processor power management may be prevented if a USB device does not enter the Suspend state when not in use.
Device Name USB Root Hub
Host Controller ID PCI\VEN_8086&DEV_3A37
Host Controller Location PCI bus 0, device 26, function 0
Device ID USB\VID_8086&PID_3A37
Port Path

CPU Utilization:Processor utilization is high
The average processor utilization during the trace was high. The system will consume less power when the average processor utilization is very low. Review processor utilization for individual processes to determine which applications and services contribute the most to total processor utilization.
Average Utilization (%) 6.46

Platform Power Management Capabilities:PCI Express Active-State Power Management (ASPM) Disabled
PCI Express Active-State Power Management (ASPM) has been disabled due to a known incompatibility with the hardware in this computer.

Warnings

Platform Timer Resolution:Platform Timer Resolution
The default platform timer resolution is 15.6ms (15625000ns) and should be used whenever the system is idle. If the timer resolution is increased, processor power management technologies may not be effective. The timer resolution may be increased due to multimedia playback or graphical animations.
Current Timer Resolution (100ns units) 10000
Maximum Timer Period (100ns units) 156001
Platform Timer Resolution:Outstanding Timer Request
A program or service has requested a timer resolution smaller than the platform maximum timer resolution.
Requested Period 10000
Requesting Process ID 2252
Requesting Process Path \Device\HarddiskVolume1\Users\Benny\AppData\Local\Google\Chrome\Application\chrome.exe

Platform Timer Resolution:Outstanding Timer Request
A program or service has requested a timer resolution smaller than the platform maximum timer resolution.
Requested Period 10000
Requesting Process ID 2916
Requesting Process Path \Device\HarddiskVolume1\Users\Benny\AppData\Local\Google\Chrome\Application\chrome.exe

Power Policyisplay timeout is long (Plugged In)
The display is configured to turn off after longer than 10 minutes.
Timeout (seconds) 1200
Power Policy:802.11 Radio Power Policy is Maximum Performance (Plugged In)
The current power policy for 802.11-compatible wireless network adapters is not configured to use low-power modes.

There's plenty of bad stuff going on there then! Probably it's a case of waiting for drivers to be updated to fix the delay.