Issue resuming from sleep

[chaoticyeshua]

Hi everyone.

I recently purchased an ASRock X58 Extreme6 motherboard. I'm not really sure how much the rest of the specs of my PC relate to my question, other than the fact that I have a solid state hard drive to boot my OS (Windows 7 Ultimate, 64-bit), so I will leave those off unless you need the specs to help me troubleshoot this issue.

When I put my PC to sleep, all of the fans turn off, the hard drive turns off, and the power light blinks on the PC. This seems normal. However, when I wake it up, everything comes back on again except I receive no video output. I cannot ping my PC either. It's like it does not fully wake up at all. I will leave it sitting there for about 10 minutes and it will do nothing. I have to hard shut down (hold the power button down) to get it to turn off.

I have altered many BIOS and Windows settings to help resolve this issue, but it has proven to be very difficult. I have updated video, network, and chipset drivers to their most recent versions. I have made sure that mouse, keyboard, and network card have permission to wake the PC.

Below are the BIOS settings I have read may cause issues, with their current settings:

In ACPI Config:

Suspend to RAM - enabled

Check Ready Bit - disabled (heard 'enabled' can cause sleep/hibernate issues with SSD; tried both and neither work)

Ring-In Power On - enabled (Wake-on-LAN)

PCI Devices Power On - enabled (tried both and neither work)

RTC Alarm Power On - By OS

ACPI HPET Table - disabled (again, heard it can cause issues with sleep/hibernate but I have tried both and neither work)

As for Windows settings... I have it set to turn off the display after 10 minutes, hard drives after 30 minutes, and sleep after 60 minutes. This does not come into effect really, as I experience the same issue even when manually putting the computer to sleep.

USB selective suspend, I have tried both enable and disable - same result. I do not know what Link State Power Management does, but I do know there is a BIOS option that is related to that as well. Regardless of the BIOS/Windows settings here, I still experience the same issue.

I am trying to use S3 mode, to make sure it uses very minimal power and suspends to RAM. I have 12 GB of RAM and my page file is disabled. Hibernation and hybrid sleep are turned off via powercfg. Even when hibernation is enabled, I still experience the same issue.

Please help me resolve this issue... It's driving me nuts and I've spent a ton of time trying to fix this problem. Thank you in advance for any suggestions you might offer!

[allen2]

If you have an nvidia video card and an hyperthreading cpu, you could try disabling hyperthreading in bios and see if it solve the problem.

[chaoticyeshua]

I do have an nVidia card with a hyperthreading CPU, but why would disabling hyperthreading resolve the issue? I would rather not do that. Surely there's another fix.

[allen2]

I agree : That isn't a fix. It seems some nvidia driver doesn't handle correctly resuming because they "forget" to wake up when hyperthreading is enabled. You can try and revert it back after the test.

Edited April 29, 2011 by allen2

[chaoticyeshua]

Thank you for the suggestion. Unfortunately, I just tried it and received the same result. Any other ideas?

[allen2]

Look at the sticky thread: http://www.msfn.org/board/topic/140247-trace-windows-7-bootshutdownhibernatestandbyresume-issues/, tracing might.

[chaoticyeshua]

I installed the Windows Performance Tools Kit as suggested in the thread you linked and ran the command for standby+resume. It went to sleep, would not resume as usual, shut the PC down and when I brought it up there are three files in the directory I specified:

xbootmgr.log

standby_BASE+CSWITCH+DRIVERS+POWER_1_km_premerge.etl

standby_BASE+CSWITCH+DRIVERS+POWER_1_um_premerge.etl

xbootmgr.log contains:

