PC takes a long time to wake from sleep. Is that normal?

[Rationale]

I'm using an i3-4360. The C7 sleep state is enabled in my Bios, and my PSU is haswell certified. My PC takes nearly as much time to wake from sleep as it does to start up, and that doesn't seem normal. Is that to be expected while using the C7 sleep state?

 

[ingtar33]

I'm using an i3-4360. The C7 sleep state is enabled in my Bios, and my PSU is haswell certified. My PC takes nearly as much time to wake from sleep as it does to start up, and that doesn't seem normal. Is that to be expected while using the C7 sleep state?

sounds like a hard drive issue.

 

[InvalidError]

It could be that your PC fails to go into sleep mode and your long time to resume is because your PC is resuming from the hibernation file instead of RAM.

 

[Rationale]

It could be that your PC fails to go into sleep mode and your long time to resume is because your PC is resuming from the hibernation file instead of RAM.

Any way to check for that?

 

[InvalidError]

Any way to check for that?

If your PC is in sleep mode, the power LED connected to the motherboard should be blinking and when you wake it up, you should not be seeing the HDD light turn on much.

If your PC is resuming from hibernate, you might be able to see your BIOS screen before the hibernation loader kicks in. While Windows resumes from hibernate, there should be a screen telling you so (unless it resumes too quickly for your display to show it) and the HDD LED will be constantly lit through most of the process.

A HDD LED getting stuck on with the system frozen/unresponsive could also be caused by a HDD issue so you might want to check SMART status with something like HDTach or try the manufacturer's diagnostic tools just to rule that out. If it was a HDD issue though, I would expect you to complain about random freezes during normal use as well.

 

[Rationale]

Any way to check for that?

If your PC is in sleep mode, the power LED connected to the motherboard should be blinking and when you wake it up, you should not be seeing the HDD light turn on much.

If your PC is resuming from hibernate, you might be able to see your BIOS screen before the hibernation loader kicks in. While Windows resumes from hibernate, there should be a screen telling you so (unless it resumes too quickly for your display to show it) and the HDD LED will be constantly lit through most of the process.

A HDD LED getting stuck on with the system frozen/unresponsive could also be caused by a HDD issue so you might want to check SMART status with something like HDTach or try the manufacturer's diagnostic tools just to rule that out. If it was a HDD issue though, I would expect you to complain about random freezes during normal use as well.

The power LED blinks while sleeping, but the HDD light stays on pretty much constantly after I hit the power button, and the Bios screen shows up for a second. It'd be safe to assume it's hibernating for some reason instead of sleeping?

 

[InvalidError]

The power LED blinks while sleeping, but the HDD light stays on pretty much constantly after I hit the power button, and the Bios screen shows up for a second. It'd be safe to assume it's hibernating for some reason instead of sleeping?

It certainly looks like your PC is rebooting instead of waking up and recovers from the hibernation file instead of memory.

Looks like something is causing suspend-to-RAM to fail. It could be a power supply issue on the 5VSB rail or a problem with how the motherboard handles memory during sleep. It could also be other stuff but those are the two things I can think of.

 

[Rationale]

The power LED blinks while sleeping, but the HDD light stays on pretty much constantly after I hit the power button, and the Bios screen shows up for a second. It'd be safe to assume it's hibernating for some reason instead of sleeping?

It certainly looks like your PC is rebooting instead of waking up and recovers from the hibernation file instead of memory.

Looks like something is causing suspend-to-RAM to fail. It could be a power supply issue on the 5VSB rail or a problem with how the motherboard handles memory during sleep. It could also be other stuff but those are the two things I can think of.

Well, to rule out parts...
The problem existed both before and after I added my GTX 750 Ti, so it can't be that.
I used this HDD in my last PC and it worked perfectly right until I put it in this one (and formatted the whole thing with a reinstall of Windows, ofc), so it's unlikely to be the culprit.
I've tried 2 different sets of RAM, and the problem exists for both, so it can't be the RAM.

So, as you said, I suppose it's probably either the power supply or the motherboard. :/ The two hardest parts to replace, and right after I finally got my cable management perfect. >_>

Does anyone know of any way to test whether the motherboard or the PSU, or something else, is most likely to be the issue?

 

[InvalidError]

Does anyone know of any way to test whether the motherboard or the PSU, or something else, is most likely to be the issue?

If you have a multimeter and know how to use it, you could try measuring the 5VSB supply when:
1- when the PC is off
2- when the PC is on
3- when the PC is on standby/sleep
4- weird voltage changes as you repeatedly turn the computer on and off. You might want to disconnect your HDD(s) during this test to avoid unnecessary spin-up/down. You need to repeat this measurement several times since 5VSB glitches might be too quick for your multimeter to pick up. You should not notice any major deviations.

If the 5VSB supply steps outside the 4.75-5.25V range in any of those circumstances, there is a high probability you have a standby power supply issue.

 

[Rationale]

Does anyone know of any way to test whether the motherboard or the PSU, or something else, is most likely to be the issue?

If you have a multimeter and know how to use it, you could try measuring the 5VSB supply when:
1- when the PC is off
2- when the PC is on
3- when the PC is on standby/sleep
4- weird voltage changes as you repeatedly turn the computer on and off. You might want to disconnect your HDD(s) during this test to avoid unnecessary spin-up/down. You need to repeat this measurement several times since 5VSB glitches might be too quick for your multimeter to pick up. You should not notice any major deviations.

If the 5VSB supply steps outside the 4.75-5.25V range in any of those circumstances, there is a high probability you have a standby power supply issue.

Does it need to be a high quality multimeter to pick up such quick changes accurately, or will cheaper ones work? Because some of the more expensive ones cost as much as a new power supply. :3

 

[InvalidError]

Does it need to be a high quality multimeter to pick up such quick changes accurately, or will cheaper ones work? Because some of the more expensive ones cost as much as a new power supply. :3

Accuracy s not too much of a problem since even $20 multimeters usually are better than 2% accurate for DC voltage so they should still give you a reasonable idea of how far out your PSU might be.

Update rate on the other hand varies wildly and depending on how severe the glitch might be, it could be too fast to catch even with a good multimeter. I threw that test in there just because there is a chance that whatever multimeter you might have on hand or be able to get for fairly cheap might catch something. The ideal tool for this would be a stand-alone oscilloscope but there are not many of those really worth having below $400.

 

[ingtar33]

I don't think this is your psu... this might be the infamous haswell USB 3 sleep-bug; try updating your bios.

 

[Rationale]

Does it need to be a high quality multimeter to pick up such quick changes accurately, or will cheaper ones work? Because some of the more expensive ones cost as much as a new power supply. :3

Accuracy s not too much of a problem since even $20 multimeters usually are better than 2% accurate for DC voltage so they should still give you a reasonable idea of how far out your PSU might be.

Update rate on the other hand varies wildly and depending on how severe the glitch might be, it could be too fast to catch even with a good multimeter. I threw that test in there just because there is a chance that whatever multimeter you might have on hand or be able to get for fairly cheap might catch something. The ideal tool for this would be a stand-alone oscilloscope but there are not many of those really worth having below $400.

I don't think this is your psu... this might be the infamous haswell USB 3 sleep-bug; try updating your bios.

This problem has persisted since I assembled the PC, meaning it continued through the Bios updates.