ab9 quadgt cc error

[Methadras]

hi all. i'm new here as a poster but lurked forever. the reason why i've decided to register is because abit forums are gone and this seems the closest to replicating it. so here goes and i hope you can bear with me.

I have an ab9 quad gt running bios 16 that i've had stable with an e6700 and 4 gigs (2x2) of g.skill ddr2 800 ram and a 7950gx2 car for over a year. i decided to upgrade the cpu and video card to a q6600 g0 and an 8800 ultra. left the ram alone and i'm running thermaltake 850 toughpower.

i installed everything and when i powered up (i forgot to reset bios) i got a c.c or cc error on the motherboard. The cmos resets are in their proper positions on this board but i still get this error. it will power up and i get to the graphics abit screen where it asks you to hit tab or delete to continue, but i get nothing doing either. not sure what to do at this point and was wondering if anyone could help with any knowledge. I've done searches all over, but nothing really applies. thank you for any assistance. take care.

[BUFF]

try putting the E6700 back in, update BIOS, try the GO Q6600 again.

[Methadras]

try putting the E6700 back in, update BIOS, try the GO Q6600 again.

I'll give that a shot and let you know. Thank you for the reply. I didn't even think to do that. Just out of curiousity, do you think it's a bios update issue or is this a sort of look-see to see if it is part of a larger problem?

[Richh]

do you think it's a bios update issue or is this a sort of look-see to see if it is part of a larger problem?

The CC report code means that the board thinks the clear CMOS state is set, there are no other likely causes for this particular error.

If you're absolutely 100% sure that both the CCMOS1 jumper and the EZ-CCMOS switch are in the correct positions, it could be some debris inside the switch. Remove the CCMOS1 jumper completely, power up the board, and flick the switch back and forth a few times, keeping an eye on the debug display throughout.

Might also be worth removing the battery for an hour or two just to see if that unlatches uGuru. With a bit of luck you'll clear whatever it is.

[Methadras]

The CC report code means that the board thinks the clear CMOS state is set, there are no other likely causes for this particular error.

If you're absolutely 100% sure that both the CCMOS1 jumper and the EZ-CCMOS switch are in the correct positions, it could be some debris inside the switch. Remove the CCMOS1 jumper completely, power up the board, and flick the switch back and forth a few times, keeping an eye on the debug display throughout.

Might also be worth removing the battery for an hour or two just to see if that unlatches uGuru. With a bit of luck you'll clear whatever it is.

Hey Rich. It's me Methadras from the abit forums. Long time no type. How have things been? Yeah, I was thinking that either the cmos is corrupt or the actual chip went bad, but I didn't think about debris in the actual switch. I'll try what you suggested and see if that works. Honestly, this board was working just fine for over a year without any real serious issues and after I fried an IP35 pro that I had as an upgrade, I then decided to put the q6600 and the 8800 ultra into this setup and then BAM, the CC error. This rebuild has been a complete hassle I have to tell you, but hey, this is why I love solving problems. Anyway, I'll give your suggestion a shot and incidentally, I have a spare cmos chip that I will reinsert if all else fails and see if that works? Who knows.

Anyway, I've tried to get on abit forums, but i think they are down or not working. What have you been up to? Any new bioses you've been cooking? I know Abit is having issues and they are getting out of the motherboard business so I was thinking that another build should be an Asus build? What do you think?

[BUFF]

Anyway, I've tried to get on abit forums, but i think they are down or not working.

they moved the US servers incl. the forums to Taiwan a while back. Then over the last fortnight or so they've obviously been playing around in Taiwan & the sites are now back up but the forums haven't resurfaced.
A few of the old heads are at http://www.theraptorpit.com/forum/in...?showforum=124

[Methadras]

The CC report code means that the board thinks the clear CMOS state is set, there are no other likely causes for this particular error.

If you're absolutely 100% sure that both the CCMOS1 jumper and the EZ-CCMOS switch are in the correct positions, it could be some debris inside the switch. Remove the CCMOS1 jumper completely, power up the board, and flick the switch back and forth a few times, keeping an eye on the debug display throughout.

Might also be worth removing the battery for an hour or two just to see if that unlatches uGuru. With a bit of luck you'll clear whatever it is.

Rich,

Okay, I am 100% sure that the ccmos1 jumper and the ez-ccmos switch are in the correct positions. I removed the ccmos1 jumper and powered up the board. It powered up and I flicked the switch a few times and it was still stuck on the c.c error while I was watching it throughout the boot up. It gets to the bootup screen and says there is a cmos checksum error. I can get into the bios, but it won't let me save because it hangs on the exit and save dialogue box.

I've gone ahead and removed the battery and I'll let it sit for awhile and put it back in. But let me ask you a question. why would a board that has been working all of a sudden display this behavior? This is the strangest thing I've ever seen a motherboard do and it was working just a few hours before. It's so damn frustrating.

[Methadras]

well guys, my abit days are over. I'm done with abit completely. I installed a p5q deluxe and it's a pretty damn nice board. to bad to see abit go this way, but that's life right? thanks for all of your help.