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: Oldest
  1. Anonymous
    2016-05-06T06:40:11+00:00

    original serial number from lot 1548 was 041075...

    new number on currently working device is 103409...

    New one shipped from Ontario, Canada.

    My original 1045... was also lot 1548, so it looks like the serial numbers don't run sequentially.

    The most recent replacement shipped from California.  Not sure what to make of any of that.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-05-06T09:55:58+00:00

    I can report after a little bit over 36 hours of success after those STEPs, the problem has resurfaced and I've had to revert back to hibernation.

    Good while it lasted but non the wiser on if its SW/HW. I'm tempted to think HW but surely if it was, then why would I have 1.5 days without incident (with heavy testing of both user and system initiated and different durations) and then all of a sudden, come back. Clearly the DISM did something to stable a situation that affected me on over 90% of sleeps, so I'm still of the mind that it's SW related.

    OBSERVATION:

    Since I previously reported that the SFC and DISM initally worked (up to 36 hours) and then followed up with the above, I've noticed that one thing that has always seems strange is the Type Cover interaction with the display.

    After a full reboot (from the start menu), if you disable all screen off, sleep and hibernation options from powercfg.cpl, the action of closing the screen atleast on the first attempt actually turns the screen off, or shifts it over to a second monitor even though it's not supposed to. After a Winkey +P to reset the screen, this never happens until the next full reboot. So there appears to be some sort of bug between the cover and the display.

    That got me thinking and I setup the setting like this

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=36502d34-23fc-48ed-919c-7f69708a8866)

    and lid function like this:

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=337eee83-726f-463d-8d03-59ad2eb540d4)

    So what this allows me to do set sleep via the Start Menu so the Type Cover doesn't affect the screen (thats the theory anyway) ...and it's been stable so far. And incase the "nowake from sleep" happens again, the power button sets it to hibernate which still seems to work when the screen is black. This then alllows me to bring the machine out of hibernate rather than hard reboot.

    However, I've not yet have to use the power button to send into hibernate since this config (whilst using sleep from the start menu) seems to work for me everytime.

    Test for yourselves and see if you also see some kind of success.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-05-06T23:24:34+00:00

    I have a Surface Book, but I've found a solution that works for me, and I think it should work for the SP4 as well. Just the other day I remembered that I had the same problem with my old Windows RT tablet, and was able to fix it. I charged it up, found out what I did and applied it to my Surface Book, and it appears to have solved the not waking problem. Everything seems to be working better actually. Here's what I did.

    1) Right click on the start button and select device manager. 

    2) Go to the bottom and expand "Universal Serial Bus controllers"

    1. Right click on "USB Root Hub (xHCI)" and select properties.
    2. Click the "Power Management" tab and uncheck the box for "Allow the computer to turn off this device to save power"
    3. Click ok, and that should do it. Like I said it permanently fixed my RT tablet, and I haven't have a failure to wake on my Surface Book since I did it a few days ago. I was going to wait a few more days to make sure it was a permanent fix but I saw this topic and figured I'd post it now. I also posted this in the SB forum.

    I don't know why that fixes it, or why this continues to be a problem since Windows RT. Maybe someone could finally release a patch that fixes this?

    Hope this helps!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-05-07T02:23:08+00:00

    This is the first solution that I saw here, that is extremely simple and works! Thanks for sharing, Mike.

    Was this answer helpful?

    0 comments No comments