Striker Extreme CMOS ERR

M

Mystery

n00b
Joined
Feb 22, 2007
Messages
8
So yeah I'm sure this has been brought up plenty of times before...

I decided to unhook my system, reseat my zalman cooler, and fix up some of the wires to make it look clean (it's impossible btw). Upon trying to boot up my system I got a CPU INIT error, okay.... so I then popped out the cmos battery for 15-30 minutes, popped it back in, got my system to boot, of course I didn't have my drives hooked up because I was just in the testing portion of it. I turn off my system then I reconnect my drives and my keyboard, now I'm getting a CMOS ERR. Simple right, I moved the jumper and cleared cmos (while powered down) and the result still occurs.

The system was working fine prior to this, other than the odd temps and random crashing due to my ram or my video card. As of right now my system is sitting, deconstructed, with the CMOS battery out, which I plan to put back in later tonight when I get home from work.

Are there known issues? It just seems odd to me that a perfectly bootable system turns into a POS can't boot ECS clone just due to changing positions of ram and reseating the cooler.

Specs

E6600
Striker Extreme
2-4 gb DDR2 800 6400 PRO Corsair xms2 ram (I say 2-4 because the system has never ran with 4)
150gb Raptor
300gb Maxtor Sata
X-FI Extreme Gamer Fatality Professional Series
XFX 8800 GTX XXX Vid
Cooler Master Stacker
Silencer 750


I'm hoping that letting the battery sit out for an obscene amount of time might fix this, but to be perfectly honest I doubt it will.

Any help would be great, thank you all in advance.
 
Define odd temps and crashes due to the gfx card ? Somehow Corsair ram and Striker don't work well together... I cannot get my 2 gig of Corsair 6400C dominator ram to work without bluescreening each day... I have a buyer for them hope he will pick them asap

Be carefull when you reasaet a CPU cooler you ca put too much stress on the CPU socket and it could be due to this fact it won't boot, I had some sort of prob with my watercooling setup
 
Odd temps, meaning abnormall high. High 50s to low 60's under load. Crashes were mostly the result of an NV4_display error, and some crashes were due to ram, although right now it's impossible to tell why I crash because event viewer doesn't record them, and the blue screens only come up for a split second

On a side note the system booted when I put the cmos battery back in, now it's up and running.

So corsair doesn't like asus and vice versa? Honestly this ram has been the root of most of my problems. I wouldn't mind going to corsair to get a refund or an upgrade... but seriously, if it's the corsair issue I'd go with kingston or ocz in a heartbeat.
 
I'm really starting to think that the Striker has some problems with the 8800GTX's and its suspend routine. If the computer goes into suspend mode at all, and then powers up again, the video card never feels like it powers up quite enough after that. Eventually the computer freezes. I restart and get a long beeping sound from the motherboard. From memory I think this means that the video card isn't installed? I can't remember... Leeghoofd, do you know what that beeping sound means at all? I couldn't find it in the Striker manual. To fix the problem I have to uplug the power, wait ten seconds and start the computer again..

My Corsair 6400C3DFs are working flawlessly in the Striker in a 2GB config.. Its just when I put in 4GBs that I have problems. I don't know if the 1102BIOS fixed any compatibility with my RAM (although it said it did in the fix list) but after I installed that BIOS and put 2GBs in my computer, the RAM is running beautifully at 3-4-3-9-1T. :) It took a whole 1:10 off my 32M SuperPi time.
 
hey. go into control panel, system, click on the advanced tab. Choose 'startup and recovery'... go down to 'system failure' and uncheck 'automatically restart'

this should give you enough time to check out whats going on.


The long beeping sound is only one steady beep?? none after the first?

If so, (and I do think that bios is Award, right?) says its a memory issue.

I had an asus board that didnt like my timings and it gave me that bullcrap. Got rid of the board mighty quick.

Oh, and Mystery. Go to the cruical memory advisor tool. see if your ram is listed as 'supported' for that motherboard.
 
Yeah the BIOS is Award - Just when I thought I had the memory issues sorted with this board. Haha...

I think I should just give up and swap out the RAM. This is ridiculous... :mad:
 
You must log in or register to reply here.
Back
Top