Hello to all

I/m trying to overclock the following system:

 

SB 2700K

NOCTUA NH-D14

2x4GiB GSkill Ares 1866 9-10-9-28 (currently @ 1600 11-11-11-28 while CPU OC tests)

ASUSP8Z77-V LE PLUS

 

I consider that system is stable @4.2Ghz - Vcore 1.280 with Prime95 for 14 hours.

1 click more at 4.3Ghz and BIOS Vcore 1.300 I still have Prime95 failing in less than 1 hour

I find Vcore 1.300 @ 4.3 a bit high

 

You can see my BIOS settings screenshots , realtemp and CPUz in Windows here (while Prime95)

If you have any Ideas to help you 're welcome.

 

P.S.: I know that FSX is not stressign CPU that much.

Firstly I would make sure your BIOS is updated to at least v1708 updating from v1504 allowed me to go from 4.7 to 4.8.

 

These are the settings that work for me on my P8Z77-V Pro

 

BIOS Screen #1

AI Overclock Tuner - There is no need to lower your memory timings if you are just overclocking by the multiplier, I would set to XMP to auto populate the correct settings.

Internal PLL - I have mine set to Auto rather than Disabled.

 

BIOS Screen #2

At some point I would reccomend using voltage offset rather than a fixed voltage but for the time being you may as well stick with fixed until you know what you need.

 

BIOS Screen #3

CPU Ratio - Just leave this at Auto it will take what you set in Screen #1

 

BIOS Screen #4

CPU Load Line Calibration - I have this set to Ultra High, it allows additional voltage through if your CPU needs it, keep an eye on voltages via CPUz.

CPU Voltage Frequency - I have this set to Manual with a value of 350

CPU Power Phase Control - I have this set to Extreme

CPU Power Duty Control - I have this set to Extreme

CPU Current Capability - I have this set to 140%

CPU Power Thremal Control - I have this set to 130

DRAM Current Capability - I have this set to 130

 

BIOS Screen #5 / #6

I know folks say that enabling HT restricts your OC potential leads to higher temps and requires higher voltages, personaly I have not found this to be the case (OK 0.008v more). I have HT enabled and use the AffinityMask setting in FSX.cfg to restrict FSX to use physical cores, leaving HT enabled for other applications that may be able to use it.

Execute Disable Bit - I have this Enabled

 

BIOS Screen #7

CPU Ratio - Just leave this at Auto it will take what you set in Screen #1

CPU C1E - I have this set to Enabled

 

/Edit - Regarding voltages, I understand that on Sandy Bridge chips you should avoid going past 1.425v and not much above 80c on any core when stress testing, so you have some more headroom and I wouldn't get too hung up on voltages until you get to these limits.

Here you go, Sam; There are three pdf's in the folder, showing settings which work for the 2600K and the 2700K. 1.30 is low, the SB can easily go to 1.4 without scaring the pants off you. 1.385 is where mine sits at this moment, and shows as red when setting it. Don't be alarmed. Also DON'T ever set this voltage as "Auto".

 

You might also try setting the memory to 1600 and 8.8.8.24 1T.

 

All the Best,

Gentlemen,

Thanks for your comments and assistance. I will try your recommendations and I will give feedback.

.

Here you go, Sam; There are three pdf's in the folder, showing settings which work for the 2600K and the 2700K. 1.30 is low, the SB can easily go to 1.4 without scaring the pants off you. 1.385 is where mine sits at this moment, and shows as red when setting it. Don't be alarmed. Also DON'T ever set this voltage as "Auto".

 

 

I have a dumb cpu... but my vcore is actually set to auto because ANY OTHER SETTING causes a failed P95/IBT. My 2500K is probably the only on on the planet at 1.356v @ 4.4GHz. I wouldn't recommend auto either fwiw lol!

Where is the Vcore setting located Paul. When are you online for a chat? Wayne. AEST .

Online right now, Wayne, at the ts3.DigitalThemePark.com - New York 21 Club channel...

