seekermeister
Honorable Member
- Joined
- May 29, 2009
- Messages
- 1,496
- Thread Author
- #1
It's never been a problem before...at least not like this. At about 4:00 A.M. I noticed that Windows time was 2 hours behind the actual time, so I ran a sync on time.nist.gov, which corrected it. However, just ~20 minutes later, I was dismayed to see it had gone back again, but this time 3 hours. I changed the time server to time.windows.com to correct it, and then left computer until now, and found it now 4 hours in the past.
This behavior isn't because of a problem with the BIOS time, and since it occurred on two different time servers, I doubt that is a problem. Why does it keep jumping back in time?
EDIT: Not only are the time jumps progressive in scale, but they are to precise hours...the minute time is always correct. Thinking this may possibly be due to some kind of AV infection, I just started a custom full scan of the OS drive with Kaspersky, even though it had automatically run a rootkit scan at 6:00 A.M.
This behavior isn't because of a problem with the BIOS time, and since it occurred on two different time servers, I doubt that is a problem. Why does it keep jumping back in time?
EDIT: Not only are the time jumps progressive in scale, but they are to precise hours...the minute time is always correct. Thinking this may possibly be due to some kind of AV infection, I just started a custom full scan of the OS drive with Kaspersky, even though it had automatically run a rootkit scan at 6:00 A.M.