- September 1, 2008
- 21,544
- 8,236
- Home Country
-
New Zealand
Thanks skipterry - I see what you mean.
It's an odd situation. I'm not an expert with W10 (still using XP) or power problems, but I don't see anything obviously wrong.
Having said that, there is this one error in the TV Server Configuration log which hints at a potential problem with your PowerScheduler configuration:
[collapse]
[2016-01-06 11:40:32,606] [Log ] [SetupTv ] [ERROR] - Exception
ystem.ArgumentOutOfRangeException: Value of '0' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at PowerScheduler.Setup.PowerSchedulerSetup.buttonPowerSettings_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)[/collapse]
I'm not sure whether that's something that could cause what you're seeing or not.
The other thing I notice is that there's an entry in your Windows system event log which looks like a reference to the wakeup timer:
"06/01/2016 11:41:22";"Microsoft-Windows-Kernel-Power";"(102)";"Information";"The description for Event ID '107' in Source 'Microsoft-Windows-Kernel-Power' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'5', '5', '5', '2016-01-06T11:58:00.000000000Z', '2016-01-06T11:58:00.000000000Z', '2', '2'";"107"
Again, unfortunately I don't know what this means...
It's an odd situation. I'm not an expert with W10 (still using XP) or power problems, but I don't see anything obviously wrong.
Having said that, there is this one error in the TV Server Configuration log which hints at a potential problem with your PowerScheduler configuration:
[collapse]
[2016-01-06 11:40:32,606] [Log ] [SetupTv ] [ERROR] - Exception
Parameter name: Value
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at PowerScheduler.Setup.PowerSchedulerSetup.buttonPowerSettings_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)[/collapse]
I'm not sure whether that's something that could cause what you're seeing or not.
The other thing I notice is that there's an entry in your Windows system event log which looks like a reference to the wakeup timer:
"06/01/2016 11:41:22";"Microsoft-Windows-Kernel-Power";"(102)";"Information";"The description for Event ID '107' in Source 'Microsoft-Windows-Kernel-Power' cannot be found. The local computer may not have the necessary registry information or message DLL files to display the message, or you may not have permission to access them. The following information is part of the event:'5', '5', '5', '2016-01-06T11:58:00.000000000Z', '2016-01-06T11:58:00.000000000Z', '2', '2'";"107"
Again, unfortunately I don't know what this means...