"Your previous overclock setting have failed"

[ThiefOfOranges]

Okay, so I have been trying to overclock my i5-4670k from 3.4 to 4.6 GHz, but I keep getting random crashes. The crashes are coming at random times, usually not even times when the PC would be stressed. I've been able to play BF4 for hours without getting crashes, but then sometimes while watching twitch streams, it'll just randomly reboot and tell me "your previous overclock setting have failed, Press F1 to enter setup or F2 to load default values and enter setup. The issue definitely isn't cooling because I never get over 70C when this happens.

Just wondering if someone could take a look at my settings and tell me if there is a glaring mistake I've made that would lead to this.

http://pasteboard.co/2G8Jj3hGh.jpg

http://pasteboard.co/2G825A1kX.jpg

Sorry for having to take phone pictures, my USB drive can't be read in my BIOS for some reason to screenshot.

Build:
i5-4670k
MSI GTX 1070
Z87-G41 PC Mate
Corsair H80i cooler
EVGA SuperNOVA 650 GS, 80+ GOLD 650W

 

[scuzzycard]

I would lower VCCIN to 1.95V and raise Vcore to 1.30.

 

[ThiefOfOranges]

I'll give that a shot

 

[Cole_9]

Yes raise the voltage. insufficient voltage can cause hardware failures especially if your CPU is overclocked. Raise the vcore by little bits at a time and then test system stability each and every adjustment you make.

 

[ThiefOfOranges]

Failed again with those settings. The max Vcore it'll let me use is 1.3 so I can't possibly raise that any more, should I raise the VCCIN back up?

 

[ThiefOfOranges]

To anyone it may concern, I figured out the problem. I should've mentioned that I recently upgraded to Windows 10 from Windows 7. I realized today that the crash only happened on cold boots, about 10 minutes in, then on restart it would run perfectly.

For some reason, the fast boot option in Windows 10 must mess up some of the OC settings causing the crash. So I went to the control panel>power options>change what the power buttons do, and disabled the fast boot. It's now working properly.