Surface Pro 4 - Screen won't wake from sleep

Someone suggested that I go to Device Manager, and disable the USB Root Hub (xHCI).

I'm not sure what it does, but others said they didn't have issues anymore after doing so.

I'm going to give it a shot, and hope this fixes the screen issue for me.

Press the Windows Key, and type in "Device Manager" .

Select it when it appears after your search.

Scroll down to "Universal Serial Bus controllers", and click on the arrow to expand.

Right-Click USB Root Hub (xHCI), and select "Properties".

Select the "Power Management" tab.

Uncheck "Allow the computer to turn off this device to save power, the select "OK".

My SP4 used to crash 3-5 times a day, not waking up from sleep or screen dimming. The updates are all current.

I did 3 things that seems to have solved the problem for now:

1. I uninstalled BitDefender Total Security as I found that the program would automatically change the SP4's power settings.
2. I then restored the power plan to default settings.
3. I unchecked the stay connected to WiFi while asleep boxes.

I have not changed the usb root hub power management settings (the box is still checked).

Hopefully the stability will continue and I hope this is of use to others.

KHC, are you still seeing success with Bitdefender removed ?

I have done pretty much ever test listed here with the exception of removing my Norton Security package.

Currently the USB method works very well for me. And even though the sleep study report shows this now as the highest offender, it mostly seems to lose no more than 1% per hour which I can happily live with since I have no store access in the UK.

FWIW, I do not use any third party-antivirus or security stuff, was (until last week, when the last round of updates caused it to wedge at least daily) running the default power plan, and have unchecked the WiFi connected access boxes.  It doesn't help.

My machine still fails to wake a fair fraction of the time.  Things had gotten a little better with some of the intervening updates after the disastrous 2/17 update, but the 5/9 update put me right back into February mode where my SP4 will lock up at least daily unless I disable sleep when plugged in, and still fails at least half the time when trying to wake on battery (especially if it's been asleep more than a few minutes, in which case a forced reboot is pretty much certain.)

And yes, I'm still utterly disgusted with Microsoft's refusal to acknowledge this problem in any way since their last "we fixed it" post with the 2/17 update release.

At this point, I'm tired of waiting, and will gladly join a class-action lawsuit - given the repeated refusal to communicate, this is flat-out lying and theft by fraud.  It's time MS either steps up, comes clean, and owns the problem, or gets called on their perfidy in court.  I had really hoped things wouldn't get to this point, but apparently, the lawyers are running the show, hoping silence will dissuade enough customers from making trouble, while the customers who spent their hard-earned money on a system that Microsoft and Intel's best cannot make work are just left hanging out to dry.  This is no way to run a company.

Someone suggested that I go to Device Manager, and disable the USB Root Hub (xHCI).

I'm not sure what it does, but others said they didn't have issues anymore after doing so.

I'm going to give it a shot, and hope this fixes the screen issue for me.

Press the Windows Key, and type in "Device Manager" .

Select it when it appears after your search.

Scroll down to "Universal Serial Bus controllers", and click on the arrow to expand.

Right-Click USB Root Hub (xHCI), and select "Properties".

Select the "Power Management" tab.

Uncheck "Allow the computer to turn off this device to save power, the select "OK".

I did that, and everything worked great for a couple of weeks. Then I had a fail to wake and had to force restart. So, the USB trick improves things greatly-at least it did for me--but it isn't a 100% solution. The big problem with the force restart after failing to wake is that you inevitably get corrupted system files that "sfc /scannow" can't fix. If you don't go through the PITA procedures to fix your files, you start getting other issues. At least, that's how the progression happened on my SP4.

BTW, so far my lot 1613 SP4 is working great after 30 hours of use. This is better than anything I've seen before except for the USB trick. Interestingly, the image backups I made--that worked fine on my original unit and the refurb--fail to load on this new unit. My mostly ignorant guess is that something is different enough with the new unit causing the failure. Same model, i5--256 GB--8 GB. As a side benefit this new SP4 absolutely loads programs faster. My original took maybe 3 seconds to load word or chrome. This unit loads them almost instantly.

BTW, the refurb had a fail to wake issue before I loaded any software or restored a backup image. Bone stock, out of the box, all updates were already applied when I got it-- it had 2 fail to wakes. The issue continued when I restored a backup image.