Finally made the Windows 7 move on all workstations and I have been testing sleep mode on several machines. After many trials and tribulations - trying to understand Microsoft massive sleep changes since Vista (the big one being - the machine will not go back to sleep within the proper timeout window after an unattended wake-up with the High Performance Plan in place) - I decided to live with the way 7 sleeps - and even tho the bloody machine falls asleep every half hour if I am not on it - it's a pain but I am getting used to it.
One thing that I am NOT getting used to is this crap - as seen in the System Event log:
The system time has changed to 2010-06-17T06:11:26.500000000Z from 2010-06-17T03:46:49.531021100Z.
Seems that if a 7 machine is slumbering away - regardless of power plan set - when this "event" or whatever the f it is happens - the machine bolts awake and stays that way until the plan timeout - 30 minutes, 3 hours..whatever - expires.
What on God's green earth causes this event - and how do I shut it off? I have probed every service, ****** and area in the OS trying to understand what causes it and I am tapped out.
Is it a motherboard problem? A weak CMOS battery....some BIOS thing that I do have set right. In my wife's case - she got totally pissed off with the 30 minute sleepfest that I told her about with the "balanced plan" in play and made me set her machine to sleep every five hours...
But of course if one of these "system time has changed" events occur - like at 12:37am...the damn machine will then stay away for 5 bloody hours as it attempts to fulfil the parameters of the power plan. Vista on the other hand:
A) Did not do this ridiculous event
B) If it did wake up for an event (Windows Update, Backup, Scheduled Task)...it would go back to sleep 120 seconds after being officially idle.
Really need to understand just WTF this event is and how to rip out whatever is causing it. For the record the event occurs on both mine and my wife's machine and we have the identical GigaByte mobos - so that may be related to some setting in the BIOS....
I look forward to anyone's insight on this.