Ocing gone wrong....

[crispy2010]

I was trying some ocing on sys in my sig. A couple of times I had to reboot, or clear cmos and reboot. When I cleared cmos the last time it booted into cmos setup. I set the auto oc to 15% auto oc, it booted past startup and I thought it was going to start booting windows but the screen just stayed black. I turned off psu switch and tried to reboot.

Now the only thing I get is asus voice saying "failed cpu test". I have tried to clear the cmos, and have been as far as taking totaly apart and putting back togather, with the same results. Is it possible that I ruined the cpu? The mobo? Its not the ram I have tried all options with that.

This sucks, thank god for my trusty lappy!




Thanx for the help!

 

[stevty2889]

I never use the autoOC feature, because it fails to take voltages, ram speed, and other things in to consideration. It's not likely you damaged your CPU. I would unplug it, and reset the CMOS, and you should be good to go.

 

[crispy2010]

Originally posted by: stevty2889
I never use the autoOC feature, because it fails to take voltages, ram speed, and other things in to consideration. It's not likely you damaged your CPU. I would unplug it, and reset the CMOS, and you should be good to go.

Yea I have cleared the cmos and still the same. I recon I will let it sit unplugged over night with the battery out, and hope it will start in morn. I am loosing valuable crunching time!:frown:

 

[crispy2010]

Update: I left the pc unplugged all night with cmos battery out and jumper on clear. Today it is doing the same thing, "system failed cpu test", any fresh ideas on this?

Any one out there have this problem before?


Thanx for the help!

 

[crispy2010]

Went out and bought me a new mobo to test cpu and it booted, must be asus's bios. Isnt it strange their own ocing progy would corrupt their bios!