K
K
klopodav2013-01-20 20:39:25
Iron
klopodav, 2013-01-20 20:39:25

Weird Clock Behavior in Windows 7

Hello, help me deal with the following problem:
On a desktop computer, the clock behaves completely inadequately - the minutes are running normally, but at the end of the hour the hour counter does not increase, and the same hour starts as if from the beginning, i.e. after 21.59 comes 21.00.
What could be the problem and how can it be cured?
My only guess is that it's something with the motherboard, since the bios doesn't clock at all.
Replacing the BIOS battery and flashing it to the most up-to-date results did not give any results. I'm at a loss as to what else can be done.
Axis - Windows 7
Motherboard - Asrock z77 pro with firmware 1.90
If necessary, I can clarify other performance characteristics.
In which direction to look, dig?

Answer the question

In order to leave comments, you need to log in

10 answer(s)
D
Daniel Reed, 2013-01-20
@Remasik

Maybe the problem is in the automatic synchronization of the clock with the time server on the Internet?
Either the clock is synchronizing with some server that is currently having problems, or the computer thinks that you are moving along with time zones in a circle in the opposite direction of time zones, that is, every hour you are moving to the "-1 hour" time zone.
If there is no time in the BIOS, try to synchronize on the Internet with some well-known time server, if this fixes the problem, then at least we are one step closer to the true problem.

D
Daniel Reed, 2013-01-20
@Remasik

And try to boot into another OS from live and check the time there ... if it doesn’t fail, then it’s your OS.

D
Dmitry Pavlov, 2013-01-21
@Dimonyga

>> In the BIOS, time does not go at all.
At one time I met with this when I worked in the SC.
Option 3:
1 - the master quartz has fallen off.
2 - bent / fallen off / dusty legs or processor pads.
3 - the bridge began to burn.
In the first two it is solvable, the 3rd - alas, no.
Look at the processor, wipe it with a dry cotton pad, look at the socket legs. Check quartz contact.

I
ipswitch, 2013-01-20
@ipswitch

Any program may have its own time synchronization function. Synchronizing the time to an exact one, but with an incorrectly configured time zone (remember all these changes?) leads to this result.
Disable EVERYTHING from startup.
Set the correct timezone.
Disable sync.
We are watching.

N
nerudo, 2013-01-20
@nerudo

With a high degree of probability, hardware problems. Try to open the case while in the BIOS and press the system quartz 32.768 kHz. And watch the seconds. If they go, it means bad contact-soldering. If not, perhaps the quartz itself is bad. In any case, it is solved by soldering. Either standalone or serviced.

I
ipswitch, 2013-01-21
@ipswitch

"Workaround" We set
the time synchronization to automatic with a frequency of 3-5-10-30 minutes - as it will be more accurate =)
With a stable Internet, the problem will be solved.

L
lubezniy, 2013-01-20
@lubezniy

In theory, the operating system contains its own internal clock, and the motherboard has its own. As a result - a test of RAM, reinstalling the OS. If there is no effect, then, most likely, change the mother.

H
howeal, 2013-01-21
@howeal

How about in bios?

R
rvller, 2013-01-21
@rvller

Isn't this automatic time conversion by any chance? And then I remember there was a problem that the time itself was translated in the same way as yours.

N
Nikolai Novikov, 2019-08-20
@nnikokolay

The two of us are the same bullshit. I understood where the wind was blowing from, even once the clock started working and synchronized itself, but not for long. This Windows left is most likely blocked.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question