System clock running fast

My system clock is now gaining about a minute every hour! Sometime ago, it was gaining ~ 7-8 sec/hour. I got that to ~ 7-8 sec/day by disabling spread spectrum in BIOS. Ran like that for 4-5 months.
Any ideas on what is going on?
Thanks
K7N2-Delta L, Athlon XP 2600
Antec 350 watt ps
CPU temp 43-45C, system 36-37C
2 7200 HDD
1 CDRW.

Quote
Originally posted by jelenko
It's the battery that came with the motherboard [say cr2032].
In any case, replacing the battery removed the problem. No time gain after two days.
Thanks
That was the battery I was talking about. Glad you got it working.

Similar Messages

VM System clocks running fast

I'm running 3 VMs (OEL R4) on a single host.
I've noticed the clocks in the VMs are running faster than the host.
I found a couple of threads about this in the XEN groups - including one about adding "xen.independent_wallclock=1" in sysctl but I get errors with that.
Right now I'm reduced to running a timesync (ntpdate) every 3 minutes to keep the clock on time.
It averages a gain of about 3 sec/min and even more than that when the CPU is 100% loaded.
Anyone else ran into this?

Alan3 wrote:
I'm running 3 VMs (OEL R4) on a single host.
I've noticed the clocks in the VMs are running faster than the host.Are these HVM or PVM guests?
I found a couple of threads about this in the XEN groups - including one about adding "xen.independent_wallclock=1" in sysctl but I get errors with that.This setting only works on PVM guests -- by default, a PVM guest uses the hardware clock of the VM Server. Setting this option means the guest can keep its own time.
Right now I'm reduced to running a timesync (ntpdate) every 3 minutes to keep the clock on time.
Anyone else ran into this?Yes, it's pretty standard on Xen virtual machines. I always insist that clients run ntpd inside HVM guests and the Dom0 (for PVM guests) on all my Oracle VM Servers. You can also use the independent_wallclock option and ntpd for PVM guests if you don't want to run ntpd in Dom0 (or perhaps have no access to ntp time sources from the Dom0).

STRANGE!!! Windows Xp clock running fast....

Hi guys. Youve helped me in the past so I hope you can help me again!
My MSI system has been running solid as a rock for about 1and1/2years now. Very happy with it. untill now..
It all started after I installed a bluetooth dongle (or so i though). I suddently realised that my xp clock was running fast about 10seconds every minute. I though this is weird so did the obvious things... restarted comp checked bios which was running fine. It is only when I get into windows that it starts to run fast. I uninstalled the bluetooth software thinking it was the culprit but obvoisuly wasnt. I then decided it was about time that i reformatted again anyway so reformatted and sure enough it fixed the problem, proving to me that it is a software problem not a hardware. Then, after about 4 months of my new reformatted system being up and running it suddenly has started doing it again. I havent even installed the bluetooth software or anything that is obviouslty the problem. I dont know if this has anything to do with it but my firewire card has also stopped working for somereason. I replaced it with a new one and that doesnt work either!
Any ideas anyone, ive searched the whole forum and internet and it doesnt seem like a common problem!
Many thanks
Jon.

