Why is NextPVR waking my Windows 10 system from sleep?

[sub]

You should be able to run the following to see what times NextPVR has requested the machine to be awake. It does this for the EPG update time, and around each recording.

Code:

C:\Windows\system32>powercfg /waketimers
Timer set by [PROCESS] \Device\HarddiskVolume5\Dev\NPVR5\NPVR5\bin\Debug\netcoreapp3.1\NextPVRServer.exe expires at 3:00:00 am on 7/03/2021.
Timer set by [PROCESS] \Device\HarddiskVolume5\Dev\NPVR5\NPVR5\bin\Debug\netcoreapp3.1\NextPVRServer.exe expires at 8:27:30 pm on 6/03/2021.

ie, this is the epg update time, and a couple of minutes before a recording at 8:30pm.

The nrecord.log would have matching info logged:

Code:

2021-03-06 15:17:19.702    [DEBUG][10]    Requesting wake up for 'EPG-UPDATE' [EPG Update] at 7/03/2021 3:00 am
...
2021-03-06 15:18:57.152    [DEBUG][9]    Requesting wake up for 'RecordingOID941' [Alexander] at 6/03/2021 8:27 pm

[PapaJay]

Hi

NextPVR V5 is keeping my Windows 10 system from sleeping again - it has been keeping it awake since late last night.  After implementing a change in the properties of the Realtek GbE adapter to block all but Wake ON LAN magic packets on Friday March 5 later in the day, it slept as expected Saturday and Sunday - during the day when there is nothing to do the system sleeps unless I wake it up by pressing a mouse button.  NextPVR wakes it just before 7:05 PM for a EPG update from Schedules Direct and also for any scheduled recordings.  We wake the system to watch recorded shows.

The Windows 10 Sleep Study Report clearly shows that 'Timer - NextPVRService.exe' has been waking Windows continuously for many hours. NextPVR woke it up at 2021-03-07 at 22:37:39 and there has been a constant cycle of Windows sleeping and NextPVR waking it just over a minute later, except starting at 22:58:45 for 2 hours a 59 minutes when the two shows that recorded successful were being converted to mp4, after which the battle started again and continued until I started gathering PD and making this update which keeps the system awake.

I will upload the NextPVR logs in this post and in a second post I will upload the Sleep Study Report I gathered at 14:52:42 today.

I have no idea why NextPVR needs to keep Windows awake.  Perhaps there is some configuration that I have set incorrectly.

Thanks.  Jay.

[PapaJay]

Hi

Attached is the Sleep Study Report from this afternoon.

Sub, powercfg /waketimers will not run on this level of Windows 10 - no idea why as I has worked in the past.  Here is the command and the error:

---------------------------
C:\WINDOWS\system32>powercfg /waketimers

Unable to perform operation.  An unexpected error (0x65b) has occurred:  Function failed during execution.
------------------------------

The system was updated to a new Windows 10 service level in the last 2 or 3 weeks - perhaps this messed up /waketimers.  Hence I have been running the Sleep Study Report which works.  Also powercfg /lastwake works - I just ran it and here is what it reported at 4 PM this afternoon.

------------------------------
C:\WINDOWS\system32>powercfg /lastwake
Wake History Count - 1

Wake History [0]

  Wake Source Count - 1

  Wake Source [0]

    Type: Wake Timer
    Owner: [PROCESS] \Device\HarddiskVolume2\Program Files\NextPVR\NextPVRServer.exe


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

The wakes that occurred after midnight and until mid afternoon were not due to scheduled recordings or an EPG update as that should not occur until 7:05 PM

Thanks

[PapaJay]

Hi

Maybe attaching the Sleep Study Report will work this time.  Thanks

PS.  Just discovered I can only upload ZIPed files.  Sorry.

[mvallevand]

I am confident it is not Kodi so I am dropping out of this thread. Make sure your advanced power setting don't have the hard drive sharing option enabled.

I will say your system is acting oddly there is now way I can see that it should be issuing spurious Resumes while live TV is streaming.

Code:

2021-03-07 22:08:50.812    [DEBUG][150]    Request had range request
2021-03-07 22:08:50.813    [DEBUG][150]    Requested Range: bytes=146516484- (4371381452 bytes)
2021-03-07 22:08:51.143    [DEBUG][7]    Client has disconnected
2021-03-07 22:08:51.143    [DEBUG][7]    Sent total of 1748400 bytes
2021-03-07 22:09:37.852    [DEBUG][61]    [Resume]
2021-03-07 22:09:37.855     [DEBUG][61]    OnResume...
2021-03-07 22:09:38.086    [DEBUG][61]    [Resume]
2021-03-07 22:09:38.087    [DEBUG][61]    OnResume...
2021-03-07 22:09:43.463    [DEBUG][150]    Client has disconnected
2021-03-07 22:09:43.463    [DEBUG][150]    Sent total of 14607600 bytes
2021-03-07 22:09:45.151    [DEBUG][150]    Got request [192.168.2.102]: /live

Martin

[PapaJay]

Sub

I do know that I need to run the command 'powercfg /waketimers'  from an Administrator Command Prompt window.  The common reason for the command to file with 'An unexpected error (0x65b) has occurred' is that people try to run it without administrator authority.  Somehow the security for the /waketimer option is messed up; all the other powercfg options work fine and most of them require administrator.

Thanks.

[PapaJay]

Hi

Whatever NextPVR was trying to do while it was battling with Windows putting the system to sleep and NextPVR waking it up, finished while I was collecting PD data and updating this post.  The work NextPVR was doing finished somewhere between 2021-03-08 at 14:42:36 and 16:44:03

I can upload another set of NextPVR logs if needed.  Let me know.  Thanks.

PS.  I stopped and restarted the NextPVR Service as there are serval recordings scheduled for tonight.

[Ludron]

We will add this on list for further investigation....

I'm not aware of any NextPVR limits on this stuff, and given there is thousands of people using it regularly - I'm pretty sure I'd have heard about this type of problem before.

Almost like something we hear from SES Astra

[Graham]

The work NextPVR was doing finished somewhere between 2021-03-08 at 14:42:36 and 16:44:03

I can upload another set of NextPVR logs if needed.

Please upload logs that show the period ... between 2021-03-08 at 14:42:36 and 16:44:03 ... Thanks

[PapaJay]

Hi

Here are the logs covering the requested time period.  I stopped and restarted NextPVR Service around 6 PM local time on March 8.  Therefore, I believe it is log1 that covers the time period.

There server where NextPVR Server runs was awake when I got up at 6:20 AM this morning - it should have been asleep as it should have had nothing to do.  I immediately ran the powercfg -lastwake command with the following results:

-------------------------------------------
C:\WINDOWS\system32>powercfg -lastwake
Wake History Count - 1
Wake History [0]
  Wake Source Count - 1
  Wake Source [0]
    Type: Wake Timer
    Owner: [PROCESS] \Device\HarddiskVolume2\Program Files\NextPVR\NextPVRServer.exe

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

I just ran powercfg - sleepstudy and the same as last night Windows and NextPVR were in a battle all night over sleeping the system.  I can upload this sleep study report if needed.

Thanks.