• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

~~~~~IMPORTANT SANDYBRIDGE OC INFO: Voltages & OC Guide!!~~~~~

DrSteve, as you're using a watercooling setup, temps shouldn't be an issue, so it's all down to voltage now.

My 2500k requires 1.38v in my BIOS at 4.6Ghz using LLC Level 2 (So pretty much no vdroop). If you're getting vdroop then set your Vcore so load voltage is around 1.38v and test again.
 
Seem to be getting the opposite actually. Getting overvolting jumps with load in cpuz. I see a few more reports of this in the forums too.
Knocked the core up another notch and I'll see what happens.
 
Trying to get 4.6 stable at the minute and it's slowly getting there. Taking me a while to get my brain round all these new bios settings.

I've left vcore at 1.295 in bios, LLC on auto, vdroop control I get better results (ie less v and more stability) for some strange reason switching that to auto.

Im also getting better results using the per core turbo multiplier function in "CPU features" instead of adjusting the multiplier through the standard MSI overclocking menu, thats left at default of 34. Its taking less vcore to get a stable oc and all the power saving features appear to work fine when its not under max load.

Definetly lower load vcore for a 100% stable 4.6ghz, 1.344v. Amazingly sharp gradient on the vcore though going to 4.7 - at least 1.392 and im not sure thats fully stable. Worth having a play with those turbo settings instead of the standard menu multiplier - just make sure you switch the short duration max wattage to around 200w if power saving is set to custom.

EDIT: oh and i've noticed droop on the PLL voltage too so thats set at 1.83 in bios to compensate, bought me stability once I got to 4.6.
 
Last edited:
Happy with the GD65, Took the UD7 back today, got the GD65 really happy with this board fantastic for the price. Although i could hit 4.8 / 5.1 GHz on the UD7. This GD65 is not too shabby im currently @ 4.6GHz on 1.3vcore i keep taking it down bit by bit.

lowervcore.jpg



It is 4.6GHz does not show it on idle



I have also worked out some BSOD CODES.

0x124 = add / remove vcore or qpi / vtt voltage
0x101 = add more vcore
0x50 = ram timing / frequency add more vcore
0x1e = add more vcore
0xd1 = add qpi / vtt voltage
0x9c = qpi / vtt likely but increasing vcore has sometimes curred this.
0x109 = add ddr3 voltage
0x0a = add qpi / vtt voltage.




Keep tweaking, boring after a while i know!



.
 
Last edited:
weird stuff happening with my 4.5ghz at 1.45vcore - gflops in linx is going down each run!

That implies you're being downlcocked to save your CPU from imminent doom. When you run Linx have CPU-Z open and make sure the CPU speed is staying at 4.5Ghz constant.

Also, DrSteve, I'm not aware of how the UEFI on the MSI boards work but have you got the latest version on there (It seems to help in the case of ASUS users so maybe the same rings true for MSI users) and tried LLC/Vdroop at low instead?

Edit: Great post rchads89, if I see another BSOD (not planning to), I'll be sure to see if the codes match up. Thanks for that, and I can only imagine you've seen a LOT of blue recently to get that info!
 
That implies you're being downlcocked to save your CPU from imminent doom.

Hope im not teaching to suck eggs, but Max3, if you've got CPU-z running and at the same time the frequency is scaling back disable "overspeed protection" but really watch those voltages, wouldnt be happy at over 1.4v load.

DrSteve - dont worry about slight overvoltage jumps if you've got power saving, PLL overvoltage/LLC and EIST features enabled, im happy jumping from lower to higher vcore under load especially with the former enabled, means im at lower voltage (1.288, not ideal i know) for 1.6ghz idle and only jumps to required voltage (1.344) under load at 4.6ghz

For some reason with all voltages at auto and just setting turbo for 1-4 cores all at 4.2 rather than the default 1 core 3.8, 2 cores 3.7, 3 cores 3.6 and 4 cores 3.5 - it will go from 0.908v @ 1.6ghz to 1.212v @ 4.2 all cores (a jump of 0.3v+ compared to 0.04-0.06v when I set manually any voltage in bios, despite what combination of turbo/power saving features I enable). It has/still is, taking a while to get my head around this architechture...
 
Last edited:
I'm now at 4.6GHz with offset voltage enabled and offset set to Auto.

The advantage to this seems to be that the undervolting when in speedstep still works. 4.6GHz seems to give 1.336 - 1.37V which is a fair bit of fluctuation, but it appears stable.

I tried 4.7 but it instantly crashed, I shall try again with PLL Overvolt enabled in a bit.
 
P8P67 (1053), 2500K, XMS3.

I didn't really check the BSOD code, as I have had it stable at the same speed with another configuration, so I just went back to that.
 
P8P67 (1053), 2500K, XMS3.

I didn't really check the BSOD code, as I have had it stable at the same speed with another configuration, so I just went back to that.

Ok have you overclocked your ram yet?

Watch out for these codes here :

0x124 = add / remove vcore or qpi / vtt voltage
0x101 = add more vcore
0x50 = ram timing / frequency add more vcore
0x1e = add more vcore
0xd1 = add qpi / vtt voltage
0x9c = qpi / vtt likely but increasing vcore has sometimes curred this.
0x109 = add ddr3 voltage
0x0a = add qpi / vtt voltage.


Write them down or print them off and you can at least tackle the BSOD better.
 
Just like to point out aswell guys, DO NOT use Intel burn test or linX to test for stability as they are using OUT OF DATE linpacks. Use prime95 OR you can update the linpacks and replace within there folders here :

http://software.intel.com/en-us/articles/intel-math-kernel-library-linpack-download/




I didn't realise this intill i ran prime95 and i was getting BSOD, I just added abit more vcore which then made me stable again with prime
 
Right just go my replacement for my msi board in the Asus P8P67 pro. Settings are a lot different to OC with than the msi board. What am I missing though, got targeted Ram speed of 1600 but only getting 1333 in windows looking at CPUz (latest version).
 
Ergh I don't get it. I set ram to run at 1600 and it runs at 1333, but I set it at 1866 and it runs at 1866. Guess I will just see if this ram speed is stable.
 
Back
Top Bottom