Softwarewindowsbatterylaptopshow-to
Windows' Built-In SleepStudy Report Shows Which Component Drains a Laptop's Battery While the Lid Is Closed
One admin command, powercfg /SleepStudy, writes an HTML report of every sleep session on a Modern Standby laptop, with drain rates and the five most active components in each.

The reason it matters is how modern laptops sleep. Microsoft’s comparison of Modern Standby and S3 says that “when Modern Standby-capable systems enter sleep, the system is still in S0 (a fully running state, ready and able to do work).” Windows 8.1 Connected Standby systems, it adds, “wake up the SoC at least once every 30 seconds to process work.” A closed lid doesn’t mean an idle machine.
The report lists each sleep session with two numbers to read first. One is the drain rate. The other is the share of time spent in DRIPS, Microsoft’s “deepest runtime idle platform state.” A session turns red when “the DRIPS rate is <80% or the drain rate is >= 1% per hour.” At 1% an hour, a full battery lasts about four days in standby. Below roughly 0.33% an hour, it lasts 12 days or more.
Then open a red session. Each one shows “the five most active components (“top offenders”),” with their type, name and device path. Types include Fx devices, activators, networking and the processor, and any component active more than ten percent of the session is highlighted red. Microsoft introduced the tool on the Windows Experience Blog in 2014 as a way to see “which apps and devices are most active during a sleep session.”
Here’s what that looks like in practice. On the Framework Community forum in February 2023, a Framework Laptop 13 owner posting as TheGoldenfox64 “ran sleepstudy report and apparently I was losing power the moment I closed the laptop.” In the report, “the system idle time during the No CS phase of sleep was running for 12 hours,” and it “ate up 81 percent of my battery.” Another member’s reply was blunt: “you’ll just have to deal with it or instruct windows to hibernate instead.”
What the report can’t do is fix the offender. A driver update, a disabled wake source or a switch to hibernate are the usual next steps, and which one works depends on what SleepStudy names.