Time keep reseting after power loss

Glad to hear your issue was resolved. Sadly bad CPUs are a lot more common than
they once were.

You can post pics here but you need to upload them to an image hosting service not
the forums.

Then you just add [ img ]link to image[ /img ] (without the spaces in the img tags).

Edited by Xaltar - 13 Sep 2022 at 9:42pm

This is just turning into a bloody nightmare.

ASRock got both the motherboards I had that were both having the issue. They were able to get them to power up, and function properly. The only issue I have is that they did not have a 5600x that I am using, but used a 5900x and 5950x.

They replaced them under RMA just in case. Both of the new ones are exhibiting the same behavior that the original ones had.

Being that the only component of this system that hasnt been replaced is the AMD CPU 5600x, John from ASRock is suggesting I replace that.

In the middle of that RMA with AMD now

My brother, who is a IT Engineer says its possible that its the CPU.
A couple "Geeks" I know say they can see no way that a CPU is going to cause a RTC clock issue. And it most certainly cant be the video card since all those lanes go thru the CPU. I also my video card to 4 other known good and working systems, and they had no issues.

Will have to see what AMD says.

Out of curiosity, what PSU are you using? Is it a PICO unit?

Also, can you PM me the serial numbers of the boards you had issues with, I will
send that along to my contacts at ASRock to check how and where they were handled
and or distributed to retailers.

I am sorry but there is no way you have the same issue with 3 motherboards. It
would seem some other aspect of your system is causing an issue that keeps resetting
your RTC (real time clock). The OS can write to your RTC registers, I would start
there. Disconnect your boot drive and see if the issue reoccurs without booting
into your OS. If it does then go through your system removing every component you
can and see if you can find the culprit. It could be RAM related, if one or both
of your RAM modules are marginal (intermittently faulty) it can cause register
corruption. It could also be what is behind your BIOS checksum errors while
updating past 3.1. I can see why ASRock is having trouble with this one, it's
not your usual hardware issue. Bit of a headscratcher for sure.

I would start with
1. Remove OS from the equation
2. Remove all USB devices except for keyboard and mouse (some USB devices have firmware that interferes with POST and BIOS function)
3. Try with one stick of RAM (then the other)
4. Make sure to clear CMOS between each step to make sure no gremlins are hiding from the previous boot.

I have been having this problem for just at 2 years.

My build
NZXT H510
1x 120 Rad
1x 240 Rad
4x 120 Noctua fans
EK pump with Reservoir
5600x
Vega64
2x16 Crucial 3600 (XMP on)
1TB Sabrent NVME
2tb Samsung 860EVO SSD
Windows 10 Pro

On my first motherboard I changed the CMOS battery, Changed XMP profiles, switched the fTPM, and a host of other things, all at Asrocks request. Nothing worked.

I RMA'ed the motherboard thru Amazon back in December at Asrocks request.

Same problem still exists.

I also can not upgrade past Bios 3.1. If I upgrade to 3.2 or 3.5 I get a checksum error. But I can downgrade back to 3.1 no problems.

Asrock wants me to RMA my motherboard, but I cant be without a computer for a month while they figure out whats going on. I bought a second X570 ITXTB3, and swapped it out for the original one, so I could send it off to Asrock, and it has the same problem. Returned the 3rd motherboard since it has the same problems.

3 motherboards, all with the same problem? Talk about aggravating.

Going to have to tear it apart and send it in anyways. Going to have to try and survive off my 8 year old laptop.

I am betting Asrock sends me a new motherboard, and it does the same thing.

Unless someone found a fix??