That's why I keep a notepad file with all my bios settings for each of my overclocks. That way I can quickly recover and easily respond if someone asks my settings. I actually had a scare yesterday where I thought I was going to have to reinstall W7. I accidentally tried to install ReadyDriver Plus when it was already installed and while I did cancel out of it, it still managed to corrup my boot configuration thus sending my comptuer into an infinite bootup loop upon the next restart. I had to go to school and rummage up a PS/2 keyboard to be able to communicate with the bios and select the last known good boot configuration. All good after that!Aaaargh, I keep getting BSOD 0x00000124 errors - probably 4 or 5 today. That either means more vcore or more QPI/Vtt is required. Odd thing is that I've stressed my computer to its' wits end and it does fine. BSOD only happens after it sits idle for a while. Anyway, I upped my QPI/Vtt from 1.12 to 1.2 to see if that fixes things. Kind of a extreme reaction, I know, but I want to single the problem out first and then I'll try to slowly drop the voltage back down. If it's not the QPI/Vtt, then I suppose I'll drop from 5.0GHz to 4.9 as I don't really want to go higher than 1.4 vcore.

That's why I keep a notepad file with all my bios settings for each of my overclocks. That way I can quickly recover and easily respond if someone asks my settings. I actually had a scare yesterday where I thought I was going to have to reinstall W7. I accidentally tried to install ReadyDriver Plus when it was already installed and while I did cancel out of it, it still managed to corrup my boot configuration thus sending my comptuer into an infinite bootup loop upon the next restart. I had to go to school and rummage up a PS/2 keyboard to be able to communicate with the bios and select the last known good boot configuration. All good after that!Aaaargh, I keep getting BSOD 0x00000124 errors - probably 4 or 5 today. That either means more vcore or more QPI/Vtt is required. Odd thing is that I've stressed my computer to its' wits end and it does fine. BSOD only happens after it sits idle for a while. Anyway, I upped my QPI/Vtt from 1.12 to 1.2 to see if that fixes things. Kind of a extreme reaction, I know, but I want to single the problem out first and then I'll try to slowly drop the voltage back down. If it's not the QPI/Vtt, then I suppose I'll drop from 5.0GHz to 4.9 as I don't really want to go higher than 1.4 vcore.

Hope that bumping your Vtt cures the problem man. Have you tried the turbo thing? A couple of guys reported good results alreadyGot one question for you please. Did you install SP1 and the new Intel Linkpack for Lynx/IBT please? Is there anything else that needs to be done like downloading a new version of Lynx or IBT? I guess not, but just in case

Excellent! Many thanks for posting! :-)OC VOLTAGE WARNING: When you OC your SB "to the max" you are all assuming the Vcore (= CPU Vcc) reported by your MB is 100% accurate. Well, it is not! The measurement error varies according to the MB manufacturer/model and is reported in the review to be an overvolt (actual voltage above measured voltage) of 60 mV for ASUS and an overvolt of 56 mV for GBT, as measured under full load at the Vcore CPU socket pins in the article linked by David Roch (Search for "CPU Vcore monitoring"). So even though you think you are within safe limits for Vcore, in practice you might actually be slightly over, causing your SB to fail after some time (Worst case: Before your SB 2011 kit arrives at your doorstep!). So overclockers, beware!Note: The preceding warning may be total nonsense if the Vcore reported by the BIOS is measured inside the CPU: Then it follows that as load (current) increases, voltage drops accross the CPU socket pin connector resistances, so the CPU signals the external voltage controller to raise Vcore to account for that drop and maintain Vcore constant inside the CPU. Perhaps someone on the know can clarify?The Asus Maximus IV vs. the Gigabute P67A-UD7review cites several important points:

1. The GBT NB's 24-phase Vcore power supply is needlessly complex, offers no benefits, makes the board more expensive and actually makes controlling Vcore more difficult, as evidenced in the Vcore noise measurements with transiemts of up to + or - 115 mV under load, vs. only 75 mV for the ASUS board, also under load.
2. The GBT MB DIMM sockets are closer to the CPU so less clearance is available for heat-sink-endowed DIMMs. But note heatsinks are now longer needed for DIMMs as heat output has decreased with latest generation DIMMs.
3. GBT's Award BIOS uses standard ASCII text screens to set BIOS parameters and is superior to the ASUS UEFI needlessly-complex, laggy and uselessly "flashy" set-up screens, even lacking in some needed basic functionality.
4. ASUS use of 2 BIOS chips with an on-board LED indicating which one is active was deemed useful.

Conclusion:Note I am only transcribing what I think I understood from a rather technically complex review. If you have any doubts, please refer to the original article. If you find any mistakes in my understanding/transcription, please do correct them :-)Cheers,- jahman.

Hi Jahman,Thanks for that overview. I read the article too and found it a bit difficult to understand what he meant sometimes. The take-away lesson seems to be that the voltage settings and readouts from the motherboards may be highly and dangerously inaccurate. That is sobering enough on it's own.Kind regards,

Hope that bumping your Vtt cures the problem man. Have you tried the turbo thing? A couple of guys reported good results alreadyGot one question for you please. Did you install SP1 and the new Intel Linkpack for Lynx/IBT please? Is there anything else that needs to be done like downloading a new version of Lynx or IBT? I guess not, but just in case

Turbo thing? I tried setting up my bios so that it only runs at 5.0GHz under load, but it still ran at 5.0GHz all the time - perhaps I did something wrong. As for SP1, I'm going to wait for an offical release. I thought it did require a new version of LinX to take advantage of the AVX instruction set. Also I think you have to have HT disabled to see the ridiculous jump in gflops. By the way, I'm really happy so many flight simmers decided to upgrade to Sandy Bridge! No doubt new technology can be a bit troublesome, so it's reassuring to have some others along for the ride.

Turbo thing? I tried setting up my bios so that it only runs at 5.0GHz under load, but it still ran at 5.0GHz all the time - perhaps I did something wrong. As for SP1, I'm going to wait for an offical release. I thought it did require a new version of LinX to take advantage of the AVX instruction set. Also I think you have to have HT disabled to see the ridiculous jump in gflops. By the way, I'm really happy so many flight simmers decided to upgrade to Sandy Bridge! No doubt new technology can be a bit troublesome, so it's reassuring to have some others along for the ride.

Well, to be honest I'm not sure how that turbo setting works. This guy said that he set his CPU ratio via turbo for each core independantly and it helped with higher clocks / lower volts. His mobo was an Asus also, so not sure if it applies to GB too, and if it was actually enabling turbo or not.I'll ask him there and will get back to you

I tried setting up my bios so that it only runs at 5.0GHz under load, but it still ran at 5.0GHz all the time - perhaps I did something wrong.

Try this:CPU CIE = EnabledCPU C3 Report = EnabledCPU C6 Report = Enabled

Turbo thing? I tried setting up my bios so that it only runs at 5.0GHz under load, but it still ran at 5.0GHz all the time - perhaps I did something wrong.

Load Line Calibration = MediumVRM Frequency = Manual, Fixed 350Phase Control = ExtremeDuty Control = ExtremeCPU Current Capability = 120%CPU Voltage = Offset Mode, Offset +0.11 (This mode allows low volts and frequency off load) Dram Voltage = 1.65 (Slightly above recommended max (1.58V?) for CPU)VCCSA Voltage = AutoVCCIO Voltage = AutoCPU PLL Voltage = 1.71 (Minimum Intel spec - supposed to reduce temp. slightly)CPU PLL Overvolt = DisabledPCH Voltage = AutoDram Data Ref Voltage on CHA = AutoCPU Ratio = AutoBCLK = 100Turbo Multiplier = 48Enhanced Intel Speedstep Technology = EnabledIntel Hyperthreading Technology = EnabledTurbo Mode = EnabledTurbo Mode Parameters = All AutoRAM Settings = 9-9-9-24 (XMP for my memory)Intel adaptive Thermal monitor = EnabledActive Processor Cores - AllLimit CPUID Maximum = DisabledIntel Virtualization Technology = EnabledCPU CIE = Enabled CPU C3 Report = EnabledCPU C6 Report = EnabledNotes:1) Vcc drifts down slightly over time to typically 1.376V-1.384V2) Tried same over-clock on individual cores but BSOD on Prime3) Peak Temp 72C4) Volts off load 1.08 at 1.6Ghz5) Asus Bios 1204.

Load Line Calibration = MediumVRM Frequency = Manual, Fixed 350Phase Control = ExtremeDuty Control = ExtremeCPU Current Capability = 120%CPU Voltage = Offset Mode, Offset +0.11 (This mode allows low volts and frequency off load) Dram Voltage = 1.65 (Slightly above recommended max (1.58V?) for CPU)VCCSA Voltage = AutoVCCIO Voltage = AutoCPU PLL Voltage = 1.71 (Minimum Intel spec - supposed to reduce temp. slightly)CPU PLL Overvolt = DisabledPCH Voltage = AutoDram Data Ref Voltage on CHA = AutoCPU Ratio = AutoBCLK = 100Turbo Multiplier = 48Enhanced Intel Speedstep Technology = EnabledIntel Hyperthreading Technology = EnabledTurbo Mode = EnabledTurbo Mode Parameters = All AutoRAM Settings = 9-9-9-24 (XMP for my memory)Intel adaptive Thermal monitor = EnabledActive Processor Cores - AllLimit CPUID Maximum = DisabledIntel Virtualization Technology = EnabledCPU CIE = Enabled CPU C3 Report = EnabledCPU C6 Report = EnabledNotes:1) Vcc drifts down slightly over time to typically 1.376V-1.384V2) Tried same over-clock on individual cores but BSOD on Prime3) Peak Temp 72C4) Volts off load 1.08 at 1.6Ghz5) Asus Bios 1204.

Thanks for posting your settings and the extra info. Another guy tried clock per core and the only thing he said he got was higher temps, so it doesn't seem to help much really. I'll be trying it anyway and will post my results

Try this:CPU CIE = EnabledCPU C3 Report = EnabledCPU C6 Report = Enabled

That did the trick, thanks! So my bios now looks like this:

