Why is NextPVR waking my Windows 10 system from sleep?

[Graham]

NextPVR was waking my system since I moved up to V5.  I could speculate that in an effort to fix weird problems on the Windows implementation of NextPVR that somewhere code was added to get NextPVR to wake the PC when NextPVR really has something to do - something like, get notified that Windows is about to sleep, create a wike timer for 1 minute from now, Windows sleeps and the wake timer wakes the PC, and NextPVR can process until Windows sleeps the system again after 2 minutes of what Windows thinks is no activity (an idle system), and the cycle repeats.
 

You might have something ... I vaguely recall reading that NextPVR tells Windows to stay awake while NextPVR is doing something ... Sub is the guy that will have to tell us what NextPVR does.

[mvallevand]

I will speculate that the initial problem was network activity waking the server on the calls from Kodi. The secondary problem was that the unattended sleep setting was happening too soon to close over certain flags in power management, however they were set

The changes weren't from NextPVR but Windows settings can change anytime not just during a software update, @PapaJoy simply had two incorrect setting. Someone, perhaps you @PapaJoy should write up a brief update on the wiki for Windows power management since these two setting, along with BIOS ACPI problems are the usual cause of sleep problems on Windows, independent from NextPVR.

Otherwise I consider this closed and I don't see anything related to a NextPVR issue (or in Kodi as I posted earlier).

Martin

[koijh65]

Hi

I have spent since March 10, when I did my last update, trying to figure out what is going on.  Using suggestions from Graham, Martin, Sub and other information on this forum I put together a set of steps to try to isolate and find a solution to why NextPVR kept waking my PC in the middle of the night.  Here are the steps I took:

1. Tuesday, March 9 - slept Shield when we went to bed around 11 PM - per Windows Sleep Study and entries in the nrecord log, no change in behaviour - once MCEBuddy processing was finished, Windows and NextPVR got into a battle with Windows trying to sleep the PC and NextPVR waking it up with a timer event through the early hours of March 10
   
2. Wednesday, March 10 - powered off Shield (unplugged it) when we went to bed - again no change early morning March 11
   
3. Thursday, March 11 - during the day, reset and re-established Windows sleep values - sleep set to 20 minutes - no change early morning March 12
   
4. Friday, March 12 - investigated and did changed unattended sleep to 20 minutes - finally no battle early morning of March 13
   
5. Saturday, Mach 13 - no changes, no battle early morning March 14
   
6. Sunday, March 14 - left Shield powered up (plugged in) overnight, but asleep overnight - no battle early morning March 15
   

Conclusion: Martin suggested I look at the Windows unattended sleep.  It is controlled by a configuration variable called 'System unattended sleep timeout'.  This is a hidden variable and the Windows registry must be changed to make it visible.  Default is 2 minutes.  It is the timer that is used when a timed event triggers a Windows resume from sleep, or when a Wake on LAN magic packet received by the network adapter triggers resume from sleep.  The other Windows sleep value 'Sleep after' is the timer that is used when an attended event (mouse click, opening a laptop, etc.) wakes Windows.


I set 'System unattended sleep timeout' equal to my value for 'Sleep after'.  Now no matter how my PC wakes, it will only sleep after 20 minutes of inactivity.

More Information:

• Using the Windows Event Viewer and my customized Power Events view, I was able to determine that Windows and NextPVR have been in a battle over sleeping the PC in the early hours of the morning since I installed V5 on December 28.  Early in the morning of December 29 the battle first appeared.  I am not saying that there is anything wrong with NextPVR, just that V5 surfaced a dependency on 'System unattended sleep timeout' that was not there in V4, at least in my experience (it may have been exposed for other users prior to V5).
  
• Between 2020-12-12 and 2021-01-14 no Windows updates were made to this PC (per View Update History)
  

• I had no knowledge of 'System unattended sleep timeout'.  I suspect many other users don't either based on searching the NextPVR forum.  Perhaps this should be documented in the NextPVR Windows material - it would have saved may people a lot of time and effort.
  
• There appear to be 3 scenarios where the default value for 'System unattended sleep timeout' of 2 minutes has impacted users.  1) windows is not sleeping because NextPVR keeps waking it up (my scenario)  2)  Windows is sleeping when NextPVR has woken it to do a recording: 'Recording stopped less than 2 minutes in'   https://forums.nextpvr.com/showthread.ph...dows+sleep  3) During playback - another scenario that we hit where Windows slept when we paused a playback for more than 2 minutes, and another where it was playing and suddenly stopped (we use the Kodi NextPVR client) and after upgrading from Kodi 18 to 19 the sleep during playback problems started - in both of these cases Windows slept the PC because it was idle per the Event Viewer.  
  

Last comments:


Graham.  I am going to disagree with you.  I think Windows is accurately recording the reasons PCs are waking.  

NextPVR was waking my system since I moved up to V5.  I could speculate that in an effort to fix weird problems on the Windows implementation of NextPVR that somewhere code was added to get NextPVR to wake the PC when NextPVR really has something to do - something like, get notified that Windows is about to sleep, create a wike timer for 1 minute from now, Windows sleeps and the wake timer wakes the PC, and NextPVR can process until Windows sleeps the system again after 2 minutes of what Windows thinks is no activity (an idle system), and the cycle repeats.

In my case V5 surfaced a dependency on 'System unattended sleep timeout'.  Is this happening elsewhere?  If possible perhaps the first advice to users seeing weird problems around sleep is to adjust 'System unattended sleep timeout' to equal their value for 'Sleep after' and see if this helps to solve the problem.  Here is a link to the webpage that I used to make 'System unattended sleep timeout' visible and then set it   https://appuals.com/windows-10-sleeps-af...nactivity/

Thanks you to everyone for their patience and help. 

I had the same problem as you. I tried the registry hack. It worked for a couple of days. But, the PC now wakes after 4 seconds of sleep. Do you know any other solutions?