Hello hurndall:
I see you are running XP/SP2 with all patches. Besides that, are you running any third party software that monitors communication? Looking at this from the paranoid perspective, have you run a spyware/malware sweep of your system?
The Windows Time service that you stopped is used to synchronize time across a network and does not directly control your RTC. Unless systems on your network are using it there will be no effect, so you can probably leave it stopped.
Regarding your fast clock problem, I have had this type of problem on PC platforms that were using the RTC interrupt to start background tasks such as data logging or other hardware. The hardware RTC clock uses IRQ 8; old MS-DOS software would modify the code associated with this interrupt to give pseudo-real time operation to specific processes. As I recall there is/was a timer that pinged this IRQ at 13.8 ms intervals and so kept the clock going. Although the usual symptom in these cases was a clock running SLOW, not fast, it is possible to have a clock run fast due to a bug in the added software.
You can do a rudimentary check on your system by starting Control Panel - System - Hardware - Device Manager - View - Resources By Connection - IRQ
Look at IRQ 8 - it should only be associated with the RTC function.
This is probably not going to get you anywhere but it is something that should be checked anyway.
Looking at your problem from the other direction, it seems that your system has issues with communication devices - Bluetooth, FireWire and now Remote Login. I'm not sure how you are communicating with your system remotely (network - i.e., ethernet or dial-up, i.e., modem), but you might want to reinstall/update the drivers associated with your Ethernet or Modem hardware. Since the problem seems to go away on a reinstall, which refreshes all these drivers, you might want to try this. It's a lot simpler than a reinstall.
The Remote Login Service installs and/or starts a number of services that depend on the svchost.exe module. It seems unlikely that there is a problem there but you might want to make sure that svchost.exe is truly the SP2 version or whatever is the most recent. I don't know if any patches since SP2 have modified it. You could look at another XP system can check the properties of svchost.exe.
My system reports
File Version 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
Product Version 5.1.2600.2180
for svchost.exe
Sorry I can't give you any more specific help.
Good luck,
ss

Clock runs fast

I just got my new Mac Pro (3.0) and I've found the clock runs fast, easily slipping an hour every day. Even when I have it set to use Apple's time servers, I've found that the clock easily slips several minutes into the future.
1) Can I fix this somehow?
2) Can I get "set date and time automatically" to update more frequently?
Thanks!

Thomas-
Are you running Leopard Server? I am, and I think I've narrowed it down to that.
On a separate, newly formatted drive, I created two partitions. On one, I installed Server. Bare bones, no updates, etc. On the other, I installed Client. End result? Server runs fast (4 s/m), Client runs fine. Client also runs fine on my MacBook. When I make a copy of my Server drive to my MacBook (Restore from Disk Utility), I have no time loss.
So, it seems it's combination of software and hardware (in my case). I really hope you're running Server so I can report this bug, somehow.

Mavericks clock running fast

Since my Mavericks upgrade, my 27" iMac clock runs fast. It was about 3 min fast today after a few weeks since I reset it last.
If I open my Date & Time Preferences it corrects the time, but then continues to run fast.
I have it set to: Set date and time automatically: Apple Americas/ U.S. (time.apple.com)
I do not have a check to set time zone automatically, but chose the city.
Any suggestions?

Hi...
Try this support article > OS X: Incorrect date or time displayed in various applications

Windows 2008 R2 OS Clock runs fast and gains 2-3 seconds in a day

I have got many servers running Windows 2008 R2 Ent 6.1.7601 Service Pack 1 Build 7601 on HP DL 360 gen7 servers. The problem is that the clock being maintained by the OS runs fast. NTP is being used to mitigate the issue but need to identify the root
cause of the problem. I have verified that the hardware clock is not at fault as after running the system for 5 days the clock went ahead by nearly 12 seconds and when the server was rebooted the OS clock showed nearly accurate time. NTP was turned off completely
on this server for this testing. As at power-on the OS picks the time from the BIOS/Hardware clock this proves that the hardware clock is working fine and once the OS is up and running, the timer/function that it is using to maintain the system clock is not
functioning properly. The systems are not under any kind of load and no temperature fluctuations have been observed. Enabling HPET also did not help.
Please do not answer saying, "use w32tm or ntp" as that mitigates the problem but does not solve it. The server is not a DC. The OS is running directly on the server, no VM involved.
Thanks

Hello,
the Windows time services was and is never built for high accurate time. So you have the need for special devices.
http://blogs.technet.com/b/askds/archive/2007/10/23/high-accuracy-w32time-requirements.aspx
Best regards
Meinolf Weber
MVP, MCP, MCTS
Microsoft MVP - Directory Services
My Blog: http://blogs.msmvps.com/MWeber
Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
Twitter:

Satellite L775D clock running fast

Our tech support friends are stumped by this one so I thought I would try polling the "unwashed masses":
The clock on the Satellite is always running fast, approx 15 minutes every 12 hours regardless of turned on, turned off, sleep, AC plugged in, AC not plugged in.
So far we have unchecked the automatic sync with internet time.windows and reset the BIOS settings, with no improvement.
Any thoughts / suggestions?
TIA Keith
Solved!
Go to Solution.

