Cannot wake from longer sleeps - Windows 10

TridenT

Lifer
Sep 4, 2006
16,800
45
91
My system is having an issue that happened around the same time I installed a new stick of ram in addition to one I already had in (BIOS was reset too but I can't find a setting relevant to this issue). They're not exact duplicate types of ram but I don't think that should be an issue.

The issue: I'll put my computer to sleep or it'll fall asleep on its own. After being asleep for so long (I'd say this is like a 80/20 likely occurrence), usually overnight, I'll hit the keyboard.. It'll flash the numpad light on and then I can hit the keyboard a couple more times and it'll flash the light again... fans spin up on the computer, but no mouse lights, and then no more keyboard... and the system refuses to boot. Monitors get no signal. I can't do anything as far as I can tell. The keyboard eventually stops lighting up like it did.

Only fix is to turn the power off and then flip it back on. System powers immediately back on even though turn on after AC reset is off in the BIOS. Thoughts?
 
Last edited:

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
Trade RAM slots and see if things get better.

If that doesn't work, take out your new stick and verify that the RAM is the problem.
 

sm625

Diamond Member
May 6, 2011
8,172
137
106
I'm assuming you have hibernation/hybrid sleep enabled. If so, open a command line and issue a hibernate command

Code:
shutdown /h

(if hibernation isnt enable it will tell you immediately and will not shut down)

Wait a minute for it to shut down completely. Now try waking it. Does it wake up properly?
 

TridenT

Lifer
Sep 4, 2006
16,800
45
91
Trade RAM slots and see if things get better.

If that doesn't work, take out your new stick and verify that the RAM is the problem.

I honestly don't think it's the stick of ram though. I have no errors in anything I run. Admittedly, I haven't ran memtest yet but everything seems /really/ smooth.

I'm assuming you have hibernation/hybrid sleep enabled. If so, open a command line and issue a hibernate command

Code:
shutdown /h

(if hibernation isnt enable it will tell you immediately and will not shut down)

Wait a minute for it to shut down completely. Now try waking it. Does it wake up properly?

Gonna try this now.

EDIT: Closed all my programs just for this to be said to me...
"C:\Users\Admin>shutdown /h
Hibernation is not enabled on this system. You must enable hibernation in order to use the -h option."
 

TridenT

Lifer
Sep 4, 2006
16,800
45
91
Man, I cannot figure this out.

Sometimes it turns on. Sometimes it doesn't!

It is completely finicky. It is super annoying and means that I have to shutdown every application (foobar2000 completely chucks itself after the reboot) when I am even stepping away from the computer for 30 min or else the data gets destroyed.
 

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
Is telling the computer never to go to sleep an option? I know that would just be a workaround, but when I updated an older Lenovo to Windows 10 (and MS said that everything would work fine), I still found that their were some pretty vanilla drivers in device manager. So that may be part of your problem, but that is strictly a guess.

Question: have you looked to see if there is a particular piece of software tied to when this happens/doesn't happen?
 

TridenT

Lifer
Sep 4, 2006
16,800
45
91
Is telling the computer never to go to sleep an option? I know that would just be a workaround, but when I updated an older Lenovo to Windows 10 (and MS said that everything would work fine), I still found that their were some pretty vanilla drivers in device manager. So that may be part of your problem, but that is strictly a guess.

Question: have you looked to see if there is a particular piece of software tied to when this happens/doesn't happen?

I've tried disabling a bunch of shit and uninstalling a lot of programs from around the time I thought it started but I haven't gotten any success. I switched the ram slots today. But if it occurs again over the next week or so, I'll know that wasn't it. The last resort would to remove one of the sticks of ram and do a trial run for a couple weeks to see if that's the issue. (Mixing ram brands/stuff)

Definitely not going to let my computer stay on. That would be stupid annoying and make my room boil over.
 

TridenT

Lifer
Sep 4, 2006
16,800
45
91
Still happening. Switched the ram slots with no effect. Works fine with a single stick. I shall try using the new stick exclusively at some point soon to completely rule it out.

Looking at either buying new ram or a new motherboard. Thoughts? I'm really not going to deal with this anymore. Which would be easier to sell aftermarket? Motherboard or ram? Maybe same ram brand wouldn't fix it either. Who really knows.
 

UsandThem

Elite Member
May 4, 2000
16,068
7,383
146
Is the ram you have on the motherboard manufacturer's QVL (qualified vendor list) or tested by the ram manufacturer for your board? Since you added a stick later on, is it the same model number as your original stick?

You'll probably take the biggest hit on the motherboard, and some people don't like dealing with used motherboards.

Edit:

I saw the sticks are different. If they are different timings and speeds, that could be your issue right there. From my experience, you want your sticks to at least be the same (especially on voltage, timings, and speed).
 
Last edited:

TridenT

Lifer
Sep 4, 2006
16,800
45
91
Is the ram you have on the motherboard manufacturer's QVL (qualified vendor list) or tested by the ram manufacturer for your board? Since you added a stick later on, is it the same model number as your original stick?

You'll probably take the biggest hit on the motherboard, and some people don't like dealing with used motherboards.

Edit:

I saw the sticks are different. If they are different timings and speeds, that could be your issue right there. From my experience, you want your sticks to at least be the same (especially on voltage, timings, and speed).

I'm pretty sure the timings are exactly the same. I can set them in the BIOS too. I haven't looked in the last 6 months but I remember them being identical on the main timings that are advertised. There's so many different timing configurations when you get into the nitty gritty.
 

UsandThem

Elite Member
May 4, 2000
16,068
7,383
146
I'm pretty sure the timings are exactly the same. I can set them in the BIOS too. I haven't looked in the last 6 months but I remember them being identical on the main timings that are advertised. There's so many different timing configurations when you get into the nitty gritty.

Have they ever worked properly together, or did you get the sleep issue as soon as you added the 2nd stick of ram? Are you running them on auto, or did you manually set any of the timings?
 

TridenT

Lifer
Sep 4, 2006
16,800
45
91
Have they ever worked properly together, or did you get the sleep issue as soon as you added the 2nd stick of ram? Are you running them on auto, or did you manually set any of the timings?

I think I got the issue as soon as I installed the 2nd stick. It's not a faulty stick as far as I can either. It's just a mixing issue of some sort. I'm going to try manually setting the timings to be exactly the same, if I can. I don't recall if I can do it for both... It feels like I tried it but it didn't work anyway. I'll let ya know.
 

nerp

Diamond Member
Dec 31, 2005
9,867
105
106
You won't solve it with that stick. There is a problem with the stick or it's not compatible. Either swap it with a good stick, buy a matching pair of new sticks, or stop using sleep.
 

UsandThem

Elite Member
May 4, 2000
16,068
7,383
146
You won't solve it with that stick. There is a problem with the stick or it's not compatible. Either swap it with a good stick, buy a matching pair of new sticks, or stop using sleep.

+1

Although mixing different kinds of ram may work fine in some cases, it can also be incompatible and cause weird issues like you are experiencing.
 

TridenT

Lifer
Sep 4, 2006
16,800
45
91
Tried all the possible settings being disabled. Same ram speeds, all of it.

No go. :(

I'm just running on one 8GB stick right now. I'll either buy new ram or get a new motherboard. Either one isn't a good way to go because I'm running on a i7-4770 with DDR3. I don't think I could easily sell the motherboard either. I might just sell the ram and see if I can find ram that's on the qualified list for my motherboard (it's a short list with a lot of them not being made anymore).
 

nerp

Diamond Member
Dec 31, 2005
9,867
105
106
Compatible ram is the solution. You know most RAM has lifetime warranty, right? What ram is it and where did you get it?
 

UsandThem

Elite Member
May 4, 2000
16,068
7,383
146
Tried all the possible settings being disabled. Same ram speeds, all of it.

No go. :(

I'm just running on one 8GB stick right now. I'll either buy new ram or get a new motherboard. Either one isn't a good way to go because I'm running on a i7-4770 with DDR3. I don't think I could easily sell the motherboard either. I might just sell the ram and see if I can find ram that's on the qualified list for my motherboard (it's a short list with a lot of them not being made anymore).

Just because the motherboard manufacturer is not updating their QVL anymore, the memory manufacturers all have RAM finder tools on their website where they tell which of of their RAM is compatible with your motherboard.

http://www.corsair.com/en-us/memory-finder