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-03T03:04:32+00:00

    FINALLY

    Through trial and error I finally managed to get a clean SFC / SCANNOW 

    and I have not had the sleep issue since doing this and getting a clean system.

    Knock on wood.

    Here is the summary of what I did, leaving out the parts where I banged my head against a wall.

    I started with my Surface Pro4 fully updated.  The build number was 10.0.10586.0

    I have never done a reset.  The Pro4 is pretty new, but I wanted to avoid a full reset.

    My problem was I had no image to run the DISM command against because there wasn't one on my machine, and it wasn't able to use Windows Update to get the image.  DISM command would always report Error 0x800f081f - no matter what I tried.  It could not find the source for some reason.

    So this is what I had to do to clean up my system:

    Step 1:  Run CMD as Administrator.  Click Start, type CMD, right click Command Prompt, and run as Administrator.

    Step 2:  I ran this command three times in a row as suggested on a technet article:  SFC /SCANNOW

    This detected corrupted files, and a bunch of issues but it could not fix some of the issues.

    Step 3:   Ran checks:

    This command told me I had corruption:

    DISM /Online /Cleanup-Image /ScanHealth

    This command reported that the corruption could be repaired:

    DISM /Online /Cleanup-Image /CheckHealth

    Step 4: Found an image, finally!  

    I had no image for the DISM command to use!  My C:$Windows_BT and C:$Windows_RT folders did not have the image anywhere within.

    I tried creating an image with the online Microsoft ISO Tool but that didn't work with DISM.

    It would not recognise the install.ESD as a source no matter what I tried.

    So I downloaded a tech bench Windows 10 image from Microsoft from this URL:

    https://www.microsoft.com/en-us/software-download/techbench

    Step 5: Mount the image downloaded

    I mounted the image that was downloaded, by right clicking the file, and selecting Mount.

    This will assign a drive letter (say D:) to that mounted image, which is used in the command below.

    Step 6:  This command finally repaired the damage:

    DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:**D:**Sources\Install.WIM:1

    This fixed my issue with the opencl.dll

            This also resulted in clean scans coming out of SFC /SCANNOW

    So far I have allowed the Surface Pro 4 to sleep for various periods of 5 minutes, up to a half hour, and it has been waking up each time.   I haven't had to do a forced reboot (Hold power down 30 seconds, let go, and push power button to turn on) yet.

    I think this method might just have become a winner for me too.

    After completing the steps above exactly (with the exception of step2, 3 times in a row, of which I just did once) and then added a couple more steps in

    Step 7: Reset the powercfg.cpl settings back to System defaults, because I had customised Hibernation settings previously.

    Step 8: Changed screen setting to turn of after 3min on battery and 10min when plugged. Changed sleep setting to 5mins on battery (to ensure the screen setting doesn't conflict with this one) and 30mins when plugged in.

    Step 9 (Maybe Optional): Changed the "When I close the lid" settings to "Do Nothing" on both battery and plugged in. The reason for this was mainly because I use a MS Dock with Mini Port Display to an external monitor which kept becoming primary when closing the type cover but also, because I wanted to ensure the user sleep was only initiated by one type of action and that would be the power button.

    So after testing this for well over 12 hours it no longer seems to be suffering and normally it would fail to wake over 90% of the time with either system or user initiated sleep.

    I will ofcourse continue to monitor and report any changes I experience.

    Not sure if this fixed my sleep issue yet, but it DID get me clean scans from SFC /scannow finally!

    A little over 12 hours later, and zero sleep issues so far (keeping fingers crossed).  Went in my bag overnight and woke up this morning at work with no problems.  Battery was still at 100%!  Hoping things continue working well.

    Well that lasted less than 24 hours.  Went to use it at work and it wouldn't wake up.  Had to hold power button for 20 seconds then release and press to turn it back on.  Got home from work and same thing - except that time it was warm, and battery (when it came back up) had dropped to 25%.  I guess it's back to hibernate for me.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-05-03T02:39:27+00:00

    This doesn't apply to most of us

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-05-02T16:49:27+00:00

    Unfortunately cleaning up component store (sfc reports no errors) didn't work for me.

    What seems to work is insider build 14332 (fast ring) - I'm unable to reproduce the bug!

    Wakes up perfectly every time.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-05-02T15:47:19+00:00

    Fortunately, there’s an easy solution as long as you have your Type Cover handy. What seems to be happening is that the display driver forgets that it’s using the local screen and tries to project to a non-existent external display. The solution in this case is fairly simple:

    Unfortunately that key sequence does nothing on my machine when it's doing the "black screen/keyboard lights on" fail trying to wake from sleep.  Win+P has never worked on my SP4, but I tried it again just now to make sure.

    Was this answer helpful?

    0 comments No comments