I'm antsy to get back up to previous settings so I've done some numbers with mostly failed results lolAll settings are default in BIOS, except ram is XMP profile, turbo boost is disabled, and:45x and vcore 1.39 = BSOD within minutes of getting into Windows (also, ET6/CPUz show vcore much lower than 1.39, shows more like 1.33-1.35 so it apparently won't run with 1.39 at all.45x + 1.30 = Windows doesn't load45 + 1.36 = Same40 + 1.30 = appears to fine initially but my screen went blank (PC still on), and it seemed like it went to hibernate because I pressed spacebar and it "woke up" again. Not sure what's up with that!These voltages seem really high though - that SB OC guide for beginners shows their 2600K on like 1.27 max for a 4.5 GHz overclock. For their 4GHz all they did was up the multi to 40x and vcore 1.12! How is that possible?Is there some other settings I'm just missing here? Do I really need all those other special settings?edit: did some more testing but have concerns...44 + 1.30 BSOD error 12444 + 1.32 BSOD error 124(and just for kicks)45 + auto BSOD error 10140 + 1.30 still shows alright with P95 stress test but the vcore on CPUz and ET6 drops like a brick under load. Set in bios to 1.30, shows 1.284 idle (cpuz/et6), and amazingly 1.236 under load!!! That's not right lol! My voltage was rock solid two weeks ago at 45x and 1.34v. Why all this drop stuff? Do I need LLC enabled?

Maybe the cpu damage (over voltage) or the motherboard.

I suppose it's possible, but unlikely considering most people run much higher vcore than I was...

BSOD 124 is memory related. Bump your QPI/VTT.

Yeah, I'm a bit confused about this one - most sites state the 124 error WAS qpi/vtt related but now is vcore related. Also from the various guides most say don't touch the qpi/vtt for low clocks below 4/4.5. So if I bumped the qpi it would just be a tiny tiny bit right? Default is 1.05, and Corey recommended 1.12 - and that's what I originally ran for about the week and a half until the BSODs.But overclock.net seems to agree with you!"0X00000050 << Incorrect Memory Timing/Freq or Uncore Multi0X00000124 << Incorrect QPI/Vtt Voltage (To Much/Not Enough)0X00000101 << Not enough Vcore Voltage0X00000109 << Not enough or too Much memory voltage"As an update I enabled LLC and the vcore is much much more stable now. Out of stupidity I neglected to log my settings from weeks ago right before I started getting those BSOD's. I may have enabled LLC at that time. Either way it's ON now.

Yeah, I'm a bit confused about this one - most sites state the 124 error WAS qpi/vtt related but now is vcore related. Also from the various guides most say don't touch the qpi/vtt for low clocks below 4/4.5. So if I bumped the qpi it would just be a tiny tiny bit right? Default is 1.05, and Corey recommended 1.12 - and that's what I originally ran for about the week and a half until the BSODs.But overclock.net seems to agree with you!"0X00000050 << Incorrect Memory Timing/Freq or Uncore Multi0X00000124 << Incorrect QPI/Vtt Voltage (To Much/Not Enough)0X00000101 << Not enough Vcore Voltage0X00000109 << Not enough or too Much memory voltage"As an update I enabled LLC and the vcore is much much more stable now. Out of stupidity I neglected to log my settings from weeks ago right before I started getting those BSOD's. I may have enabled LLC at that time. Either way it's ON now.

124 on Sandy Bridge is mainly Vcore too low as far as I recall. In my experience you will definitely need LLC for 4.5Ghz. Its just a question of using the minimum you can get away with so as to keep the volts as low as possible.

124 on Sandy Bridge is mainly Vcore too low as far as I recall. In my experience you will definitely need LLC for 4.5Ghz. Its just a question of using the minimum you can get away with so as to keep the volts as low as possible.

Yeah I tried the same settings as bit-tech used for their 4.5 GHz OC with my identical board.http://www.bit-tech.net/hardware/cpus/2011/01/07/how-to-overclock-the-intel-core-i5-2500k/4BSOD with a 101 (needs more vcore right?) error right after boot into Windows:45x multi1.3 vcore1.12 qpivtt1.135 system agent voltageIt sucks trying to figure this stuff out. Say I only play around with those four settings, still practically endless possibilities for error Ugh... so for now I'm back at 40x multi, 1.3v, LLC enabled.

Ryan the Vcore you set in BIOS doesn't mean anything at all. It's full load Vcore what matters. Personally I like my LLC as high as it can be, and then adjust my BIOS Vcore to have it where I need it to be at FULL LOAD for it to be stable.Enable PLL overvoltage too

Ryan the Vcore you set in BIOS doesn't mean anything at all. It's full load Vcore what matters. Personally I like my LLC as high as it can be, and then adjust my BIOS Vcore to have it where I need it to be at FULL LOAD for it to be stable.Enable PLL overvoltage too

I only have one setting for LLC, enabled lol. There's not different levels on the UD4.It must be a mixture of QPI and VCORE, because I've gone through a bunch of settings at 45x multiplier and all of them give me a BSOD error 124/101 ughRegarding the PLL overvoltage... there's no setting for enabled/disabled, just a number that I'd enter. Default is 1.80 I think.

You definitely want LLC enabled. Like the table I posted a couple days ago, LLC enabled gets you the voltage you specified in the bios almost exactly. LLC disabled is going to undershoot by quite a bit, just as you saw for yourself.As with your board and any other, you want the LLC setting that achieves the same voltage at load as what you set in the bios (or as close to it as possible).Have you tried different PLL voltages, like 1.70 or 1.72?

Which version of BIOS you are using? I would suggest trying changing the performance setting in memory options from turbo to standard.

f3bThis is the odd thing - Windows wouldn't boot the first time I tried to manually set my RAM. The Corsair stuff I have should run (factory spec) 1866mhz, 9 10 9 27 2T. If I put those settings in PC doesn't like it. But when I set to XMP profile1 it inserts everything correctly. Seems to be most stable. It's odd because all my last builds I always set the memory manually.

You definitely want LLC enabled. Like the table I posted a couple days ago, LLC enabled gets you the voltage you specified in the bios almost exactly. LLC disabled is going to undershoot by quite a bit, just as you saw for yourself.As with your board and any other, you want the LLC setting that achieves the same voltage at load as what you set in the bios (or as close to it as possible).Have you tried different PLL voltages, like 1.70 or 1.72?

LLC is enabled with my 4GHz clock.I haven't tried a different PLL. I'm not really sure about what PLL even does. I was hoping to KISS as long as possible hehe. My AMD3700 back in the day was easier than this and the multiplier was locked pfffff!

I´m at 4.6 Ghz stable with the i5 2500K and these settings:It´s the Asus P8P67 EFI Bios...AI Overclock Tuner: ManualBLCK Freq: 100.00Turbo Ratio: Enabled (All Cores)By All Cores: 46Internal PLL OverVoltage: EnabledMem Freq: (AS PER YOUR RAM)EPU Power Saving: DisabledLoad-Line Calibration: RegularVRM Freq: Manual Set to 350Phase Control: ExtremeDuty Contorl: ExtremeCPU Current Capability: 100%CPU OverVoltage: Offset ModeCPU Offset: + 0.060DRAM Voltage: (AS PER YOUR RAM)VCCSA Voltage: AutoVCCIO Voltage: AutoCPU PLL Voltage: AutoPCH Voltage: AutoCPU Spread Spectrum: DisabledCPU Ratio: AutoAdditional Turbo Voltage: +0.012 (start with +0.012, you may want to increase it)Intel Adaptive Thermal Monitor: EnabledIntel Virtualization: DisabledIntel SpeedStep: EnabledTurbo Mode: EnabledCPU C1E, C3, C6: EnabledWas at 4.8 Ghz for some time, but reducing the O´clock made FSX more stable...

It's a Seasonic (very high quality), 60A+ on the 12v rail (plenty of power) - I'm not saying it isn't the PSU, but I am saying it's a quality well-known brand. Really 750w is plenty for my system. If I were running dual GTX 580's I would be concerned. Most people buy way too much of a PSU for their system.Thanks for the error codes, I had a copy of that saved to my desktop. If I had to guess I'd say it was a vcore issue.1) I set RAM to XMP profile1 (which was set before), manually setting everything seems to give me problems2) Will run Memtest boot cd before I go to work today

