Surface Pro 4 - Screen won't wake from sleep

Anonymous
2015-10-27T05:32:42+00:00

I received my Surface Pro 4 today and it worked fine. I put it on "sleep" for awhile, came back and turned it on. Once again it worked fine. I made an error and instead of putting it on "sleep" I  hit the power button to turn it off when I finished. Now it won't come on at all. The screen stays dark. If I push the power button I can see lights under the keyboard keys, then if I hit the power switch again they go off. But nothing happens to the screen no matter what I do. Has anyone else suffered from this?

Surface | Surface Pro | Display and screen

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2016-08-19T19:27:34+00:00

It works fine for me after the Anniversary Update to Windows 10 Pro (Version 1607). It no longer goes into a coma.

I just traveled all week. Put my Surface Pro 4 (SP4) to sleep 10 to 20 times each day, and currently my task manager shows the up time to be 7:21:35:21 - 7 days! It is actually working the way I expected it to when I bought it!

It was such a relief to not be scared to put it to sleep during meeting breaks to save battery when working with my Pen and OneNote. For the past 7 months I've had to have it on power when in meetings so that it wouldn't go into a coma. That was always so embarrassing.

You can update to the latest version of Windows 10 by opening Settings > Update & security > Windows Update, and selecting Check for updates.

Was this answer helpful?

10 people found this answer helpful.
0 comments No comments

2,411 additional answers

Sort by: Newest
  1. Anonymous
    2016-07-12T16:53:00+00:00

    This workaround did work. But it is still a workaround. 

    Yes, the downside is increased power consumption. I get ~600mW during sleep when I leave the USB Hub always on. When using the default settings, I get ~250mW sleep power.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-07-10T19:51:04+00:00

    This solution completely resolved the sleep of death (or persistent vegetative state, as another poster put it) problem for me.  Is there any downside to it, e.g., significant increased power consumption in sleep mode?

    Device Manager ->USB Root Hub (xHCI) -> Properties -> Power Management -> uncheck the box that lets the system turn it off to save power.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-07-08T22:45:14+00:00

    @Mike,

    Sounds like you expended a lot of effort and did your homework here.  Thanks for that.  Did you fill out the survey I offered a few pages back?  I want to make sure that we capture your successful experience with the 1613 machine in the numbers of users represented here, because the point of the survey is to hopefully uncover a trend.  It seems as if, with your attention to detail and scientific analysis, proof of newer tradeins working should emerge in the survey.

    I think we have to be careful, because there have been multiple issues around sleep, hibernate, lack of sleep, and then there were the graphics issues with the detachable screen on the Surface Book.  Panos talked about a lot of things, and I don't know that he said the sleep problem (the one being described in this thread, for the most part) is fixed.

    At any rate, let's all keep it civil and work through the problem towards a solution.  The minute we start ranting and lobbing insults, the whole group loses credibility

    -e

    I mostly agree with Mike. I think you lose a little bit of credibility here Chief.

    Read the blog post again, it wasn't hard to find. I think it's quite fair to assume that "power management" includes waking from sleep. It's ridiculous to try and give Panos an out there. They are well aware of the issue and knew exactly what he was trying to address with the blog post. The next day the media is reporting that the issues had been fixed solely on what Panos said. Mission accomplished for them.

    MS has failed consumers on this, period. They sold us on their quick wake architecture (watch the video above). Someone mentioned 10's of seconds for Windows Hello, unacceptable. I have a working unit that works as advertised. Wake from sleep, Hello, to desktop takes seconds total. Something is certainly wrong with a lot of units, I lean towards hardware or maybe fatal flawed updates process that hosed a bunch of machines.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-07-08T21:40:54+00:00

    OK, here's an interim update on how things are going (ONLY one week in) with my new replacement SP4 hardware (Lot 1618, so probably around early May, depending on the week calendar Microsoft uses: ISO week 18 was May 2-8 this year).

    The good news is that for the past week, I have only suffered one conventional Sleep O' Death or Dark Wake failure, and that one was uncharacteristically immediately after UNdocking.  I have never gone this long without a SoD failure, with either of other two SP4s.  I'm beginning to lose a bit of my terror to put the machine to sleep or wake it.  I will say that while this one wakes, it's sometimes not instant, and can take 5 seconds or so, plus another 10-20 seconds before Windows Hello wakes up, recognizes you, and puts you back into your session.  This is noticeably slower than my previous SP4, discounting the reboots - weird.

    I also suffered an unexplained mystery crash in the middle of the night last night, while the machine was (or should have been) asleep.  Here's what the Reliability Monitor has to say about it - of course there are no solutions for the hardware errors, which are for PCIE and USB3 hub hardware...

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=d2c6e911-32ef-4437-a1aa-6a0bf92b14ba)

    It's a bit too early to say for sure that the newer hardware truly avoids SoD problems, but it's starting to look that way.

    I'm reserving final judgment until after the August 2nd Redstone update, since we've seen a couple of previous updates make power management and sleep/wake/dock problems much worse.

    So far, so good though - it looks like there really may be enough of a difference in hardware to actually make a difference.  Another week like this, and I'll likely have more successful wakes on this SP4 than seven and a half months of using the other two SP4's combined. 

    I'll keep y'all posted when there's more to say...

    Was this answer helpful?

    0 comments No comments