Pc turns on, then off, then on again, if overclocking amd fx 8320.

Pedro Vianna

Reputable
Jul 17, 2014
1
0
4,510
I've bought an AMD FX 8320 and tried OCing it to 4.0 ghz, keeping the original voltage,
But with the oc, my pc doesn't turn on properly. It turns on, then off, then after a couple seconds on again, booting windows and everything normally.

Tested the oc in prime95 for some hours and I didn't find any other problem. And it only turns on normally if I return the clock speed to the default 3.5 ghz.

I don't know why it happens. I don't think it's a bios problem or psu. I was able to change the voltage it no problem (since I couldn't oc it, I did an undervolting) and my psu is really good according to every forum I searched.

I want to resolve this because my plan is to buy an 212 evo and oc the 8320 at least 4 ghz.

My system is:
gigabyte 970a ud3
amd fx 8320
sapphire r9 270x vapor-x
8 gb RAM (two 4gb sticks on dual channel)
xfx pro series 550w (44 amps on 12v rail)
seagate barracuda 1 tera (i think)
combo dvd drive
 
Solution
That sounds like when you adjust a setting in the BIOS like the multiplier or CPU/NB or something then exit the BIOS. Itll shut down then restart again. I kinda think it could be a BIOS issue too. Check and see what version you have and see if its the latest. It could be something to do with the compatibility of your chip. If the computer is running fine its not that big a deal but is kind of annoying. Updating to the latest BIOS should fix the problem cause it sounds an awful lot like BIOS behavior.

axe1592

Distinguished
Mar 29, 2010
232
0
18,710
That sounds like when you adjust a setting in the BIOS like the multiplier or CPU/NB or something then exit the BIOS. Itll shut down then restart again. I kinda think it could be a BIOS issue too. Check and see what version you have and see if its the latest. It could be something to do with the compatibility of your chip. If the computer is running fine its not that big a deal but is kind of annoying. Updating to the latest BIOS should fix the problem cause it sounds an awful lot like BIOS behavior.
 
Solution