I found this thread well worth reading as it relates to the issues at hand with the SB:
surface book battery drain while shut down
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.
283 answers
Sort by: Most helpful
-
Anonymous
2016-03-01T22:25:35+00:00 -
Anonymous
2016-03-01T21:30:08+00:00 The 3/1/16 Windows updates are said to address, among other things, these items:
"Windows Update installation, startup . . . resuming from hibernation, shutdown, kernel, Start menu, storage, Windows Hello, display modes".
-
Anonymous
2016-03-01T21:05:35+00:00 Looks like the battery drain issue has resolved itself with the last update. It did create two other issues though. The task bar showed the screen was detached whether it was or not, and the front camera quit coming on during sign it.
I got updates today that solved the new problems, I only hope they didn't recreate the drain problem. I will discharge, recharge and shut off to see where we are on that, and report back.
BTW I have the I& 16GB 512 MB machine and I have not had the instability problems, but I do not use hibernate or sleep, I just shut down, so I cannot offer any help on those issues.
-
Anonymous
2016-02-23T18:06:11+00:00 Exact same problem for me (i7/16GB). Thanks for documenting.
-
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?
- 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