Never purchasing another Gigabyte again
Never purchasing another Gigabyte again
Earlier this year, I acquired a Gigabyte X79 motherboard that has remained functional for an extended period. It exhibited a peculiar issue when attempting to boot—specifically, I needed to execute a precise sequence: power on, press the power button, then perform a delete action to enter BIOS. If I bypassed this method, the system would refuse to start or would restart immediately. This procedure had to be repeated seven times over three years, yet it consistently succeeded. The challenge arises only when pushing the processor beyond a certain threshold, likely exceeding 3.8GHz on the 3930k chip. Below that speed, normal booting occurs without such steps. However, anything above 4GHz demands this extra ritual. This isn<|pad|>’s procedure isn<|pad|>, not due to reset settings or default configurations, but because it’s essential for the overclock. After seven years, I’m confident the stability has held. Now I own a Gigabyte X570 Aorus Master, assembled with a custom loop and modified case. What am I experiencing? A nearly identical issue. It seems there’s a fundamental flaw in Gigabyte’s boot firmware. Although closely related, the problem isn’t identical. I suspect a consistent pattern exists—possibly a mandatory reset step during overclocking. While I haven’t confirmed the exact cause yet, my observations point toward a critical flaw in the BIOS handling. Although it’s similar to the X79, it isn’t exactly the same. I haven’t pinpointed the exact cause yet, but so far, a straight cold boot always fails. Windows Boot Manager may display a blue screen when attempting to load a kernel file, or it might freeze during POST. If I enter BIOS and choose save and exit, it usually boots again, though the POST screen can become unstable. This freezing occasionally disrupts installation and updates, turning them into a challenge. It’s possible that during a crucial boot phase—such as the first startup or after a major update—the system might fail to locate the kernel file, prompting Windows to assume an error and revert to recovery or attempt a rollback. This process can also backfire, potentially corrupting the whole system. I’m not certain if this issue is exclusive to overclocking, but I haven’t conducted sufficient testing. Still, I know the freezing only occurs during overclocking, not with default settings. I’m using PBO, which isn’t a manual overclock like the previous setup, and my clock is stable. The problem lies in the POST sequence, which remains highly sensitive. Between these two boards, I opted for an ASUS Rampage Extreme VI for a year—no complications there. It performed flawlessly, with no strange glitches. In contrast, the X570 BIOS can shift settings unexpectedly, altering the “settings” menu and adding unfamiliar options. That’s quite a situation.
Occasionally I notice this message appears. It’s clear you’re not getting a consistent overclock when problems arise after enabling it. Just because another CPU hits 5 GHz doesn’t guarantee the same for yours—it’s all about luck with the silicon draw. If your system often fails to boot, it signals instability. Like any troubleshooting, start by turning off all overclocks—CPU, GPU, RAM—and returning everything to default settings. If the issues vanish, chances are it was just an unstable overclock. Gradually increase the settings again until problems return, then reduce them one step at a time. Run your stress tests to confirm stability and acceptable temperatures. If the problem continues, consider reinstalling Windows (keeping only the relevant drive connected) or updating your motherboard’s BIOS if needed. If nothing works, reach out to Gigabyte or your seller, describe the issues, and request an RMA.
I prefer stable overclocks. Anything else leads to crashes or weird behavior. Plus, I’m here if the system goes beyond specs and stops working—should it be the manufacturer’s responsibility?
*P.S.: Stop pushing your systems to unstable limits before updating Windows. Pro tip.*
It's fully reliable after startup, I can handle whatever I need, top performance at 95%, and testing is straightforward. Still puzzled about the initial failures—if it's just unstable, it should boot at least occasionally. I've been doing this a long time now; I understand overclocking, stability checks, and what counts as stable. My assumptions suggest the issue might relate to the specific configurations I use. The X79 came from a PCIE SSD, and the X570 is now running RAID0 with two 970 Pro drives. It's likely the problem occurred before the array was fully set up, causing incorrect file reading. Or perhaps memory timing is inconsistent, leading to different behavior between cold starts and reboots.
It means you can describe it as reliable, though usually a steady system works by pressing the start button and it launches. Being unpredictable isn't the goal—consistency matters. If you're unsure about the effects of overclocking, it's okay to skip that step and focus on other fixes. You noted you haven't experienced booting from a RAID setup before, only occasional issues. Looking into PBO suggests it doesn't involve actual overclocking, which makes it less likely. Still, testing without OC could help clarify the issue. If it doesn't work, OC isn't the root cause and you've identified the real problem.