Is this normal behavior on x58 system boot?

[DuyNgn]

Hey,

I just recently got the Core i7 in my sig built. I notice that whenever I perform a cold boot from the power button, the system goes "wooosh" and comes to life.... for 1 second.... then goes silent as if it's completely off for the next 2-3 seconds and then it comes to life again and proceed with normal boot up.

System ran perfectly fine once booted. Is it something unique about my motherboard? What could it be doing acting strange like that?

It behaves normally on soft reboot. Also behaves normally on shut down. It only behaves like I described when starting a cold boot from the power switch. Also note that on FIRST ever boot(after all components are finally installed), it did not do this. It only does this after the first full shut down.(which is after I installed the chipset drivers)

My guess is that Gigabyte motherboard has some features that I'm unaware of. Anyone has any idea?

 

[PC_User]

This sounds like the infamous double boot issue. It has been happening on many P35/P45 motherboards. It's not an issue if it in fact is the double boot. I'm 95% sure because it really sounds like it. My old P35 IP35-E motherboard does the same thing on a cold boot.

 

[DuyNgn]

This sounds like the infamous double boot issue. It has been happening on many P35/P45 motherboards. It's not an issue if it in fact is the double boot. I'm 95% sure because it really sounds like it. My old P35 IP35-E motherboard does the same thing on a cold boot.

Ah I see. I googled "double boot" and it seems this is the deal with a dual bios set up. Though from what I read, people reports that it didn't like the settings on the first bios and revert to used the settings on the second bios instead... which should be default.

I don't think this is the case as whenever I get into windows, CPUz reports the settings as I've set in the bios for overclocking, which should sit on the first bios.

I've also read about undervolting and what not, I have my cpu at 3.0Ghz (150x20) with 1.151v(as reported by CPUz) and primed for hours with no errors. Also game on it at these settings for a whole night with no issues. It was also doing this when I had it set at 3.2Ghz with 1.21v. I really don't think 1.21v is insufficient for such low clock speed.

Hmmm anyone else has any ideas?

 

[Dangman]

There really hasn't been a definitive reason why the double boot issue occurs. However, don't fret. the double boot issue does not harm any hardware but it's just an annoyance. Usually a BIOs update fixes the double boot issue.

 

[PC_User]

There really hasn't been a definitive reason why the double boot issue occurs. However, don't fret. the double boot issue does not harm any hardware but it's just an annoyance. Usually a BIOs update fixes the double boot issue.

Usually is the key word. When I first got my ABIT IP35-E, I had the double boot and thought that I could live with it until the next bios update. I went through 5 bios updates (from version 13 to 18) and the issue is still there. I guess some companies don't care enough to fix it. But you're right, thankfully it's just annoying and not harmful.

 

[engiNURD]

Usually is the key word. When I first got my ABIT IP35-E, I had the double boot and thought that I could live with it until the next bios update. I went through 5 bios updates (from version 13 to 18) and the issue is still there. I guess some companies don't care enough to fix it. But you're right, thankfully it's just annoying and not harmful.

IIRC, mine had BIOS 15 or whatever, and fixed the dual boot issue for my IP35-E. I don't think its as simple as Abit didn't care enough to fix it, but rather, a more likely explanation is that it is/was a hard issue to pin down.