OCUK Sandy Bridge, SB-E and Ivy Bridge 5GHZ Club

Thanks 1day. Trying to get > 3200 on the custom PC benchmark but the encoding section seems to just eat vcore! I've made it about half way at 1.57 @ 5.3 a few times however it just doesn't want to finish. I'm not really sure if I want to push any further on high end water as I like my 24/7 and don't want to risk degradation.

Has anyone here suffered degradation?
 
This is my last try, 5.3 !!

Had to go to 1.55v.

Tried 5.4 & ran the volts up to 1.65, got to the windows screen then it just hung (no BSOD though), definitly not trying higher than 1.65.

Back to 4.7 for 24/7 running at 1.325.

53.jpg
 
There are a number of factors that determine a 'good' Super Pi 1 mil time. The main one is CPU core speed of course. But when you get to the top 1% it comes down to other factors. OS, ram, number of active services and so on. You do have to understand we are talking hundreds of seconds here in difference.

There is a kind of easy way to check how efficient your run is. Multiply the time taken by the core speed. That is called the PP index.


Hope I got the maths right. :D
 
Thanks 1Day, would i be better to do a fresh install of win7, only install the m/board drivers & Super PI, CPUZ & possibly coretemp. Would this increase my Super PI score ?

Also should i try & change any of the following, or would i be at the limit of my chip :-

DRAM 1.5
VCCSA 0.925 (on auto at the mo)
VCCIO 1.053 (on auto at the mo)
CPU PLL 1.8
PCH 1.050

I tried 5.400, up to 1.65v on the cpu & it would only start the windows screen then hang. Would this mean a bottleneck in the memory as it didn't BSOD ?
 
Last edited:
OS - XP pro SP2 or SP3
No drivers - none at all
Disable as many services as you can without crashing your system +- 14 left
Super Pi shortcut on desktop nothing else.

Run x16 twice
Run x1mil
Use your keyboard to do all this
Ram as tight as can be.


What was the code on your BSOD? That will tell you what is needed.
 
1Day said:
OS - XP pro SP2 or SP3
No drivers - none at all
Disable as many services as you can without crashing your system +- 14 left
Super Pi shortcut on desktop nothing else.

Run x16 twice
Run x1mil
Use your keyboard to do all this
Ram as tight as can be.


What was the code on your BSOD? That will tell you what is needed.
Click to expand...


1Day, thanks for the reply, wiil try the reinstall hopefully tonight or tomorrow night, i had been using an old h/d with win 7 on it, with everything i could think off, deleted off it. The only xp i have is xp media center edition, will that do or should i just try win 7 ?

my ram is set to '9 9 9 24 1t' in the bios, should i change this ?

Can't remember what the BSOD code was, i think i seen 80, but not sure, sometimes all it said at the bottom was 'dumping memory to ...........' i will make a note of it next time.

Is there somewhere on the internet i can get the code definitions ?

thanks again, sorry for all the questions, seen your posts on the LN setup, just awsome !!!!!
 
Last edited:
Oma-Lan-DP said:
[Is there somewhere on the internet i can get the code definitions ?
!
Click to expand...

Enable trust account please


BSOD Error codes and what they mean:
0X00000050 << Incorrect Memory Timing/Freq or Uncore Multi
0X00000124 << Incorrect QPI/Vtt Voltage (To Much/Not Enough)
0X00000101 << Not enough Vcore Voltage
Click to expand...


BSOD codes for overclocking
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
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
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom