topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Thursday March 28, 2024, 6:30 pm
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: PC Time  (Read 7649 times)

Knutchen

  • Participant
  • Joined in 2008
  • *
  • default avatar
  • Posts: 12
    • View Profile
    • Donate to Member
PC Time
« on: March 29, 2012, 01:17 PM »
Hi all,

I am asking for help.

I would like to know when PC

a) has started from off or resumes from standby/hibernate
b) went off or went to standby/hibernate

for, let's say, the last 14 days.

Can anybody help? I use Windows XP.

Best regards

Knutchen

Shades

  • Member
  • Joined in 2006
  • **
  • Posts: 2,922
    • View Profile
    • Donate to Member
Re: PC Time
« Reply #1 on: March 29, 2012, 02:13 PM »
The tool you will find after following this link should be of help to you. It freeware and portable.

Knutchen

  • Participant
  • Joined in 2008
  • *
  • default avatar
  • Posts: 12
    • View Profile
    • Donate to Member
Re: PC Time
« Reply #2 on: March 29, 2012, 02:16 PM »
Thanks for telling. I tried this program before, unfortunately it does not work correctly.

Best regards

Knutchen

40hz

  • Supporting Member
  • Joined in 2007
  • **
  • Posts: 11,857
    • View Profile
    • Donate to Member
Re: PC Time
« Reply #3 on: March 29, 2012, 03:01 PM »
Probably the most reliable way would be to set up a custom view in the event viewer to log and then filter for informational events about going from normal power (S0) to sleep states (S1,S2,S3) and the hibernate state (S4). When you transition from one power state to another Windows broadcasts a system power status change. Those power state changes should show when you 're going in and out of sleep/hibernation.

I'm on the road right now so I can't give specifics, but maybe somebody else at DC could help you from here?

Luck. :Thmbsup:

Knutchen

  • Participant
  • Joined in 2008
  • *
  • default avatar
  • Posts: 12
    • View Profile
    • Donate to Member
Re: PC Time
« Reply #4 on: March 29, 2012, 03:28 PM »
Thanks a lot, 40hz.

I looked up the EventLog, but I admit I was not yet able to find out which EventID numbers are for the named power states.

Perhaps you can consider to give more information later, my question is not urgent. I suppose all the needed information is in the EventLog, but I did not find a program to read it easily. "PC On/Off Time" does not work correct, else it would have been satisfying for my purpose. I would like to distinguish between "off", meaning S1, S2, S3, S4, S5 and "on".

Result given as list, e.g.

on:2012-03-29-17.54.23
off: 2012-03-29-18.23.57
on:  2012-03-29-19.08.12
...

and so on





Knutchen

  • Participant
  • Joined in 2008
  • *
  • default avatar
  • Posts: 12
    • View Profile
    • Donate to Member
Re: PC Time
« Reply #5 on: March 29, 2012, 03:31 PM »
and so on...

[Sorry, sent by accident]

or as graphic, where time can be estimated, will do.

Best regards

Knutchen

4wd

  • Supporting Member
  • Joined in 2006
  • **
  • Posts: 5,641
    • View Profile
    • Donate to Member
Re: PC Time
« Reply #6 on: March 29, 2012, 04:05 PM »
What OS are you running?

If it's Win7 then the attached Event Log filter will display WakeUp events, (which includes Sleep/WakeUp times), for the last 30 days.  Looking at the details for the events will also tell you whether the Hybernation file was written, (hyber.sys).

Open the Event Log and choose:
1) Import Custom View..., select the Sleep-WakeUp.xml file and hit OK to get back to Event Log.

You'll now have a Custom View called:
2) Sleep-WakeUp, you can select the events and save as a CSV for import into Excel, etc. for a bit of data massaging.  You just need the lines starting with Sleep Time and Wake Time, (the time is in UTC so you need to allow for timezone).

2012-03-30_08-02-24.jpgPC Time

Event Source Kernel-Power with an Event ID of 42 will also tell you when the system is entering Sleep mode but doesn't provide much info on why.  I've only seen two reasons on my PC: Application API or System Idle.

There's also the free Event Log Explorer, (register for the free license), that'll work on WinNT and later.
« Last Edit: March 29, 2012, 04:37 PM by 4wd »

40hz

  • Supporting Member
  • Joined in 2007
  • **
  • Posts: 11,857
    • View Profile
    • Donate to Member
Re: PC Time
« Reply #7 on: March 29, 2012, 07:40 PM »
@4wd - thanks for putting that together!  :Thmbsup:


Knutchen

  • Participant
  • Joined in 2008
  • *
  • default avatar
  • Posts: 12
    • View Profile
    • Donate to Member
Re: PC Time
« Reply #8 on: March 30, 2012, 12:34 AM »
Hi 4wd,

I use Windows XP. How can I list WakeUp events there?

Best regards

Knutchen

4wd

  • Supporting Member
  • Joined in 2006
  • **
  • Posts: 5,641
    • View Profile
    • Donate to Member
Re: PC Time
« Reply #9 on: March 30, 2012, 06:52 PM »
I use Windows XP. How can I list WakeUp events there?

I'll have to check further but the XP Pro machine I'm on atm doesn't appear to have any power events listed, which I find a little strange but maybe this is normal for XP.

There appears to be some ready made scripts over on the AutoIt forum so I'll see if I can adapt for your output requirements.

@4wd - thanks for putting that together!  :Thmbsup:

Thanks 40, I kind of like the Event Log in W7 - it and the Task Scheduler are so much better than previous versions.

40hz

  • Supporting Member
  • Joined in 2007
  • **
  • Posts: 11,857
    • View Profile
    • Donate to Member
Re: PC Time
« Reply #10 on: March 31, 2012, 02:10 AM »
Thanks 40, I kind of like the Event Log in W7 - it and the Task Scheduler are so much better than previous versions.

That makes two of us. I especially appreciate the improvements to the task scheduler since I'm big on automation for many systems maintenance tasks. I also try to use embedded utilities within an OS rather than 3rd party tools whenever possible to minimize the opportunity for "bad surprises."
 :Thmbsup: