surface book battery drain while shut down

Anonymous
2015-12-09T16:09:58+00:00

Split from this thread.

I have been noticing that when I shutdown my surface book, when I power it on the next day the battery has drained some. If I leave it off for a couple of days it will drain down from 100% to around 85% or lower.

I disabled fast startup... and then just decided to disable hibernation altogether. That didn't help.

I have windows hello disabled, but that shouldn't matter anyway since I'm shutting it down, not sleeping.

Some searching and I found a general windows 10 issue with the "Intel Management Engine Interface" driver. Some say that v11 can cause this issue. One solution that I have seen suggested is to go into device manager and in the power management tab for this device uncheck the option that allows windows to power it down to save power. I tried that and it didn't help.

Others have suggested downgrading the driver from v11 to v9 or v10, but I don't know where to get v9 or v10 of this driver that is compatible with the surface book. Anyone know if one of the downloads on Intel's site would be compatible?

So, has anyone else noticed this issue and know of a fix?

Surface | Surface Book | 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

283 answers

Sort by: Oldest
  1. Anonymous
    2016-02-23T05:54:05+00:00

    Battery drain during shutdown usually wasn't a problem for me even before this latest "fix".

    My problem has always been with the sleep mode.  This is where my Surface Book drains even when it's in sleep mode and significantly at 4 to 5 percent per hour. 

    Since the "fix" I still have issues with it in sleep mode. Sometimes it works and other times it's like it was before. There's still something wrong with the way the Surface Book "sleeps". It's unreliable and if you can't trust it, then it's useless.

    Anyone else still having issues?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-02-23T12:27:10+00:00

    Yes, I have these issues same thing you havd, but if you go to my twitter account @dhahran2009 you will see that I uploded video that showing my surfacd freezing with wired sound!!! I think they batter admit they fool us with thins no one can believe that this problem since I bought SB 11/12/2015 until now ! Battey drains+ freezing + no sleep mode. My device is up to date ! Still same thing.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-02-23T13:52:06+00:00

    Got a #hotbag yesterday.... After installing the new update, it was correctly entering the low-power state as reported from a sleep study. However, after my latest hotbag I checked again and that one time (out of 12) it chose to not enter the low-power state and when I took it out the fan was blasting and I lost about 8% battery in 15 minutes. I didn't have anything streaming or playing when I put it to sleep. So, it seems that I still can't trust it to sleep EVERY time, only 90% of the time. 

    Also, after about 1.5 months with no more BSODs, after the update I got one on day 3, and another horrible error that I've never seen where my SB just quit but displayed hundreds of fine multi-colored lines in a seemingly random way and was unresponsive until I did a hard reset. I've also had a few instances of the screen not coming on from sleep with the keys lighting up and needing a hard reset, and last night it restarted itself when it should have been asleep (no updates installed).

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-02-23T15:16:52+00:00

    I am in the same boat than you. I never had problem with Hibernate, only with sleep.

    The day after the update sleep was still draining. The following day it went to sleep without lost of battery.

    I will keep watching to see if it will now sleep correctly consistently or not.

    Claudia

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-02-23T17:52:43+00:00

    I've been using the new firmware since the 17th and the good news is that sleep no longer seems to cook my machine.  But the bad news is that the system is a lot less stable.  There have been more lockups and blue screens, but also the system fairly frequently crashes while in sleep mode.  The event log doesn't appear to include information about the cause of the crash other than the Kernel-Power message "The system has rebooted without being cleanly shut down first."

    But there are a lot of other problematic messages in the event log.  Many instances of PushNotifications-Platform saying "Connection to the Windows Push Notification Service failed because of a failure to configure the connection to run properly in low-power states.  Please ensure all network drivers are up to date." before the crash.

    I also have the following event log entries from the reboot process itself (i.e. these happened in the morning when I rebooted, not during the failure at night):

    • A series of complaints that "The driver \Driver\WudfRd failed to load for the device ACPI\MSHW0041\2&daba3ff&2." as well as for the devices
      • ROOT\WPD\0000, HID\MSHW0030&Col01\5&294f3b18&0&0000
      • {6c8abe47-dac0-4b99-affa-4fff050e3cdc}\SurfaceDigitizerPenPairing\5&141f7bd2&0&0
      • {4E781CFC-87EE-459B-A319-9B0531EB7485}\SurfaceKeyboardAmbientBacklight\8&18c2e47d&0&0
      • {5E9A8CDC-14AB-4609-A017-68BCE594AB68}\SurfaceBaseFwUpdate\8&18c2e47d&0&1
      • BTHLEDevice{00001812-0000-1000-8000-00805f9b34fb}_Dev_VID&02045e_PID&090e_REV&002f_de1d55c5fbb6\8&9ad2fe7&0&001b
    • The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\WINDOWS\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.
    • Session "ReadyBoot" stopped due to the following error: 0xC0000188.
    • Kernel-Processor-Power: The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.

    Any ideas what's going on?

    Was this answer helpful?

    0 comments No comments