Boot Failure Detected OC
Boot Failure Detected OC
When I updated my AMD 8320E using a Gigabyte 970A-UD3P, the settings at 4.0ghz with 1.3volts performed well. During stress tests with Prime95 while monitoring via HWMonitor and AMD Overdrive, I adjusted it to 4.5Ghz at 1.45v, staying below 1.5v. After 30 minutes of testing, all cores passed without failure. However, when booting up, the system reports a Boot Failure Detected error and shows a CPU speed of 0.00mhz. Pressing "Go into Bios" and following the steps still results in Windows 10 startup. Am I damaging my CPU?
When I updated my AMD 8320E on a Gigabyte 970A-UD3P, the settings at 4.0ghz with 1.3 volts performed well. During stress tests using Prime95 while monitoring with HWMonitor and AMD Overdrive, I adjusted it to 4.5Ghz at 1.45v, staying below 1.5v. After a 30-minute test, none of the cores failed and passed on Prime95. However, whenever I restart the system, I encounter a Boot Failure Detected error and the CPU speed reads 0.00mhz. After entering BIOS, pressing F10, saving, and exiting, it boots into Windows 10. Am I damaging my CPU?
I noticed others with the same mainboard and CPU face the same problem. Both use Revision 2.x and the latest FC BIOS. My observations are:
If you want to increase the multiplier beyond 20, keep Turbo enabled and match its multiplier value to the "normal" setting. I discovered this tip in a forum—it’s a common Gigabyte issue.
Secondly, once you surpass that 20x mark, unusual behavior appears. This board simply can’t cope, and Gigabyte’s product isn’t fixing it. Running my 8320E at 4.2Ghz, I always have to reload settings and keep seeing "Boot Failure Detected." Pressing F10 after loading settings brings the PC back online and allows Prime95 to run smoothly for extended periods.
A closer look at the error messages shows a consistent 4000 MHz maximum. If I apply the “turbo trick,” it drops to 0 MHz, as if the board fails. It seems this issue isn’t unique to my setup—many users report similar problems. There are numerous forum discussions about turning core unlockers off or changing to UEFI-only mode, but nothing resolves the problem except running at a maximum clock speed of 4 GHz. This bug isn’t limited to AMD boards; Intel models also exhibit similar behavior. Simply searching “Gigabyte Boot Failure Detected” reveals countless reports.
In short, it appears the hardware is unsuitable for such high speeds, and Gigabyte’s reliability is questionable. I’ve experienced multiple failures with their products in the workplace as well.