Missing 8:53 am \StartRecording task

Discussion of getting WMC to work on Windows 10 (unsupported)
Post Reply
Djpasek

Posts: 7
Joined: Tue Jul 21, 2020 2:39 am
Location:

HTPC Specs: Show details

Missing 8:53 am \StartRecording task

#1

Post by Djpasek » Sat Oct 09, 2021 3:00 pm

I am having a problem in Windows 10 Pro v. 21H1 with Windows Media Center v.8.8.5 not waking up properly from Sleep (S3) at the correct time at 8:53 am for a scheduled recording scheduled to start @ 9:00am (and configured to begin recording 2 minutes before the show starts at 8:58 am). Recordings scheduled in WMC for other times of the day wake this HTPC properly at the proper time (5 minutes before the recording begins, which is 2 minutes before the show begins, for a total of 7 minutes before the show begins). I am using an i5-11600 Rocket Lake CPU, Gigabyte Z590 Vision D MB, 64 GB RAM, 2 Hauppauge HVR-2250 TV tuner cards and an ASUS nVidia GeForce 1030 fanless Video Card. W10 and all drivers are completely updated. Everything else works perfectly.

After this HTPC fails to wake properly @ 8:53 am, it remains asleep until 8:58 am when it wakes up. Several minutes later it begins to record the 9:00 am show, usually at 9:01 am, missing the first minute of the show. In the Event Viewer @ 8:58 am when the HTPC wakes it registers the Power-Troubleshooter Event “Wake Source Device-ACPI Wake Alarm” instead of the expected “Wake Source Timer-Windows will execute ‘NT Task\Microsoft\Windows\Media Center\StartRecording’ scheduled task that requested waking the computer”. In Task Scheduler, in the History tab of “Task Scheduler (Local)\Task Scheduler Library\Microsoft\Windows\Media Center\StartRecording” I get a warning @ 8:58 am “Missed task started” with the notation “Task Scheduler could not launch task “\Microsoft\Windows\Media Cener\StartRecording” as scheduled. Instance “(ce56b89a…d233a)” is started now as required by the configuration option to start the task when available, if schedule is missed.”

So it appears that for some reason when I schedule WMC to record a 9:00 am show (configured to begin 2 minutes early @ 8:58 am) the StartRecording task does not launch at 8:53 am like it should. At 8:58 am however, the ACPI Wake Alarm wakes the HTPC anyway, and because the \StartRecording task missed its scheduled start at 8:53 am, it starts at 8:58 am when the HTPC is awakened by the ACPI Wake Alarm, and the show begins to record a little late at about 9:01 am.

Does anyone have any idea why \StartRecording is failing to wake this HTPC @ 8:53 am yet wakes this HTPC up at the correct times for all other recordings during the day? Why is the \StartRecording task at 8:53 am being missed?

Thanks to all in advance for your opinions and insight.

technodevotee

Posts: 728
Joined: Thu Sep 10, 2015 4:10 pm
Location: West Midlands

HTPC Specs: Show details

#2

Post by technodevotee » Sat Oct 09, 2021 5:16 pm

Has the system always done this or did it only start after upgrading to 21H1?

Have you tried scheduling some other task at 08:53 to see if it is peculiar to MWC?

Do you have fast start enabled?

And finally, are you using Don't Sleep?

Djpasek

Posts: 7
Joined: Tue Jul 21, 2020 2:39 am
Location:

HTPC Specs: Show details

#3

Post by Djpasek » Sat Oct 09, 2021 8:18 pm

Good ideas.

1) The CPU, MB, and RAM are new as of June, 2021, so I don't know how they behaved on versions of W10 prior to 21H1. The 21H1 installation was "clean".

2) No I haven't. Good idea. I will try to do that and report back.

3) Fast boot in NOT enabled.

4) I am NOT using Don't Sleep.

Thanks again.

Space

Posts: 2389
Joined: Sun Jun 02, 2013 9:44 pm
Location:

HTPC Specs: Show details

#4

Post by Space » Sat Oct 09, 2021 10:25 pm

My first thought is have you installed the latest BIOS/UEFI for your motherboard? Waking the computer is controlled by the BIOS, so if there is some sort of bug with waking at specific times, it might be fixed by flashing the most recent BIOS. I've had a few times where I had to flash the latest BIOS on a new MB to get it to work properly (and in some cases had to wait for a bug-fix BIOS to be released).

It is a good idea to see if you can set up other tasks to wake the PC to see if they work at the time with which you are having issues.

I also see that Win10 has a "new class of wake timers" called "important wake timers". I have no idea if your issue is related to this, but you may want to research exactly what that means, although if the PC is waking up at other times to record with no problems, it sounds like it may not be related to this, but you never know.

Another thing to look at is if there are any other tasks in the Task Scheduler that may be interfering around that time. I don't see why they would, but perhaps they have priority over other tasks for some reason.

It's my understanding that the way the sleep wakeup timer works is that Windows determines the next time the PC needs to wake up and tells the BIOS (not sure when it does this, if it is just before it goes to sleep, or earlier than that). The BIOS only has the ability to schedule itself to wake up at one time, so there are not several wakeup timers in the BIOS (corresponding to the Windows Tasks), just the one. After it wakes up from that timer, it then sets the next wakeup time in the BIOS before it goes to sleep again.

What this means to me, is that if for some reason it "misses" waking up at the time it was scheduled to wake up (should never happen) it will then never wake up due to any subsequent "wakeup" Tasks in Task Manager, because that was the only wakeup time it knew about. Of course once the PC is woken due to other reasons, it is able to set the next wakeup timer in the BIOS.

This (to me, at least) means that something is either wrong with the BIOS (bug), or something in Windows is overriding the setting of the wakeup timer to the correct time.

These are just the things that came to mind, I'm certainly no expert on this subject, so take my suggestions and thoughts as just that, suggestions and throughts.

Post Reply