Boot Failure Detected OC

irexygorawr

Commendable
Jul 26, 2016
12
0
1,510
When i OC my AMD 8320E on a Gigabyte 970A-UD3P, my settings at 4.0ghz w/ 1.3volts worked.
I stress test that setting with Prime95 while watching the results with HWMonitor and AMD Overdrive.

I then OC it to 4.5Ghz at 1.45v, knowing not to go past 1.5v. I stress-tested that OC Setting for 30 minutes and none of the cores failed and passed the test on Prime95.

Everytime i go to boot my system up though, it says Boot Failure Detected, and Current CPU Speed 0.00mhz. I press " Go into Bios", clicked F10, Save and Exit and it boots into my Windows 10.

Am i killing my CPU?
 

Gerrit507

Prominent
Feb 21, 2017
1
0
510



Hey,

I have the same mainboard and CPU with the exact same issue. It's Revision 2.x and I'm using the latest FC bios.

What I figured out first:
If you want to take the multiplier higher than 20 you have to keep Turbo enabled and set the turbo multiplier to the same value as the "normal" multiplier. I found this trick in some forum. That's typical Gigabyte bug No.1

Second:
As soon as you pass that magical 20x multiplier mark all strange things start to happen. This board just can't handle it, and this garbage factory Gigabyte is not able to fix it. I'm running my 8320E @ 4,2 GHz and EVERY SINGLE TIME I start my PC I have to reload the settings, "Boot Failure Detected". I load the settings hit F10, the PC boots normal and runs rock solid on Prime95 for days.

Let's look closely on the Boot Error Message, it always shows 4000 MHz at max, if I do the previous mentioned "turbo trick" and 0 MHz if I don't do it, like you. I can't remember right now if I was I able to boot at all without turbo enabled, but it seems like it works for you at least.

I've found lots of different information in forums about this bug, like "turn core unlocker off", which I never had enabled or change to UEFI only mode, nothing solves that problem except a clockspeed of 4 GHz at max. This goes even further, not only AMD boards have this issue, Intel boards have a similar bug, too. Just google "Gigabyte Boot Failure Detected" and there are tons and tons of bug reports.

So summarized that means, the board is crap because it can't handle 4+ GHz and Gigabyte is a crap company I'll never buy from again. I had already tons of problems with their boards at work, too.
 

TRENDING THREADS