POST Error Occurs! CMOS Checksum Error - Defaults Loaded, press F1 to Continue

Volta13

Honorable
Jan 28, 2014
62
0
10,630
Good Morning, before I start I want to apologise for repeating this topic, I am fully aware it is present on other threads, all of which I have read.

Around three weeks ago, I installed an Asus Xonar DSX 7.1 Surround Sound Card, onto my motherboard. Upon boot up, I see my motherboard splash screen, and then a blue screen. The following message occurs:

Post Error Occurs!
CMOS Checksum Error
Defaults Loaded
Press F1 to Continue

I am then given a choice of profiles which I can load, by selecting them with my arrow keys and hitting enter. I am also given the choice to load 'Last Known Good'.

Now, I know how this sounds, you will typically say CMOS Battery. Below is a list of the things I have tried:

Resetting and Reseating the CMOS Battery ( I have to remove the Sound Card to do this then replace it when I am finished)

Changing the CMOS Battery

Leaving my PC on for 12 hours

Removing the soundcard and booting without it.

Now, just to be clear, this issue happens on every boot, and a small 'click' can be heard, it sounds electrical, like something is discharging.

I am forced to manually reset the date and time every time I get to my desktop, and some of my icons do not show in the notification area, and my default programs (EVGA Precision X, Corsair Link) do not load.

If I try to reboot, even two or three times to get my default programs back, the date and time stays the same, but my PC Hangs terribly (task manager fails) on desktop, forcing me to reboot several times.

Now, I have been told that this could either be a motherboard or PSU Issue. I will list my specs below:

CPU: AMD FX 8320 - Black Edition Octo Core Processor (Vishera)
GPU: NVidia GeForce EVGA GTX 780ti SC (w/o ACX cooler) 3GB
Cooler: Corsair H100i Hydro Liquid Cooler
RAM: 16GH Corsair Vengeance 1333Mhz (2x8)
PSU: OCZ Vertex ZS Series 750W (Non Modular)
Motherboard: Gigabyte 970A-DS3
Boot Drive: OCZ Vertex 128GB SSD
Main Drive: Seagate Barracuda1TB 7200rpm HDD

This issue is driving me insane, and I refuse to believe that a CMOS battery could cause this because I have tried everything apart from jumping it (something which I am neither willing or confident enough to do) and even changing it didn't work, and yes I did use a 3V 2032.

Any help would be massively appreciated!

Thanks

Volta13
 
1 To enable AM3+ AMD FX-Series CPU support, please update your motherboard with the most current BIOS found in your motherboard's download section.

2 replace the motherboard as soon as possible ... this model is no longer available because of his hardwares problems



 

Volta13

Honorable
Jan 28, 2014
62
0
10,630
There were no unusual smells when I first did it. Also, how do you know that the Motherboard is no longer available, please could you provide proof of these hardware problems? The vendor that sold me my PC (Custom gaming rig) gave me this motherboard as standard.
 

Volta13

Honorable
Jan 28, 2014
62
0
10,630




It specifically says supports AM3+, which means that it should work, and also the fact that I have been using it for over a year with no problems whatsoever...but I can understand what you are saying. What would you recommend I replace it with?
 

Volta13

Honorable
Jan 28, 2014
62
0
10,630


Okay, Thanks so much you guys, the people I got it from said they would fix it under warranty. But this would take 5 days minimum, which is far to long! What would you recommend I do?
 

Volta13

Honorable
Jan 28, 2014
62
0
10,630
Okay guys, got this fixed a couple of months back, sorry for the delay! This is actually embarrassing, but it turns out that when I installed the soundcard, I had to remove a couple of wires to get access. In the process, when reattaching the power cable (power button on the tower), I actually connected it onto the Clear_CMOS Header on my motherboard, and not the Power_ON header.

Therefore, for the last the last four months before repairs, I had been clearing my CMOS like three times a day, every day.

I want to thank you guys for all the support, all the time you took to help me out, and say how awesome you all are! The issue is now fixed and I'm back up and running.

Thanks again guys,

Volta13