pc wont boot

  • Thread starter Thread starter k3v
  • Start date Start date

k3v

k3v

Associate
Joined
26 Apr 2006
Posts
1,198
Location
NE Derbyshire
I've put a dfi lanparty ut sli mobo in my pc and some new ram. its been running fine for a couple of days. I've today decided to overclock it. I have an opteron 170 and I've clocked it to 2.5 and went back into the bios to further tweak it, rebooted then nothing...... well not quite nothing. I get 4 beeps, a flashing power light and it won't post. I think its 4 beeps as it beeps v. quickly if its not 4 then its 5.
I've searched for beeps on my phone and it doesn't look good!
any ideas ? I've swapped the ram over with no change. I do have another cpu and mobo that I could try but I've been setting it up all day and I can't face doing it if there is another way

any help much appreciated
 
sorry - i take it you have tried to clear the cmos. get that out the way first.

sorry if thats a stupid question.
 
thanks for the replies, I've had the battery out for a min or 2 to clear it, yesterday this was long enough to reset it. I'm now leaving it longer, just to make sure. I'm just trying to find what bios the dfi mobo uses
 
cheers, that's ruled the bios out then. hmm looks like I'm gonna have to swap the mobo back over. I'm just wondering if its maybe a psu problem because the light flashes, probably going to be expensive whatever
 
thanks for the reply, ill try the cmos jumper tonight, is this any different to taking out the battery?
after more research last night, I found the molex power connector the fdd style power connector, I hadn't connected these. I also noticed I hadn't put the 4 pin power lead in to make 24 pins. so originally I had the 20 pin main power connected and the separate 4 pin power lead connected and nothing else. I plugged in the molex power and plugged in the 4 pin main power to make 24 pins and it still doesn't work, the only one left to add is the fdd style one. all the fans come on and spin continually so I'm hoping I haven't fried anything.
this is a lesson for me to read the instructions properly and not attempt to build after a bottle of wine.
 
cheers, I've been reading over on dfi street and this seems a very common problem. I've got some ideas on how to cure it.
 
reseting the bios with the jumper worked a treat, thanks for all your help
 
it was, I was starting to think the worst, I didn't help matters that I'd spent all day reinstalling software... note to self must use ghost or something now its all working.
 
Last edited:
Back
Top Bottom