ANAVEM
Languagefr
Windows laptop displaying Event Viewer with power management logs and glowing power indicator
Event ID 105InformationMicrosoft-Windows-Kernel-PowerWindows

Windows Event ID 105 – Microsoft-Windows-Kernel-Power: System Power State Transition

Event ID 105 from Microsoft-Windows-Kernel-Power indicates system power state transitions, typically when Windows enters or exits sleep, hibernate, or shutdown states. Critical for power management troubleshooting.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
18 March 202612 min read 0
Event ID 105Microsoft-Windows-Kernel-Power 5 methods 12 min
Event Reference

What This Event Means

Event ID 105 represents one of the most fundamental power management events in Windows systems. Generated by the kernel-level power subsystem, this event provides comprehensive logging of all significant power state changes that occur on a Windows machine. The event captures not just the transition itself, but also the context surrounding it, including the power source, system capabilities, and the reason for the transition.

The Microsoft-Windows-Kernel-Power provider has evolved significantly with Windows 11 and the latest 2026 updates, now including enhanced telemetry for modern standby scenarios and improved battery life optimization features. The event structure includes multiple data fields that provide granular information about power states, including the previous state, target state, transition time, and any associated error codes if the transition failed or was interrupted.

Understanding Event ID 105 is crucial for modern system administration because power management directly impacts user experience, system reliability, and energy efficiency. In corporate environments, these events help administrators identify systems that aren't properly entering low-power states, which can significantly impact battery life and energy costs. The event also serves as a diagnostic tool for troubleshooting wake-on-LAN issues, scheduled task execution problems, and hardware compatibility issues with newer power management features.

Applies to

Windows 10Windows 11Windows Server 2019/2022/2025
Analysis

Possible Causes

  • User-initiated shutdown, restart, or sleep commands through Start menu or keyboard shortcuts
  • System-initiated power state changes due to power button press or lid closure on laptops
  • Automatic sleep transitions triggered by power management policies and timeout settings
  • Hibernate activation when battery levels reach critical thresholds
  • Wake events from network activity, scheduled tasks, or hardware interrupts
  • Fast startup operations during system boot and shutdown sequences
  • Modern standby entry and exit on compatible Windows 11 systems
  • Power source changes between AC adapter and battery power
  • System firmware (UEFI/BIOS) initiated power management operations
  • Driver-initiated power state requests from hardware components
Resolution Methods

Troubleshooting Steps

01

Review Event Details in Event Viewer

Start by examining the specific details of Event ID 105 to understand the power transition context.

  1. Open Event Viewer by pressing Win + R, typing eventvwr.msc, and pressing Enter
  2. Navigate to Windows LogsSystem
  3. Filter the log by clicking Filter Current Log in the Actions pane
  4. Enter 105 in the Event IDs field and click OK
  5. Double-click on recent Event ID 105 entries to view detailed information
  6. Examine the General tab for power state codes and transition reasons
  7. Check the Details tab for XML data containing power source information and system capabilities
  8. Note the timestamp patterns to identify if power transitions are occurring at expected intervals
Pro tip: Look for the PowerTransitionReason field in the event details to determine if transitions were user-initiated (0), system-initiated (1), or caused by other factors.
02

Analyze Power Events with PowerShell

Use PowerShell to extract and analyze power transition patterns from Event ID 105 logs.

  1. Open PowerShell as Administrator
  2. Query recent power events with detailed information:
Get-WinEvent -FilterHashtable @{LogName='System'; Id=105} -MaxEvents 50 | Select-Object TimeCreated, Id, LevelDisplayName, Message | Format-Table -AutoSize
  1. Extract specific power state information from event data:
Get-WinEvent -FilterHashtable @{LogName='System'; Id=105} -MaxEvents 20 | ForEach-Object {
    $xml = [xml]$_.ToXml()
    [PSCustomObject]@{
        Time = $_.TimeCreated
        PowerState = $xml.Event.EventData.Data | Where-Object {$_.Name -eq 'PowerState'} | Select-Object -ExpandProperty '#text'
        Reason = $xml.Event.EventData.Data | Where-Object {$_.Name -eq 'PowerTransitionReason'} | Select-Object -ExpandProperty '#text'
        Source = $xml.Event.EventData.Data | Where-Object {$_.Name -eq 'PowerSource'} | Select-Object -ExpandProperty '#text'
    }
}
  1. Export power event data for analysis:
Get-WinEvent -FilterHashtable @{LogName='System'; Id=105} -MaxEvents 100 | Export-Csv -Path "C:\temp\PowerEvents.csv" -NoTypeInformation
Pro tip: Use the -StartTime parameter to focus on specific time periods when investigating power-related issues.
03

Configure Power Management Settings

Adjust Windows power management settings to control when and how power state transitions occur.

  1. Open SettingsSystemPower & battery (Windows 11) or Power & sleep (Windows 10)
  2. Click Additional power settings to open the classic Power Options control panel
  3. Select Change plan settings for your active power plan
  4. Click Change advanced power settings
  5. Expand Sleep settings and configure:
    • Sleep after: Set appropriate timeout values
    • Allow hybrid sleep: Enable or disable based on requirements
    • Hibernate after: Configure hibernate timeout
  6. Expand Power buttons and lid to configure physical button behavior
  7. Use PowerShell to view current power configuration:
powercfg /query
  1. Generate a power efficiency report to identify issues:
powercfg /energy /output "C:\temp\energy-report.html"
  1. Create a sleep study report for modern standby analysis:
powercfg /sleepstudy /output "C:\temp\sleepstudy.html"
Warning: Disabling hibernate on systems with limited RAM may impact performance during low-memory conditions.
04

Investigate Wake Sources and Power Requests

Identify what devices and processes are preventing or causing power state transitions.

  1. Check current wake sources using PowerShell:
powercfg /waketimers
  1. List devices that can wake the system:
powercfg /devicequery wake_armed
  1. View active power requests preventing sleep:
powercfg /requests
  1. Examine the last wake source:
powercfg /lastwake
  1. Disable wake capability for problematic devices:
powercfg /devicedisablewake "Device Name"
  1. Check Task Scheduler for wake-enabled tasks:
    • Open Task Scheduler
    • Navigate to Task Scheduler Library
    • Look for tasks with Wake the computer to run this task enabled
    • Review and modify wake settings as needed
  2. Monitor network adapter wake settings in Device Manager:
    • Open Device Manager
    • Expand Network adapters
    • Right-click your network adapter → Properties
    • Go to Power Management tab
    • Configure wake-on-LAN settings appropriately
Pro tip: Use 'powercfg /requestsoverride' to temporarily override power requests from specific processes during troubleshooting.
05

Advanced Power Event Correlation and Registry Analysis

Perform deep analysis of power events and system configuration for complex power management issues.

  1. Create a comprehensive power event timeline:
$StartTime = (Get-Date).AddDays(-7)
$PowerEvents = @(105, 107, 109, 1074, 6005, 6006, 6008)
$Events = Get-WinEvent -FilterHashtable @{LogName='System'; Id=$PowerEvents; StartTime=$StartTime} | Sort-Object TimeCreated
$Events | Select-Object TimeCreated, Id, LevelDisplayName, Message | Export-Csv "C:\temp\PowerTimeline.csv"
  1. Examine power management registry settings:
Get-ItemProperty -Path "HKLM\SYSTEM\CurrentControlSet\Control\Power" | Format-List
  1. Check power policy registry entries:
Get-ChildItem -Path "HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings" -Recurse | Where-Object {$_.Property -contains "ACSettingIndex" -or $_.Property -contains "DCSettingIndex"}
  1. Analyze system firmware power capabilities:
powercfg /availablesleepstates
  1. Generate battery report for mobile devices:
powercfg /batteryreport /output "C:\temp\battery-report.html"
  1. Check for power-related Windows updates and driver issues:
Get-WmiObject -Class Win32_QuickFixEngineering | Where-Object {$_.Description -like "*Power*" -or $_.HotFixID -like "*KB*"} | Sort-Object InstalledOn -Descending
  1. Monitor real-time power events using WEvtUtil:
wevtutil qe System "/q:*[System[EventID=105]]" /f:text /rd:true /c:10
Warning: Modifying power management registry settings directly can cause system instability. Always backup the registry before making changes.

Overview

Event ID 105 from the Microsoft-Windows-Kernel-Power source fires when Windows undergoes power state transitions. This event captures critical information about system power management operations, including transitions to sleep (S3), hibernate (S4), shutdown (S5), and wake events. The event appears in the System log and provides detailed power state data that system administrators use to diagnose power-related issues, unexpected shutdowns, and sleep/wake problems.

This event becomes particularly important when investigating systems that fail to wake from sleep, experience unexpected power cycling, or have issues with modern standby modes introduced in Windows 10 and enhanced in Windows 11. The event contains power state codes, timestamps, and transition reasons that help identify whether power changes were user-initiated, system-initiated, or caused by hardware issues.

In enterprise environments, Event ID 105 serves as a key indicator for power management policy compliance and helps administrators track energy efficiency metrics. The event data includes power source information (AC vs battery), which makes it valuable for laptop fleet management and power consumption analysis in 2026's increasingly mobile-first workplace environments.

Frequently Asked Questions

What does Event ID 105 from Microsoft-Windows-Kernel-Power actually mean?+
Event ID 105 indicates that Windows has undergone a power state transition, such as entering sleep mode, hibernating, shutting down, or waking up. The event contains detailed information about the power state change, including the previous state, target state, power source (AC or battery), and the reason for the transition. This event is completely normal and occurs whenever your system changes its power state, but the frequency and patterns can help diagnose power-related issues.
How can I tell if Event ID 105 indicates a problem with my system?+
Event ID 105 itself is informational and not an error. However, you should investigate if you see unusual patterns such as: frequent unexpected wake events during sleep hours, power transitions occurring without user action, systems failing to enter sleep mode when expected, or rapid cycling between power states. Look at the PowerTransitionReason field in the event details - values other than 0 (user-initiated) or 1 (system policy) may indicate hardware or driver issues. Also check for corresponding error events around the same time.
Why am I seeing multiple Event ID 105 entries when my computer goes to sleep?+
Multiple Event ID 105 entries during sleep transitions are normal, especially on modern Windows 11 systems with Connected Standby or Modern Standby capabilities. You might see separate events for different power state transitions: entering sleep preparation, actual sleep state entry, brief wake events for maintenance tasks, and final sleep state. Each component (CPU, display, storage) may generate separate power transition events. This is expected behavior and indicates that Windows is properly managing power states across different system components.
Can Event ID 105 help me troubleshoot battery drain issues on my laptop?+
Yes, Event ID 105 is valuable for battery drain troubleshooting. Analyze the events to identify unexpected wake events that prevent deep sleep states, which consume more battery. Look for frequent power state transitions that indicate the system isn't staying in low-power modes. Use PowerShell to extract power source information from the events to correlate battery usage with power state changes. Combine this data with 'powercfg /sleepstudy' and 'powercfg /batteryreport' commands to get a complete picture of power consumption patterns and identify applications or drivers preventing efficient power management.
How do I configure Windows to reduce the number of Event ID 105 entries in my logs?+
You cannot and should not try to suppress Event ID 105 entries, as they provide critical power management information. However, you can reduce unnecessary power transitions by: configuring appropriate sleep timeouts in Power Options, disabling wake timers for non-essential scheduled tasks, turning off 'Allow this device to wake the computer' for network adapters if wake-on-LAN isn't needed, and ensuring drivers are up to date to prevent spurious wake events. If log size is a concern, configure Event Viewer log retention policies or use PowerShell filtering to focus on specific time periods when analyzing power events.
Documentation

References (2)

Emanuel DE ALMEIDA
Written by

Emanuel DE ALMEIDA

Senior IT Journalist & Cloud Architect

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...