Hello Captains,First of all please note that this may or may not solve your problem. This fixed it for me, but might not fix it for you.Since I've had my Asus P8Z68-V Pro. I overclocked it to 4.5 GHz stable. Every now and then, I had a problem. Sometimes, maybe once a day, when I booted up my computer, it didn't post, my screen stayed black, and after around 15 seconds it shut itself off again. Right away it rebooted again, and upon the second time, it always booted succesfully. Although I did not really have a big problem with it, I still was a little worried and started to look on the net. After some research I found that pretty much everyone with an (overclocked) Asus P67 or Z68 motherboard is seeing this problem. This was the so called "double boot" problem.After this I got quite relieved, and decided to live with it.Recently, I decided to overclock my CPU just a little further for better performance. I decided not to go over 1.4V, and wanted to see how far I could push the multiplier. I couldn't push it further than 47, and in the end, I managed to get the voltage as low as 1.39V (not any lower than this otherwise I will get BSOD with the 0x124 error). I managed to get it 12 hours stable in Prime95 with ease, and my tempatures are great also. However - suddenly after this increased overclock I got much more double boots. But this time, instead of succesfully booting upon the second time, it didn't, the screen stayed black, and didn't shut itself off again. I had to reboot manually, and then I got an error message saying something like. "Overclock failed! Please press F1 and change your settings." Seems strange doesn't it? Knowing that I just managed to get 12 hour stable in Prime95. And when it did boot upon the second time after a double boot, it just locked up during Windows startup, the logo froze and did nothing. Again I had to reboot manually. This problem was very annoying, because around 1 out of 3 boots there was a double boot upon this overclock.So, I didn't want to lower my overclock and started to look for a solution on the net again. After long time of searching, I came upon a thread, where someone said that double boots can be caused by two things:1. Something with Internal PLL Overvoltage and sleepmode. (I have heard this same thing from Word Not Allowed by the way)2. The Marvell Storage adapter.I tried the fix right under here, and haven't had a single double boot for over 1 and a half weeks. and in that time have maybe booted my PC 50 times. Because I put on my PC around 5 times a day.The fix:First of all I highly recommend updating your BIOS to the latest version, for improved system stability, and for the same BIOS layout (just in case it's not the same). Simply Google your motherboard, and the first link should be the Asus website on the page of your motherboards. Click on the Download tab and download the latest BIOS version. In February this year, the latest BIOS version for my board, version 3203 was released, I think it's the same for all Asus P67 and Z68 motherboards.When booting up your PC, press the DEL (Delete) key on your keyboard several times, until your computer goes to the BIOS. Inside the BIOS, in the top right corner of the screen, should be a button saying "Exit/Enter Advanced Mode", click it and a menu should appear, now click "Advanced mode".Now you should see several tabs. Main, Advanced, etc.Go to the Ai Tweaker tab, and set Internal PLL Overvoltage to Auto. I always used to set this to Enabled, but even before I applied those other settings, Auto gave me much better results, and is still perfectly stable.Go to the Advanced tab, now click on. Onboard Devices ConfigurationIn the Marvell section, set Marvell Storage OPROM to Disabled. I initially thought that this would disable would disable one of my HDDs or my DVD/RW drive, but it still all working perfectly.In the JMB section, set Display OptionRom in POST to DisabledOn top of the screen, click on the Boot tab.Set Option ROM Messages to Keep Current.It could be that this doesn't fix your problem. The higher the overclock, the more double boots you will have, so due to your high overclock, it might not fix your problem. However, here are my overclocking settings that I got the best results with:OC mode: XMPBCLK: 100By all cores: 47 (you may have it higher than this)Internal PLL Overvoltage: AutoEPU Power Saving Mode: DisabledLoad-Line Calibration: Ultra HighCPU Current Capability: 130%VRM Frequency: Manual: 370Phase Control: ExtremeDuty Control: ExtremeCPU Voltage: Offset Mode: this allowed me to lower my VCore by around 0.02V, with manual I need 1.41V, and with Offset I have set it to +0.040, and gave me 1.39V. Let's say for example that if your CPU would put your VCore to 1.35 on Auto, and if you put it to +0.040, it would increase it to 1.35 + 0.040 = 1.39V. Please not that your voltage may significantly differ from mine, because not all CPUs are the same. You maye need more, or maybe need less voltage than me.DRAM Voltage: 1.5V (put this to the specified voltage by your memory manufacturer)VCCIO Voltage: 1.1VCPU PLL Voltage: 1.9VPut all the other voltages on AutoSpread Spectrum: Disabled. Very important to have this DISABLED, otherwise you'll have some serious instability!Intel Virtualization Technology: DisabledEnhanced Intel Speedstep Technology: DisabledC1E: DisabledC3: DisabledC6 DisabledExecute Disable Bit: EnabledIntel Adaptive Thermal Monitor: DisabledTurbo Mode: Enabled.I really hope that this fixed your problem, cuz it fixed mine!Happy landings.Regards,

Hi Arjen,Just to let you know I gave this a try this afternoon and so far in 6 or 7 reboots and a bit of torture testing I managed to get a little more overclock and I finally figured out how to enable Vcore offset mode on a Maximus IV Extreme-Z MB. It is stable so far and no cold/double reboot issues. Sometimes I can go weeks without them and then all of a sudden get them regularly for days after that, once in a blue moon I get a bad one where it just hangs at the flashing cursor screen and I have to reset, but that is a very rare occurrence, so it may be too early to say this is a fix yet.I am convinced this is all down to the SATA Chipset that caused the big recall by all the motherboard manufacturers when the Sandy Bridge boards first came out. I think they tried to fudge it with a quick software fix in the end, I'm convinced it is a fundamental design flaw in the actual silicon, the issue is too widespread and has taken far too long to fix for it to be anything else.I left some of your settings out as I like my chip to run cool and quiet when its idle, so I ignored the steps you mentioned below and it has zero impact on stability for me.Enhanced Intel Speedstep Technology: DisabledC1E: DisabledC3: DisabledC6 Disabled I'll come back and let you know if I get any more booting issues in the future, I have the thread saved in an email for future reference.Thanks for the info.

Hi Arjen,Just to let you know I gave this a try this afternoon and so far in 6 or 7 reboots and a bit of torture testing I managed to get a little more overclock and I finally figured out how to enable Vcore offset mode on a Maximus IV Extreme-Z MB. It is stable so far and no cold/double reboot issues. Sometimes I can go weeks without them and then all of a sudden get them regularly for days after that, once in a blue moon I get a bad one where it just hangs at the flashing cursor screen and I have to reset, but that is a very rare occurrence, so it may be too early to say this is a fix yet.I am convinced this is all down to the SATA Chipset that caused the big recall by all the motherboard manufacturers when the Sandy Bridge boards first came out. I think they tried to fudge it with a quick software fix in the end, I'm convinced it is a fundamental design flaw in the actual silicon, the issue is too widespread and has taken far too long to fix for it to be anything else.I left some of your settings out as I like my chip to run cool and quiet when its idle, so I ignored the steps you mentioned below and it has zero impact on stability for me.Enhanced Intel Speedstep Technology: DisabledC1E: DisabledC3: DisabledC6 DisabledI'll come back and let you know if I get any more booting issues in the future, I have the thread saved in an email for future reference.Thanks for the info.

Although those power savers will not cause serious instability, it's still the best to put them off for the best stability though. However, I think there's no problem of having one of them enabled. I see no need to enable any other power savers than C1E and EIST, becaue you need to have C1E enabled for EIST. I will try it now with C1E and EIST on, if I have a double boot, I know what's wrong...

I doubt any of those settings are relevant at boot time to be honest so I don't see how they will be an issue. If you are getting 124 bluescreens then maybe try with them as you suggested, but as for them causing boot problems, I doubt it.

Same issue here. I was getting a double boot with a stuck in the windows logo at least once a day with my p8p67 and i5 2500k 4.7ghz. I did this tweak, dont know if technically it aims to this type of problem but practically it did for me. No more double boots. http://forums.guru3d.com/showthread.php?t=318079

Arjen VanderveldeThx. fixed my double post! great find.

Same issue here. I was getting a double boot with a stuck in the windows logo at least once a day with my p8p67 and i5 2500k 4.7ghz. I did this tweak, dont know if technically it aims to this type of problem but practically it did for me. No more double boots.

Did nouthing. Vodoo.

First of all I highly recommend updating your BIOS to the latest version, for improved system stability, and for the same BIOS layout (just in case it's not the same).

I have a P8Z68 Deluxe board, Updated the BIOS and BANG the BSOD's started! I have updated my BIOS on at least 10 different occasions and never had this happen. Result - $300 out of pocket and the new owner of a P8Z68 Deluxe Gen 3 Motherboard. Go figure?

Did nouthing. Vodoo.

+1

I have a P8Z68 Deluxe board, Updated the BIOS and BANG the BSOD's started! I have updated my BIOS on at least 10 different occasions and never had this happen. Result - $300 out of pocket and the new owner of a P8Z68 Deluxe Gen 3 Motherboard. Go figure?+1

That's not my fault is it. Asus boards are just not that good as we think. MSI is the best in my opinion.

That's not my fault is it. Asus boards are just not that good as we think. MSI is the best in my opinion.

Didn't say it was.............Just saying this is what happened to me.The double boot issue or cold boot issue is caused by something in the P67 and Z68 boards themselves. Changing settings or updating a BIOS may fix the issue temporarily but it will return........guaranteed.How do I know? It has happened to me on more than one occassion where I have done that ,the double boot has stopped but returned at a later date.

That's not my fault is it. Asus boards are just not that good as we think. MSI is the best in my opinion.

I've used Asus boards for years and I had issues with every single board. I switched to MSI and I have never looked back.Now I spend more time flying and having fun instead of tweaking and upgrading.

I've used Asus boards for years and I had issues with every single board. I switched to MSI and I have never looked back.Now I spend more time flying and having fun instead of tweaking and upgrading.

I have no problems with this baord except for the double boot problem. Which I have now fixed, or at least, decreased a lot. If the Asus Z77 boards will also have the double boot problem, I will go with MSI for sure. If not, I will take Asus again. Just waiting for the reviews.Have you ever had any double boot problems with your MSI board?

I have no problems with this baord except for the double boot problem. Which I have now fixed, or at least, decreased a lot. If the Asus Z77 boards will also have the double boot problem, I will go with MSI for sure. If not, I will take Asus again. Just waiting for the reviews.Have you ever had any double boot problems with your MSI board?

NO problems means, NO problems. I gave you the advice months ago. Be patient. New hardware comes out every few months.

I doubt any of those settings are relevant at boot time to be honest so I don't see how they will be an issue.

Boot Option ROM, Marvell Storage OPROM, JMB Display OptionRom not relevant at boot?I've found BIOS options for on-board controller initialization plenty relevant to boot results over the years and not just for ASUS boards.Thanks Arjen for looking into this. Your suggestions seem consistent with what I have read here and there about the subject. Worth a try.

Your quoting out of context, I was talking about these settings below, but I forgive you ;PEnhanced Intel Speedstep Technology: DisabledC1E: DisabledC3: DisabledC6 Disabled

Your quoting out of context, I was talking about these settings below, but I forgive you ;PEnhanced Intel Speedstep Technology: DisabledC1E: DisabledC3: DisabledC6 Disabled

Ahh...I see that now. Sorry, thanks for the absolution!