First boot always fail but second is always ok (cycle repeats)

[pui92]

Hi there,

Here's my PC Components list
i7-3930K
Thermaltake Water 2.0 Extreme
AsRock X79 Exreme9
32GB Corsair Vengeance DDR3-1600 Quad Channel
PSU Corsair HX750 Then switched to EVGA Supernova G2 850W
XFX R9-390X DD
2 SSD + 1 WD Green
AsRock SoundBlaster

So my problem is that there is this pattern.
- Power on, few seconds passed, PC Shuts itself down
- Then i powered it on again, Boots nicely & smooth without any hitch. Shut down normally when i'm done.
Then this pattern will repeat again where the pc will shut itself down and after powered on again, it will boot fine.

What i've tried:
Test RAMs - Removed them and tested them one by one. Tested them on other PC as well. works fine
PSU issue - figured there might not be enough juice or maybe bad psu, so i switched to the new 850W PSU.
Swap GPU - i swapped in an old GTX 670, i thought perhaps the 390x is a dud.
BIOS settings - i've cleared CMOS, reset to default, flash BIOS.
bad Front panel switch - i've removed them and try powering on by the on board switch
CPU cooler & Thermal paste - i've removed and re-apply them.

I was hoping if anyone could help me find the solution and i really really hope that it's not the motherboard( getting a x79 motherboard is almost impossible in indonesia, RMA is just as bad)

 

[Caring1]

Try manually setting your Ram timings in the BIOS instead of auto.

 

[pui92]

Try manually setting your Ram timings in the BIOS instead of auto.

Thank you for your reply.
Unfortunately that did not work

 

[Ebo]

change the battery on your MB, its a CR 2032

 

[RejZoR]

Is CPU overclocked? My Core i7 920 on Rampage II Gene (X58) had a cold bug when overclocked. It was doing exactly the same thing, but only when booting from cold. If I turned it off (even if unplugged) and then tried turning it on again, it would work directly. But if it was sitting OFF for few hours, always 2 cycles to boot.

 

[Mussels]

Hi there,

Here's my PC Components list
i7-3930K
Thermaltake Water 2.0 Extreme
AsRock X79 Exreme9
32GB Corsair Vengeance DDR3-1600 Quad Channel
PSU Corsair HX750 Then switched to EVGA Supernova G2 850W
XFX R9-390X DD
2 SSD + 1 WD Green
AsRock SoundBlaster

So my problem is that there is this pattern.
- Power on, few seconds passed, PC Shuts itself down
- Then i powered it on again, Boots nicely & smooth without any hitch. Shut down normally when i'm done.
Then this pattern will repeat again where the pc will shut itself down and after powered on again, it will boot fine.

What i've tried:
Test RAMs - Removed them and tested them one by one. Tested them on other PC as well. works fine
PSU issue - figured there might not be enough juice or maybe bad psu, so i switched to the new 850W PSU.
Swap GPU - i swapped in an old GTX 670, i thought perhaps the 390x is a dud.
BIOS settings - i've cleared CMOS, reset to default, flash BIOS.
bad Front panel switch - i've removed them and try powering on by the on board switch
CPU cooler & Thermal paste - i've removed and re-apply them.

I was hoping if anyone could help me find the solution and i really really hope that it's not the motherboard( getting a x79 motherboard is almost impossible in indonesia, RMA is just as bad)

this is normal POSTing behaviour on a lot of motherboards. It's part of the 'failed overclock' safety settings, it boots into 'good' settings then 'quickly' loads the ones saved in the BIOS and boots fully.

It may be annoying but i've had it happen on half a dozen motherboards (usually gigabyte and asrock) going all the way back to the 775 days.

 

[silentbogo]

this is normal POSTing behaviour on a lot of motherboards. It's part of the 'failed overclock' safety settings, it boots into 'good' settings then 'quickly' loads the ones saved in the BIOS and boots fully.

It may be annoying but i've had it happen on half a dozen motherboards (usually gigabyte and asrock) going all the way back to the 775 days.

+1
Had this problem on two x58 boards (both gigabyte) - both times due to RAM overclock instability (had 6 very old OCZ Platinum sticks at the time).

 

[pui92]

No OC has been manually set by myself. I've always leave it to the default settings, so most of the settings are usually on "auto"

But let me check it again, replace the mb battery as well and get back here.

 

[Ferrum Master]

Up the uncore voltage, if you have dedicated setting for boot voltage use that.

 

[bug]

@pui92 Your motherboard has a diagnostic display. Use it to pinpoint your problem.

 

[Bill_Bright]

change the battery on your MB, its a CR 2032

My first thought too.

this is normal POSTing behaviour on a lot of motherboards. It's part of the 'failed overclock' safety settings,

A case of semantics but I would not call this "normal" behavior because it happens when there is an "abnormal" condition. Though it is an "expected behavior" when a failed overclock occurs.

We have seen this error before too but it was not always due to improper clocking. It can also occur after adding dissimilar RAM or if the existing RAM becomes faulty. In those cases when the client added dissimilar RAM, MemTest86 found no problems. And there were no problems when the old RAM only was used, or when the new RAM only was used. But old and new together resulted in these errors. Very frustrating to troubleshoot.

