This is a Sticky Thread to consolidate the Power Management info on the Surface Pro 3 _________________________________________________________________________ Traditional Sleep is the S3 Power State, it stores everything in RAM and is maintained via the battery or mains but a loss in power (through failure or drain) will mean loss of data. Connected Standby in the x86/x64 Architecture is S0iX it is an ultra-low power "ON" State and replaces the S3 Power State. On all Connected Standby enabled Machines (with the exception of the Surface Pro 3) the only Power States Available are: S0 - On S0iX - Connected Standby (now known as InstantGo) S5 - Off The Surface Pro 3 uses an additional EEPROM to manage Power and Thermals that runs at a lower level than the OS, this adjusts the Power States the SP3 uses: S0 - On S0ix - Connected Standby S4 Modified - Lite Hibernation S4 - Traditional Hibernation S5 - Off On battery it will cycle through the above, on mains it will only use S0 and S0ix 0-4 Hours - Connected Standby 4-12 Hours - Lite Hibernation 12+ - Traditional Hibernation (It can maintain remaining levels for over a year in this state) ____________________________________________________________________________ Connected Standby is very different from traditional Sleep (ACPI S3) and Hibernate (ACPI S4) states. Sleep and Hibernate completely pause all activity on the system when the processors are turned off. Activity remains paused until the user turns the system back on by pressing the power button, keyboard or touchpad. Connected Standby automatically pauses and resumes activity on the system while the screen is off to maintain connectivity and sync content from the cloud. The amount of activity is tightly controlled to help ensure low power and long battery life. However, the amount of activity varies for each Connected Standby as app activity changes with available networking or incoming data. Sleep and Hibernate states do not maintain connectivity on the network (Wi-Fi, LAN or cellular). In Sleep and Hibernate modes, the networking devices are turned off until the user powers the system back on. Connected Standby keeps the networking devices powered on, but in an extremely low-power mode to maintain connectivity. The Wi-Fi device is able to automatically roam between networks preferred by the user and alert Windows to important network traffic. Sleep and Hibernate states completely pause all app, service, and driver activity when the processors are powered off. Connected Standby allows apps, services, and drivers to keep running, but in a tightly controlled manner to save power and extend battery life. Windows Store apps get a few seconds every 15 minutes to run background tasks, but desktop applications are paused for the duration of Connected Standby. Allowing apps to run in a controlled manner is how email sync and tile updates are performed during Connected Standby. The traditional Sleep (ACPI S3) state consumes 500 milliwatts or more of average power consumption to maintain memory in self-refresh and allow the platform to wake on user input. This gives the typical mobile system with a 45-watt-hour battery just under 100 hours of Sleep time on a full charge. However, Connected Standby systems use low-power memory and power-optimized embedded controllers to consume less than 150 milliwatts in most configurations. This allows the typical platform to remain in Sleep for 300 hours on a full battery charge—3 times longer than the traditional Sleep state. Connected Standby has longer battery life than Sleep and also maintains connectivity. This allows the user to no longer worry about the battery life tradeoff between Sleep and Hibernate, nor worry about the differences in resume performance. A user of a Connected Standby PC can just shut the lid or press the power button and be assured the system will enter a low-power mode and maintain connectivity—just like a smartphone. http://download.microsoft.com/downl...4C9FDB/introduction-to-connected-standby.docx ______________________________________________________________________ Connected Standby Troubleshooting: From an elevated CMD Prompt: powercfg /sleepstudy powercfg /battery powercfg /energy By default all of these command will create an HTML report in the Windows\System32 directory and to read the report requires you to copy them to your profile or you can add the path to your profile in the Command. The Sleep Study will report on each Connected Standby Session showing battery drain and which processes are consuming or preventing successful Connected Standby Sessions. The Battery Report will show your battery performance The Energy Report is a more general report for overall battery usage and consumption, useful in narrowing down likely culprits impacting battery life.