sladdo

update: ive taken the comp into getright so they can test each component i would have it a guess that either the bios is corrupt, the mb is dead or the cpu is dead i just hope its the mb

alpha0ne

Sounds like a corrupt bios

sladdo

the more i think about it the more it sort of makes sence, becuase the comp paused on looking for hdd's on the raid controller, this could mean that the bios may of buggered up from the initial pause, this would also account for it not finding the cpu i think, i guess ill find out in a couple of days, note 2 self when getting the comp back not 2 use systool 2 overclock

all about the experience i guess just hope it dont hurt the bank 2 much

alpha0ne

Could you have just bought a new preflashed bios chip ??, its always handy to have a spare (I found out the hard way)

sladdo

lol well i did not really even think of it untill i read the_rick's post and by that time i was already planning on taking the comp 2 getright, i hope for my bank account sake that getright confirm its the bios chip ill find out monday/tuesday

AusTerror

Sounds like something that would happen when the PCI clock was too high.

Maybe for whatever reason the BIOS is still thinking it should run HTT of X (whatever it is past 200) and the hardware does not like it?

On my SLI-DR, I have 'reset' the BIOS a few times and more often than not it remembers the previous HTT settings I was using.

sladdo

It turned out 2 be the motherboard in the end brad (scragley) from these forums confirmed it yesterday 2 me. I should have it all back in action this week some time I believe