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-28T05:05:58+00:00

    Well I just did a complete recovery from a downloaded recovery image, reinstalled windows from scratch, not keeping files, not using the image on the machine.

    Nothing installed, just syncing OneDrive and changed the screen to go off in 2 minutes, with the default sleep on battery at 5. First system initiated sleep...BLACK SCREEN...tried all the tricks to no avail. Just wasted hours of my time, hopefully I won't have to waste more as I'm ready to dump this machine.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-04-28T04:59:32+00:00

    What I'm saying is the Watchdog timer IS NOT installed at all on our systems. When we run the Diagnostic Tool it adds it, it doesn't update an older version of the Watchdog timer.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-04-28T03:06:24+00:00

    Ok so Sunday night I reset my surface. Downloaded all windows updates. They all installed except for intel corporation driver update for Intel HD Graphics 520.Windows said it would try updating again in the future. I did not set up windows hello, I signed in with a pin.I also installed the watchdog timer driver & driver update for intel 100 series chipset thermal subsystem from the surface diagnostic tool. I left all sleep settings to there default setting.Miraculously My sleep issues have disappeared. I have put this to sleep for half  an hour,1 hour ,2hours, 5 hours & 8 to 10 hours. All with good results. Thinking that this is all tied in with windows hello. Have not set up windows hello for fear that this thing will not wake up. I also have not gotten the update for intel hd graphics 520. I will keep testing thru out the week & keep you posted.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-04-28T00:43:10+00:00

    Actually, considering what a watchdog timer actually does (basically, reset stuff when a program goes off in the weeds - see my earlier post on this), it's probably vital that it be fixed to ensure stability.  It's unlikely to be needed for enterprise management unless it keeps wake-on-LAN or the like from working.

    As I've said before, though, this problem shows all the signs of *multiple* timers, state machines, and drivers in various (dynamic!) software, hardware, and firmware components fighting like strange bulldogs in a bag, which is why MS and Intel are reduced to playing a "whack-a-mole" game trying to fix this. 

    The fundamental problem is really crappy architecture in the first place (Surface devices aren't the only PCs suffering, just the worst), and I strongly suspect that a fair part of the problematic architecture is cast in silicon (hardware), making software/firmware workarounds even more difficult.  (Hence Microsoft's claim that this is a "very hard computer science problem, especially with new hardware."  This is why I suggested moving to ONE state machine to rule them all, put wherever it needs to be - probably in firmware (what passes for a BIOS these days), if there's enough code space there (and there may not be, which could make this approach anywhere from way harder to impossible...))

    Was this answer helpful?

    0 comments