Quite far ago I was solving issue of sudden PC wake up from sleep.

I disabled some features but the issue is caused by Fast Startup. I have read somewhere that this issue relates to old devices with some behavior.


  1. PC is turned off.
  2. Then in about 1 min. is turned back.

Event data:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <Provider Name="Microsoft-Windows-Power-Troubleshooter" Guid="{CDC05E28-C449-49C6-B9D2-88CF761644DF}" /> 
  <TimeCreated SystemTime="2018-01-07T19:22:38.826625500Z" /> 
  <Correlation ActivityID="{A0293265-C13C-4FB6-8463-0E8E1102BF70}" /> 
  <Execution ProcessID="4412" ThreadID="8792" /> 
  <Security UserID="S-1-5-19" /> 
  <Data Name="SleepTime">2018-01-07T19:21:34.358049600Z</Data> 
  <Data Name="WakeTime">2018-01-07T19:22:30.192846100Z</Data> 
  <Data Name="SleepDuration">1521</Data> 
  <Data Name="WakeDuration">696</Data> 
  <Data Name="DriverInitDuration">322</Data> 
  <Data Name="BiosInitDuration">1508</Data> 
  <Data Name="HiberWriteDuration">12214</Data> 
  <Data Name="HiberReadDuration">0</Data> 
  <Data Name="HiberPagesWritten">539627</Data> 
  <Data Name="Attributes">33575169</Data> 
  <Data Name="TargetState">4</Data> 
  <Data Name="EffectiveState">5</Data> 
  <Data Name="WakeSourceType">5</Data> 
  <Data Name="WakeSourceTextLength">12</Data> 
  <Data Name="WakeSourceText">USB Root Hub</Data> 
  <Data Name="WakeTimerOwnerLength">0</Data> 
  <Data Name="WakeTimerContextLength">0</Data> 
  <Data Name="NoMultiStageResumeReason">0</Data> 
  <Data Name="WakeTimerOwner" /> 
  <Data Name="WakeTimerContext" /> 

I am (almost) sure that the device of blame is KB or mouse (their nor old neither archaic I think) or both since they share the same USB radio. I would like to keep actual devices with benefit of fast boot.

Because of this I am interested in params (the meaning of them and also meaning of their respective values):

  • Attributes
  • TargetState
  • EffectiveState
  • WakeSourceType
  • WakeSourceTextLength

I suppose these are some C/C++ kind of constant.

Event viewer screen shot

  • 1
    I’m sure this information can be cross referenced but why don’t you just read the event in event viewer. There is an event that tells you why the computer went to sleep, and an event telling you why it woke. If you suspect it’s the keyboard/mouse just unplug them. Within 1 minute you’ll know. – Appleoddity Jan 7 '18 at 20:43
  • @Appleoddity: XML code comes from Event Viewer. You definitely must agree that plug/unplug usb-radio each time of PC use is not really pleasant. – Ucho Jan 8 '18 at 8:25
  • You didn’t understand me. If you think it is the keyboard and mouse, unplug it and test to see if it is or not. In regards to event viewer - I don’t know if what you posted is the proper event or not - all I see are numbers that you are asking us to explain. What I do know is that there is an event generated for each transition of power state and it tells you clearly WHY the transition occurred. So keep looking. – Appleoddity Jan 8 '18 at 13:15
  • @Appleoddity: I’ve add screenshot of Event Viewer so you can see what event describes posted event data. Description is my native language. Just use the text w/o diacritics in G-Translate. It works. I can try the unplugging the devices but there are 2 buts: 1. Not every time this happens. 2. I know the event so maybe it is not so important to test devices. – Ucho Jan 9 '18 at 18:46

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.