I have the same configuration running at 4200 on a 620W supply so I doubt (but not sure) that your PS is the problem.Happy landings...

I´m at 4.6 Ghz stable with the i5 2500K and these settings:It´s the Asus P8P67 EFI Bios...Was at 4.8 Ghz for some time, but reducing the O´clock made FSX more stable...

Thanks, I do appreciate the template but the fact that I've got a different board doesn't really help hehe.On a positive note, I've got the 4GHz OC "somewhat" stable. I've only tested with P95, but it ran for 10+ hrs without any errors. Perhaps 4GHz is the most I'll get, and maybe the uk guy is right - I burned something up running 1.34... FSX performs much better at 4 then 3.3GHz (even with turbo) so if that's what I get - that is what I get <_<

There's no freaking way you burned anything up at 1.34v. People have juiced these chips with 1.6v and above (not a very good idea) and come away without any damage. However, if 4.0GHz is all you can get stable then I would seriously take that back and exchange it.

There's no freaking way you burned anything up at 1.34v. People have juiced these chips with 1.6v and above (not a very good idea) and come away without any damage. However, if 4.0GHz is all you can get stable then I would seriously take that back and exchange it.

+1. Never heard of any one burning their chip at that voltage and that is within intel spec. Poor oc'ing 2500/2600's are maxing at 4.5....something weird if you cannot get stable at 4.5 with 1.36 or so.... I would take it back too...settling on 4.0 seems a little crap...

+1. Never heard of any one burning their chip at that voltage and that is within intel spec. Poor oc'ing 2500/2600's are maxing at 4.5....something weird if you cannot get stable at 4.5 with 1.36 or so.... I would take it back too...settling on 4.0 seems a little crap...

Pretty sure you can't "take it back" once you've voided the warranty lol...It's not worth the hassle, take the cooler off, wait a week for the RMA (if possible), wait another week to get a new CPU (and get some AS5 cause I'm out hehe), put it back on and hope it works at 4.5 - bah....It's probably just a setting I've overlooked. I haven't cleared CMOS at all, maybe I should do that. What effect on bios and or my PC will that have?

4GHz is plenty for anything you want to do on a PC.

Everything except a poorly coded FSX :LMAO:On another note... I decided to give it a try again. My plan was to test for a suitable vcore at 45x. Starting with 1.31. Windows booted but BSOD within 2 minutes. Not only that but it was a PITA to get back into BIOS. PC kept restarting on it's own (like an infinite loop), and finally after a few loops I was able to get back to BIOS but it warned me that previous overclock settings cause hardware instability and some settings won't be set like they were. It appeared to load the optimized defaults automatically. I guess I can thank the GB backup bios for that. Note to self, next time either buy a dual bios board OR get a mobo with a freaking clear cmos switch LOL!One more thing I just thought of. I plug my entire system (minus monitor) into a large battery backup device:http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=770423&CatId=234It will hold the load of a power failure (we've had 3 bumps this month alone) but sometimes I wonder if it's a factor in this mess.