Let's start here.
Keith, open Services (services.msc) and verify that the Windows Time service exists and that Startup Type is set to Manual.
If it's not started, start it. If it won't start, give us the message.
If all that's okay, come back for more.
Also, tell us which Satellite L775D that is and the bitness of Windows.
-Jerry

Clock running fast

Since updating to Mavericks, I think probably specifically the latest update, the clock is running fast on my 2012 (thin) iMac. It can gain a minute in a day.
I'm set to Apple Europe (time.euro.apple.com.). If I turn this setting off and on again, the computer fetches the correct time.
Until recently I also had Set time zone automatically using current location (I'm on CET), but I've now unselected this to see if it makes any difference.
As a control, I have an older iMac running Snow Leopard sitting next to it on the same connection which has perfect time.
This 2012 iMac had no problem either with the time before Mavericks.
P.S. Also since updating to Mavericks I've had all sorts of sync problems with Mail/Gmail, 1Password and Dropbox, usually resulting in missing files. I wonder now if this isn't all clock related as it must be difficult to sync without an accurate clock.

OK Drew, I can confirm that booting in Safe Mode http://support.apple.com/kb/HT1564?viewlocale=en_US fixes the problem, at least as long as I stay in Safe Mode. I.e. the clock keeps perfect time.
I have now rebooted in normal mode and will monitor to see if the problem has been fixed permanently.
As an aside, in Safe Mode, Mail, message centre, Finder all behave weirdly. The message centre actually displayed text 180 degrees inverted in the vertical plane - like a mirror image ! I couldn't take a screen shot though, it would disappear when I tried to do this. I saw this behaviour somewhere else several years ago on my old computer in a different place - I think the Get Info window. It fixed itself after a few months.
Also, in Safe Mode, before actually logging in (but after rebooting), the clock is still wrong, but this time, strangely, it is slow, not fast. As soon as I log in the clock corrects and stays correct.
In fact, just logging in after a normal restart is also enough to set the clock correctly, but then it would start to gain time.
Anyway, will monitor and report back if my problem is now permanently fixed or not.

Clock runs fast, gains time

The Date & Time in my wife's 17-inch G4 iMac gains about a half-hour every day. This has been going on for a few weeks, I'd guess. To correct the time, it's necessary only to open the Date & Time preference pane (either from System Preferences or from the Date & Time displayed in the menu bar). The pane opens and the time automatically sets back to the correct time: the hands even go backward on the analog clock in the pane.
What can be causing this?
The iMac is running on 10.4.8, with all security and other updates. It is usually restarted only for system updates and shut down only when we're going to be away for two days or more. "Set date & time automatically" is checked, and the time zone is correct.
PM G5 2GHz & iBook G4 Mac OS X (10.4.8)

I restarted and it's no longer a problem. I don't know why this last restart fixed it, if it did: it involved only the last two Security Updates. The problem had outlasted at least two or three prior restarts.
And the remission, of course, does not much elucidate the cause of the problem, though it supports the opinion of the Genius at my local Apple ministore. He said that it was almost certainly a software issue and suggested restarting, then a clean restart from a CD or external drive, then bringing it in for examination if need be. I wondered if it might be the battery, now 3 years old. He said that those batteries usually last 5 or 6 years and often make the Date & Time lose time/run slow, but he'd never heard of a bad battery making the system gain time.
PM G5 2GHz & iBook G4 Mac OS X (10.4.8)

System Clock is faster then bios3.3

:O

Quote
Originally posted by jemi
i have no choice, flashed back to 3.3.
I have too many bugs, such as TEMP(CPU.TEMP
fixed it for you.

Mac Mini - Screensaver starting on its own and clock is fast ...

Hi there experts ....
I've got a 4 month old Mac mini
Model Identifier: Macmini3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.53 GHz
I've noticed for the past couple of months the clock is 4 minutes fast ....
And the screeensaver is coming on by itself out of nowhere ...
I/ve run disk repair ... Maintenance ... put screensaver to never and even disabled front row screensaver
I've reset pram and nvram ... ANy clues ....?

So even if you put the screensaver to never it still starts on its own?
Also you clock runs faster by 4mins?
I smell an OS issue. Partition your drive and install a fresh OS onto it. If it works(no problem there) then restore the partition into 1 drive. Zero out the drive and put a fresh OS in it
**back it up first
If the fresh OS on the new partition still fails. it could be a hardware failure.

[SOLVED] System Clock Issues (Wrong UTC?)

**RESOLVED -- SEE END FOR FIX
Hello everyone.
First off I'd like to say that I am thrilled to be here. I've been an Ubuntu user for a few months now, but decided that it was time to take a trip down the rabbit hole and see all that Linux had to offer--and to that end I switched to Arch. And I must say that I have nothing but positive things to say of it. The documentation on the Arch Wiki was phenomenal in helping me get started on the process, and the installation of it has proved to be a very enjoyable learning experience.
With that said, I have run into a bit of a snag, and after perusing the documentation on the Wiki, as well as running a few Google searches and searches of this particular forum, am no closer to a solution that when I started, so here I am. The problem is with my clock.
Okay, so I live in the Eastern United States, and as a result have my local time set as Eastern, and I have my hardware clock running UTC. Here is the problem. . . For whatever reason, the time displayed on my clock is five hours behind. Perplexed, I decided to see if I had set up my time zone info incorrectly and ran the "timedatectl status" command, and the results were really strange. A copy paste of the output is here:
Local time: Thu, 2012-12-20 19:27:02 EST
Universal time: Fri, 2012-12-21 00:27:02 UTC
RTC time: Fri, 2012-12-21 00:27:02
Timezone: America/New_York
UTC offset: -0500
NTP enabled: no
NTP synchronized: no
RTC in local TZ: no
DST active: no
Last DST change: EDT → EST, DST became inactive
Sun, 2012-11-04 01:59:59 EDT
Sun, 2012-11-04 01:00:00 EST
Next DST change: EST → EDT, DST will become active
the clock will jump one hour forward
Sun, 2013-03-10 01:59:59 EST
Sun, 2013-03-10 03:00:00 EDT
As you can see, the time zone is set correctly to America/New_York (originally US/Eastern, but I changed it to try and resolve the problem--to no effect, obviously). However here is where it gets strange. As I type this, it is 00:27 local time. My computer has decided to use the local time for UTC, and then subtracts five hours (as I live in UTC -5) to get the local time that it displays.
I've tried rerunning the hwclock --systohc --utc command, to no avail.
If anyone has any input as to why my computer is confusing UTC and local time, and any way I could fix it, I would greatly appreciate it.
I could just change my timezone to UTC - 0, that would cause my system to display the right time (I think) but I'd rather actually fix the problem, instead of simply covering it up with a band aid, if it is possible.
Thank you,
Douglas
EDIT:
I probably should mention that the machines (I'm having this same problem on two different computers) are both running Arch Linux and Arch Linux alone, although one was originally a Windows 7 and the other a dual boot of Win 7 and Ubuntu.
RESOLUTION (Thanks lhoffman):
Install the network time protocol daemon. This will allow you to sync your system time over the internet.
sudo pacman -S ntp
Once installed, run the following command:
ntpdate pool.ntp.org
This will link your computer with the time servers of the NTP Pool Project. For me my clocks fixed themselves quickly after running the command. And that was it.
After running this command and setting the system clock, run:
hwclock -systohc (thanks Scimmia)
Otherwise the computer will mistake local time for UTC and subtract/add time based upon your timezone again upon reboot.
Last edited by douglasr (2012-12-21 21:23:11)

Scimmia wrote:Not exactly. The root of the problem is that your hardware clock is set to localtime. To change this, you need to update the system (software) clock, which ntpd already did for you. The timedatectl command would have just done that manually. Now that your system clock is correct, you need to write this to your hardware clock so that it is correct when you reboot. hwclock --systohc does that. If you don't run that command, the system will boot up thinking it's getting UTC from the hardware clock and will subtract 5 hours. Then, once ntpd runs, the time will skip ahead 5 hours. This will cause all kinds of issues.
I fixed this on my system too. Thanks for the explanation.

Please help: OEL clock running too fast

Hi,
I have tried everything I could find on the internet,
I have downloaded the latest OEL 64bit, installed it on a server (Asus m/b + AMD Phenom™ X4 Quad-Core cpu).
The clock runs 3 times faster than it should, how do I fix this?
Tried all the "noapic" etc options on older RHEL discussions in the grub.conf, but nothing works.
PLEASE someone help!
We are trying to do a OEL + 11g setup.

As a sidenote, please reconsider the previously proposed NTP solution.
Even with systems without clock problems, there will always be a difference in clock speed between computer systems and also with the other systems surrounding them.
Almost any computer system is using remote services, or provides services, or even has a setup where multiple systems are used to provide a single task (for example: the task of having a standby database using dataguard). If diagnosis of events on multiple systems, or diagnose of the sequence of events or tasks is needed, the clocks needs to be in sync. Otherwise diagnosis will be hard or impossible, or simply done wrong.
NTP is the solution for that by carefully examine the local clock speed, and compare it to the networked time sources, and adjusting the clock accordingly.
This is the reason most datacentres have timeservers internally with which computer systems can sync, so the clock is in sync on all systems. These timeservers are internal, thus need no internet access for the time clients. It is advised to use a 3rd party time source for the timeservers (like using timesources on the internet, or have a special card which sync with some atomic clock) But please mind you can do without.

Hallo My system runs slow. how can i reorganize the date, that the pc runs faster? In the window world i hade to delete some fils. how it work in the apple world?

Hallo My system runs slow. how can i reorganize the date, that the pc runs faster? In the window world i hade to delete some fils. how it work in the apple world?

See these:
Switching from Windows to Mac OS X,
Basic Tutorials on using a Mac,
Mac OS X keyboard shortcuts,
Anatomy of a Mac,
MacTips,
Switching to Mac Superguide, and
Switching to the Mac: The Missing Manual, Mountain Lion Edition.
Additionally, *Texas Mac Man* recommends:
Quick Assist,
Welcome to the Switch To A Mac Guides,
Take Control E-books, and
A guide for switching to a Mac.
Once you get familiar with the Mac, see:
Mac Maintenance Quick Assist,
Mac OS X speed FAQ,
Speeding up Macs,
How to Speed up Macs, ,
Macintosh OS X Routine Maintenance,
Essential Mac Maintenance: Get set up,
Essential Mac Maintenance: Rev up your routines,
Maintaining OS X,
Five Mac maintenance myths and
Myths of required versus not required maintenance for Mac OS X for information.

Display Synchronised System Clock With Milliseconds (HH:MM:SS:mm)

Hello All,
I need to display the system clock with hours, minutes, seconds and milliseconds (the system clock it synchronised via NTP or GPS and needs to be accurate)
Using the Buddy API time functions I can display the time with an accuracy of seconds but the inbuilt lingo "the Milliseconds" and Ticks does not correspond to the system time.
for example I tried using
member("MyTimeStamp").text = baSystemTime("%0H"&":"&"%0M"&":"&"%0S"&":"&chars(""&the milliseconds, 6,7))
but the seconds change out of synch with the milliseconds, the milliseconds are approximately 10-12 ms faster and I don't want to fudge the timing, I recorded the display with a slow motions camera and can see the seconds reset to 0 when the milliseconds are already at a value of 10 - 12.
Any Idea how I can derive milliseconds using the system time? HH:MM:SS:mm
thanks.

10-12 ms delay (error) is the correspondent of a 80-100 FPS (polling interval).
Theoretically speaking, to get 1ms delay (error) you need to run your script at 999 FPS (the max value allowed by D12).
Practically speaking, that's not possible (many other factors are involved here).
cheers

System clock running fast

Similar Messages

Maybe you are looking for