PC clock losing time becasue of SL...

hi...

for the last few weeks.. sl is suddenly making my pc clock lose time...
at first i thought it was the battery on my motherboard... but the board is only 2 months old and also i only seem to lose time on my clock when sl is running..

has anyone else got this problem?
does anyone know why its happening?
does anyone know how to fix it?

please help if u can
Sara Lukas

More detail please... at minimum, post the machine spec from About > Second Life so we know what you're running.

Also, just because the board is new doesn't mean it isn't a piece of crap... most electronics fail within the first six months or last six months of their design lifespan, with the fewest failures between or beyond those ranges.

Could also be software: strange clock problems tend to be a long-time Windows specialty.

The answer to this is simple. Overloaded system.

Windows takes the time from the BIOS on startup, and from that point forward, updates the time manually. It never looks at the internal system hardware again. So if your computer is suffering from local system lag, the clock is going to slow down. The longer this condition persists, the further from the real time it gets.

So your best bet is to restart your computer more often, and also to run less software to free up cpu cycles (disabling some add-ons like your anti-virus software, defrag utility that's always on in the background, boinc to run seti@home, ea download manager, winamp's agent software to preserve file associations, etc. etc. etc.etc.) Also consider more system memory. Looking at your free hard drive space can help too. For example if you have two gigs of memory in your computer, you should have at minimum three gigs of free hard drive space on drive C for the windows swap file.

this has only jsut started happening about 2 weeks ago though..

Check your date and time settings and see if it's set to synchronize with an internet time server, or if it's synchronizing properly. Computer clocks will drift over time, but reset themselves periodically so you shouldn't notice it.

Though, if your computer's timezone is not set correctly, that would cause synchronization to throw the clock way out of skew. I wish Windows handled this the right way, since it's less confusing to set the computer to UTC and adjust the user environment to the local timezone and DST, as opposed to the way Windows does it. It makes it more apparent who is wrong, too: If the hardware itself is ever too far from UTC when the system itself isn't, then the hardware is wrong. And if the hardware is close to UTC and the software clock isn't accurate, then the software's wrong. But when the OS tries to keep both synchronous all the time, that makes it tricky...

OTOH, Microsoft does know their audience, and their audience doesn't care about clock accuracy that much, or they wouldn't have an audience at this point...