[SOLVED] Windows 10 - Laptop won't go into sleep mode

[eldavies]

---

It may be a BUG.  But your explanation is curious.  You may be right about the system activity, but the reason it cannot enter sleep is usually based on a HARDWARE or DRIVER fault preventing it.  However, as I have tried to explain already, the system never really gets to SLEEP (S3 mode) and crashes instead prior to finally getting there.  It is like when you are going to sleep at night and you are just about to get there and something disturbs you.  Something is disturbing a driver or other (my bet is on the video driver) that prevents it from finally getting to the end of the cycle which enables S3 sleep mode. 

I may be wrong -- it has happened before, but my bet is not tied to system activity or length of uptime.  I have had mixed results (as others also report) with getting to sleep mode immediately after reboot, 3 hours after reboot, a day after reboot.  The data is all over the place to definitively state that it is necessarily tied to a lengthy uptime experience or system experience.  

---

Well it most certainly IS a bug, cuz we're pretty darn sure it's not in the hardware is it? Using your own logic- it worked fine in 8.1, the only thing that's changed is the software. Plus, the failure happens across a wide swath of different hardware setups from different manufacturers.

But the thing is, it's obviously the worst kind of bug- a random intermittent one. I'm not sure why everyone is so focused on the video drivers. Could be a USB port driver for all I know. Or audio, or ANYTHING.

I agree it might not be CPU or video activity that triggers the bug, but they do seem the most probable. I think it's pretty fair to say that the longer it's been running and the more use the computer has had the higher the odds of failure.

And remember it's not just sleep. It also fails to hibernate or even simply shut down.

One more factoid- when going into hibernate even though it doesnt fully turn off, the hibernated state IS saved. I have on more than one occasion done a hard shutdown after telling it to hibernate, then was able to (not easily) return to that hibernated state once powering back on.

[eldavies]

---

@Sat3rn wrote:

Alright guys! i still havent got the sleep freeze 😄 😄 😄 i think this really is the fix!  2 days complete

---

Best to clarify. Describe everything you've done---

[Sat3rn]

Im sorry im not typing again read from 40-47.....

[re4med]

---

@eldavies wrote:

---

@Sat3rn wrote:

Alright guys! i still havent got the sleep freeze 😄 😄 😄 i think this really is the fix!  2 days complete

---

Best to clarify. Describe everything you've done---

---

The user did a Win 10 install from ISO (not the desktop icon).  i.e. revert back to 8.1 and then ISO install Win10.  I think that was what happened if memory serves.

[Sat3rn]

*Sigh* I reverted to win 8.1 from win 10 than got my BIOS updated than went back to win 10, not from the Get Windows icon but from the Media Creation Tool from microsofts website .... tested sleep/hibernate 50+ times now no issues....

[re4med]

@eldavies wrote:

---

It may be a BUG.  But your explanation is curious.  You may be right about the system activity, but the reason it cannot enter sleep is usually based on a HARDWARE or DRIVER fault preventing it.  However, as I have tried to explain already, the system never really gets to SLEEP (S3 mode) and crashes instead prior to finally getting there.  It is like when you are going to sleep at night and you are just about to get there and something disturbs you.  Something is disturbing a driver or other (my bet is on the video driver) that prevents it from finally getting to the end of the cycle which enables S3 sleep mode. 

I may be wrong -- it has happened before, but my bet is not tied to system activity or length of uptime.  I have had mixed results (as others also report) with getting to sleep mode immediately after reboot, 3 hours after reboot, a day after reboot.  The data is all over the place to definitively state that it is necessarily tied to a lengthy uptime experience or system experience.  

---

Well it most certainly IS a bug, cuz we're pretty darn sure it's not in the hardware is it? Using your own logic- it worked fine in 8.1, the only thing that's changed is the software. Plus, the failure happens across a wide swath of different hardware setups from different manufacturers.

But the thing is, it's obviously the worst kind of bug- a random intermittent one. I'm not sure why everyone is so focused on the video drivers. Could be a USB port driver for all I know. Or audio, or ANYTHING.

I agree it might not be CPU or video activity that triggers the bug, but they do seem the most probable. I think it's pretty fair to say that the longer it's been running and the more use the computer has had the higher the odds of failure.

And remember it's not just sleep. It also fails to hibernate or even simply shut down.

One more factoid- when going into hibernate even though it doesnt fully turn off, the hibernated state IS saved. I have on more than one occasion done a hard shutdown after telling it to hibernate, then was able to (not easily) return to that hibernated state once powering back on.

---

It may be a bug in the OS or it may be a bug in the drivers as they interact with the OS.  I have always said that MS/HP will need to resolve whatever issue is causing it.  

Definitely not hardware. Right. 

Good point about the hibernation issue.  I ran into that at one time as well but since it was only once I didn't think much of it.   If it is an issue related to system uptime and activity I cannot imagine why.  All of the code required to run the hardware (drivers, etc.) is loaded resident on boot up.  Years ago I ran across an interesting issue related to CPU throttling but that had more to do with video playback and audio playback than anything like this. 

I think the reason many of us are hooked on the video as a POSSIBLE culprit is for two reasons:  First, the drivers have been removed/replaced. Two, MANY issues related to computers are often tied to video (my experience).  

At any rate -- I am not interested in being right.  I am interested in a resolution.  All of us can agree about that.

[DatEnvy]

Man, this issue has been interesting. I shared my current situation with this issue earlier in this thread, but I guess I'll also share the types of situations taht have gotten it into this mode.

