Surface Pro 4 - Screen won't wake from sleep

Your assumptions are incorrect.  Out of curiosity I changed my power settings so I could place my sp4 in sleep without it going to hibernate.  Last night I placed the sp4 with 100% charge in sleep on battery at 11pm by closing the keyboard cover.  This morning at 7am the sp4 woke immediately with no problems and after 8 hours on sleep the battery was at 67% charge.  These are very acceptable numbers.  I should note that I have connected wifi disabled, I have fast startup disabled, I have the latest Intel beta installed and the latest windows update KB3140741 installed 3/22.  I also have the latest Samsung NVMe controller driver installed(v1.4.7.17)

100% to 67% after 8 hours while in sleep with WiFi disabled is FAR from acceptable...something in the low 90's would be OK. But at least your machine woke. I wonder if the NVMe driver is what is the cause of sleep issues

My sp4 always wakes from sleep and 4‰ per hour is perfectly acceptable to me.  I don't understand why u would keep any laptop in sleep for such extended periods of of time when hibernate is available and has zero power consumption.  I have also yet to understand the burning need for connected standby on battery.  Please explain why this feature is so necessary?

My sp4 i7 512 works right and never fails to wake from sleep as do 4 other sp4s (i5s) I have setup for clients.  I do have the issue of excessive battery usage during sleep but I find it a minimal issue since I have configured my sp4 to hibernate after 30 minutes which it does even from sleep.  I do have fast startup disabled as I prefer a fully refreshed OS when I power up.  Nothing special about my installs and updates other then installing the latest betas.  I create system restore points once a week and always before installing new drivers and software.  I get 6 to 7 hours on the battery at 40% brightness with battery saver enabled and light usage(browsing, emails, ustream, etc).  Observation: if you use the keyboard a lot keep the keyboard backlight at it's lowest setting, it will give you noticeably more battery time and put a bluetooth shortcut on your desktop so you can quickly disable it when not using. 

My point is that there are good sp4s out there.  This forum is like a doctors office.  Everyone here is sick. If u only see sick people you might tend to believe everyone is sick.  On the other hand Microsoft's bedside manner has been less then acceptable.

Perhaps your experience is a bit non-representative because you have you computer going to hibernate relatively quickly. I wonder if you were to not have it hibernate if you wold see the issue. Also, the excessive battery drain is still not acceptable.

#SurfacePro4 #nowake

My takeaway from SteveG47’s comment is that his sleep state is likely burning (reducing his battery) at a higher rate and as such, doesn’t have the sleep/wake problem.  Before the Feb 17, 2016 update, my sleep battery drain was consistently at around 400mW’s per hour.  I had no sleep/wake issue.  After the update, constant wake problems but my sleep battery drain dropped significantly – sometimes to a single digit mW #. 

I rolled back all of the drivers that had been updated which got me mostly back to normal.  Still, I’d get a random wake issue but over time I learned it wasn’t so random.  For my SP4 i5,  it happens while on battery just after a full charge.  Not every time, but many times.  As a test, I started putting it into hibernate each time I fully charge and I went over 4 days without a wake issue until it timed-out into sleep while on battery just after a full charge.  For my experience, I’ve learned that updates cause problems. 

Your assumptions are incorrect.  Out of curiosity I changed my power settings so I could place my sp4 in sleep without it going to hibernate.  Last night I placed the sp4 with 100% charge in sleep on battery at 11pm by closing the keyboard cover.  This morning at 7am the sp4 woke immediately with no problems and after 8 hours on sleep the battery was at 67% charge.  These are very acceptable numbers.  I should note that I have connected wifi disabled, I have fast startup disabled, I have the latest Intel beta installed and the latest windows update KB3140741 installed 3/22.  I also have the latest Samsung NVMe controller driver installed(v1.4.7.17)

Thank you SteveG47, but I’m not sure if your response was meant for Wallstreet.  Regardless, your curiosity test does help make my point, that a higher battery drain while in sleep increases the likelihood of a good wake (since your system seems to be waking).  I would approximate 400 mW’s per hour to equal a little less than 2% battery drain per hour.  Over 8 hours we should expect something in the order of 16% drain.  Your test shows that you are burning 33%.  Which I assert is the reason that you are not experiencing a wake issue.  Though there can be other things that maybe at play causing the high burn rate which may be unassociated with keeping the system sufficiently active to wake, I believe, there is a general correlation between them.

Clearly though, there are some who experience both high burn rates and nowake.  However, in my case, I believe I experience one where low drain rates have some relation to my wake issue.   I think the fix will need to focus on the system activity usage rate while in sleep and the graphics driver (4326) which was given to us through the 2/17/16 update.

My sp4 always wakes from sleep and 4‰ per hour is perfectly acceptable to me.  I don't understand why u would keep any laptop in sleep for such extended periods of of time when hibernate is available and has zero power consumption.  I have also yet to understand the burning need for connected standby on battery.  Please explain why this feature is so necessary?

Have you ever owned a tablet? It's so you can open it instantly an everything is up to date, it's synced in the background like a phone. This is not a laptop, it's a tablet! Hibernate isn't even enabled, you have to go specifically enable it like a power user. You do realize 4% per hour is unacceptable right?! Even with S3 sleep (the old sleep before Skylake) that's a lot, but with the new sleep mode it should be like a phone except without having to communicate with a cellular network in case of a call.

Ohh and THATS what we paid for also...not hibernate, and a sleep mode that works about as well as it did in the year 2000