Asrock h87m unstable after BIOS update

HoffRS

Commendable
Nov 23, 2016
3
0
1,520
Hello, I have an Asrock h87m for over two years without any problems. So I bought a water cooler to overclock my i5 4670K. I begin testing the water cooler temps and everything was working perfect. I install the ATuning and made some testing, everything working as expected. So I tried to overclock via BIOS, them in order to do that, I updated my BIOS to the Non EZ version and overclocked my processor. I was not able to make my system stable, with any voltage (1.000 to 1.3000). The temps never cross 60º Celsius and the system continues unstable. So I tried every BIOS version available and the system continues unstable. So I try to go back to the stock configuration with BIOS reset, BIOS update, downgrade and the system continues unstable. Every time that the processor go to full usage the system reboots. I have tested the system with undervolting, underclocking, removing extra hardware to test PSU and the problems persists. Any ideas of what may causing this problem?
 
Solution


Hello Calvin7, thank you for the answer. Indeed the chipset is not suitable for overclocking though is possible. I solved the problem disabling the motherboard overheat shutdown. The temps continues bellow 60º, so it’s probably a bug.

COLGeek

Cybernaut
Moderator
MERGED QUESTION
Question from HoffRS : "Asrock h87m unstable after BIOS update"



 
Intel H87 is not a chipset for overclocking.

High voltages can damage components. Software overclocking programs often use high voltages to achieve results. Warranty covers any malfunctions that occur under normal use conditions.

A Z87 may use a 12 Power Phase design, while your H87M uses a 4 Power Phase Design not really suited for overclocking.
 

HoffRS

Commendable
Nov 23, 2016
3
0
1,520


Hello Calvin7, thank you for the answer. Indeed the chipset is not suitable for overclocking though is possible. I solved the problem disabling the motherboard overheat shutdown. The temps continues bellow 60º, so it’s probably a bug.

 
Solution