The first ever time, it may have been due to me just playing with Windows 10 when I was one of the first lucky souls to get it at launch on the 29th. All I remember from those wee hours was playing some PS4 while the update process was going on. At times, I almost had a heart attack since it was frozen on a certain percentage, but then all of the sudden, it starts updating the percentage to only do so again and again until the update really started going. When I was playing with Windows 10, I might have been in the process of choosing which browser I would use the most on Windows 10 (at the time, it was going to be Edge, but a couple of days later, the lack of extensions finally got to me and I ran back to Firefox), which probably triggered whatever does in the OS somewhere to cause the issue. Didn't put it in sleep mode, but I was under the assumption at the time that shutting down my laptop was going to work as flawlessly as it did on Windows 8.1.

Woke up to play with Windows 10 some more, but found that the power light was still on, and nothing I did to the keyboard or embedded mouse worked. I might have shrugged it off at the time thinking it was some small bug that would be fixed with a hard reset or something (which is technically true) and continued on with my first adventures with Windows 10. I think for the second day or so, I probably just put Edge to its limits, and when I closed the lid for the first time on Windows 10, I might have then noticed something weird was going on upon trying to open it up again, and once I saw that the light was on again, I put two and two together and started looking up threads as soon as I powered on my device from a hard reset.

Since then, I've pretty much been going from site to site, looking up solutions, testing them out (knowing that they probably will fail in the long term), posting my results, chilling on other websites, etc. When I'm not browsing, I'm either watching videos (while testing out the configuration of one video player), writing programs in Java via Eclipse (which uses a lot of memory at times), creating webms with ffmpeg (a kind of thing that goes hand in hand with one of the Java programs I've been writing to make creating webms easier and another thing that uses a lot of memory/cpu), or just playing the games that are on Windows 10 (mostly Solitaire). At the end of each day, I pretty much just log off and then hold the power button down to shutdown (the shutdown -s trick doesn't seem to work, along with holding down shift when choosing "Shutdown" from the Start Menu).

It's pretty interesting how this issue affects both the sleep mode and shutdown process. Why is that the case? Because they both turn off the screen to a certain point? When this affects sleep mode, it seems to act like the settings for closing the lid are set to "Never", but forget to turn the screen back on when the lid is opened. For shutdown, it seems to get to the point in its process where the screen finally turns off, but you don't hear that final, big hum from the fan to signal that it's finally off. Upon doing a hard reset or trying out one of the temporary solutions, they both seem to work if the user attempts to do either of them within an hour or so. At times, I've found that even after just browsing some websites on Firefox for 30 minutes or so, the issue happens if I attempt either. I probably remember reading about it in this thread at some point earlier, but I wonder how hard resetting my laptop has affected it since the 29th. Since then, I have either done a hard reset or left it on all night with the adapter going. I can only recollect one or two times when I did this on Windows 8.1, and both were when I was downloading something big that needed a while to download. Can't remember any adverse affects on my laptop during either of those times, possibly due to me closing the lid both times, but having my setting be fined tuned to where the laptop is always on when plugged in to a power source.

It's sad yet amazing how huge this thread is and how there has not been a respsosne from HP yet. There hasn't been a response from Microsoft, either on their answers.microsoft forums, the top one that is akin to this one seeming to lose more and more steam. Possibly more people are reverting back to Windows 8.1 there or are viewing this thread more since most people over there have said that their laptop or desktop computer is an HP one. They, too, have also been catching on that solutions are and will forever be temporary unless it is from Windows or their device's manufacturer.

Other than this issue, I can't really recall any other issues I've had on Windows 10. One very minor one is this notification bug that happens randomly where it tells my my virus protection (Windows Defender) is off, when it's actually not. Everything else has been fine. Only complaint I have is this and extensions to be on Edge so that I can finally return to a Microsoft web browser to be my main browser again. Still remember the days of Netscape or and IE and all those rows of toolbars I probably jokingly used.

[painkiller17]

---

@Sat3rn wrote:

*Sigh* I reverted to win 8.1 from win 10 than got my BIOS updated than went back to win 10, not from the Get Windows icon but from the Media Creation Tool from microsofts website .... tested sleep/hibernate 50+ times now no issues....

---

Interesting. I had installed Windows 10 on my PC using the ISO on Aug 2nd. But funny thing, I had upgraded my BIOS right before installing Windows 10. So technically, unless Microsoft has changed the installation files in the ISO, this shouldn't really make any difference. But anyway, congratulations if it worked for you! 🙂

Plus, my PC somehow doesn't boot from anything but a bootable DVD or the OS, so I'm not going to burn another ISO on a disc. 

[eldavies]

My theory as to why this effects hibernate AND sleep AND shutdown is because the fail occurs at the last & final step- actually shutting off the power.

So, it goes through all the motions of saving the state (or shutting down active processes) and then just hovers there at the last moment refusing to actually turn off. Since the only way out is a hard power down the sleep status is lost.

...

Unfortunately I see no BIOS update for my computer (Envy 17 k-100), so all I've really got is trying a clean Win 10 install from the microsoft iso. Later in the week unless someone figures out something better first, since I doubt it will work.

[Caleb1120]

Only after powering down.

Also, it appears the solution is not the same, the solution for some people will not work for all others...

Another edit, for those of you that are having trouble actually shutting down your laptop, follow these steps.

1. Search Power Options in the search bar

2. Click, choose what the power buttons do

3. Click on change settings that are currently unavaliable

4. uncheck the box that says turn on fast startup. (However, this will change how your computer cuts on, of course it will take longer, with this setting off, it should function more normally, when shutting down, this fixed my shutting down issue as this would keep the kernal session hibernated, which kept freezing mine, and apparently several other's computers during shutting down.)