What is the laptop's warranty status?
If not under warranty consider the feedback hub: (
Send feedback to Microsoft with the Feedback Hub app | Microsoft Support)
Rewritten by AI:
Surface Laptop 7th Edition — Repeated Modern Standby / Hibernate Failure
Device: Microsoft Surface Laptop 7th Edition
Processor: Snapdragon X, 10-core X1P64100 @ 3.40 GHz
OS: Windows 11 Pro, build 26200
System type: ARM64
BIOS: Microsoft 175.235.235, dated 02/04/2026
RAM: 16 GB
The system is repeatedly experiencing failures during or following
Modern Standby (S0 Low Power Idle). I am requesting investigation of a possible
Surface firmware, Snapdragon/SoC, Modern Standby, or power-management driver problem.
Observed behavior
Power/SleepStudy data repeatedly shows substantially elevated power consumption while the machine is supposed to be in Sleep/Modern Standby.
For example, on
August 12, 2026, one Sleep session lasted
3:37:39:
- Energy consumed: 2,222 mWh
- Average power: 613 mW
- Battery drain: 4%
- NoHwDrips.SOC: 99% / 3:36:59
- Exit reason: Restricted Standby Battery Drain Budget Exceeded
- The system subsequently entered Hibernate and later experienced an abnormal shutdown.
The SleepStudy data indicates that the SoC spent essentially the entire session outside hardware DRIPS.
The reported device activity was comparatively small:
- Qualcomm Bus Device: 18 seconds
- PCI Express Root Complex: 9 seconds
- NVMe controller: 2 seconds
- CPU C0 time: 2 seconds
The SleepStudy data therefore does
not identify a single software/device offender whose recorded active time appears sufficient to account for the approximately 613 mW average consumption.
Repeated failures
The same general pattern has occurred repeatedly on
August 10, 12, 14, and 15:
- System enters Screen Off / Modern Standby.
- Sleep consumes substantially more power than expected.
- Modern Standby eventually exceeds its battery-drain budget.
- System transitions to Hibernate.
- Hibernate/resume subsequently fails or the system experiences an abnormal shutdown.
- Windows records Kernel-Power Event 41 with BugcheckCode 0.
August 15, 2026 — Kernel-Power Event 41
The system recorded:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2026-08-15T21:01:49.2010000Z
Event ID: 41
Level: Critical
Computer: Surface-Laptop
The associated Event 41 data includes:
BugcheckCode: 0
BugcheckParameter1: 0x0
BugcheckParameter2: 0x0
BugcheckParameter3: 0x0
BugcheckParameter4: 0x0
SleepInProgress: 5
PowerButtonTimestamp: 0
BootAppStatus: 3221226513
Checkpoint: 16
ConnectedStandbyInProgress: false
SystemSleepTransitionsToOn: 35
BugcheckInfoFromEFI: false
CheckpointStatus: 15
LongPowerButtonPressDetected: false
LidReliability: false
WHEABootErrorCount: 0
Notably:
- BugcheckCode = 0
- WHEABootErrorCount = 0
- LongPowerButtonPressDetected = false
- PowerButtonTimestamp = 0
This does not appear to be a conventional Windows bugcheck/BSOD.
Hibernate resume failure
The system also recorded:
Source: Microsoft-Windows-Kernel-Boot
Event ID: 16
Windows failed to resume from hibernate with error status 0xC0000411.
Windows subsequently recorded:
Source: EventLog
Event ID: 6008
The previous system shutdown was unexpected.
This is significant because the failure is not limited to excessive Modern Standby power consumption; the subsequent
Hibernate/resume process is also failing.
Modern Standby configuration
The system reports:
The following sleep states are available on this system:
Standby (S0 Low Power Idle) Network Connected
Hibernate
Traditional S1/S2/S3 sleep is unavailable because the system uses S0 Low Power Idle. The report also states that S3 is disabled by the current Device Guard configuration and that the hypervisor does not support S3.
Therefore, simply switching this machine to traditional S3 sleep does not appear to be an available normal Windows configuration.
Important SleepStudy evidence
The strongest evidence is the following SleepStudy result:
System Power State: Sleep
Duration: 3:37:39
Energy Change: 2,222 mWh
Battery drain: 4%
Average power: 613 mW
Exit Reason:
Restricted Standby Battery Drain Budget Exceeded
NoHwDrips.SOC:
99%
3:36:59
The system therefore remained outside hardware DRIPS for essentially the entire 3½-hour Modern Standby session.
The reported top offenders accounted for only seconds of active time, while the system averaged approximately
613 mW for the entire session.
What I am asking Microsoft to investigate
Please investigate this as a
platform-level Modern Standby/S0 power-management problem, rather than treating Kernel-Power Event 41 by itself as an unexplained unexpected shutdown.
Specifically, please check:
- Surface Laptop 7th Edition firmware/UEFI
- Snapdragon X/Qualcomm SoC power-management firmware
- Modern Standby/S0 Low Power Idle implementation
- Surface platform/system firmware
- Qualcomm chipset and power-management drivers
- PCIe/NVMe power-state transitions
- Hardware DRIPS entry and exit
- Modern Standby → Hibernate transition
- Hibernate resume failure 0xC0000411
- Whether there is a known firmware or driver issue affecting Surface Laptop 7th Edition systems running Windows 11 build 26200.
Requested resolution
The evidence shows a repeatable sequence of:
Modern Standby → failure to reach hardware DRIPS → excessive standby power consumption → standby battery-drain budget exceeded → Hibernate → Hibernate/resume failure → abnormal shutdown → Kernel-Power Event 41.
I would like Microsoft to determine whether this is a
known Surface Laptop 7th Edition firmware/driver problem and, if not, whether the device requires
firmware remediation, driver remediation, hardware diagnostics, or replacement/service.
I am specifically requesting that this be investigated as a
Modern Standby/S0 platform power-management failure, rather than simply attributing the Event 41 entries to an unexpected shutdown.
Surface Laptop 7th Edition, Snapdragon X, Windows 11 26200.
The system repeatedly fails during Modern Standby.
The power history repeatedly shows abnormally high power consumption during Sleep.
The machine then goes through Hibernate and eventually records an abnormal shutdown.
Sleep sessions consume approximately 600–1,700 mW instead of entering a low-power state,
then transition to Hibernate and eventually produce Kernel-Power Event 41 with BugcheckCode 0.
This has happened repeatedly on August 10, 12, 14, and 15.
Please investigate a Modern Standby/S0 power-management or Surface firmware/driver problem.
Code:
Event[30624]
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2026-08-15T21:01:49.2010000Z
Event ID: 41
Task: N/A
Level: Critical
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Surface-Laptop
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Code:
Event[30589]
Log Name: System
Source: EventLog
Date: 2026-08-15T21:02:01.0630000Z
Event ID: 6008
Task: None
Level: Error
Opcode: N/A
Keyword: Classic,
User: N/A
User Name: N/A
Computer: Surface-Laptop
Description:
The previous system shutdown at 13:33:10 on ?15/?08/?2026 was unexpected.
Code:
Event[30575]
Log Name: System
Source: Microsoft-Windows-Kernel-Boot
Date: 2026-08-15T21:01:46.8000000Z
Event ID: 16
Task: N/A
Level: Error
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Surface-Laptop
Description:
Windows failed to resume from hibernate with error status 0xC0000411.
Code:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 8/15/2026 3:01:49 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Surface-Laptop
Description:
The description for Event ID 41 from source Microsoft-Windows-Kernel-Power cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
0
0
0
0
0
5
0
3221226513
16
False
35
115
False
15
115
False
False
0
0
1
0
The message resource is present but the message was not found in the message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>41</EventID>
<Version>10</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2026-08-15T20:01:49.2016382Z" />
<EventRecordID>351743</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Surface-Laptop</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">5</Data>
<Data Name="PowerButtonTimestamp">0</Data>
<Data Name="BootAppStatus">3221226513</Data>
<Data Name="Checkpoint">16</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">35</Data>
<Data Name="CsEntryScenarioInstanceId">115</Data>
<Data Name="BugcheckInfoFromEFI">false</Data>
<Data Name="CheckpointStatus">15</Data>
<Data Name="CsEntryScenarioInstanceIdV2">115</Data>
<Data Name="LongPowerButtonPressDetected">false</Data>
<Data Name="LidReliability">false</Data>
<Data Name="InputSuppressionState">0</Data>
<Data Name="PowerButtonSuppressionState">0</Data>
<Data Name="LidState">1</Data>
<Data Name="WHEABootErrorCount">0</Data>
</EventData>
</Event>
www.elevenforum.com
www.tenforums.com
www.macrium.com
support.microsoft.com
techcommunity.microsoft.com