That said, it does not appear the OP added any new RAM lately and he has already "cleared CMOS, reset to default, flash BIOS". And he states he has not manually set any clocks either. So the clocks should not be the problem here.

@pui92 - when did this problem start?

 

[jboydgolfer]

this is normal POSTing behaviour on a lot of motherboards. It's part of the 'failed overclock' safety settings, it boots into 'good' settings then 'quickly' loads the ones saved in the BIOS and boots fully.

It may be annoying but i've had it happen on half a dozen motherboards (usually gigabyte and asrock) going all the way back to the 775 days.

Yeah I can confirm that, I buy asrock motherboards and they don't all do this ....but I've had one that did do it ,off the top of my head I just can't recall which one , but I want to say my Z 68

updated the bios to resolve it

 

[eidairaman1]

Pull the board out of the case place on non conductive surface and elevate with a box so you can test it with a gpu and psu., if it has surface mounted power switch use that to try and boot system. Ive seen power switches in cases go bad

 

[Mussels]

My first thought too.

A case of semantics but I would not call this "normal" behavior because it happens when there is an "abnormal" condition. Though it is an "expected behavior" when a failed overclock occurs.

We have seen this error before too but it was not always due to improper clocking. It can also occur after adding dissimilar RAM or if the existing RAM becomes faulty. In those cases when the client added dissimilar RAM, MemTest86 found no problems. And there were no problems when the old RAM only was used, or when the new RAM only was used. But old and new together resulted in these errors. Very frustrating to troubleshoot.

That said, it does not appear the OP added any new RAM lately and he has already "cleared CMOS, reset to default, flash BIOS". And he states he has not manually set any clocks either. So the clocks should not be the problem here.

@pui92 - when did this problem start?

i've had plenty of motherboards where it was normal for those motherboards. with certain CPU and ram combinations it wouldnt happen unless you had settings changed off auto, and other hardware combinations would always do it.

IMO its just a hardware quirk and if a BIOS update doesnt make it go away on default settings, it is simply normal for that hardware combination - they dont reset the settings or anything like that on the 'failed' boot, it just takes a few seconds longer.

 

[pui92]

@pui92 Your motherboard has a diagnostic display. Use it to pinpoint your problem.

My PC shuts itself not long after the diagnostic display stopped displaying codes.

My first thought too.

A case of semantics but I would not call this "normal" behavior because it happens when there is an "abnormal" condition. Though it is an "expected behavior" when a failed overclock occurs.

We have seen this error before too but it was not always due to improper clocking. It can also occur after adding dissimilar RAM or if the existing RAM becomes faulty. In those cases when the client added dissimilar RAM, MemTest86 found no problems. And there were no problems when the old RAM only was used, or when the new RAM only was used. But old and new together resulted in these errors. Very frustrating to troubleshoot.

That said, it does not appear the OP added any new RAM lately and he has already "cleared CMOS, reset to default, flash BIOS". And he states he has not manually set any clocks either. So the clocks should not be the problem here.

@pui92 - when did this problem start?

Hard to say when as i'm not the main user and the user seems clueless.

Pull the board out of the case place on non conductive surface and elevate with a box so you can test it with a gpu and psu., if it has surface mounted power switch use that to try and boot system. Ive seen power switches in cases go bad

i've already done this, like you mentioned maybe it's bad power switches, so i pull the components out and power on using onboard switch. but the result is the same.

i have yet to replace the mb battery and check on the CPU overclocking settings, maybe during the weekend.

 

[bug]

My PC shuts itself not long after the diagnostic display stopped displaying codes.

Ok, but what's the last code you see? Or does it go through the complete boot sequence and then reboots itself? Because if it does, I'd look at the OS instead (or a UEFI reflash).

 

[Rowsol]

I had the same issue for a few years except for me it didn't shut off, it would freeze. I booted it by powering it on, waiting for the HD to click on, then press the reset button. Always booted fine then. Turned out to be the Sandisk SSD I had.

I understand this is most likely not anywhere close to your issue but figured I'd mention.

 

[trog100]

failing to reliably boot first time to me is something an old past its best machine does.. my last eight year old machine did it.. i tended to leave it in sleep mode to avoid the issue..

something in there dosnt like the shock of suddenly being kicked into life from cold.. i would not even hazard a guess as to what..

trog

 

[pui92]

Hey Everyone,

Thanks for all your help, The culprit turns out to be the SSD Boot drive(samsung 840evo). I installed samsung magician (i forgot to install it when fresh installed w10) and disabled the hibernation mode. The system now boots without any hiccup.
Again i want to thank everyone here for your help! you guys are awesome!

 

[Mussels]

Hey Everyone,

Thanks for all your help, The culprit turns out to be the SSD Boot drive(samsung 840evo). I installed samsung magician (i forgot to install it when fresh installed w10) and disabled the hibernation mode. The system now boots without any hiccup.
Again i want to thank everyone here for your help! you guys are awesome!

thank you for coming back and letting us know what it was!