nPVR Continually Wakes PC

[bfos]

I have my PC set to sleep after 45 minutes of inactivity. I also manually put the PC in sleep if I am done working on it and I know there is no reason to keep it awake. However, my PC has been resuming within a minute of when it goes to sleep either on its own or manually.

I check powercfg -lastwake and the answer is nPVR:

[INDENT]C:\Windows\system32>powercfg -lastwake
Wake History Count - 1
Wake History [0]
Wake Source Count - 1
Wake Source [0]
Type: Wake Timer
Owner: [SERVICE] \Device\HarddiskVolume3\Program Files (x86)\NPVR\NRecord.exe (NPVR Recording Service)[/INDENT]

I check the system log and it also lists nPVR:

[INDENT]The system has returned from a low power state.

Sleep Time: ‎2016‎-‎05‎-‎10T12:09:30.293325500Z
Wake Time: ‎2016‎-‎05‎-‎10T12:10:33.042765900Z

Wake Source: Timer - NRecord.exe[/INDENT]

Here is the pertinent listing in NRecord.log:

[INDENT]2016-05-10 07:10:33.002 [DEBUG][22] Resuming...
2016-05-10 07:10:33.225 [DEBUG][6] cycling MVP servers
2016-05-10 07:10:34.084 [DEBUG][50] Resuming...
2016-05-10 07:10:35.227 [DEBUG][6] cycling MVP servers
2016-05-10 07:10:41.418 [DEBUG][9] Recording service noted the system was resuming...
2016-05-10 07:10:41.418 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat[/INDENT]

I've been struggling with this issue for several days trying to find the answer online. I have found threads where the user ends up determining their issue was their keyboard or mouse. I have set those devices to not be able to wake the PC.

I've found other posts where the issue was the EPG Update. I moved the time of the update to be a time that the PC is more likely to already be awake. And since the undesired wakes happen at any time of the day, I don't think this is the issue. I've also made sure that there aren't any scheduled recordings listed or and wake times requested for the times the PC is waking in the NRecord.log (I tried attaching, but the full log is too large).

I did reinstall nPVR yesterday and the first time I put my PC to sleep, it stayed in sleep all day until it's first scheduled recording last night. I thought the reinstall had solved the issue at that point, but later that night when the PC should have stayed in sleep, it continued to wake. It would sleep every 45 minutes as nothing was running on the system (I confirmed with powercfg -requests) and then immediately wake up. This happened all night and continues this morning.

I have also used the Standby Tool to help, but all I have gotten from that is that no other devices have unexpected access to wake the computer.

At this point, I have no idea what else I could check or how to solve this issue. The logs are pretty clear that it is nPVR that is waking the computer. But, I see no reason or indication by nPVR that it needs to be doing that. Is there anything that I have missed or could try?

I think the next thing I plan to try is to disable the nPVR services to see if the PC will stay in sleep. That's the last thing I can think of to prove that it is nPVR that is responsible for the wakes.

Thanks for any help.

UPDATE (5/10/16 9:46AM CST): I went ahead and disabled the nPVR Recording windows service and the PC no longer woke from sleep immediately. Given all of these facts (including the system log and powercfg -lastwake), it's hard for me to see this as an issue outside of that service.

UPDATE (5/10/16 10:27PM CST): Added NRecord log attachment.

[Graham]

(I tried attaching, but the full log is too large).

You need to zip the log before you attach it to a post. Settings --> About has a button that will do it for you.

NextPVR in general, and nrecord in particular, never wake the computer. Nrecord tells Windows that the computer needs to be awake at this or that time and leaves Windows to do its sleep and wake thing. The times for "be awake" requests are in the nrecord log.

My prime suspect would be a dodgy driver. Have you tried telling Windows not to allow your network adapter and TV tuners to wake the computer?

[bfos]

Ok. When I get a chance I'll post the zipped log file.

My network adapter is allowed to wake the computer. I require this for waking the computer via WOL. I'm pretty sure the TV tuners are not allowed, but I'll have to double check that the next chance I get before saying 100%.

A further update....I went ahead and disabled the nPVR Recording windows service and the PC no longer woke from sleep immediately. Given all of these facts (including the system log and powercfg -lastwake), it's hard for me to see this as an issue outside of that service. I do understand what you're saying about NRecord.exe only requesting times for wake by design. That makes sense with what the request entries in NRecord.log. But, absolutely everything else points to NRecord being responsible for the waking.

I'll continue troubleshooting this for a little while (such as trying to recreate the issue with nothing else allowed to wake the pc).. Hopefully, I can get some good ideas here on things to try or someone could look into this being a bug. Though, I feel like my options are going to be limited and I might have to try other solutions for DVR software....if any exist.

