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-26T01:41:43+00:00

    How are you putting it to sleep?  (Power button, Windows Menu, close keyboard cover, etc.)

    And how and how often are you waking it?  (I presume by power button, since you mentioned the onscreen keyboard...)

    Anyway, 25-30 hours is pretty impressive.  I guess we'd need to know when you're hibernating to know if that's really good, though.  It would be good to run the power report (powercfg /sleepstudy) when you're done to see what all happened.

    Intrestingly, there's some decent hunting into the heat issue over on this thread: http://answers.microsoft.com/en-us/surface/forum/surfpro4-surfperf/i5256-surface-pro-4-overheats-and-battery-drains/045497f8-1ece-49b2-aeaa-8aa10994a277 - Like this thread, it's old, with a lot of bad info at the top - you'll need to dig way down in the pages to get to the newer info.

    It's starting to look like all of this is related, even if there are multiple problems...

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-02-26T01:26:59+00:00

    Unfortunately my suggestions didn't work. I have 10 days left in my 30 day return policy. I feel this may be going back to CDW. This purchase was to test this device for recommendation to my Firm of 13 partners and 50 PMs. So close....

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-02-26T00:54:37+00:00

    Uptime here is around 25hrs.. suspend works good but the whole after x amount of hours it goes into hibernate is kind of annoying, why not just shutoff right?

    Anyways will see what happens after 30hrs.. so far the onscreen keyboard already jammed but recovered(had no reaction for a min or so).

    Will see..:

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-02-25T22:45:45+00:00

    Josh,

    This 2/17 firmware/driver package has made sleep on my machine unusable. Before it, I would have to do a Soft-Reset maybe once every few weeks. After the update, and yes, plenty of reboots, every other time my SP4 went into sleep I would have to do a Soft-Reset. As this killed productivity, I eventually gave up and completely disabled sleep and replaced it with hibernate. That's the state of my SP4 now...not exactly good. Way worse off after the Firmware/Driver package.

    I've considered a PC-Reset, but I've read others who did that and still had the same issues, post 2/17 update

    Damien

    Was this answer helpful?

    0 comments No comments