Official Seven Forums Overclock Leader boards

[essenbe]

Too hot to be Ocing right now i'll give it a go soon when the ac is on

I have been enjoying the Intel experience

Won't be long til winter now mate, then the proper overclocking can begin!

Here's a snip of the temps I get for the first few mins of switching the PC on in the cabin in the winter. It's so cold in there and stays that way for a good 30 mins until my little heater finally starts to warm it through.

0C is 32F. We have that in Florida.

Look at his core temp picks in that post, it reads 0*C

http://www.sevenforums.com/pc-custo...s-overclock-leader-boards-96.html#post2521852

He's in a cabin outside without the heat on in that picture. I'd have to do it by remote desktop.

Earlier I posted some winsat scores of 31,000+ on the i5-4670K Haswell, 16GB GSkill which then dropped to under 28,000.
The system has transmogrified to a i7-4770K on an ASUS Z87-WS, work station board with a new set of the same RAM. These scores are even more shi**y, any ideas my friends?

View attachment 284654 View attachment 284653

View attachment 284655 View attachment 284656

Gary, best I can do for the moment Haswell Overclocking Thread [With Statistics] The discussions will teach a lot, but is a long read. Haswell seems to be quite different than Sandy/Ivy. Those 'rules' do not apply to Haswell. Right now, I think overclocking and BIOS settings is a work in progress, as with any new technology.

 

[Britton30]

What is the exact ram you are using Gary?

Sorry, I thought I put it in there.
Newegg.com - G.SKILL Sniper Series 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 2400 (PC3 19200) Desktop Memory Model F3-2400C11D-16GSR

Gary, best I can do for the moment Haswell Overclocking Thread [With Statistics] The discussions will teach a lot, but is a long read. Haswell seems to be quite different than Sandy/Ivy. Those 'rules' do not apply to Haswell. Right now, I think overclocking and BIOS settings is a work in progress, as with any new technology.

Thanks Steve, I'll try to read it, but every time I open a OCN page the damn page locks up...all/any of them.

 

[pillainp]

Right:

My problems with OC'ing using the built in OC profiles are as follows:

I am repeatedly getting BSOD's when OC'ing above 4.4 GHz. All or most of them seem to indicate that VCore is too low, or that VTT/QPI need to be increased. I have these values set at the defaults applied by the profile. CPU VCore is set by the profile to a fixed value for each OC stage, but I am considering shifting to Offset Mode.

Now my questions are:

1) At 4.4GHz, the automatically applied VCore is 1.168V, and AIDA shows the idle VID as 1.2560V. When running IBT (this is the highest speed I can get it to run at without crashing, currently), VID rises to 1.2660V max (range under load 1.2510-1.2660).
--- What is my Offset and how do I calculate it.

2) What value should I set for VTT/QPI? This board has two values for VTT (VTTCPU1 and VTTCPU2), which may or may not relate to the 2 RAM Channels.

3) What should I set my LLC value to?

BTW, these are the BSOD codes for Ivy Bridge:

BSOD Codes for LGA 1155 Ivy Bridge
0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT... have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

 

[Dude]

Pillainp Im on my phone so its hard to browse the thread but Kelly posted a great explanation to calculate offset. Steve did too so go back through this threaadd and the post your oc one and you should find it.

 

[essenbe]

pillainp, This is the guide Dude was refering to. It is for Asus motherboards, but the principals are the same. No matter what board, the CPU works the same, just different boards have different termonology for the same thing (which is rediculous). But, a lot of the terms and the options in bios are explained. Ivy Bridge Overclocking Guide#

Also, it is generally a bad idea to use the software overclocking. Most overclockers will agree to that. Do it manually, and you will know and be able to learn the bios and the effect each setting has. Software, which are the built in profiles, are usually just good guesses at what it will take, and are usually wrong as you have found out. Plus, you have no idea what was changed or what it was changed to.

 

[Solarstarshines]

Earlier I posted some winsat scores of 31,000+ on the i5-4670K Haswell, 16GB GSkill which then dropped to under 28,000.
The system has transmogrified to a i7-4770K on an ASUS Z87-WS, work station board with a new set of the same RAM. These scores are even more shi**y, any ideas my friends?

View attachment 284654 View attachment 284653

View attachment 284655 View attachment 284656

With all the issues you have been having I am glad I went the other way :shock:

Maybe Haswell is a bust I don't know but I had my share of issues but now there gone

Can't imagine what is going on the settings are totally different

 

[Britton30]

Best the i7 4770K can do for me. HT is disabled, is that what most of you guys do?



I tend to agree Tommy, the do keep issuing updated UEFI/BIOS for Haswell boards.

 

[essenbe]

I don't disable hyper threading. I do think Paul did on his latest run, but am not sure.

 

[paulpicks21]

Yeah anything over 5GHz I disabled hyperthreading iirc.

 

[paulpicks21]

Best the i7 4770K can do for me. HT is disabled, is that what most of you guys do?

View attachment 284738

I tend to agree Tommy, the do keep issuing updated UEFI/BIOS for Haswell boards.

That is actually very good Gary, I must admit I wasn't sure if most Haswells would go that high.

You are getting through cpu's like I have hot dinners, you are taking over the leaderboards lol.

