Scheduling Recordings corrupts waketimers - Windows10

[dvgeek]

Hi,

Recently moved to NextPVR from Argus due to lack of any development on Argus. Built a new TVServer machine with NextPVR (HDHomeRun Tuners), recordings etc.

Next day I check - no recordings - looks like the PC did not wake up. Checked the forums - saw that NextPVR schedules wakeup via windows API's, and they should be visible via the command 'powercfg -waketimers' in a DOS Admin window. Running that command gave me an error (0x65b) - all other powercfg commands work. Did some research and the only advice was to do a restore. Oh Well.

I reformatted the drive - installed fresh Windows. This time after installing every update and every piece of software, I would run the 'powercfg -waketimers' command to see if it was still okay. Till the last - everything was okay. With all software installed I scheduled a recording. Checked the 'powercfg -waketimers' command. Corrupted - same error (0x65b). All other powercfg commands work.

Totally puzzled - how scheduling a recording in NextPVR can do this. Anyone encounter this?

Thanks!

[sub]

I'd never heard of "powercfg -waketimers" listing the wake times for NextPVR (but I just tried it, and it did work). Usually I just tell people to look in nrecord.log for "requesting wake up" messages like these:

2017-02-27 19:59:51.243 [DEBUG][8] Requesting wake up for 'RecordingOID140817' at 27/02/2017 9:27 PM

That said, if "powercfg -waketimers" is returning an error, and your machine is not waking up, then it's maybe a sign your machine has some fundamental issue with waking. I remember some users with waking problems have had to enable ACPI, or change ACPI settings in their BIOS. Maybe you're in this group.

[dvgeek]

So did some more testing.
Deleted all the scheduled recordings. With no recordings scheduled - Lo and behold - powercfg -waketimers works again!

Started creating new recording schedules and checked the command after every new schedule - 46 shows scheduled - on the 47th entry - the command fails. Could be a limit on the NextPVR database? Or there is a limit on the number of recordings that can be scheduled.

[dvgeek]

I had never heard of "powercfg -waketimers" before today either - but this was what that pointed me there --> http://forums.nextpvr.com/showthread.php...rding-time

[sub]

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.

Maybe your BIOS has some limits on the number of wake timers?

[HarryH3]

Currently have 60 recordings scheduled here with no problems, but my server is on Win 7, using an ancient Core2Duo CPU on an Intel motherboard.

[dvgeek]

No limits on the BIOS - maybe it's a Win10 issue - I did a trial on Win7 and works fine...

[sub]

No limits on the BIOS - maybe it's a Win10 issue - I did a trial on Win7 and works fine...

No, it wont be that - I'm using Win10 so would have noticed it. I'd say at least half the people here are using Win10 these days.

Maybe check if there is an updated BIOS available for your motherboard.

[mvallevand]

Perhaps your hibernate file is too small.

Martin

[scJohn]

I was curious, so I ran powercfg -waketimers and got the (ox65b) error. But my Win10 machine wakes up and records fine.