Waking from Sleep frequently - Windows 10 Home

A

Anantha Krishnan R

Hi, I have a Asus Vivobook Notebook (i5-8250U CPU) with Windows 10 Home Single Language (v1803 OS Build: 17134.228). Since last week the notebook wakes abruptly from sleep mode. It goes to sleep without any problem but wakes up after about 4 seconds or 5 minutes or even 15 minutes into sleep. And this happens every time. The duration between being in sleep mode to an abrupt wake is inconsistent. Here is what I have tried from whatever help I found on the internet:


1. I use a Logitech wireless mouse. Removed the plugged in USB transceiver to see if that helps, no it doesn't.

2. Checked running processes in Task Manager, found nothing suspicious or new running in the background.

3. Sleep gets interrupted no matter how I put the notebook to sleep - closing the lid/from power option/power button configured to sleep. These all worked perfectly fine till a week ago.

4. No malware/virus is reported from the Avast anti virus (free version, updated) scan. Have been using Avast free version since I bought this notebook about 6 months ago.

5. Haven't installed any new app in the last week.

5. Checked the Event Viewer. Here are the logs from a recent sleep interruption:


----------------------------------

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 22-08-2018 09:31:32
Event ID: 42
Task Category: (64)
Level: Information
Keywords: (1024),(4)
User: N/A
Computer: 'Leaving this blank'
Description:
The system is entering sleep.

Sleep Reason: Button or Lid

----------------------------------

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 22-08-2018 09:31:35
Event ID: 107
Task Category: (102)
Level: Information
Keywords: (1024),(64),(4)
User: N/A
Computer: 'Leaving this blank'
Description:
The system has resumed from sleep.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{'Leaving this blank'}" />
<EventID>107</EventID>
<Version>1</Version>
<Level>4</Level>
<Task>102</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000444</Keywords>
<TimeCreated SystemTime="2018-08-22T04:01:35.699400300Z" />
<EventRecordID>11611</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="7076" />
<Channel>System</Channel>
<Computer>'Leaving this blank'</Computer>
<Security />
</System>
<EventData>
<Data Name="TargetState">4</Data>
<Data Name="EffectiveState">4</Data>
<Data Name="WakeFromState">4</Data>
<Data Name="ProgrammedWakeTimeAc">1601-01-01T00:00:00.000000000Z</Data>
<Data Name="ProgrammedWakeTimeDc">1601-01-01T00:00:00.000000000Z</Data>
<Data Name="WakeRequesterTypeAc">0</Data>
<Data Name="WakeRequesterTypeDc">0</Data>
</EventData>
</Event>

-------------------------------

Log Name: System
Source: Microsoft-Windows-Kernel-General
Date: 22-08-2018 09:36:46
Event ID: 1
Task Category: (5)
Level: Information
Keywords: Time
User: N/A
Computer: 'Leaving this blank'
Description:
The system time has changed to ‎2018‎-‎08‎-‎22T04:06:46.500000000Z from ‎2018‎-‎08‎-‎22T04:01:35.699713800Z.

Change Reason: System time synchronized with the hardware clock.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-General" Guid="{'Leaving this blank'}" />
<EventID>1</EventID>
<Version>1</Version>
<Level>4</Level>
<Task>5</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2018-08-22T04:06:46.499845200Z" />
<EventRecordID>11612</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="7076" />
<Channel>System</Channel>
<Computer>'Leaving this blank'</Computer>
<Security />
</System>
<EventData>
<Data Name="NewTime">2018-08-22T04:06:46.500000000Z</Data>
<Data Name="OldTime">2018-08-22T04:01:35.699713800Z</Data>
<Data Name="Reason">2</Data>
</EventData>
</Event>

-----------------------------------



My questions:

1. Is it a problem from a recent Windows update. Has anyone else faced this recently?

2. Any solutions. I had disabled some clock/time sync setting (don't remember exactly what) after reading from a thread that had a similar issue. But that didn't help.

Continue reading...
 

Similar threads

N
Replies
0
Views
28
NoppolRungRuang
N
E
Replies
0
Views
45
Ermir osmani
E
D
Replies
0
Views
61
Dylan Schulze
D
Back
Top Bottom