BIOS boot loop

SwatKat · 11 Jan 2016 at 21:34

Had an issue today, powered on the PC, BIOS flagged up i believe about overclocking settings. I checked everything, temp was all ok etc. Not had any issues with my OC. Quit out of BIOS and then the BIOS went into a boot loop, would not even get to the point that the speaker would beep. The LED would flicker through 36,32 then restart.

Changed the BIOS to the backup one, still the same. Pulled the power, pressed power to drain, pressed, held the bios reset, power in, the same. Pulled power, pressed power button, took out bios battery for 20+ seconds, all back, still the same.

Pulled out a stick of RAM, powered on, got to the BIOS, odd thing was all the BIOS settings were still there. Thought it could be XMP profile, set back to default, saved, started doing the same, pulled RAM put the CPU multi to 44 from 46, saved, started all ok, put the RAM back in, started again, so far all ok.

Odd thing is not been able to boot although ive been running this OC no issue for about a year. Then the BIOS didn't clear. Think i tried the BIOS reset a few times.

For any reference MB is Gigabyte z97 UD5H BK, i5 4690k, TeamGroup Vulcan Red, 4x4GB. H80i.

OC is 4.6Ghz at 1.265v.

Anyone else had anything odd like this?

5960xNvidiaGamer · 14 Jan 2016 at 20:03

Does it boot without an overclock? If so your overclock maybe wasn't stable.

SwatKat · 14 Jan 2016 at 20:31

It booted after i dropped it to 4.4ghz with the same voltage but then it did the same again the next day. This time i removed the stick again, got into the BIOS and removed the uncore OC, put the stick back.

Odd that its been stable for so long, only thing that's changed is that the times i powered on the computer it was in the evening before the heating came on so rather cold.

5960xNvidiaGamer · 14 Jan 2016 at 20:33

Sounds like its not stable that is all. If it's booting fine with no overclock its obviously an unstable overclock. Give it more volts.

P4Clock · 14 Jan 2016 at 20:36

5960xNvidiaGamer said:
Sounds like its not stable that is all. If it's booting fine with no overclock its obviously an unstable overclock. Give it more volts.

+1
1.265v is low for 4.6Hgz buddy
also a lot of ppl overlook the other voltages SA and IO are impotent for high clocks

5960xNvidiaGamer · 14 Jan 2016 at 20:46

P4Clock said:
+1
1.265v is low for 4.6Hgz buddy
also a lot of ppl overlook the other voltages SA and IO are impotent for high clocks

I thought that mate, just not quite as clued up as you are. Knew it would be overclock related though.

SwatKat · 15 Jan 2016 at 19:52

I will look at the SA and IO thanks.

In the bios it was actually set to 1.27 but it also did the same when i dropped it to 4.4ghz and 1.27 the next day.

So far after the uncore drop back to auto its been fine but then again it was fine at 4.6ghz for ages.

new boy · 15 Jan 2016 at 20:35

You were running cache at 4.6?

Thats pretty ambitious. I run my CPU at 4.7 and my cache at 4.3. Trying to get my cache higher than 4.4 took more cache voltage than I was interested in giving it.

SwatKat · 16 Jan 2016 at 13:22

The uncore was at 4ghz, the core was at 4.6 originally, put down to 4.4 when i had the issue, kept 1.27v, still did the same.

5960xNvidiaGamer · 16 Jan 2016 at 16:43

Lower the uncore to around 36 and try.

SwatKat · 23 Jan 2016 at 10:24

I set the uncore to auto after i had dropped the cpu multi to 44 and it failed to boot the next day, been running fine since, uncore on auto is 35. Ive put the cpu back to 46.

SwatKat · 16 May 2016 at 20:35

Looking on the tweaktown forum for gigabyte beta bios's it sounds like it was version 8 with the haswell code that started it. Someone had the exact same symptoms as me when they upgraded from 7d. Ive gone back to 7. See how it goes.

Had the issues even when bios reset to defaults.