Hi,

I have several PCs appear to have the date change on them for periods of
less than an hour every couple of days or so.

When I go into event viewer and look at the appplication or system event
log, I leave the default view up and as you scroll down the list the date
will change then change back to the right order. If I go to View/Newest
First or Oldest First, it stays consistent, for instance one event will show
2/10/08, then the next 3/10/08 then the next back to 2/10/08.

Changes back to the correct date appear to sometimes occur after a
synchronization with a time server so I'm assuming that events in the event
log have an internal date and time that is not shown, so that in the default
list view the order is correct, but the date and time shown in the list view
reflects the date and time in windows when the event was recorded.

Do my assumptions seem correct? Has anyone seen this behaviour before?

I need to understand further how the time in the BIOS and the time in
Windows work with each other. I'm further assuming that the reason the
events are in that order is that the BIOS time is not changing and so the
internal date/time of the event then remains constant allowing me to see the
correct order of events.

Does this assumption appear to be correct?

--
Tom B.

Re: Windows Time and Event Log Order by Gerry

Gerry
Thu May 08 13:50:56 PDT 2008

Tom

This might be your problem:
http://www.computerhope.com/issues/ch000239.htm

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Tom B. wrote:
> Hi,
>
> I have several PCs appear to have the date change on them for
> periods of less than an hour every couple of days or so.
>
> When I go into event viewer and look at the appplication or system
> event log, I leave the default view up and as you scroll down the
> list the date will change then change back to the right order. If I
> go to View/Newest First or Oldest First, it stays consistent, for
> instance one event will show 2/10/08, then the next 3/10/08 then the
> next back to 2/10/08.
>
> Changes back to the correct date appear to sometimes occur after a
> synchronization with a time server so I'm assuming that events in the
> event log have an internal date and time that is not shown, so that
> in the default list view the order is correct, but the date and time
> shown in the list view reflects the date and time in windows when the
> event was recorded.
>
> Do my assumptions seem correct? Has anyone seen this behaviour
> before?
>
> I need to understand further how the time in the BIOS and the time in
> Windows work with each other. I'm further assuming that the reason
> the events are in that order is that the BIOS time is not changing
> and so the internal date/time of the event then remains constant
> allowing me to see the correct order of events.
>
> Does this assumption appear to be correct?



Re: Windows Time and Event Log Order by TomB

TomB
Thu May 08 14:09:00 PDT 2008

Thanks, a cmos issue has not been ruled out yet, that's still one possibility
in my Root Cause Analysis. So far 1 Dell D610 and 2 Dell D620's have this
issue.

I found out that each event has a sequence number associated with it, so
that's why it's shown in order in that view.

--
Tom B.


"Gerry" wrote:

> Tom
>
> This might be your problem:
> http://www.computerhope.com/issues/ch000239.htm
>
> --
>
>
>
> Hope this helps.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
> Tom B. wrote:
> > Hi,
> >
> > I have several PCs appear to have the date change on them for
> > periods of less than an hour every couple of days or so.
> >
> > When I go into event viewer and look at the appplication or system
> > event log, I leave the default view up and as you scroll down the
> > list the date will change then change back to the right order. If I
> > go to View/Newest First or Oldest First, it stays consistent, for
> > instance one event will show 2/10/08, then the next 3/10/08 then the
> > next back to 2/10/08.
> >
> > Changes back to the correct date appear to sometimes occur after a
> > synchronization with a time server so I'm assuming that events in the
> > event log have an internal date and time that is not shown, so that
> > in the default list view the order is correct, but the date and time
> > shown in the list view reflects the date and time in windows when the
> > event was recorded.
> >
> > Do my assumptions seem correct? Has anyone seen this behaviour
> > before?
> >
> > I need to understand further how the time in the BIOS and the time in
> > Windows work with each other. I'm further assuming that the reason
> > the events are in that order is that the BIOS time is not changing
> > and so the internal date/time of the event then remains constant
> > allowing me to see the correct order of events.
> >
> > Does this assumption appear to be correct?
>
>
>