>>Advanced CPU Core FeaturesCPU Clock Ratio .......................................[ 34Internal CPU PLL Overvoltage...........................[ EnabledReal Time Ratio Changes In OS .........................[ DisabledIntel(R) Turbo Boost Tech .............................[ EnabledTurbo Ratio (Core 1)...................................[ 48Turbo Ratio (Core 2)...................................[ 48Turbo Ratio (Core 3)...................................[ 48Turbo Ratio (Core 4)...................................[ 48Turbo Power Limit (Watts)..............................[ 350Turbo Current Limit (Amps).............................[ 350CPU Cores Enabled ............................ ........[ AllCPU Multi Threading....................................[ DisabledCPU Enhanced Halt (C1E) ...............................[ EnabledC3/C6 State Support ...................................[ EnabledCPU Thermal Monitor ...................................[ DisabledCPU EIST Function .....................................[ DisabledBi-Directional PROCHOT ................................[ Disabled> Advanced Voltage Control:CPULoad Line Calibration .................................[ Level 1CPU Vcore .............................................[ 1.36QPI/VTT Voltage 1.050v ................................[ 1.12System Agent Voltage 0.925v ...........................[ 0.925PCH Core 1.050v .......................................[ 1.050CPU PLL 1.800v ........................................[ 1.76DRAMDRAM Voltage 1.500v ...................................[ 1.60DRAM Vref 0.750v ......................................[ AutoDRAM Termination 0.750v ...............................[ AutoCh-A Data VRef. 0.750v ................................[ AutoCh-B Data VRef. 0.750v ................................[ AutoCh-A Address VRef. 0.750v .............................[ AutoCh-B Address VRef. 0.750v .............................[ Auto

I set the multiplier to 34 thinking it would operate at 3.4GHz while idle, but it drops all the way down to 1.6GHz. No big deal, though. With regards to my BSOD issue, more QPI/Vtt did not solve it, so I lowerd QPI/Vtt back down to 1.12 and then dropped my multi from 50 to 48.

That did the trick, thanks! So my bios now looks like this:

>>Advanced CPU Core FeaturesCPU Clock Ratio .......................................[ 34Internal CPU PLL Overvoltage...........................[ EnabledReal Time Ratio Changes In OS .........................[ DisabledIntel(R) Turbo Boost Tech .............................[ EnabledTurbo Ratio (Core 1)...................................[ 48Turbo Ratio (Core 2)...................................[ 48Turbo Ratio (Core 3)...................................[ 48Turbo Ratio (Core 4)...................................[ 48...

I set the multiplier to 34 thinking it would operate at 3.4GHz while idle, but it drops all the way down to 1.6GHz. No big deal, though. With regards to my BSOD issue, more QPI/Vtt did not solve it, so I lowerd QPI/Vtt back down to 1.12 and then dropped my multi from 50 to 48.

Ok, so you are setting your CPU ratio via turbo. Do you achieve better results with that than setting the CPU ratio to 48 and disabling Turbo Boost Tech?

Ok, so you are setting your CPU ratio via turbo. Do you achieve better results with that than setting the CPU ratio to 48 and disabling Turbo Boost Tech?

Only as of this morning - I haven't tested it, though. Do you mean I should try to re-optimize my voltage again to see if I can get it lower than when I had turbo disabled? Why would it to be any different? I am thinking it will stop the BSOD idle issues, though. By the way, did you guys see this: Intel finds Sandy Bridge chipset design flaw, shipments stopped and recalls beginning. EDIT: my mistake, it's a problem with the chipset, not CPU... new motherboards in late February anyone?

Only as of this morning - I haven't tested it, though. Do you mean I should try to re-optimize my voltage again to see if I can get it lower than when I had turbo disabled? Why would it to be any different? I am thinking it will stop the BSOD idle issues, though.

I guess it won't hurt to try. I mean If you can cut down a couple of milivolts... I have no idea if it will help or not or how much, but I will definitely give it a go just in case.If it does help with stability it might stop the BSODs, hope that's the caseHave you tried downclocking your memory temporarily to rule that out?

By the way, did you guys see this: Intel finds Sandy Bridge chipset design flaw, shipments stopped and recalls beginning. So basically it says continue to enjoy your chips for a while longer and then pick up a brand new one in late February. Maybe it will be a new batch that clocks even better!

Yeah, someone posted the link in the spanish forums too. Here's the Intel's press releasehttp://newsroom.inte...enting-solution

My memory is already downclocked - it's stock speed is 2000MHz but I'm running it at 1866. I was hoping to get it to 2133, but I get BSOD just before getting into windows if I try that.Yeah, just realized my mistake - fixed it above. I was wondering about the "chipsets sold after the 9th statement". I bought mine on the 9th, so probably no issue? Anyway, WOW! If you wanted to upgrade to SB in the coming weeks you're out of luck as I imagine there will be no motherboards in stock anywhere until these new ones start shipping again.

My memory is already downclocked - it's stock speed is 2000MHz but I'm running it at 1866. I was hoping to get it to 2133, but I get BSOD just before getting into windows if I try that.Yeah, just realized my mistake - fixed it above. I was wondering about the "chipsets sold after the 9th statement". I bought mine on the 9th, so probably no issue?

Yes, but those sticks are rated 1.65V if I'm not wrong and you're running them at 1.6. Maybe it's not enough Vdimm for those speeds/timings. A shot in the dark I know, but that's why I always overclock the CPU first with the RAM ridiculously downclocked, just to see where the chip's limit is, then bump the memory as high as I can. Not that I invented the method or anything like that of course, but it helps isolate components and their overclock limitations

WOW! If you wanted to upgrade to SB in the coming weeks you're out of luck as I imagine there will be no motherboards in stock anywhere until these new ones start shipping again.

Yeah, what a bummer. Got my Asus PRO + I5 prepaid and I have no idea how can this affect delivery timeframe, but I don't think it's going to be that bad. Probably in a couple of minutes everyone will be emailing the store asking about this so I bet someone will post an update soon for my particular case anyway hehe. They told me (the store) they didn't have stock because their providers wanted to charge them an extra 30% for the new CPUs & mobos because of the Sandy Bridge fever haha. Greedy ######s Actually an I5 went for 203€ initially... it's at 240€ ATMIt's extremely unlikely, almost imposible that any of you who already have your mobos got one of those chipsets sold by intel after the 9th. I mean they still have to assemble the boards, distribute them and sell them after that

I'm assuming you're speaking in terms of the BSOD issues I was having while at idle... I might try that. I had actually bumped them up from 1.54v for the same reason, but I may as well put them at 1.65v to be sure.If you're talking about me trying to run my memory at 2133, I've tried as high as 1.7v and still couldn't get into windows.