Hello Fliers, I hope this is the right place for this because my only flight sim is P3dv2.1 now. As we all know our flight plans are connected to the system time clock. My problem is with the system time clock not keeping correct time. I have a Sabertooth Z 87 MB and my system is 8 months old with a factory OC. I have never had a minutes problem with the clock until I cloned my HD to a larger GB HD because I was running out of GB space. The clone was successful, however, after the clone, next day I noticed the windows 7 64 bit clock was wrong. I went into the BIOS to check the system clock and it was wrong also. It was the same time as the windows clock. After reset of the system clock, the clock will run with correct time then both clocks, (system and Windows) after about and hour of so start loosing time. I reset the clocks and same thing happens again. After a couple of days both show wrong time and the same date that I reset. Don't know if the cloning had anything to do with messing up the clocks, people I have talked to said their clone went fine with no clock problem. My problem is just wrong time after an hour of reset? I have not tried anything with the BIOS or battery change. Though I would wait to here from more experienced people than me on this issue. I have done many things in Windows, advice from others but to no success. Any help on this issue will be appreciated.

Regards,

 

Lamar

"Sabertooth Z 87 MB and my system is 8 months old"

 

Still on warranty?

 

Call the store / vendor where you purchased it first ... Do not want to void the warranty.

Old battery?

Spirit

Replace the battery

 

Michael

Hello Fliers, I hope this is the right place for this because my only flight sim is P3dv2.1 now. As we all know our flight plans are connected to the system time clock. My problem is with the system time clock not keeping correct time. I have a Sabertooth Z 87 MB and my system is 8 months old with a factory OC. I have never had a minutes problem with the clock until I cloned my HD to a larger GB HD because I was running out of GB space. The clone was successful, however, after the clone, next day I noticed the windows 7 64 bit clock was wrong. I went into the BIOS to check the system clock and it was wrong also. It was the same time as the windows clock. After reset of the system clock, the clock will run with correct time then both clocks, (system and Windows) after about and hour of so start loosing time. I reset the clocks and same thing happens again. After a couple of days both show wrong time and the same date that I reset. Don't know if the cloning had anything to do with messing up the clocks, people I have talked to said their clone went fine with no clock problem. My problem is just wrong time after an hour of reset? I have not tried anything with the BIOS or battery change. Though I would wait to here from more experienced people than me on this issue. I have done many things in Windows, advice from others but to no success. Any help on this issue will be appreciated.

 

Regards,

 

Lamar

There seems to be an ongoing, yet to be solved issue with Z87 boards whereby the bios clock stops.  I suffer the same on my Z87 Pro.

 

Please see this forum thread:

 

http://rog.asus.com/forum/showthread.php?35490-Sabertooth-Z87-Bios-Clock-Issue

 

Daz

I am having exactly the same problem with my Asus Z87 .... I've changed the battery and it still runs slow 

 

I am sure Asus have an on going issue here 

 

Paul

Thank you for your replies. Yes, I read the same post in ROG. Since the clock has wrong time, it effects my  Eset virus updating as well as the clock. What are we to do? I have to reset my clock about each hour during the day if I won't to keep the time correct.

 

 

Lamar

Hey guys,

 

I have the same board. I wrote a little batch file that will automatically sync my clock up whenever it decides to not catch up, I'll post it if anyone is interested.

If its any help, I had the same issue on my relatively new sabertooth z87 a bit over a month ago.  Google lead me to the ROG forum, probably the one above.)   I followed the ASUS moderator's directions as outlined in the thread.  

 

(Don't quote me on this, without double-checking the thread -- I reset the BIOS via the jumper method he outlined -- was not a stable fix as the problem recurred, then as per additional recommendations in the thread, I re-downloaded the latest BIOS and re-flashed the BIOS.)

 

The problem has been fully stable for about a month of regular daily usage.   I know that flashing the BIOS is not without some degree of risk, but over the years I have done it any number of times on various motherboards/manufacturers and have yet to had any problems.)  At this point it appears to be a fully stable board which functions great.

 

Don

Wendall, Yes I would be interested to see if it works for me and I'm sure others that have the same problem would like to know also.....  

 

Donovan, I have never flashed BIOS, I understand when you flash BIOS you need to write down all your settings and OC's and reset everything. I also read where some people cleared their CMOS, some with success others not with this clock issue.  Is there anything else in BIOS that we should check other than just reset clock with this board? It is real strange that I can reset the clock and it will keep time for 30 or 45 minutes then go bonkos?

 

Lamar

I'll warn you in advance, just so you know, the batch file does not run automatically, so you do need to start it manually every while or so, but I'm pretty sure you can set up an event in the Event manager to make it go completely automatically. I'll post it when I get back home.

Thanks Wendall.

Alrighty.

 

So, assuming you know how to create a batch file, this is the text for the file.
 

@echo off

REM Next command will run command w32tm /resync

start w32tm /resync

@echo off

 

If you don't know, simply open up notepad, copy the text, then hit "Save As", then "all files", instead of a text file, and name it whatever you like.bat

 

Hope it helps!

This is an automatic message.

 

This topic has been moved from "The Prepar3d General Forum" to "MOBO, RAM, CPU's & Other Hardware". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

hychewright

This is an ongoing issue with asus for at least 5 months and there is no fix yet. What I did is search for and download NetTimeSetup-314.exe. Install the program and run it automatically at start-up until they find a real solution for this issue. It takes about 8 seconds after the boot process and date and time will be updated. Time update in windows will not do the trick. I had this issue with some programs especially with Active Sky new version, will ask constantly to register the software because of wrong date and time. Since I installed this program (by the way very little on system resources, no penalty or performance degradation) I have no issues, still waiting for a real fix from asus.

 

Kind regards,

Alex