Date keeps changing - ASRock H110M-HDS

  I have an ASRock H110m-hds motherboard with a i6700 cpu and I have having Clock changing problems  last 3 days the DATE has gone forward between 11:00pm and 11:30pm then at 12:01 the DATE goes forward again making me a DAY forward on the Clock.  The time always stays correct.  I have tried several things however I have two other computers running the exact same Win7pro OS and 100% of the same programs (except for the motherboard drivers and ASRock App.) My other 2 computers are ACER computers and both of them have never had a problem with the CLOCK or time since they were installed over a year ago.  On this ASRock I have installed a Clean operating system 3 times on 3 different SSD's  and everyone of them has this DATE ISSUE of going forward twice, which causes my Antivirus not to sync properly and who knows what else is going on.  I have run  Malwarebytes 3.* ; Norton Security together on one and two,  and on this third I added PCMatic to see if that program could detect the problem,  no luck there.  THE forward jumping DATE  has to be a ASRock Issue or some kind of incompatibility with the ASRock drivers causing it.

Prizm wrote: When I installed the board, i updated it to the latest bios (1.20). I'm wondering if i should revert to an older version.

My 2cents lie with this being a BIOS programming issue ASRock needs to look at.

OP, did you try each available BIOS revision on your boards download pages, and if so do one make any difference?

Prizm wrote: Haven't tried manual sleep, just disabled automatic. Yeah I actually think I forgot to disable sleep on my Win 10 PC. I agree, it causes a lot of people problems. I keep having problems where my mouse cursor disappears after turning on the monitor. Have to keep clicking blind around the screen for 20sec to get the thing back. Appears to be a common problem with Win10. I think it might be sleep related as well.

I doubt manual or automatically entering Sleep makes any difference.

What type of mouse? Wireless? That's what I use. Mostly MSoft mice, I figure they ought to get things right with their OS and hardware.

I'm not having that problem waking from Sleep at all. If I do lose the mouse somehow, I'll turn off the mouse power switch, and then on again. If that doesn't do it, I remove the wireless transmitter from the USB port with the mouse power off. Plug the transmitter in again, and turn on the mouse.

If that doesn't work, it's restart time.

Prizm wrote: Ok, I found out what causes the date change. For the record, I reverted to version 1.10 BIOS and that didn't fix it. The problem happens every time the PC comes out of sleep mode. When digging through webpages online, I found someone who had the same problem with their HP laptop. So every time you wake the computer up, the date (not the time) advances. We turned off the sleep setting in Windows 7 (set sleep to "never"), and the date problem was fixed. It's not a total win since the problem still exists underneath, but it's better than troubleshooting the hardware.

So you mean you don't let the PC ever enter Sleep mode? Or is that no Sleep mode automatically, and entering Sleep mode manually does not cause this date problem?

All I know is, over the years with different versions of Windows and various hardware and software, Windows Sleep remains a problem. The problems it has are multiple and of all kinds.

I stopped using Sleep with some older hardware (Asus P67 board) and Windows 7, since upon waking from Sleep, the video source would not work, black screen. Restart the PC, video was back.

I accidentally forgot to disable Sleep recently in Windows 10 on my ASRock X99 board system, and found the PC in Sleep mode when I walked away for a while. It woke up fine, no other weird side affects. Tried it on my ASRock Z170 board system, works fine too, so I'm back to using Sleep again.

Waking from Sleep requires many things to be restored that are not automatically done by the OS itself, apparently. So the mother board manufactures are stuck helping Microsoft with their Sleep feature. Too bad the fixes are not simple and obvious.

Prizm wrote: When I installed the board, i updated it to the latest bios (1.20). I'm wondering if i should revert to an older version.

That is worth trying, you should be able to change to the earlier version.

If the earlier version causes the problem to disappear, it seems the new version is the cause.