Here you go, Sam; There are three pdf's in the folder, showing settings which work for the 2600K and the 2700K. 1.30 is low, the SB can easily go to 1.4 without scaring the pants off you. 1.385 is where mine sits at this moment, and shows as red when setting it. Don't be alarmed. Also DON'T ever set this voltage as "Auto".

 

Thanks for posting those guides Paul. I saved them and will use them when I finish my new 2700k build.

Thanks for the guides Paul. I'm using the 4.8Ghz now and just passed 2 hours on Prime. And my voltage is a lot lower than it was!!

 

You can see the system I am running at, is very stable at 4.8Ghz OC offset at 1.38 vCore at max load. Very stable means 10 hours so far, of straight Far Cry 3 and no BSOD's. With FSX I was stable at simply 1.36 vCore, maybe even a little lower if I really tweaked. Max temps between 50-60.

 

Love SB at 4.8, definitely a sweet spot.

 

Let me know if you want more specifics, since you have similar setup.

I have read some guides provided - were very helpful indeed - and reached a 'relatively stable' 4.6Ghz @ 1360Vcore overclock.

You can see bios settings, prime95 options and CPU-z shots here.

RAM timing are by manufacturer GSKILL ARES F3-1866C9D-8GAB 33mm height, 9-10-9-28 2N

 

I say relatively because, I had a plan to run prime95 with 'In-place-FFT' option for 12 to 14 hours. After about 4 hours Worker 4 in prime95 stopped working because of a rounding error. I didn't noticed and I discovered it after 10 hours. All other workers (1,2 and 3) were still running.

 

I consider

1) increasing vcore to 1.365, or

2) leave vcore at 1.360 and set CPU Load line calibration from current HIGH=50% to VERYHIGH=75%

and rerun prime95 with same setting or IBT with high amounf of memory (4096KB) for 12-14 hours

Either option will increase voltage to the CPU and potentially lead to a more stable / higher overclock.

 

If I can say - I'm not sure why you appear to be so hung up on voltage unless your cooling isn't coping, in my opinion you are imposing a needless limit on your overclocking, you chip should be capable of 4.8GHz on voltages that are within its tolerances.

 

Proving your system is prime stable for 14 hours just proves your system is stable when running prime, it doesn't prove your system is stable for any other software. There was a recent post on this forum by someone whose system was prime stable but kept falling over in FSX until they upped their voltage by a notch.

Agreed, I ran AIDA64, IBT, and Prime 95 (custom and blend for 30 min , good enough) with no problems, then 5 hrs into FC3 and bsod 124. Had to bump vcore a bit. Those test don't mean much to me honestly.

 

In my case, I can run fsx much lower vcore with no bsod ever, yet fail prime.

I know that FSX is not 'torturing' CPU that much as Prime, or IBT. The 12 or 14 hours equates to a Long Haul flight performed with a B777, MD11 or a B744.

On the other hand I could reduce my VCore, install PMDG MD11X and B747X and let them fly for 12 hours - unless BSOD would come first!- in circles at 4000ft with clouds (ala FSmark11) .

The reason I keep my FSX SP2 installation 'clean', - no addons - is that I want to run FSXMark11 and share some results.

I know that FSX is not 'torturing' CPU that much as Prime, or IBT. The 12 or 14 hours equates to a Long Haul flight performed with a B777, MD11 or a B744.

On the other hand I could reduce my VCore, install PMDG MD11X and B747X and let them fly for 12 hours - unless BSOD would come first!- in circles at 4000ft with clouds (ala FSmark11) .

The reason I keep my FSX SP2 installation 'clean', - no addons - is that I want to run FSXMark11 and share some results.

 

What I tried to explain previously is that although Prime and IBT are good indicators of system stability 12 to 14 hours of Prime does not equate to 12 to 14 hours of FSX because they both use the CPU in very different ways. The only way to prove that FSX is stable over 12 to 14 hours is to use FSX for that period of time and see if you run into problems. FSXMark is probably your best solution and you could always bump up the textures and autogen before launching the flight to make sure you are really taxing the system.