[stustunz]

So you did all that but still didnt post the logs so others can actually see whats going on
Then threaten to find other software

[j2gbpvr]

Seems to be the same problem as this link:
http://forums.nextpvr.com/showthread.php...sleep-wake

I had to add a task to restart the recording service.

1. Open Event Viewer, Windows, Logs, System
2. Select Power-Troubleshooter Event ID 1
3. Select Attach Task To This Event..., Next, Next, Start a Program, Browse..., restartnpvr.bat, Next, Finish.
4. Open Task Scheduler, Select Task, In Properties/Triggers, Select Run with highest privileges

restartnpvr.bat
timeout /t 10
net stop "NPVR Recording Service"
net start "NPVR Recording Service"

[bfos]

So you did all that but still didnt post the logs so others can actually see whats going on
Then threaten to find other software

I've attached the NRecord.log from this morning. Sorry for the delay.

I didn't mean that as a threat (not sure who would feel threatened for that matter). It was an expression of my, admittedly, pessimistic sense that a resolution might not be available and the pain I feel just thinking about the task of searching for and testing another piece of DVR software that could replace nPVR.

[bfos]

Seems to be the same problem as this link:
http://forums.nextpvr.com/showthread.php...sleep-wake

Thanks for posting that link. That was not one that I had found previously.

I'm still continuing to read through the thread. It does sound very similar.

Between people restarting the service and scheduling daily reboots, it seems that might be the most commonly adopted workaround for this issue. A batch file to simply restart the service doesn't sound too bad. Have those forced restarts created any other issues for you?

[j2gbpvr]

I think it actually helps to restart the service at least once a day to clear any other problems that may occur.

[2leftfeet]

I have a headless server and 5 clients - all put to sleep when not in use - I have never had the problem of unattended wakeups as reported above, except when I (or wife) inadvertently scheduled a recording by mistake.

That said, I have adopted the strategy of issuing a daily restart on the server (only) after the nightly EPG update in the early A.M. I use PostUpdateEPG.bat for this process and it works well.

Whereas it is true that npvr does not wakeup the PC (Windows does), npvr orders the "hit" so to speak as evidenced by the "powercfg -lastwake" results. Usually the npvr logs provide clues to why npvr orders the hit - that's why they are being requested.

Edit: I did at one time have a problem with the server not going to sleep when expected until I added a registry hack to allow the server to go to sleep with remote opens.

see: http://www.eightforums.com/tutorials/498...opens.html

[bfos]

Does stopping the recording service cancel existing wake requests? Or are those cancelled (and rescheduled) only when the service is started?

My understanding is that the wake requests aren't cancelled and rescheduled until the service restarts as part of the OnStart() routine. If so, then it seems the Recording service must be doing something in addition to just the wake requests to cause these wakes to occur. I say this because I have seen that the unexpected wakes stop as soon as the recording service is stopped (without restarting). If the unexpected wakes were only a result of something going on with existing wake requests, then the unexpected wakes would continue even after stopping the service (because those requests would still exist under this assumption).

Also, I'm noticing some inconsistency regarding the wake requests in my logs. Most often, CancelAllWakeRequests would be followed by each individual request that was cancelled.

Code:

2016-05-09 19:12:42.248    [DEBUG][9]    CancelAllWakeupRequests
2016-05-09 19:12:42.249    [DEBUG][9]    Cancelling wake up request for for 'RecordingOID3589'
2016-05-09 19:12:42.249    [DEBUG][9]    Cancelling wake up request for for 'RecordingOID3589-backup'
2016-05-09 19:12:42.249    [DEBUG][9]    Cancelling wake up request for for 'RecordingOID3589-backup'
2016-05-09 19:12:42.249    [DEBUG][9]    Cancelling wake up request for for 'RecordingOID3597'
2016-05-09 19:12:42.249    [DEBUG][9]    Cancelling wake up request for for 'RecordingOID3597-backup'
2016-05-09 19:12:42.249    [DEBUG][9]    Cancelling wake up request for for 'RecordingOID3597-backup'

At other times and possibly only during OnStart(), the CancelAllWakeupRequests exists but is not followed by each individual cancelled request. Does this indicate that no wakeup requests were found to be cancelled?

Code:

2016-05-11 08:29:59.177    [DEBUG][9]    CancelAllWakeupRequests
2016-05-11 08:29:59.177    [DEBUG][9]    Requesting wake up for 'RecordingOID3601-backup' at 5/11/2016 5:26 PM
2016-05-11 08:29:59.177    [DEBUG][9]    Requesting wake up for 'RecordingOID3601' at 5/11/2016 5:25 PM

Would there be a way for users experiencing this issue to "query" existing wakeup requests?