• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

My clock is running too fast....what would cause that?

N

new2AMD

Diamond Member
I reset my computer clock running in the taskbar to the time on my tv at around 4:15. Now at 6:36 on my tv it says 6:46 on my computer. The reason I had to reset my clock time was cause I noticed it was over an hour off. What would cause this on how do I fix it?

windows xp BTW
 
The best thing I can think of to fix this is to sychronize the clock to a windows time server nightly. I have heard of clocks slowing down because of the CMOS battery dieing... but never speeding up. Try replacing your CMOS battery and see what happens.
 
Wow, wierd. There are two sources of time in Windows, actually there are more but for practical purposes... there is a hardware timer chip (that long ago ceased being a chip and became just some more transistors in the integrated chipset) that drives things like interrupts and the system clock. There is also a CMOS clock. I don't know which one the Windows desktop clock relies on. It is possible to program the 8254 timer chip to run faster, and if you aren't careful you can make all the other clocks run faster. I don't think you can change the tick rate of the CMOS clock from software, but maybe you can. Have you installed any utilities or services lately that might be expected to hook system time?
 
This happens on my computer too. I have a custom built machine based on a Abit NF7-S 2.0. Its really annoying. I have never figured out why the clock is so fast.
 
Are you overclocking? I remember back in the Celery 300a + BH6 days, running my Celery @103 MHz FSB (Abit had a "turbo" setting that would add 3 MHz to the FSB) so it was @ 464 MHz total would cause the clock to run faster than normal. I'd be off by 15 minutes at the end of a month.

I think it was because 103MHz wasn't a standard frequency and was probably overclocking whatever timer chip it was using. I bet if I had the normal overclock @100MHz FSB, I wouln't have had the whacked clock.
 
it has happened to me a few times as well. it only happened when i tried to syncronize the clock. and i could never get it back to normal. sometimes it would go back to normal on its own, but i have had no solution for it :/
 
This system has been together for a while now (a good 2 years) and I have made no changes so the CMOS battery seems to be the culprit. It just started happeneing. I will replace the battery and update this thread.

thanks
 
Try pulling any PCI cards you may have installed and see what happens. I fixed this condition on one of my old PCs by moving a card to a different PCI slot.

CxP
 
Originally posted by: ClockerXP
Try pulling any PCI cards you may have installed and see what happens. I fixed this condition on one of my old PCs by moving a card to a different PCI slot.

CxP
Click to expand...

No pci cards in use. Im telling ya, I have not changed a thing and all of a sudden this has happened.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top