wliao Veteran 398 Posts user info edit post |
I'm running windows xp x64 on my laptop which is an emachines m6805. I"m having a problem with the system time being way off. The time gradually gets further and further behind until i change it. Whenever the time is off i'd syncronize it with the windows network time, but then it would be off again. Like when the actual time shold be 9:00 it incorrectly states something like 8:50 or something. Btw, i also have windows xp home edition dual booted and when i'm on that, the time is never wrong. Does anyone know how to fix this? 3/1/2006 9:13:18 PM |
Specter All American 6575 Posts user info edit post |
Get the cmos battery checked out 3/1/2006 9:24:36 PM |
wliao Veteran 398 Posts user info edit post |
^i don't think that's the problem since it works fine with 32bit windows xp home when it just doesn't work properly on xp x64. 3/1/2006 9:26:40 PM |
wliao Veteran 398 Posts user info edit post |
bttt 3/2/2006 9:22:22 AM |
darkone (\/) (;,,,;) (\/) 11611 Posts user info edit post |
I'd get the cmos battery checked anyway. That's the source of the problem 99.999% of the time. Otherwise, I'd search through the window's documentation on microsoft's website to see if the problem has been reported before. 3/2/2006 11:02:59 AM |
HaLo All American 14276 Posts user info edit post |
is it possible that the x64 version doesn't sync with internet time servers and the 32 bit version is set to? 3/2/2006 5:31:46 PM |
Aficionado Suspended 22518 Posts user info edit post |
Quote : | "I'd get the cmos battery checked anyway. That's the source of the problem 99.999% of the time. Otherwise, I'd search through the window's documentation on microsoft's website to see if the problem has been reported before." |
if it is fine on 32 bit then the battery is fine...dont waste your time changing it because it isnt worth it3/2/2006 5:38:28 PM |
Excoriator Suspended 10214 Posts user info edit post |
running in 64bit mode could possibly affect the system clock frequency by a marginal amount - I know that older versions of windows base their time off the system clock, but i dunno about all these new fangled OSes 3/2/2006 5:44:09 PM |
smoothcrim Universal Magnetic! 18968 Posts user info edit post |
thats really the only way to do it, short of putting an actual clock on the board 3/2/2006 5:45:39 PM |
Excoriator Suspended 10214 Posts user info edit post |
well a few posts up was the first i'd heard of windows syncing with some internet server somewhere so i was just assuming that xp64 would do that also... my speculation would be any combination of these:
A) when running in 64bit mode, the processor's system clock frequency changes marginally due to additional capacitance or whatever
B) the processor's system clock drifts marginally in either mode
C) 64bit windows doesn't properly sync with the servers, but the other version of windows does
In any event, ur screwed. Could be a failing capacitor somewhere on your board... Tracking down system clock slowdown/speedup beyond cmos battery is a notorious pain in the rear. 3/2/2006 6:02:16 PM |
wliao Veteran 398 Posts user info edit post |
^ well today i woke up and looked at the clock and it was not a marginal difference. it was behind by almost an hour. when i manually syn the time with the windows time server, it changes to the correct time. the syncing should not be the problem. even if i turn off the windows clock syncing altogether, the time still gets off. and also, i don't think it's that capacitor problem since evertying works properly on when running xp home. i'm thinking that it's a problem with x64 and either notebook computers in general or a specific bios incompatability with my machine, or else this problem would be occuring on both of my operating systems. 3/4/2006 3:00:15 PM |
Wolfrules All American 1880 Posts user info edit post |
is there anything running that is killing the processor?
the OS may not be checking the CMOS clock at the regular intervals it should be doing, so over time it falls behind. 3/5/2006 1:17:00 AM |
dFshadow All American 9507 Posts user info edit post |
i have no idea what's wrong but just running the sync every hour with a scheduled batch task or some small app like this] 3/5/2006 1:20:53 AM |
wliao Veteran 398 Posts user info edit post |
there is nothing running that is killing the processor. and buy just running a program to sync the clock is a temporary fix. even after say 5 minutes the clock is already wrong by like 1 minute. by just syncing the clock every hour really just masks a bigger problem with the OS.
btw, Is anyone actually using windows xp x64?
[Edited on March 5, 2006 at 1:53 PM. Reason : btw] 3/5/2006 1:52:37 PM |
Wolfrules All American 1880 Posts user info edit post |
i'm running x64.. clock has always been accurate.. and i leave this computer on all the time, run cpu intensive stuff sometimes (HDTV decoding)..
now on my 32-bit system before upgrading.. my clock would be a few minutes slow in a 24 hour period.. I had to change the registry entry to make the time sync more often than a week..
just change out the CMOS battery and see what happens.. worse case.. you're out a few bucks.. 3/5/2006 2:04:18 PM |
wliao Veteran 398 Posts user info edit post |
^ what computer do you have? are you running desktop or laptop? 3/5/2006 2:31:36 PM |
Wolfrules All American 1880 Posts user info edit post |
custom built athlon 64 3200+ venice core on an epox 9npa+ultra board.. 3/5/2006 5:39:22 PM |