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 Win7 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 Utilizationrocessor 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 CapabilitiesCI 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 Resolutionlatform 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.

Well the CPU utilization was just because I had some programs running when I did the report, and I temporarily disabled sleep so that explains the first error.

The ones I am concerned about are the "USB could not enter suspend" errors. Vista took about 10 seconds to wake up for me when I struck the keyboard or mouse. 7 takes about 30-45 seconds.

Am I just up sh!t's creek here?

Guess no one really knows much about this? I flashed my bios to the latest version from Gibabyte's website. The USB ports are all on my mobo, and I disconnected every external USB device available. I still get the "USB device could not enter suspend" errors though. I was able to decrease the number of errors to about two, but I'm still getting them.

Any other suggestions for how I might go about getting this fixed? The slow wake from sleep is really killing me.

The USB error messages MAY just mean the device carried on being powered throughout sleep mode, so you would think these USB devices don't even need to wake up. Your problems would then be elsewhere. It's a difficult one for sure. Have you enabled S3 mode in your BIOS, that's usually the best one. There may be a few other BIOS entries you can try as well for sleep mode. In Device Manager there should be some wakeup entries for your NIC worth trying. Event Viewer could help, but I'm no expert on its use.

The only other slow wakeup problem I've ever had was with XP, I suppose it could be a 7 problem also, and that was that browsing didn't work for about 30 seconds. That turned out to be DNS not working as browsing worked fast if I typed a web page address in as numbers (try Google on Google). The fix was to let my router have all the DNS server address info, and just point Windows to the router's address (often it's 192.168.0.1) for its DNS server address. Then it works instantly after waking up.

Well it seems I found the culprit. It's my Samsung Spinpoint F3 1TB HDD. When I disconnect the drive, Windows resumes from sleep within about 10-15 seconds. Connected, it takes almost a minute.

I'm going to test the drive with Samsung's software.

EDIT: Software is incompatible with Win7x64

Looking at it again, I get varying write speeds when moving large files to the drive. I can transfer group of files at around 15-30 MB/s. On the other hand, I can transfer a large group of files to my Seagate at about 115 MB/s.

Strange, the Samsung F3 was top drive for read/write speeds with large and small files in a UK magazine very recently, beating Raptors. My Samsung F1 works fine with Win7.64 in speed/sleep matters, in fact I would regard 10 seconds as very slow, mine's about 2 seconds with either MS or Intel HD controller drivers. I reckon your problem is an AMD HD controller one.