Newbie and overclocking 2500k

Frank31uk

Frank31uk

Frank31uk

Associate
Joined
19 Jun 2011
Posts
24
Hi guys,

Im a newbie to the forum so first off hello ;)

Im basicly inexperienced with overclocking and need some guidance to wether im OC my new 2500k system correctly.

Ok, Ive just had my new SB build up and running for a few days and have read some guides detailing how to OC the 2500k and setting RAM timings.

First off I noticed my RipjawsX memory running on these timings :-

9-9-9-28 with command rate set to 1T @ 1.65v

I changed these timings in accordance to the timings on my memory stick apart from I have left the command rate set at 1T instead of 2T because I read 1T gives better performance should it work on that setting. So I now have them running at :-

8-8-8-24 1T @ 1.5v and completely stable

Next I changed just the Multiplier leaving everything else set to default in my P8P67 BIOS. I first went to 4Ghz, then 4.2, 4.3..etc just through use of Multiplier only.

For my Overclock I am using Prime95, CPU-Z, Realtemp and Coretemp.

So here are my OC results using Blend test in Prime95 for 30 mins each...
---------------------------------------------------------------------------------
4Ghz @ 1.256v = Max temp 59c
4.2Ghz @ 1.288v = Max temp 62c
4.3Ghz @ 1.296v = Max temp 63c
4.4Ghz @ 1.328v = Max temp 65c

After doing some more research I discovered it would be better to enter my voltage manually in the BIOS as opposed to leaving it set as AUTO.
So here is my result today with using a Manual voltage of 1.280v in BIOS...

4.5Ghz @ 1.280v = Max temp 65c (Ambient 19c)

Ive just did another Prime95 test for 35mins on this lower voltage and so far so good. I will attempt lowering the voltage to 1.275v next and continue until I get a BSOD or something. When I get it to the lowest working voltage I will be happy to keep my PC at 4.5Ghz.

Am I doing everything correctly guys and will using my PC at 4.5Ghz on this voltage be safe enough for daily usage ? AFAIK some people go over 1.4v+ and have no issues.

Sry this was a long post but it`s my first one so further posts will be shorter, lol :D

EDIT - I have a screenshot of my latest OC...

http://img689.imageshack.us/img689/3269/45ghzmax63degrees1280v3.jpg
 
Last edited:
Frank31uk said:
So I need to make sure my memory is error free before lowering my vcore then. What is the reason for this?
Click to expand...

No reason at all....

If you're not having RAM problems there's no reason to run MemTest.

You lower the CPU voltage until the system becomes unstable and then put it back up a bit.

Your voltages and temperatures appear pretty reasonable though it doesn't hurt to get them as low as you can.
 
Last edited:
No reason at all....
Click to expand...

Riiight. So it`s just an optional test I could do to check for memory stability and has no effect on the lowering of my vcore. I guess that is what you meant Koooowweeee. Thanks for your replys guys. Appreciated

Your voltages and temperatures appear pretty reasonable though it doesn't hurt to get them as low as you can.
Click to expand...

Thats billiant! I am using the Hyper 212+ btw. I understand it that as long as your under 80c it should be fine right.
 
if your getting bsod then it could be because of the ram.

set your ram to stock clock you cpu and test it make sure that is ok then start on your ram
 
if your getting bsod then it could be because of the ram.
Click to expand...

Thats a good point.

I just this sec had my 1st BSOD which had some error like 0x000234 after running Prime.

I have now upped my voltage back to 1.280v.

Guess I could put back my memory to stock if I BSOD again...
 
koooowweeee said:
if your getting bsod then it could be because of the ram.

set your ram to stock clock you cpu and test it make sure that is ok then start on your ram
Click to expand...

The OP isn't getting any BSOD's.

If they get a BSOD after lowering the CPU voltage that has nothing to do with the RAM they just need to increase the CPU voltage again.

Like above.
 
I just BSOD again at 1.280v which was working stable on 4.5Ghz. I noted the error and it`s 0x00000124. Ive now upped the voltage to 1.290v. Gonna see what happens....
 
Last edited:
I was thinking you should increase the RAM voltage a touch.

I'm not sure if you've done that or if you've increased the CPU voltage.
Click to expand...

Sry I didnt make that clear. I have raised the CPU voltage now to 1.290v and have Prime running again. Not touched the RAM yet.

Should I set the memory back to 2T now and try it with CPU voltage at 1.280 again do you think..?

I could then up the memory voltage if that failed leaving my vcore as 1.280 right
 
Last edited:
Frank31uk said:
Sry I didnt make that clear. I have raised the CPU voltage now to 1.290v and have Prime running again. Not touched the RAM yet.
Click to expand...

What you should do is change the setting on one thing at a time.

Set your RAM back to the safe settings you had before.

Now if you get any errors you know it's down to the CPU overclock.

Once the CPU overclock is stable you can then change the RAM settings.

Then if you get any errors you know it's down to the RAM settings.

By overclocking the CPU and changing the RAM settings at the same time you don't know which one is causing the error.
 
The OverClockers BSOD code list
BSOD codes for overclocking
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
 
You must log in or register to reply here.
Back
Top Bottom