Updated.

 

[kbrady1979]

Looks like you got a winner Gary!

 

[Solarstarshines]

Best the i7 4770K can do for me. HT is disabled, is that what most of you guys do?

View attachment 284738

I tend to agree Tommy, the do keep issuing updated UEFI/BIOS for Haswell boards.

I never did it is suggested it stays on but like paul said anything over 5 ghz it should be taken off

 

[Britton30]

Thanks guys for the advice. Well, my damn ASUS Z87-WS took a dump now!
I was running Furmark and the GPU LED lit up as bright as the sun and smoked. Board won't even post, the BIOS Flashback light keeps blinking even without pushing it.

I think it's time to try Ivy out, suggestions welcome, lol.

 

[Solarstarshines]

Thanks guys for the advice. Well, my damn ASUS Z87-WS took a dump now!
I was running Furmark and the GPU LED lit up as bright as the sun and smoked. Board won't even post, the BIOS Flashback light keeps blinking even without pushing it.

I think it's time to try Ivy out, suggestions welcome, lol.

I think it's time to get your money back and run Ivy Haswell seems to be a major issue

 

[NoN]

Right:

My problems with OC'ing using the built in OC profiles are as follows:

I am repeatedly getting BSOD's when OC'ing above 4.4 GHz. All or most of them seem to indicate that VCore is too low, or that VTT/QPI need to be increased. I have these values set at the defaults applied by the profile. CPU VCore is set by the profile to a fixed value for each OC stage, but I am considering shifting to Offset Mode.

Now my questions are:

1) At 4.4GHz, the automatically applied VCore is 1.168V, and AIDA shows the idle VID as 1.2560V. When running IBT (this is the highest speed I can get it to run at without crashing, currently), VID rises to 1.2660V max (range under load 1.2510-1.2660).
--- What is my Offset and how do I calculate it.

2) What value should I set for VTT/QPI? This board has two values for VTT (VTTCPU1 and VTTCPU2), which may or may not relate to the 2 RAM Channels.

3) What should I set my LLC value to?

BTW, these are the BSOD codes for Ivy Bridge:

BSOD Codes for LGA 1155 Ivy Bridge
0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT... have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

I've got a bit of the same problem...:sarc:

But i'm using "GPU Boost" with lucidlogix virtu MVP (iGpu + dGpu) , so i've to set aswell the iGpu load-line calibration to "high" for not getting Blue Screens and those warning "WHEA-Logger" eventID 19.

I'm now using Offset Mode (-) Cpu Offset voltage (0.020) at 4.2GHz, and the VCore CPU-Z is now 1.152V, CoreTemp shows VID 1.2260V.

Those value seems normal to me as it looks by the crash dump codes in screenshot, i was too low with Vcore.

The machine seems far more stable than when i didn't set the iGpu Load-line calibration to "High" => 110%, which increased the Vcore from 0.816V to 1.168V at 4.2MHz (Offset Mode (-) & Cpu Offset Voltage (0.005)).

I have now set at (0.020). i'll increase this value to 0.025, 0.030, 0.035....til it works stable.

I've no choices unless i get rid off multiple display in bios to low Vcore.

That's mean if i go above 4.2MHz, my Vcore will jump high and watts either than average but at least it doesn't crash! (i mean til the board will handle the load)

 

[Dude]

Thanks guys for the advice. Well, my damn ASUS Z87-WS took a dump now!
I was running Furmark and the GPU LED lit up as bright as the sun and smoked. Board won't even post, the BIOS Flashback light keeps blinking even without pushing it.

I think it's time to try Ivy out, suggestions welcome, lol.

Wow, sorry to hear that Gary Your Ivy rub=n will go smooth for you

 

[essenbe]

NoN, you mentioned WHEA Errors. Some people don't worry about them, others do. But if you would like to get an alert when you get one, this is a very good way to do it. Basically to get out of the WHEA errors, raise the Vcore. But to set up the alert, this is an excellent way to know when you get them, it will automatically put an alert on your screen.
WHEA Error Alert Guide (or "How I got out of WHEAville")

 

[paulpicks21]

Thanks guys for the advice. Well, my damn ASUS Z87-WS took a dump now!
I was running Furmark and the GPU LED lit up as bright as the sun and smoked. Board won't even post, the BIOS Flashback light keeps blinking even without pushing it.

I think it's time to try Ivy out, suggestions welcome, lol.

Sorry to hear that Gary

What happened to the Sabertooth? I didn't think you were changing that in the end.

You could try Ivy, obviously it would be the 3770k and a nice mobo, but if I was you then personally I would hold off just a few more days and try out the Ivy-E i7-4820K which is supposed to have a retail price of around $310 and a nice X79 board to go with it. (I know, I can hear you saying well they ain't out yet and it might be bad as they have not been tested, but with the luck you have been having it can't get any worse! And you might just like it).

Paul.

 

[kbrady1979]

Gary, did all 3 Haswell motherboards go bad?

 

[Britton30]

Well the Z87 Deluxe, Z87 Saber Tooth, and Z87-WS all went bad or didn't work right from the beginning, all returned with the CPUs.
I've went ahead and ordered a Z77 Saber Tooth and i7-3770K and I hope I have as much luck as you all have had with that combo.