I'm interested to know what other users tend to see when running the "powercfg /sleepstudy" tool on their Surface Pro 3s (as per http://blogs.windows.com/windows/b/windowsexperience/archive/2014/06/26/sleep-study-diagnose-what-s-draining-your-battery-while-the-system-sleeps.aspx ). I'm finding that all my "InstantGo" sessions have a drain rate of between 1200 and 2200mW, which can correspond to between 10% and 20% of the battery drain in the 4 hours before the machine hibernates. Looking at the culprits, almost all the sessions show the following device running for the entire "sleep" period: USB xHCI Compliant Host Controller (\_SB.PCI0.XHC) Fx Device 100% 4:00:00 Is this expected? FWIW, I tend to leave the keyboard cover connected during sleep. Sometimes (when the drain is at the high end of the range), I also see the following: Intel(R) HD Graphics Family (\_SB.PCI0.GFX0) Fx Device 100% 4:00:00 Interestingly, during the first few days I had the SP3, the graphics driver was appearing in every session of the sleep study report. More recently, though, it has stopped appearing. Recently I've been leaving the Surface at the start screen rather than the Desktop, so this may be related - is there a recommendation about coming out of the Desktop before going to "sleep" I also never see anything in the "DRIPS histogram" - should I? What are other people seeing? On a related note, does anyone know if there is a way of changing the time before the machine hibernates? For me, 2 hours (or even 1 hour) would probably be fine - if I'm actively going from one office to another, then the "instant" resume is great, but if I'm at home, leaving the machine for a while, then 4 hours is overkill.

Thanks, that's interesting. How much time does your unit spend in Low Power State?

In my case, a normal 4-hour sleep on SP3 tends to consume 3%-5% of the battery. However, if the " USB xHCI Compliant Host Controller (\_SB.PCI0.XHC)" is being activated forcibly by some incompatible desktop applications, the 4-hour battery drain will shot up to 11% or more. Some of the incompatible desktop applications I have noticed include: Kensington Trackball " TrackballWorks 1.2" Driver Google Chrome when visiting some flash-enabled websites.

Screenshot attached. Notice the battery drain of up to 3500mW!

Guys I'm wondering if we're going down the wrong path with this USB xHCI thing. The USB controller is presumably a low power device that is meant to remain on. In the absence of a true "battery drainer" this will of course promote what's left to the top of the offenders list! Remember the tool is ranking them by time activated, not actual battery drain. Instead, what I think the issue is (at least for me) is the device simply never enters low power state. I don't have AnyConnect or Skype installed at all. I tried to attach a screenshot and ran into issues, so I'll try that in a separate post. I was hoping some others here could mention what their % Low Power State Time is, and where the USB controller sits on their offenders list, if at all. Both viewpoints (with and without battery issue) are helpful, but please state which camp you're in :) Thanks

Thanks -Joon, I don't use it much, i ended up removing it - but have the same issue, I then removed Citrix Receiver 4.2 (recent updated that around the time this popped up) - same issue Removed Citrix Sharefile (Powercfg /requests showed a bunch of ShareFile sync requests) - same problem. Its driving me crazy! Sleep study shows: Fx Devices USB xHCI Compliant Host Controller (\_SB.PCI0.XHC) % ACTIVE TIME ACTIVE TIME 100% 4:00:00 No active components. by the time it gets to the 4 hours hibernate, it will have consumed a couple of hours of battery life in CS. after having the device for a while, and it working normally, its a huge pain not having this functionality working properly.

What should "sleepstudy" show for a Surface Pro 3

Anonymous

I'm interested to know what other users tend to see when running the "powercfg /sleepstudy" tool on their Surface Pro 3s (as per http://blogs.windows.com/windows/b/windowsexperience/archive/2014/06/26/sleep-study-diagnose-what-s-draining-your-battery-while-the-system-sleeps.aspx).

I'm finding that all my "InstantGo" sessions have a drain rate of between 1200 and 2200mW, which can correspond to between 10% and 20% of the battery drain in the 4 hours before the machine hibernates.

Looking at the culprits, almost all the sessions show the following device running for the entire "sleep" period:

USB xHCI Compliant Host Controller (\_SB.PCI0.XHC)	Fx Device	100%	4:00:00

Is this expected? FWIW, I tend to leave the keyboard cover connected during sleep.

Sometimes (when the drain is at the high end of the range), I also see the following:

Intel(R) HD Graphics Family (\_SB.PCI0.GFX0)	Fx Device	100%	4:00:00

Interestingly, during the first few days I had the SP3, the graphics driver was appearing in every session of the sleep study report. More recently, though, it has stopped appearing. Recently I've been leaving the Surface at the start screen rather than the Desktop, so this may be related - is there a recommendation about coming out of the Desktop before going to "sleep"

I also never see anything in the "DRIPS histogram" - should I?

What are other people seeing?

On a related note, does anyone know if there is a way of changing the time before the machine hibernates? For me, 2 hours (or even 1 hour) would probably be fine - if I'm actively going from one office to another, then the "instant" resume is great, but if I'm at home, leaving the machine for a while, then 4 hours is overkill.

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

82 answers

Anonymous

2015-01-01T23:54:03+00:00

Thanks, that's interesting. How much time does your unit spend in Low Power State?
Was this answer helpful?

0 comments No comments
Anonymous

2015-01-01T11:41:45+00:00

In my case, a normal 4-hour sleep on SP3 tends to consume 3%-5% of the battery. However, if the " USB xHCI Compliant Host Controller (\_SB.PCI0.XHC)" is being activated forcibly by some incompatible desktop applications, the 4-hour battery drain will shot up to 11% or more.

Some of the incompatible desktop applications I have noticed include:

Kensington Trackball " TrackballWorks 1.2" Driver

Google Chrome when visiting some flash-enabled websites.
Was this answer helpful?

0 comments No comments
Anonymous

2015-01-01T11:32:02+00:00

Screenshot attached. Notice the battery drain of up to 3500mW!
Was this answer helpful?

0 comments No comments
Anonymous

2015-01-01T11:21:38+00:00

Guys

I'm wondering if we're going down the wrong path with this USB xHCI thing. The USB controller is presumably a low power device that is meant to remain on. In the absence of a true "battery drainer" this will of course promote what's left to the top of the offenders list! Remember the tool is ranking them by time activated, not actual battery drain.

Instead, what I think the issue is (at least for me) is the device simply never enters low power state. I don't have AnyConnect or Skype installed at all. I tried to attach a screenshot and ran into issues, so I'll try that in a separate post.

I was hoping some others here could mention what their % Low Power State Time is, and where the USB controller sits on their offenders list, if at all. Both viewpoints (with and without battery issue) are helpful, but please state which camp you're in :)

Thanks
Was this answer helpful?

0 comments No comments
Anonymous

2014-12-29T22:47:03+00:00
Thanks -Joon,

I don't use it much, i ended up removing it - but have the same issue,
- I then removed Citrix Receiver 4.2 (recent updated that around the time this popped up) - same issue
- Removed Citrix Sharefile (Powercfg /requests showed a bunch of ShareFile sync requests) - same problem.
Its driving me crazy!

Sleep study shows:

Fx Devices
- USB xHCI Compliant Host Controller (\_SB.PCI0.XHC)
% ACTIVE TIME ACTIVE TIME

100% 4:00:00

No active components.

by the time it gets to the 4 hours hibernate, it will have consumed a couple of hours of battery life in CS.

after having the device for a while, and it working normally, its a huge pain not having this functionality working properly.
Was this answer helpful?

0 comments No comments