AMD Motherboards - 980DE3/U3S3 bios time

Print Page | Close Window

980DE3/U3S3 bios time

Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=1907
Printed Date: 18 Jul 2025 at 10:13pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: 980DE3/U3S3 bios time

Posted By: Bossie12
Subject: 980DE3/U3S3 bios time
Date Posted: 02 Feb 2016 at 9:03pm

Good day to all,

Just updated my Asrock mobo 980DE3/U3S3 bios from 1.400 to 2.00, but now the bios time is not correct. On every boot i have to F2 into the bios and correct the time manually, else my pc won't boot into windows 10 x64.
What could cause this, every other change in the bios is correctly saved, only the time isn't.

My pc :
Processor : AMD FX-4300
RAM : 8,00GB Dual-Kanaal DDR3 @ 801MHz
Motherboard : ASRock 980DE3/U3S3 (CPUSocket)
GPU : 2047MBNVIDIA GeForce GTX 750 Ti (MSI)

Thanks in advanced for every help.

http://forums.tweaktown.com/asrock/62486-980de3-u3s3-bios-time.html" rel="nofollow -

Replies:

Posted By: Xaltar
Date Posted: 02 Feb 2016 at 10:46pm

Is it reverting to the date of the BIOS release every time you power on or is it simply slow? Either way you can try replacing the BIOS battery and seeing if that corrects it.

-------------

Posted By: Bossie12
Date Posted: 02 Feb 2016 at 11:47pm

Thank you for your reply.
Will first go back to my old bios version, if that's no solution i will go for a new battery.
Let it know how this is going.

Posted By: Bossie12
Date Posted: 05 Feb 2016 at 7:00pm

Ok, i tried all bios versions, but only v1.400 is good for this board.
Every other bios is giving troubles and doesn't start Windows 10 right away,
without setting time in bios every time i start my pc.
Strange behaviour, so i will stay on v1.400.

Posted By: wardog
Date Posted: 05 Feb 2016 at 7:13pm

Replace the CMOS Battery.

The board is going on four years old and most likely now in need of a new battery.

Why 1.40 doesn't give you issue I don't understand as the boards BIOSes have matured well enough that the only two thing I can think of that would do this is a weak dying battery, and or a now defective crystal that keeps time sync'd.