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-02-24T17:25:17+00:00

    I still have problems with this. Doesn't wake up from sleep.

    I have to hard reset it each time it does this. It is extremely annoying.

    I have checked my update history.

    These were the latest updates.

    • Microsoft driver update for Surface System Aggregator Firmware
    • Microsoft driver update for Surface Management Engine
    • System Hardware Update - ‎17/‎2/‎2016
    • Microsoft driver update for Surface UEFI

    I am assuming it's the system hardware update.

    So assuming its properly installed, what else can I do?

    I has to hard reset 3 times in an 30 mins. I can't even leave the computer alone for a while.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-02-24T17:24:21+00:00

    Whacked the hornet's nest to raise awareness with a post in the comments here: https://www.thurrott.com/mobile/microsoft-surface/64842/surface-and-the-power-of-sleep

    I'm tired of asking politely, especially when Microsoft has refused to even acknowledge the very serious problems with their flagship machines or to meaningfully engage with their customers after a single, non-commital post back in December.  (Their false claim that the 2/17 update fixed everything is laughable - they even had the gall to use that post to mark this entire thread "fixed" - see page 1).

    One thing is VERY CLEAR - the power management problems (sleep/wake, hot bag/fan issues, poor battery life, etc.) on the SP4/SB are NOT fixed for a great many customers, and in fact the update made them much worse.  (To be fair, it seems to have helped some people - go figure...)

    I really want a functioning Surface device (one that works as advertised), but I may have to ditch my investment in the Surface/Microsoft ecosystem for a current (pre-Skylake) Mac just to get some work done.

    As I said in the other post - enough is enough.  Microsoft needs to respond to this debacle NOW.

    It's a testament to Microsoft's clout that they've kept this out of the press as well as they have, but that's no testament at all to their commitment to their customers.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-02-24T17:08:50+00:00

    I am having a very similar problem. My Surface Pro 4 was having this issue before the Feb 17 update and it is actually happening more frequently since the update. Before the update the Surface would not turn back on maybe once a week or so, but now it does it almost daily.

    I have not had to resort to the volume up and power button fix yet. Usually I have to disconnect the keyboard before holding down the power button for 15 seconds or so to get it working again. However, it often takes a couple of tries before it comes back on.

    I am still trying to figure out what the Feb 17 update actually did, because on my Surface Pro 4 nothing was fixed (display driver still crashes, screen still flickers occasionally, WiFi sometimes disabled after coming out of standby, sometimes the battery still drains overnight) and a couple issues are worse than they were before. Hopefully it is just me.

    Sadly these ongoing issues are why I do not recommend getting a Surface Pro 4 to my family or friends. I have been telling them to wait until the major issues are fixed or get a different computer.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-02-24T16:08:21+00:00

    The "Clean Boot" I was referring to was after going through msconfig to select the Diagnostic Startup as suggested in another support suggestion. It didn't have any effect.

    I have tried the process suggested above and since it didn't specify, I did it from the machine being powered off as well as while logged in. In both cases the machine always ended up at the BIOS/UEFI setup screen.

    In case it is significant, what follows is the Firmware data.

    System UEFI:            104.1085.768

    SAM Controller:           103.1081.260

    Intel Management Engine:          11.0.0.1202

    System Embedded Controller:        103.899.256

    Touch Firmware:        1.51.149.106.4.36

    I can also confirm that the sequence reported by TheCyberKnight is exactly what I am experiencing but it isn't happening occasionally, it is all the time.

    As an additional info -- system Restarts seem to work fine.

    Was this answer helpful?

    0 comments No comments