BSOD after overclocking cpu

tmangfoo

Reputable
Jun 2, 2014
18
0
4,510
I recently overclock my cpu and my computer has been restarting randomly and blue screened a few times. I am using an after market cooler but noticed my cpu temps are high. I reverted the core speed back to stock but still have the same issues. Also, I made sure my cooler is connected properly, my cable management is good, and applied the right amount of thermal paste. Any help would be appreciated.

Here's my build:

cpu: amd athlon x4 760k
mobo- gigabyte F2A55M-HD2
gpu- MSI r9 270 OC
psu- thermal intake 650w bronze
case- antec mid tower case
ram - 8gb corsair vengeance LB
 


Check the CPU voltage level, along with the multiplier. Just make sure EVERYTHING is back to stock.

You could try resetting your BIOS too.
 

tmangfoo

Reputable
Jun 2, 2014
18
0
4,510
I actually have reapplied it recently. At first I had to much thermal compound then cleaned my cpu/heatsink and applied about a pea size amount on the cpu. Also, for some reason i'm getting the same temps when i use the stock cpu cooler compared to the aftermarket cooler. My temps are around 45- 50c while web browsing and around 70-80c while gaming which seems really high to me. This is my first computer build btw so I am still learning
 

Tradesman1

Legenda in Aeternum
Zalman should be good, so possible that the BIOS is feeding more voltgae than needed or am back to reapply thermal compound - or could look at adding fans to case - do you have 1-2 fans blowing air in at the bottom of the case and the one beside the CPU blowing air out? Might want to check fans are blowing the proper direction
 

tmangfoo

Reputable
Jun 2, 2014
18
0
4,510
Yes, I have one rear fan in my case and I have the cpu cooler fan blowing in the same direction, so all of the hot air should be blowing out of my case. How would I know if my BIOS is feeding too much voltage. Another thing that I noticed was that my screen would flicker when I first sign into windows after putting in my password. After doing a system refresh it hasn't happened.