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: Most helpful
  1. Anonymous
    2016-08-13T20:00:44+00:00

    This just happened to me, I did not know how to trouble shoot the problem. So I took it to the Connecting Point Store, they could not get it to work either, maybe they did not know the correct trouble shooting steps, anyway they said that it had to be sent in for repair, they did that yesterday.  This is one of the most disappointing pieces of technology ever, in my humble opinion.  Purchased it because for some of my business I need a windows machine.  Otherwise I run only Apple, iMac, MacBook Pro and iPad.  I do not have good confidence in the Surface.  We will see how this turns out.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-08-13T17:24:12+00:00

    My system started working fine at some point, maybe a month ago.  Sorry I don't have many details, but I'm on 14393.67, and have all the latest updates.

    No problems waking from sleep any longer.

    Looking at battery life as a bit lower than it used to be.  I'll create a new thread when I know more.

    Not that concerned because my main use of the unit is for development.  Netflix in the evenings, but sure, but mostly dev'ing during the day.

    -thanks

    -e

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-08-13T04:22:44+00:00

    I am using Surface Pro 4 i7 with the latest updated Win10 1607. I also encounter the Sleep to Death(SoD) Problem. 

    This forum is so long.

    I am attempting to fix this SoD after reading some articles. See if it works. Please notice that I am still testing this solution upon writing this forum. 

    Go to Control Panel > Device Manager > 

    Turn off the following 2 power saving mode

    1. Univeral Serial Bus Controllers > USB Root Hub > click on it , go to Power Management, disable the SAVE power option.
    2. System Device > Intel Management engine interface > click on it, go to Power Management, diable the SAVE POWER option.

    I will test for several days, see if this works. Feedbacks are welcome to point out this will helps or not. : )

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-08-10T13:23:32+00:00

    Sleep issues is fixed with that USB solution,but I rolled back to version 1511 instead of anniversary updates. Everything works fine now after rolling back to older version.

    Thanks for your help!

    Was this answer helpful?

    0 comments No comments