wierd little problem on my m15x

hey guys,
ok so i got this stupid little problem but its really annoying me.
my clock in the bottom left of my screen seems to be slightly slower than it should be. i set it to exactly the same time as my watch and then a week or so later its about 35 minutes slow. it does this everyrime i set it.
i know its nothing of concern bt i look at that clock a lot an it annoys me that its wrong.
any help appreciated

 

what is the clock synced to? right click on the clock and select "change date/time" and then on "internet time" (or something like that). there you can choose which clock you want to sync with.

PS: are you sure it's not your watch that is 35min too fast every week?

 

I have the same problem, after some testing I have realized that it is not the cmos battery as many people think but the x34 bios version. This bios version is terrible and not worth using at all. The only problem is that the x36 version has a bug in the temperature reading system, and always places your system temp at 80 degrees. This causes your fan to run at full speed all the time. I suggest either waiting it out, or moving back down to the x32.

There should be a fix to the temp reading problem out shortly, but that statement was made about 2 weeks ago.

 

just curious how you feel the bios is the culprit?

 

whizzo, lol ye im sure its not my watch.dunno wots doin it.

 

see yankeesbaseball's reply, cathal. apparently, it's the X34 BIOS.

 

I mean unless it is pure coincidence, I update the bios to x34 and started to have trouble with the clock, audio poping, touch controls (which never were working right).

The other reason is that the system clock slows only when my computer is on. To test your system, try leaving your computer off for about a day (I know it is hard) and see what time your system clock has. I know that mine maintains accuracy, but when the computer is on, I start to have clock problems.

 

while i am not discrediting your theory, i just can not see how a bios can effect a time stamp from the internet...
even if you did not set it to get the time from the net, (which i believe is based from the atomic time in the states), losing that much time can not be a fault of a bios as your system is based on clocks anyway.
the only way i can see this is with the same issue as the low latency issues. but the issue was clock timing in applications and how fast they are executed vice a set basic clock...

just throwing stuff out there...

 

I've never seen reoccurring clock problems like this (where it's exactly X minutes/hours behind) unless the Reigonal settings are wrong.

The time I saw this, an individual, we were in eastern time, had their clock set to mountain time (or some such nonsense)... the clock would re-set itself to the incorrect time on every NTP update (network time), and therefore be wrong. the individual kept fixing the symptom (the clock) rather than looking for the cause (wrong time zone)

check it out.

 

good idea mystik, but based on his post and your answer, would not there be more then the 30 mins he says is a difference?
most time zones measure in hour differences....

 

True, most timezones are 1hr change, rather than .5 however, depending on where he lives, there may be a .5 hr timezone nearby...

I'm going out on a limb and like I said, it was just what I've experienced. so who knows? it was worth a toss out there.