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
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

2,411 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2016-07-21T10:33:54+00:00

    Same here,

    I thought the Problem was fixed but after last firmware upgrade the damn Problem is back to my SP4 i5.

    Just today I lost some work changes because going to the lunch break without closing everything. When I came back 1 hr later screen was black and no response. Force Boot worked but some of my files were corrupted.

    Greakt reliable business device you build there M$... Not.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-07-18T05:38:59+00:00

    I'm getting consistent waking behavior now which is good. Sometimes it looks like it will fail and I get the black screen as usual, but if I wait about 30 seconds then press the button again it usually starts up (either from hibernation or sleep). Once it opened to a completely white screen (hmmm, the opposite, compensating for all the black ones?), twice Windows Hello did not work (camera off), but there is a definite improvement.

    I have USB root checked.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-07-17T02:52:24+00:00

    I don't mean to burst anyone's bubble, but y'all probably want to wait longer than 2 or 3 days before getting all excited or declaring success that this (or any other) patch has fixed the issue.  The last big patch that a bunch of people (including myself) thought had fixed the issue didn't.  Everything worked great with that patch for me for two weeks, and I thought the issue had been fixed.  At the two week mark I had the "sleep of death" start up again.  Honestly, I'm really not expecting a fix for the issue anymore.  I'm just going to leave everything set on hibernate instead of sleep, because I never have any issues at all with that - and the couple extra seconds it takes to come out of hibernate is never a big deal for me.  I never have a situation where I need it to instantly wake up.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-07-17T00:37:05+00:00

    This is really curious, I don't know my lot since it is my 4th refurb but my reliability looks opposite to yours since the 7/14 update with no failures in the last two days. However, I am keeping my fingers crossed - I've seen two days without failure before and then the re-emergence of dark wake.  However, I am letting the computer manage the USB Root Hub and still have not had a failure (plugged or unplugged yet). The fact that your SOD was fixed by the June update and broken by the July one whereas others have it seemingly fixed (like me) by the July update points to hardware issues.  I wonder if anyone else with 16XX lots have experienced the same thing as you?

    Was this answer helpful?

    0 comments