[2011/04/30-02:20:44.709] Starting trace...
[2011/04/30-02:20:44.803] Enabled user-mode logging to 'D:\TEMP\standby_BASE+CSWITCH+DRIVERS+POWER_1_um_premerge.etl' for flags '0063715b-eeda-4007-9429-ad526f62696e+06184c97-5201-480e-92af-3a3626c5b140+dbe9b383-7cf3-4331-91cc-a3cb16a3b538+9c205a39-1250-487d-abd7-e831c6290539+5322d61a-9efa-4bc3-a3f9-14be95c144f8+43e63da5-41d1-4fbf-aded-1bbed98fdd1d+de7b24ea-73c8-4a09-985d-5bdadcfa9017+aea1b4fa-97d1-45f2-a64c-4d69fffd92c9+a68ca8b7-004f-d7b6-a698-07e2de0f1f5d+030f2f57-abd0-4427-bcf1-3a3587d7dc7d+49c2c27c-fe2d-40bf-8c4e-c3fb518037e7+30336ed4-e327-447c-9de0-51b652c86108+63d2bb1d-e39a-41b8-9a3d-52dd06677588+1fd7c1d2-d037-4620-8d29-b2c7e5fcc13a+e23b33b0-c8c9-472c-a5f9-f2bdfea0f156+4ee76bd8-3cf4-44a0-a0ac-3937643e37a3+67fe2216-727a-40cb-94b2-c02211edb34a+e6307a09-292c-497e-aad6-498f68e2b619+2a274310-42d5-4019-b816-e4b8c7abe95c:96:0+a6ad76e3-867a-4635-91b3-4904ba6374d7:64:0+15ca44ff-4d7a-4baa-bba5-0998955e531e+206f6dea-d3c5-4d10-bc72-989f03c8b84b+e8316a2d-0d94-4f52-85dd-1e15b66c5891+331c3b3a-2005-44c2-ac5e-77220c37d6b4+9d55b53d-449b-4824-a637-24f9d69aa02f'.
[2011/04/30-02:20:44.803] Enabled regular logging to 'D:\TEMP\standby_BASE+CSWITCH+DRIVERS+POWER_1_km_premerge.etl'
[2011/04/30-02:20:44.803] Changing power state...

The corresponding analysis command for sleep/standby uses the filename standby_BASE+CSWITCH+DRIVERS+POWER_1.etl as the file which should exist in the directory for the analysis... that file doesn't exist. When I run the "xperf /tti -i [filename].etl -o summary_sleep.xml -a suspend" on the files that do exist, I receive the following error:

xperf: warning: applying restriction of access for trace processing
XPerfCore: Could not load addin '' [0x80004005]; ignoring
XPerfCore: Could not load addin '' [0x80004005]; ignoring
xperf: error: standby_BASE+CSWITCH+DRIVERS+POWER_1_km_premerge.etl: The specifie
d path is invalid. (0x800700a1).
No action available
xperf: error: suspend: unknown action.

    Available Action:


    xperf -help <action> [<action> ...] for detailed help

    If no action is present, dumper will be invoked.

It doesn't look like this is going to be very helpful either, unfortunately...

[MagicAndre1981]

this is only the temp file, so xperf can't use it.

run

xperf -merge standby_BASE+CSWITCH+DRIVERS+POWER_1_km_premerge.etl standby_BASE+CSWITCH+DRIVERS+POWER_1_um_premerge.etl standby_BASE+CSWITCH+DRIVERS+POWER_1.etl

the merge both files. Are you now able to open the merged file?

[chaoticyeshua]

I hate to be a pain, but this still isn't working. I merged the files but still receive an error when running the command "xperf /tti -i standby_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_sleep.xml -a suspend"

D:\TEMP>xperf /tti -i standby_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_sleep.xml -a suspend
xperf: warning: applying restriction of access for trace processing
XPerfCore: Could not load addin '' [0x80004005]; ignoring
XPerfCore: Could not load addin '' [0x80004005]; ignoring
No action available
xperf: error: suspend: unknown action.

    Available Action:


    xperf -help <action> [<action> ...] for detailed help

    If no action is present, dumper will be invoked.

[MagicAndre1981]

which nVIDIA card and which driver do you use?

[chaoticyeshua]

I have an nVidia GeForce GTX 460 with the most recent drivers from their website, version 270.61. I also used a couple of previous versions with the same result as well.

[MagicAndre1981]

Win7 Sp1 or RTM?

[Tripredacus]

You say you are "trying S3" which makes me wonder. I know in XP if you had installed it on S1 and changed to S3 (or vice versa) you could end up having stability issues. Was this problem fixed in Windows 7?

[cluberti]

Win7 will use whatever is available at the time of sleep. In general, though, sleep problems due to changing S1 vs S3 shouldn't be an issue. Windows 7 does prefer hybrid sleep over the legacy sleep methods, though. Also, if this is a Win7 SP1 install, it would be useful to make sure that the post-SP1 sleep/hibernate hotfix was installed as well for systems with SCSI miniports:

http://support.microsoft.com/kb/2495523/en-us

It would be best to re-enable hibernation and hybrid sleep, install the hotfix, reboot, and attempt again. However, given the symptoms, if the problem persists Windows itself is probably out of the picture here still, and hardware is probably a good place to be troubleshooting.

[chaoticyeshua]

This is indeed Windows 7 SP1; installed from an MSDN copy of Windows 7 SP1 Ultimate (64-bit). I will try installing the hotfix when I get some time tonight. Thank you for your suggestion!

Edit: The article you linked references SCSIport devices - I am running an SSD with a SATA (3 gb/s) connection. Should this still apply?

Edited May 2, 2011 by chaoticyeshua