What should "sleepstudy" show for a Surface Pro 3

Anonymous
2014-07-02T16:59:58+00:00

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.

Surface | Surface Pro | Power and battery

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 No comments

82 answers

Sort by: Oldest
  1. Anonymous
    2015-05-14T16:26:15+00:00

    I know what you mean about the reading of 2835052, but the issues with Windows tablets (I've seen this on both the SP3 and a Dell Venue Pro) is that the power options for the "monitor" affect the entire PC.  In other words, when the "screen" is off, the entire machine is asleep.

    Whether this is by design or accident, I don't know - all I know is that I hit issues where, for example, I'd send an email in Outlook then immediately lock my SP3 (e.g. Windows key + L).   I have a 1 minute Outbox delay set up in Outlook (to avoid those "oh no - did I really just press send" moments) and I'd find that before my minute was up, the SP3 would go from locked to asleep meaning my email didn't get sent until I woke the machine up again (I timed it, and sleep would kick in after around 31s of lockscreen).

    The change in 2835052 sorted me out - I set the limit to 1 hour, which means I no longer get emails stuck in the Outbox; it also means that other jobs that I might be running don't get put to sleep after 30s!

    In terms of the hibernate after 4 hours, I've checked with my IT department - they run the commands in 

    https://support.microsoft.com/en-us/kb/2998588 as part of their deployment of Win 8.1 Enterprise.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-05-15T15:49:25+00:00

    Wow, I'm not sure if our team lead on our SP3 tablet rollout is aware of that!!  I'll definitely pass this on (re: when the screen is off the machine is asleep).  Perhaps this is all part of the new InstantGo feature.....and likely this is documented but just something I missed. 

    So, my thoughts are:

    • should we adjust our GPOs which control our power management accordingly?

    -  is there even a need for a GPO that is responsible to "Turn off the display" after x minutes when that would be redundant since we also have a "...system sleep timeout"  GP.

    Do you know if your IT dept. uses GPOs to configure their Power Management?

    I'd be interested in picking their brains on a few issues...

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-05-15T17:52:46+00:00

    I know we use the GPOs to enforce screen savers, but I'm not sure we use them to control the other power management settings.

    I'll ask and see if I can get one of our IT guys to weigh in on this thread.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-05-19T07:46:00+00:00

    Looks like I solved high battery drain in sleep on my Surface Pro 3. It started when I installed VirtualBox. I didn't know that issue with high battery drain was there a lot more time, since VirtualBox installation. :)

    So solution in my case is: Control Pannel -> Network and Internet-> Network and Sharing Center -> Change adapter settings -> 1) Disable VirtualBox Host-Only Network (wired connection) and 2) Right click and choose Properties on Marvell AVASTAR Wireless-AC Network Controller and untick VirtualBox Bridged Network Driver. (I am using Windows in my locale language, so I hope all "translations" are understandable.) Guest OS in VirtualBox is still able to use wireless connection in my case, but there is no more high battery drain in sleep. :))

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-05-19T08:19:12+00:00

    Ahh yes, VirtualBox.  This wasn't installed when I started this thread (so isn't the root cause of my initial problems) but I have noticed that when I did install Virtual Box, it absolutely killed my battery - it was so power hungry, it even seemed to stop the SP3 from charging successfully when docked (it could take many hours before it would get back to 100%).

    I've uninstalled it, but if I need it again, I'll try your recommended settings to see if that helps.  [My worry is that in the scenario I had, I actually needed two Virtual Box VMs to talk to each other, so I suspect I may have needed the host-only and bridged adapters.]

    Was this answer helpful?

    0 comments No comments