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-05-07T14:45:56+00:00

    Thought I'd contribute again with updates of my experience with a (third) replacement SP4.  I had posted positive results right after the replacement and again a week later.  This is a "new lot 2016 batch" and all that. 

    Continues to be stable wrt BSOD/no-wake (do we have an official catchy label for this anyway?).  Latest Preview build with all updates, default sleep settings, never hibernate.  Wakes reliably all the time.  Although sometimes it turns on with Surface logo, suggesting it did hibernate (correct?).  Could be because I selected "save me power when you know I'm away" setting.  But either way, no blank screen on wake at least, which is a giant leap forward. 

    Yep, this is where Microsoft is in 2016: people consider it a giant leap forward if their computer...turns on.

    At aaany rate, the unconnected complication, however, occurred with current build 14332, with Surface Pen acting up - the button suddenly doesn't work at all.  This is surely just another build glitch - after all, what fun would it be if the basics actually worked for once.  But as part of the same problem perhaps, the screen often just locks up while in any Ink Workspace, requiring a hard reset again.  So not quite the wake-from-sleep problem, but display-related still.

    Furthermore, I recently  noticed a fairly prominent light leak on the display, albeit more apparent only during startup, when the screen is jet black.

    So yea, the hardware definitely *was* the problem before - but it's not to say we should expect it to be no longer a problem. 

    Amidst all this nonsense, I got a Mac.  Now to begin the inevitable ecosystem exit process....just don't have the time for this rubbish anymore.

    Oh well, it's been fun!

    I just set mine to hibernate, but it seems the only fix is to go to a Microsoft Store, show them your device keeps Black Screening, and getting a NEW unit. In my limited tested, your workaround, is working.

    Unless people with newer units that do in fact come in and out of sleep can verify that their USB Power Management is in fact disabled, I seriously caution using this and thinking you have a fixed unit.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-05-07T14:31:13+00:00

    So if it's never entering s0 sleep, then it probably has nothing to do with USB hardware or software issues.

    It is a nice workaround, but it's not a fix. I'm definitely concerned people will use this, forget about it, and they will never truly get what they paid for. In other words, there 1 year warranty will run out, and when the SP5 comes out and actually works, they will find out there SP4 does support s0, but just doesn't work.

    It still seems the best option is to return the device to a Microsoft Store, and get a new replacement with a new lot#. These devices deep sleep without issue according to users.

    In fact, that may be what I do today...hour and a half drive. 3 hours minimum of my time, gas, and money, on top of the many 10's of hours I've already spent. First I'm going to call ahead and make sure they have new units for my particular configuration.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-05-07T14:15:24+00:00

    Exactly, the device never goes to deep sleep - see powercfg /sleepstudy

    There's no wake problem because there's no (deep) sleep, however it's better than hibernation after 5 minutes, there's no "restore from HDD" phase and device is online much faster.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-05-07T13:53:43+00:00

    I also just verified, this workaround allows USB devices to drain your battery. In other words my device sleeping is charging my phone! This was never the case before in sleep...

    On the bright side, it certainly seems that Mike1098 may have identified the offending component here to sleep woes. I'm super curious to here what people who replaced their SP4's in store and got a newer lot unit are seeing here with regards to USB. I'm betting they still have USB Power Management enabled, and when in sleep on battery, their USB devices are not being powered.

    If so, then it's back to being a probable hardware issue. The sad part is, we all have to spend time reverse engineering and applying workarounds, instead of Microsoft being up front with us.

    Was this answer helpful?

    0 comments No comments