Surface Pro 4 - Screen won't wake from sleep

I don't mean to burst anyone's bubble, but y'all probably want to wait longer than 2 or 3 days before getting all excited or declaring success that this (or any other) patch has fixed the issue.  The last big patch that a bunch of people (including myself) thought had fixed the issue didn't.       

I've had the black screen of death in a slightly different scenario: I use me SP4 as 'server' and have it docked and powered (no sleep) 24/7, but every time I got back to it in the morning the screen wouldn't wake and I had to hold the power button for like 20 secs to restart.

Then I read this thread over 2 weeks ago, did the USB Root Hub (xHCI) save power disable and haven't had the problem since. So this solution did fix my problem and it's up and running for over 2 weeks now without any problems.

So, if MS tech is reading this; take a good look at power savings for the USB Root Hub, because it's causing problems!

Your (scot30) suggestion to wait for 2 weeks before responding is valid but it might be that in that timeframe there were updates for the Surface that put back the power saving option on that hub as a default again? Atleast I'm gonna check it out if the problem would ever return.

:

Can we please get some sort of explanation from Microsoft how come their premium PC, where they own the whole experience just like that popular fruit company, has the reliability of some generic junk kit running a pirated copy of Windows ME, 

I actually had a windows ME computer once, loved it.... till it fried it's battery and decided not to run ever again. But I got it from a garage sale so... lol

In my case mid July's patches solved SoD troubles. I switched on the power management of USB again and I don't experience issues for about 14 dys. Today the Surfacecspecific updates appeared. I hope they will not break things as happen on Febreuary. So far so good.

In addition to the wake problems (that come and go like the tide), I have started to experience a very similar "logoff of death" crash lately. By simply logging off, I sometimes get to that dreaded black screen (with a seemingly working keyboard and a steady IR light), forcing me to power off hard. The event log indicates a 0x14f bug check had occurred. Symptoms are exactly the same as when waking from sleep, merely triggered by a different action.

Interestingly, the fatal logoffs were prompted by a weird issue affecting both the Netflix app and their web site: First, the Netflix app simply hung on launch and eventually terminated. Then, Edge also froze up when trying to log in from the main netflix.com page, or trying to follow any link from there. However, entering the URL of the Netflix login page manually worked, but then Edge hung again when submitting my credentials. No other apps or web pages were failing while this was going on, surprisingly. Assuming my session had got into some bad state (since Netflix wasn't down on other devices), I tried to log off, and then - boom. This definitely has the smell of a graphics driver bug.

That was the constructive part, here is my frustrated rant:

Can we please get some sort of explanation from Microsoft how come their premium PC, where they own the whole experience just like that popular fruit company, has the reliability of some generic junk kit running a pirated copy of Windows ME, and when they are going to fix it? The steady stream of driver updates looks like a large scale game of whack-a-mole by trial-and-error, but we need a solution, not another rearrangement of deck chairs on the Titanic. (And you know what's really sinking here.) Judging from the activity in this thread, the black screen crashes are not isolated incidents, but plague a fair number of SP4 owner, if not all of them to some extent. It's nothing short of a disaster.