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-12-16T03:47:29+00:00

    OH NO!  IT'S BACK!  I guess any more than about three months without the Intel/Microsoft Power Management Monkeys screwing up my computer was too much to ask...

    Things were *finally* starting to work mostly as they should, and I hadn't had to do the YAPORRAC dance (Yet Another Power-Off, Reboot, Restart Apps Cycle) for weeks.  Unfortunately, this week's update has my SP4 failing to wake about once a day - so far, it's always been when docked, but I haven't done much out of the office this week, so it hasn't had much chance to fail to wake when undocked.

    I'm currently at 14393.576, and for the first time in a long time, I'm back to at least daily failures to wake.  I'm not actually sure if the offending release is KB3206632 (the most recent one), or the previous one, KB3201845, which was replaced by KB3206632 in only three days.

    Anyway, after being pretty stable for a long time, this is definitely broken again.  Who else is having this problem again?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-11-22T04:13:07+00:00

    Mine had that problem,  and the issue of locking up when I first got it. After about a month, when it had downloaded several updates, those problems disappeared.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-10-24T21:38:44+00:00
    1. I don't know for sure if this is related, but in the past two weeks, I've lost touchscreen(and pen) access two or three times.  It comes back after a reboot, but at least once, it came back after several wake cycles WITHOUT a reboot.  (Nothing shows as wrong in Device Manager.) This is my biggest concern now, as it makes OneNote effectively useless and again you're left with forced poweroff as the only option if you don't have a Type Cover with you...

    ^This. I'm on my third SP4 now (touchscreen failure on the first, complete loss of SSD on the second) and on my second day of using the replacement, I lost touch and pen just as you described, after waking from hibernation. Suspending and resuming brought the screen back. Right now I'm debating with myself whether I should return this replacement as well, or if this is a software regression that will hopefully be fixed soon™.

    My patience is running low...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-10-24T15:33:33+00:00

    I haven't updated in a while, and I wanted to take the opportunity to report good news.  Somewhere in the weeks after the 1607 (Anniversary) Update, sleep/wake and power management started working pretty much as it should.  I haven't had a SoD event in quite some time now.

    Although it took nearly a year to get a fix, kudos to the Microsoft engineers for coming up with a fairly viable software/firmware solution to a hardware failing.  I'm familiar with the degree of difficulty of fixing problems like this, and it's off the scale.  Again, great job got getting this far, but there's still a bit of flakiness to wring out - please keep fixing the SP4 and don't just transition over to SP5/SB2 development, even though I'm sure there's pressure that way now.  Please honor those of us that toughed it out, stuck with you, and didn't return our SP4s outright by making it work as well as you possibly can.

    My three biggest complaints with the SP4 now:

    1. Although sleep/wake works, battery life still sucks pond water.  There may not be anything to do about this, due to power management (esp. S0ix) just being fundamentally broken in Skylake, and the battery being sized assuming S0ix works ; 
    2. There are still bugs and instability in the sleep/wake code, especially around USB and Bluetooth - these often (at least a few times a week) prevent my SP4 from sleeping properly in the SP3 dock;
    3. I don't know for sure if this is related, but in the past two weeks, I've lost touchscreen(and pen) access two or three times.  It comes back after a reboot, but at least once, it came back after several wake cycles WITHOUT a reboot.  (Nothing shows as wrong in Device Manager.) This is my biggest concern now, as it makes OneNote effectively useless and again you're left with forced poweroff as the only option if you don't have a Type Cover with you...

    Overall, though, I'm willing to call this one pretty much fixed, at least for me.  Hope others are faring as well...

    Was this answer helpful?

    0 comments No comments