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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-01-13T02:58:41+00:00

    Just tried it with my SP4 in the SP3 docking station to a monitor connected via DVI. No problems.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-01-13T00:04:45+00:00

    Somewhere buried in this thread was a comment that the NEW driver did not work properly with the docking station and another monitor attached.  Can anyone confirm that, or the opposite? Is the new driver working fine with docking and use of another large desktop monitor?

    If it works fine, great, and thanks. If not, then that could be the reason MSFT is not releasing it yet in updates.

    I'll check this. I have a SP3 docking station at home. As I recall, I have no issues with external monitors directly connected to the SP4 OR through the SP3 docking station with the new drivers, but I will double check.

    I have an SP3 - that said the issue is pretty much the same as you folks with the SP4 - goes to sleep, wakes up but screen is black, ctrl-alt-del wakes it up properly if teh keyboard is attached, etc etc.  In addition when docked it would sometimes totally lose its marbles as far as the external display requiring the volume-power "fix".

    So I installed the latest drivers for this machine per instructions, I also modified the power plan according to the excellent tip about hidden settings and set to hibernate after sleep.

    All the changes seem to work beautifully so far.  It wakes up as it should, the dock hasn't lost its mind on the external display yet.  In fact, I unplugged it hot, ran in tablet mode, let it sleep, plugged it back in to the dock to wake it up and it worked flawlessly.  I still think MS needs to address this issue "officially" but I can't express my gratitude enough for you folks helpful tips!

    Kudos!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-01-12T18:10:22+00:00

    Somewhere buried in this thread was a comment that the NEW driver did not work properly with the docking station and another monitor attached.  Can anyone confirm that, or the opposite? Is the new driver working fine with docking and use of another large desktop monitor?

    If it works fine, great, and thanks. If not, then that could be the reason MSFT is not releasing it yet in updates.

    I'll check this. I have a SP3 docking station at home. As I recall, I have no issues with external monitors directly connected to the SP4 OR through the SP3 docking station with the new drivers, but I will double check.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-01-12T18:09:02+00:00

    I suggest those who are experiencing this problem who have not yet moved to the Intel display driver "...4352" as explained in Dyndragon's January 7th post seriously consider doing so.  I stressed over this issue for weeks until I decided to go ahead and try it - which I did approximately 10 days ago and have not experienced the wake up from sleep issue even once since installing that driver.  I also loaded it in a co-workers Surface Pro 4 who had been experiencing the same problem, and it corrected it for her as well.

    Dyndragon's post takes you through it step-by-step (with one suggestion Dyndragon may wish to consider as an update to the procedure - if one is not familiar with Windows drivers, they may not know how to get to your first screen shot (which is...Control Panel...Device Manager...Display adapters...right-click on Intel HD Graphics 520...Properties...Update Driver Software) - then carefully follow the existing instructions in the Jan. 7 post, including the text below the final screen shot.  <Dyndragon, I did not include your post in this reply as I did not want to appear as if I were threadjacking or taking over your solution - but I do wonder if there are a few people out there who don't know how to update a driver, hence my reply here...anyway, thanks again, your solution removed considerable stress from my SP4 life :-) >

    And, if you tried Dyndragon's solution and it didn't fix your SP4, I feel for you and COME ON MS!!

    Thanks bud, glad I'm helping somebody here. I don't care if someone wants to hijack my solution and write up!--But, thanks for being courteous. I just want notifications from this thread from people who are complaining that the most helpful solution is to do a 2-button reset to stop!

    New-comers to the thread--please read through at least some of the latest posts to get the idea that the top solution is NOT the best solution!

    Was this answer helpful?

    0 comments