I suspect someone will come along with that board who can try to duplicate this for you, but if they don't, I'll try, though I can't today.
Yes, sleep suspends to RAM, hibernation to disk. To my knowledge, RAM is on in sleep. Which brings up the question: do you see the same thing after hibernation?
Does using Process Explorer glean anything?
The disk activity thing is so stupid that you may not even want to look at this thread. It's a sad "feature," let me tell you:
rseiler: Thanks for your reply, it’s good to hear from you again. You asked if the problem exists after hibernation, so I ran some tests. Starting from W7/64’s unmodified Balanced Power Plan I changed sleep after 30 min to sleep never, and hibernate never to hibernate after 30 min. The system hibernated and recovered successfully; however this time all the cores were idle after recovery, and there was no sign of the problem. Unfortunately the recovery process takes about the same time as a cold boot (30 sec), so hibernation isn’t a very attractive option.
I downloaded Process Explorer and took a look around. Unfortunately it offered no details on the ISRs and DPCs process, although that may not be surprising given how close to bare metal it runs. However I should mention that I’m no expert with Process Explorer, so I may have missed something.
Thank you for the link to the disk activity thread. It certainly engendered strong emotions in a few of the participants! I based my assertion that I was seeing SSD activity on the absence of audible activity in the mechanical drives; after reading the thread I no longer have much confidence in that logic.
If you could find the time to try to reproduce the issue I’d be grateful; I’d appreciate having more solid confirmation than a solitary Newegg reviewer!
OK, I should be able to do it today or tomorrow. Our systems are very similar (exact same MB, CPU, memory), though differences include: I don't have RAID (though do have an SSD and spinning drive), don't have a video card, am still on BIOS 0027 (too much risk in an upgrade given the paltry and contradictory revision notes for 0028), and am using Win8 Consumer Preview. So, if it doesn't happen here, it could still be a whole lot of things, but if it does, then it narrows considerably.
BTW, that disk activity thing drove me so batty that I leave my DVD in a disabled state now and enable it as needed.
I was finally able to do this after a string of days where I needed to keep the computer going. I put it to sleep (Balanced plan like you), and I checked TM immediately after waking it up, but all four cores had little to nothing going on. I have a friend with an even more similar system to yours (Win7, add-on graphics), and if he ever reports back I'll post his findings too.
rseiler: Many, many thanks for running that test. Your result clearly demonstrates that it is not a widespread problem, but something that is unique to my situation, so I should be able to fix it. Fortunately I have not taken the machine into everyday use yet (this is my first exposure to Win 7 and I’m easing my way in gently), so the only applications on the machine are Firefox and Intel’s Extreme Tuning Utility. Here’s what I propose to do – any suggestions will be gratefully received:
Uninstall the Extreme Tuning Utility
Remove the graphics card and its drivers.
Look for anything else I’ve installed and forgotten about
If all else fails, don’t use sleep!
It will take a few days to get through this list – spring has come to Massachusetts, and I have a lot of yard work to do! Thanks again for your help.
I’ve just completed some additional testing on the “wake from sleep busy” issue. Rather than removing things one at a time as outlined in my post dated 18 April I decided to start with a fresh installation of Win 7/64 to provide a reproducible baseline, and add/change things one at a time. Here are the details:
I removed the graphics card and the RAID 0 array, leaving me with this very basic system:
DZ68BC + i5-2500K, 8GB G Skill X (2x4GB) DDR3 1600 memory, CNPS9700 HSink
SSD: Kingston HyperX SH100S3B 120GB SATA 6GB/s
BD-ROM: Samsung SH-B123L/RSBP
Antec P183 V3 case, CP-850 PSU
Win 7 Pro SP1 64 bit
Reset BIOS (0028) to defaults, then changed SATA mode to RAID
Used Diskpart (from the W7 DVD) to clean, partition (align=1024) and format the SSD.
Installed W7/64 with network unplugged. No Win updates or Intel drivers installed
At this point W7’s Balanced Power Plan was not offering sleep (hardly surprising!), but for completeness’s sake I let it sit for >1 hour. Sure enough it did not sleep.
I then installed these Intel drivers (but no Intel apps):
Chipset, Graphics, Network, Rapid Storage, Management Engine, Realtek, SATA 6.0, USB3
I also “installed” Lucidlogix but I believe that just dropped a link on the desktop.
Now the default Balanced Power Plan offered sleep after 30 min. I let the system go to sleep, and when I woke it one of the cores was close to 100% utilized (System CPU usage 22%). The Resource Manager showed the guilty party to be my old friend, “Deferred Procedure Calls and Interrupt Service Routines”.
I then plugged in the network, installed MS Security Essentials and waited out the blizzard (64+6) of Windows Updates. I re-ran the Wake Up test with virtually identical (System CPU usage 18%) results. I used Intel’s Driver Update utility to update the Graphics and Rapid Storage drivers, reconnected the RAID 0 array and retested – no change, System CPU usage 23%.
So that’s where I am now. The problem was present at the first point at which I could test for it. I may be able to learn a little more by installing the Intel drivers one at a time, starting with the Chipset driver (which I hope will enable sleep). I’ve decided to give it a few days to see if anyone has any suggestions or comments and then choose between further testing or simply not using sleep.
rsnelson: Thank you very much for the link, which was new to me. The symptoms described sound very much like those I’m seeing. Before running the test described above I did try the procedure described in the link several times, but it did not help. However, after the reinstall, on one occasion I did see ‘audiodg’ listed very briefly in Task Manager (or perhaps Process Explorer) when I woke the system. I’ll explore further – at the very least if I rebuild adding one driver at a time, I’ll make sure Realtek is the last to go in.
Just some out of the box thinking: did your try to disable some of the embedded devices in the BIOS? The DZ68BC has some devices (second sata, usb 3.0, infra-red, COM port, etc) that are non-essential to boot the system that can be disabled. This may help to pinpoint the device\driver which is root cause of your problem.
To touch on vbaderks' suggestion first, the only thing I've disabled from those is the Marvel controller. I did that because I'm never going to use it and because it reduces the amount of time (by a lot) that the system sits on the BIOS screen before booting.
Speaking of BIOS, do you have UEFI enabled? I don't. That would be a fundamental difference and could be involved if you did an install with it enabled.
I think you went quite a bit too far in reinstalling things after your new install. After installing the chipset driver alone and rebooting, I can't think of any reason at all that sleep wouldn't be available to you, do you? That would be the ideal time to test.
I know what RST is, but what's "SATA 6.0" in terms of a software product?
@ Steve and rseiler: I believe you will find that Sleep mode is available only after installation of Graphics Driver. I agree with vbaderks, BIOS settings. Several settings have strange or unexpected results. In the performance settings, setting to automatic, instead of manual changes operation sometimes, even if it appears that the individual settings are the same.
Intel recommends that you start with automatic, and then switch to manual for extra performance enhancement, but when I went from BIOS 0021 to 0028, mine was 'defaulted' to manual, I had problems with sleep mode and also with failure to shutdown. I found that changing to automatic fixed the problem, but I could not see what the difference was in the individual settings. I have experiemented with it a lot, and can not determine why this is so. On another board, I had problems with Processor C States, had to be disabled, but I see in your original post that you have already disabled it. Is it still disabled? Maybe try disableing it in conjunction with other changes.
I had a simillar issue after installing Win 7 64.
Are you using any Microsoft mouse or keyboard?
Microsoft Intelipoint driver which include with Win 7 are not updated and may couse issues with sleep.
If you run akk windows critical updates, one of them is Intilipoint driver fix.
Another option, is your ethernet driver.
Go to you device manager, open Network adapter, double click on Ethernet device, go to the 'power management' tab
and disable the option "Allow this device to awake the computer".
Also, you may find a solution for other known Win 7 awake issues here:
It's not a bios issue. Dont update to BIOS 0035 in any case. This is a bad BIOS s you can read on the forum.
I'm preaty sure this is a WIn 7 issue, and not a hardware issue.
I have a very similar system to you:
DZ68BC + i5-2500, 16GB Corsair Vengeance (4x4GB) DDR3 1600 memory, Stock heatsink
SSD: Corsair Force Series 3 CSSD-F60GB3A-BK 60GB SATA 6GB/s, Kingston SSDNow V100 Series SV100S2N/64GZ 64GB SATA 3GB/s
Several HDD drives, all SATA 3 GB/s and all 7200 RPM except for a 300GB 10K RPM VelociRatpor drive
Graphics: eVGA 8800GT SuperClocked
DVD-RW: Sony SATA 1.5GB/s, LG SATA 3 GB/s
Fractal Designs R3 chassis, CORSAIR Professional Series Gold AX650 650W PSU
Win 7 Ultimate SP1 64-bit
I have recently had the same problem, or at least it has gotten substantially worse in the last few days.
The only changes that have been made to my system is that I received about a dozen Windows/MSE/Office updates and I updated my GPU driver to the most recent version. I have tried rolling back the GPU driver update, but didn't have any improvement. The problem actually happened several times before the Microsoft updates, but it seems to happen more often and to a more severe degree since I installed them.
I might try playing with uninstalling the updates to see if I can't improve the problem, but I'm thinking that the culprit here must be something in the Win 7 64-bit software being run on the Intel DZ68BC board. I am open to being proven wrong, though, as I really want to get this problem fixed, as well!