Computer Won't Sleep After Upgrade to v6

[Radar73]

Everything was fine on v5, after upgrading to v6 NextPVRServer.exe prevents the computer for going to sleep.  NextPVR isn't recording at the time or doing an EPG update, but it still keeps the computer awake.  A reboot fixes it for a short time.  Tuners are not primed, I toggled it to make sure it's off.  powercfg output is below and logs are attached.  Anything obvious I should check?  Thanks.


C:\WINDOWS\system32>powercfg -requests
DISPLAY:
None.

SYSTEM:
[PROCESS] \Device\HarddiskVolume2\Program Files\NextPVR\NextPVRServer.exe

AWAYMODE:
[PROCESS] \Device\HarddiskVolume2\Program Files\NextPVR\NextPVRServer.exe

EXECUTION:
None.

PERFBOOST:
None.

ACTIVELOCKSCREEN:
None.

[mvallevand]

Windows sleep is magic. There are other posts telling use that NextPVR v6 would sleep more than v5.

It looks like your PC is sleeping and on minute later waking which indicates an issue with your hidden sleep setting for unattended sleep mode.

Code:

2022-10-05 22:17:58.319    [DEBUG][50]    [Suspend]
2022-10-05 22:17:58.321    [DEBUG][50]    OnSleep...
2022-10-05 22:17:58.322    [DEBUG][50]    stopping device process
2022-10-05 22:18:11.518    [DEBUG][15]    <?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
<Status>
<Device oid="20" identifier="Hauppauge WinTV-7164 BDA ATSC/QAM Tuner     (ATSC)"> </Device>
<Device oid="22" identifier="Hauppauge WinTV-7164 BDA ATSC/QAM Tuner     (ATSC)     (#2)"> </Device>
</Status>
</rsp>

2022-10-05 22:18:17.939    [DEBUG][15]    [Resume]
2022-10-05 22:18:18.024    [DEBUG][15]    OnResume...
2022-10-05 22:18:18.730    [DEBUG][51]    [Resume]
2022-10-05 22:18:18.737    [DEBUG][51]    OnResume...

Martin

[Radar73]

Thanks Martin, I'll check out windows sleep settings for unattended sleep mode and see if it helps.

[Radar73]

So this issue persists for me, what you see in the previous log there may just have been when I was testing and restarting the computer after a sleep test.  I don't think it's tied to unattended sleep mode as the computer never tries to enter sleep due to NextPVRServer.exe blocking sleep as seen in C:\WINDOWS\system32>powercfg -requests posted above.  NextPVRServer shouldn't be doing anything to stay listed under powercfg ... EPG update is not happening, the NTray shows no active streams, client is not running, digital tuners are not primed, yet it doesn't relinquish it's hold on power settings.  If I restart the NextPVR service the computer sleeps as expected since NextPVRServer.exe is no longer present in powercfg -requests.  After some period of watching LiveTV and exiting the NexPVR Client, powercfg -requests will show a wakelock again for NextPVRServer.exe, preventing sleep.

New log is attached.

Thanks.

[mvallevand]

What do you want us to see in those logs? The server is awake because you are watching LiveTV and NextPVR does tell the server to stay awake during Live TV.

2023-01-07 17:22:18.033 [DEBUG][9] Active...staying awake

I am not sure if there is an corresponding message when NextPVR stops preventing sleep but there wasn't enough time after you stopped live tv for NextPVR to sleep.

Martin

[Radar73]

Not sure what the log would or would not show about NextPVR not removing the wakelock after exiting the client, which is why I posted it.  What is responsible for removing the wakelock?  Is that done programmatically in NextPVRServer or does Windows do that by itself?  What would cause NextPVRServer to maintain a wakelock when it isn't doing anything after exiting a client?

[mvallevand]

I would need to see it go long enough to actually sleep. I know my Windows test machine does sleep after live tv.

Martin

[Radar73]

I don't think you'd see anything about sleeping in the log as once NextPVRServer gets into the state of not removing the wakelock, it stays like that indefinitely or until the service is restarted, the service must think it's still active for some reason.  Is there anyway to get more detailed logs that may say something about still being active after the client exits?

I realize this issue seems to only affect me ... I may have to go extreme and reformat and install from scratch.  This issue only started after upgrading to v6, currently on 6.1.1 (221106).

Thanks for your time.

[mvallevand]

Sub probably needs to log when the lock is closed to help analyze this further.

Martin

[Radar73]

I'll hold off on formatting to see if Sub has any insights.  It's good to know that you don't have sleep issues on your windows machine with v6, so at least in the eventuality I format, I might get back to normal.