i think I fried my cpu

Toggle sidebar Toggle sidebar
Gate9er

Gate9er

Distinguished
Feb 15, 2012
1,460
0
19,660
Hey guys

I accidentaly set my 6700k vcore to 1.995 V and frequency at 4.4Ghz, then clicked save and restart and now when I power it on it does not boot and gives an error code FF (FF code could be anything) . I have reset the bios but still no luck...

Update: It seems that the BIOS will not reset might a fried motherboard..

Any suggestions?
 
Solution
synphul
That could be a possibility, it just depends on what fried. It's also possible that the motherboard was ok and the cpu cooked. You could either try that cpu in a different board or try a different cpu in your board, both would be first steps to identifying the problem. Having neither spare on hand to test with the motherboard would be the less expensive route to start with for sure.
Sort by date Sort by votes
Shaun o

Shaun o

Illustrious
Oct 7, 2007
6,113
1
41,960
I dare say if you set the voltage to almost 2 volts.

Then it would of hit a few of the transistors on the cpu and likely damaged them.
That is why, as you know it`s always stated when over clocking to heed the maximum core voltage each cpu will take.

The more voltage you feed to a transistor of any size or scale will result in it heating up, in the same way as asking it to switch much faster in speed, based on the frequency you set in Mhz.

FF always relates to a hardware issue with something connected to the motherboard sockets, or interface slots.
Every time you turn on, or power the system things like the cpu have to send information to the bios to identify them-self.

So the bios can verify the current settings for the hardware are correct.
It`s called the microcode of each cpu.

The only way you are going to know if it`s the cpu, or the motherboard as it stands is to at least fit another cpu to the cpu socket of the motherboard.

But I suspect you popped a few transistors of the current cpu in the socket due to the 1.995 voltage feed to the cpu.



 
Upvote 0 Downvote
synphul

synphul

Champion
Mar 11, 2011
9,477
7
54,965
You might try unplugging the cable from the power supply to the wall then removing the cmos battery for a minute or two and placing it back in. Then plug your psu back into the wall and attempt to start. Sometimes the ez bios resets don't work or run into an issue when they're still plugged in and may be receiving power from the wall (the idea to remove power from the cmos to clear it).

If neither of those work you may need to start from the ground up using a known good motherboard to verify if it's the cpu or the board. That was a lot of vcore, it could have possibly damaged either the mobo or cpu. Hopefully just the board.
 
Upvote 0 Downvote
Shaun o

Shaun o

Illustrious
Oct 7, 2007
6,113
1
41,960
To be honest, it depends on what you need to do reset the bios.

If the board has a set of jumper pins on it to reset the bios back to factory default settings.
With a bridge connector.

Move it over to the reset bios position on the motherboard.
Then power the system on, for a brief few seconds.

Shut it down.

Then move the bridge pin back over to normal operation of the bios.
And power it up again.

See if it resets the bios back to factory default mode Gate9er.

 
Upvote 0 Downvote
synphul

synphul

Champion
Mar 11, 2011
9,477
7
54,965
I know some have onboard reset switches and things, they don't always work properly though. Or don't always work the first time. The old tried and true method of removing the cmos battery is still one of the simplest and most effective ways to ensure no power is getting to the cmos so it can clear itself.

I had one that crashed on startup (oc settings were unstable) and went to clear the bios. It didn't work at first until I went that route and removed the cmos battery. Reinserted it, plugged it back in and problem solved. It still may not work, my issue was instability not overvoltage on vcore to that degree. However it's easy enough and free to try. It at least eliminates that possibility.
 
Upvote 0 Downvote
synphul

synphul

Champion
Mar 11, 2011
9,477
7
54,965
That could be a possibility, it just depends on what fried. It's also possible that the motherboard was ok and the cpu cooked. You could either try that cpu in a different board or try a different cpu in your board, both would be first steps to identifying the problem. Having neither spare on hand to test with the motherboard would be the less expensive route to start with for sure.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom