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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2016-04-05T10:44:39+00:00

    Exactly.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-04-05T07:13:16+00:00

    But, it seems most machines are working reasonably well now.  And hibernate seems to help most others.  

    The perpetual growth of this thread would seem to indicate otherwise.  I don't feel like hibernate should even be considered a solution, either.  We may as well be using a laptop that costs half as much, if we're going to start disabling features that make the Surface worth owning in the first place.   What's next?  Full shut down, in lieu of turning off the screen?

    The average Surface 4 owner probably spent >$1000 for a device that can't do what a $49 Kindle can do... simply wake back up when you hit the power button.  It's just not acceptable, any way you look at it.

    I cannot think of any other device I've used that fails as miserably at such a basic feature.  I had to reset mine at least five times today, which is almost every time I attempted to use it.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-04-05T00:20:22+00:00

    Having just this morning changed my power settings to only hibernate, I can say it still happens when using hibernate instead of sleep. Just had it happening after I tried to wake my SP4 after a hibernate.

    "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000014f (0x0000000000000000, 0x0000000000000100, 0x0000000000000000, 0x000000004f4d524d). "

    Okay, this is my take.  There was a problem, and it was fixed in February.  It is not clear why the fix was not for EVERY machine, and it's odd that if there are random quality control issues, why would it cause this one symptom....not waking up, along with heating up.  But, it seems most machines are working reasonably well now.  And hibernate seems to help most others. 

    SO, if your SP4 doesn't even wake from hibernate, take it to the store and get a new one.  And don't leave the store until you test it in front of them.  And it would help the others who still can't wake, to hear how this goes.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-04-04T20:46:56+00:00

    Having just this morning changed my power settings to only hibernate, I can say it still happens when using hibernate instead of sleep. Just had it happening after I tried to wake my SP4 after a hibernate.

    "The computer has rebooted from a bugcheck. The bugcheck was: 0x0000014f (0x0000000000000000, 0x0000000000000100, 0x0000000000000000, 0x000000004f4d524d). "

    Was this answer helpful?

    0 comments