System having a problem due to motherboard defect

aquaticcolor

Reputable
May 29, 2014
28
0
4,540
Hello,

So I am using a computer that has i5-4670k OC @ 4.2Ghz. The motherboard is MSI Z97S-SLI Plus motherboard. While I really like the layout and most of the motherboard itself, the computer has been constantly having a problem for a while. I have no idea why this is keep happening, so I am seeking a help.

What my computer does is that when I first turn it on, around after 3~4 minutes the system will reboot and show "Overclocked failed" bios message, which gives me a choice to bring back last stable setting (which is the current setting). After I enter the bios, and just save and exit, the system runs perfectly fine. And as long as I don't shut down my computer, it runs perfectly stable for very long time. (I've managed to run prime95 test for 2 days without a single error).

So every time I turn off the computer, when I turn it back on it automatically considers that my OC failed and requires to boot again for some reason. Is this a hardware defect that I need to call my manufacturer and get it fixed, or some error in setting that can be tweaked to be fixed?

I would appreciate any help.
Thanks.

p.s. One thing that crosses my mind is that when I first got the processor, I accidentally set the voltage too low for OC setting, resulting system failing to boot to bios. As a result, I cleared CMOS through using a screwdriver (which acts exactly like a jumper) to short the clear CMOS jumper. Did that permanently damaged the MOBO and cause this problem?
 


Yeah, if that was the case, the OC unstable message should be popping up during the usage. This only happens during the first boot up. After it resets it never happens again.
 

Yes, exactly how it should work. The instability is detected right away and bios setting are reverted temporarily until next boot. And that happens at every cold boot.
 


Before assuming someone is non-manual reading noob, how about actually trying to guess the problem? While you were treating me like an idiot, I managed to find a solution myself. I guess your nickname suits you well, since you clearly had no idea since the beginning of this post. I re-flashed the bios and used the saved profile, which solved the problem. Guess what? IT WASN'T THE OC.