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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2016-04-14T01:29:42+00:00

    This is no laughing matter. I looked it up, I have lot 1541, and it even says date/lot#. So it's obviously 2014 week 41. I don't think lot number tells us anything, but older machine may be having the issues

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-04-14T01:34:58+00:00

    After looking into lot # a bit more, I really don't think this is identifying. It's just the year and week, I'm 1541...year 2015, week 41...it's the manufacturing date. I also don't think the issue is a display.

    My guess now, and it's a guess subject to change, as we are in the dark if you will, is it's Intel's Skylake processor. And the later revisions of that chip have fixed the issue, thus the later iterations of Surface don't have the issue.

    All processors iterate their chips as they find bugs, and they don't change the name or model number of the chip. They just fix the previous iterations with firmware, or microcode if they can. It's possible that some iterations of the Intel chips can't be fixed with microcode updates, or a firmware fix.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-04-14T01:43:43+00:00

    After looking into lot # a bit more, I really don't think this is identifying. It's just the year and week, I'm 1541...year 2015, week 41...it's the manufacturing date. I also don't think the issue is a display.

    My guess now, and it's a guess subject to change, as we are in the dark if you will, is it's Intel's Skylake processor. And the later revisions of that chip have fixed the issue, thus the later iterations of Surface don't have the issue.

    All processors iterate their chips as they find bugs, and they don't change the name or model number of the chip. They just fix the previous iterations with firmware, or microcode if they can. It's possible that some iterations of the Intel chips can't be fixed with microcode updates, or a firmware fix.

    If that's true, and discovered, it deserves a class action suit and possibly federal fines. It's almost like VW and it's fake emissions. Really, turn out a defective chip, don't have a recall?  Unfortunately, hard to prove.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-04-14T01:48:35+00:00

    Sorry dkb1898, did not mean to be so flippant really. I'm having to turn it completely off every time because of other bugs, this is just one of them.

    Was this answer helpful?

    0 comments