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

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

1. Open Event Viewer by pressing Win + R, typing eventvwr.msc, and pressing Enter
2. Navigate to Windows Logs → System
3. Filter the log by clicking Filter Current Log in the Actions pane
4. Enter 102 in the Event IDs field and click OK
5. Double-click on recent Event ID 102 entries to view detailed information
6. Examine the General tab for power state transition details
7. Check the Details tab for XML data containing specific power state codes
8. Note the timestamp patterns to identify if transitions are occurring at expected intervals

Use PowerShell to query and analyze Event ID 102 patterns across time periods.

1. Open PowerShell as Administrator
2. Query recent power transition events:

   Get-WinEvent -FilterHashtable @{LogName='System'; Id=102} -MaxEvents 50 | Format-Table TimeCreated, Id, LevelDisplayName, Message -AutoSize

3. Filter events from the last 24 hours:

   $StartTime = (Get-Date).AddDays(-1)
   Get-WinEvent -FilterHashtable @{LogName='System'; Id=102; StartTime=$StartTime} | Select-Object TimeCreated, Message

4. Export power events for analysis:

   Get-WinEvent -FilterHashtable @{LogName='System'; Id=102} -MaxEvents 100 | Export-Csv -Path "C:\Temp\PowerEvents.csv" -NoTypeInformation

5. Analyze event frequency patterns:

   Get-WinEvent -FilterHashtable @{LogName='System'; Id=102} -MaxEvents 200 | Group-Object {$_.TimeCreated.Hour} | Sort-Object Name

Examine system power management settings that might be causing unexpected power transitions.

1. Open Control Panel → Hardware and Sound → Power Options
2. Click Change plan settings for your active power plan
3. Click Change advanced power settings
4. Review critical settings:
   • Sleep → Sleep after (check both AC and battery settings)
   • Sleep → Hibernate after
   • Sleep → Allow wake timers
   • USB settings → USB selective suspend setting
5. Check wake sources using PowerShell:

   powercfg /waketimers
   powercfg /devicequery wake_armed

6. Review power policy using command line:

   powercfg /query

7. Generate a power efficiency report:

   powercfg /energy /output "C:\Temp\energy-report.html"

Identify specific devices that might be causing unexpected power state transitions.

1. Open Device Manager by right-clicking Start and selecting Device Manager
2. Expand device categories and look for devices with power management capabilities
3. Right-click problematic devices and select Properties
4. Check the Power Management tab for wake settings
5. Use PowerShell to identify wake-capable devices:

   Get-WmiObject -Class Win32_SystemDriver | Where-Object {$_.State -eq "Running"} | Select-Object Name, State, StartMode

6. Check network adapter wake settings:

   Get-NetAdapter | Get-NetAdapterPowerManagement | Where-Object {$_.WakeOnMagicPacket -eq "Enabled"}

7. Review USB device power settings:

   Get-WmiObject -Class Win32_USBHub | Select-Object Name, DeviceID, Status

8. Generate a sleep study report (Windows 11/Server 2025):

   powercfg /sleepstudy /output "C:\Temp\sleepstudy.html"

Perform advanced analysis of power events and examine registry settings for comprehensive troubleshooting.

1. Create a comprehensive power event correlation script:

   $Events = @(1, 6008, 41, 102, 107, 109)
   $PowerEvents = foreach ($EventID in $Events) {
       Get-WinEvent -FilterHashtable @{LogName='System'; Id=$EventID} -MaxEvents 20 -ErrorAction SilentlyContinue
   }
   $PowerEvents | Sort-Object TimeCreated -Descending | Format-Table TimeCreated, Id, LevelDisplayName, Message -AutoSize

2. Examine power management registry settings:

   Get-ItemProperty -Path "HKLM\SYSTEM\CurrentControlSet\Control\Power" -Name "*"

3. Check hibernation file settings:

   Get-ItemProperty -Path "HKLM\SYSTEM\CurrentControlSet\Control\Power" -Name "HibernateEnabled"

4. Review power policy registry entries:

   Get-ChildItem -Path "HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings" -Recurse | Select-Object Name

5. Enable detailed power logging:

   wevtutil sl Microsoft-Windows-Kernel-Power/Thermal-Operational /e:true
   wevtutil sl Microsoft-Windows-UserModePowerService/Diagnostic /e:true

6. Create a custom power monitoring script:

   Register-WmiEvent -Query "SELECT * FROM Win32_PowerManagementEvent" -Action {
       Write-Host "Power event detected at $(Get-Date)"
       Get-WinEvent -FilterHashtable @{LogName='System'; Id=102} -MaxEvents 1
   }