Surface Pro 4 - Screen won't wake from sleep

One fix is to avoid sleep and use hibernation.

The other seems to be manually adding the new driver.

The problems noted there seem odd.  Someone now had a problem with hibernation, and NOT sleep?

Someone else seemed to find that the new drivers were not working well with 2 monitors. 

I have a docking station, and often use my large monitor alone.  I use hibernation, occasionally sleep only for less than an hours, with no problems over a couple weeks.

Thought that I would post my experience with this issue as it may give someone insight into the root cause.

I received my SP4 i7/16/512 back at the end of November. I did not start experiencing the Screen will not wake from Sleep until recently. Not sure yet what caused it but here are my symptoms and possible causes. Screen would not wake from sleep and sometimes it would say Camera Loading, but it would not load and other times just a dark screen with boxes/pixels highlighted in different areas of the screen. From this screen by hitting a key I would sometimes get a Display Menu to slide out from the right. Try as many times as I could I could never get it to select any of the display options. I found after the 2 button reboot that the camera was not working for the Windows Hello function, but appeared to be working for regular use. See attached pictures for screen shots.

Things that had changed recently. End of December and early January there were a couple Microsoft updates.  I have updates set on automatic so I had not really been paying attention to the updates and when the problem started as it started and I did not think anything of it as  I thought it was just a momentary glitch. Another thing that had changed was that I had just recently unboxed and plugged into the Surface Dock for the first time. Previously I was just using the power cord that came with the SP4 and had not used the Dock. When I bought the SP4 I was new to Surface Pro and windows 10 and did not rush in and transfer everything over and start using it as my laptop replacement. I was taking it slow and loading things as I became more comfortable with the SP4. What makes me suspicious of the Dock was the menu that comes up about selecting the Display Options.

I have gotten back to where my SP4 WILL wake from sleep by using the Recovery option and going back to a set point at the end of December. I think that the recovery should have removed the updates and possibly undone any settings that may have been changed by plugging into the dock. I only had it plugged into the Dock for power and had not yet gotten to connecting to the network or external monitor through the Dock. We shall see what happens when I let it update again and then try the dock again. I do not know enough about computers to say that either of these were the cause, but it seems awfully coincidental. Perhaps someone else can comment.

Well I can confirm that the old three finger salute of CTRL+ALT+DEL is the most reliable way of waking up after the case is closed.

I always get the 'do you want to enter tablet mode' toast as well. The 2 buttons do not respond to touch, pointer or keyboard but the X close works.

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?

I found the same problem and my 9 year old grandson discovered that keyboard entry of Ctrl+Alt+Delete replaced the "blank" screen with the User Login screen every time.   This even worked if using without the keyboard, and then attaching keyboard when Surface failed to switch on when being used in tablet form.  So far, this solution has worked 100% and means not having to re-boot and lose unsaved work.