Understanding how Nrecord.exe controls sleep / wake?

[j2gbpvr]

No power events occurred between 6:57 and 12:02 in the event viewer.

At 8:57 I opened NPVR on the computer and canceled it on the guide.
Not sure why it says Resuming...

The EPG guide has an error that has 11:50 as the end of the program but it actually goes to 12:00.
Been like that for months.

My sleep setting in Power saver options are to sleep after 2 minutes.
Not sure why it sleeps early. I have also tryed 3 and 5 minutes which sleeps after 2.5 and 4.5 minutes.

I disabled EPG update to reduce timers and update manually.
Them MC2XML stopped working and I went to zap2xml.

Attached are todays full logs which did the same thing as yesterday.
It should not have woke at:
2015-10-13 12:03:33.402 [DEBUG][159] Resuming...

[tjzi422xlk]

New upgrader to Windows 10, so new NextPVR user. Thanks for a good replacement for Windows Media Center. Painless switch over except for this one issue.

I need to jump on this thread as I am now seeing this sleep/wake behavior also. It seems to have started after running a day or so. There are no recordings scheduled to run at the time.

My system unattended sleep timeout is 10 minutes. System goes to sleep, and then around a minute later system wakes up. System sits idle for 10 minutes, goes to sleep, and then around a minute later, system wakes up. Windows event log indicates NRecord.exe as the wake source.

NPVR logs don't indicate any thing other than it was resuming:

2015-10-22 15:10:45.343 [DEBUG][3] Resuming...
2015-10-22 15:10:46.500 [DEBUG][6] cycling MVP servers
2015-10-22 15:10:53.116 [DEBUG][9] Recording service noted the system was resuming...
2015-10-22 15:10:53.116 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2015-10-22 15:22:14.312 [DEBUG][21] Resuming...
2015-10-22 15:22:14.421 [DEBUG][6] cycling MVP servers
2015-10-22 15:22:22.194 [DEBUG][9] Recording service noted the system was resuming...
2015-10-22 15:22:22.194 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2015-10-22 15:22:32.209 [DEBUG][21] Resuming...
2015-10-22 15:22:32.522 [DEBUG][9] Recording service noted the system was resuming...
2015-10-22 15:22:32.522 [DEBUG][9] No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2015-10-22 15:22:32.553 [DEBUG][6] cycling MVP servers


Other than this issue everything is great. I rather not have the computer cycling on/off, so any thoughts are appreciated. I can provide more log info or anything else if needed.

Wanted to add:

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\HarddiskVolume2\Program Files (x86)\NPVR\NRecord.exe (NPVR Recording Service)

[j2gbpvr]

Just add the task to restart the recording service.
This works fine for me on all three of my WIN 10 Pro computers.

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"

[jksmurf]

I'm still struggling with this waking the PC every 3 mins.
In this case from 1:52 am onwards. Server is in the bedroom so quite disturbing.

I recorded the lone ranger 9:29pm~12:47am, the PC has a 1hr05mins sleep timer, so that seems to coincide with it trying to sleep. What I still don't get is NRecord appearing to wake it every 3 mins.

cheers

k.

[RTKAT]

A very simple way to fix the problem is to just leave the computer running 24 hours a day. It really does not "hurt" them to run all the time. I have had three year old desktop computers that were purchased off lease and ran them 24 hours for 4-1/2 years without any problems. They were used for CCTV camera servers.

[jksmurf]

A very simple way to fix the problem is to just leave the computer running 24 hours a day. It really does not "hurt" them to run all the time. I have had three year old desktop computers that were purchased off lease and ran them 24 hours for 4-1/2 years without any problems. They were used for CCTV camera servers.

RTKAT - it's certainly one solution; not one I would prefer though. I'm not worried about hurting it (longevity), but noise, the environment and cost are all factors too. I might try j2gbpvr's solution but it's a bit of a hack to get around the issue, rather than addressing it.

[RTKAT]

I do understand. If not used often there would be considerable time just running. In my case, I record so much and so often, it makes it the best way to go. I watch too much TV.

[sub]

RTKAT - it's certainly one solution; not one I would prefer though. I'm not worried about hurting it (longevity), but noise, the environment and cost are all factors too. I might try j2gbpvr's solution but it's a bit of a hack to get around the issue, rather than addressing it.

I spent a few hours trying to reproduce this problem the other day, with the intention of fixing, but I unable to reproduce, so at this stage I don't really have any decent info to go on. No ideas what would be causing it.

[jksmurf]

Thanks for giving it a go anyway sub, appreciated. I wish I could provide enough info for you to troubleshoot it as only you know how.

[jksmurf]

Just thought I'd cross link this thread to bfos' one which seems similar, for future reference.
I know sub had a crack at fixing it (or rather reproducing it) with no firm results.

http://forums.nextpvr.com/showthread.php...y-Wakes-PC

k.