Starting overclocking

[Clay]

I'm not sure if I remember this right but I think SoundX has posted 315. But I'm not sure if had them onna' divider or not. UTT-BH5 Some of those will do 260+ in nf4 1-1. And I blew mine up on the eve of gettin' my Opty!LOL.

[skinnie]

these are good old bh5..I'll get a 2x256kit of old bh5 just to play with

[Gothic Case]

Yep 2x256MB BH5 are very unexpensive... but it would be surelly nice to find some 2x512MB BH-5.. who has them won't sell, or already burnt them...

 

If I remeber correctly, LastViking got some BH-5 @ 310MHz 1.5-2-2-0 stable.... under some heavy cooling and extreme volts... just try to imagne what kind of sick bandwidth he would get from those sticks...

[skinnie]

2x512 were good if I had vmods on my board..and sell the tccd...I only want a 2x256 bh5 cuz they are unexpensive..good for benching and a good piece of collection..

well..the 1st round of exams finished..so I am getting started with the tccd and the IQYHA..for now just with the stock cooling with the tornado..the si97 only arrives friday...

[email protected] 3h prime stable..then I must turn off the computer cuz my mom was shouting at me..lol

edit: I only could boot @2.5-3-3-x 1t/2t no chance of 2.5-2-x-x or 2.5-3-x-x

[skinnie]

ppl what are +- the voltage for 2000mhz?I'm trying 250x8..to see where the instability comes form...

it's so stupid..I have the mems ont the two sltos further from cpu and so in the bios I put this in the rates: 5/11/1/10/5/11 is it right?i guess not because with this I cant even start memtest!!!and in auto it passes :S

[kitfit1]

At 2ghz somewhere around the 1.6v mark should be enough Skinnie. With your ram the two slots furthest from the cpu, 1/10,5/11,5/11.

[skinnie]

i'm using hellfire's rev3..my SI97 finally arrived...I'm priming @250x10 (only cpu mode ) @ about 5hours...so i'll have to shutdown to put the si97...

let the party begin

ppl is this psu http://www.lc-power.com/htm/products_detai...u_id=21&a_id=67 better than mine?

[skinnie]

ppl..I don't know what to do..@first when I test my mems @250(x7) in memtest they didn't get errors...but it was strange @prime blend it fails in about 2minutes..I pput 250x10 and run memtest...lots of errors :S

tried several things and became "stable" @vdd 1.8 vdim 2.8 and tdoe 5 all the other alphas auto..but now it seems that the proc isn't stable :S

what do I do?more vcore?I'm already @1.9...burn in?with what program?I use cpu burn in.

and plz answer..is this psu http://www.lc-power.com/htm/products..._id=21&a_id=67 better than mine?

edit: I ogt a pair of 2x256 OCZ PC3500 Limited Edition OLd School BH5 :) do 290 in nf4

[NEOAethyr]

Hey dude, back off the cpu multi.

 

Goto 8.5x, which is around 2125mhz.

For that should only need 1.45v vcore for.

If you need more, then by all means, you shuoold'nt need more then 1.65v absolute max.

 

From there, which everything getting less hot, and less cpu probs, and less pull from the cpu, it'll be easier on you.

 

Why you guys allways wanna max it out lol...

I mean from the get go.

 

You gotta start low and work your way up .

 

So work on an everyday use setting, something with the stock vcore for that cpu, not the bios stock, but your cpu's rated vcore.

 

 

Let it prime.

Once that's all settled, go up a multi or 2 until you reach around 10x or more.

Then lower it and go up the fsb.

 

If you have to, to get a feal for it.

Go down to 200mhz fsb, and try 12x and 12.5x.

To check the cpu...

 

 

This part is the hardest to explain...

When you get yourself into trouble, the system stability will go down the drain.

It will never recover.

I mean it could but...

It's the cmos, it gets corrupted somehow majorly.

 

This is the hard to explain part.

You have to clear the cmos.

Seems easy right?

Well it's not.

The cmos is finiky.

You may have to clea that sucker many times before it's right again.

So how do you tell it's corrupted?

Well...

 

Look for the vcore, or vmem, that's one sign.

If it's higher or lower then the bios'es stock, then it's a bad cmos after clear.

 

Other ways to tell are by jumping to something that's tight, like 266x8 maybe or whatever.

It may not boot right after a clear, but it should(just a possible example).

Well, clear it again and try that fsb setup again, it's supposed to boot.

It may be 250 in your case, stuff like that.

For example, you know it's memtest stable, and prime stable...(say it was).

Well it shoudl boot, but it does'nt.

Clear that cmos, don't even try forcing it, it'll be problematic in the long run.

For example you'll probably have some errors in s&m when there should be none.

That's how I've caught that one.

 

Sometimes, even if it seems all good form the get go, it may not be.

Ie the s&m errors.

Clear a few more times and they are gone, multble runs of s&m too.

I no longer bother on that though, I mean clearing to get stable.

I just ensure that stuf seems normal and I go ahead anyways.

 

As long as it boots, and as long as everythign itn eh bios setup seems normal, continue on.

 

Something I noted today.

Clearing the cmos and holding insert to boot does'nt clear the cmos as good on avg as compared to just clearing the cmos.

I dn why, like I would know...

I noticed it when modding spd's.

Holding insert 75% of the time allowed me to oot an invlaid spd, and everytime it had th ewrong stock vmem and vcore.

This would'nt happen everytime, but...

When not holding insert, it did it right the 1st time.

Not saying it will clear correctly 100% at all times this way, but it's got a betetr avg of doing it right.

That is, if you can boot initally without holding insert, some people can't.

 

 

 

A status update on my part.

Enabled the PLL, phase lock loop on both my sticks of memory.

Tested on my adata, before hand and never realized it.

It's ok.

The samsung I dn.

I will test with memtest and lower cas and such when I get my dvdrw back in, that should be good enough I would think, the rest needs testing at 280...

 

A PLL is somehting that checks and redoes phase..

Err...

Well, it monitors the crystals, the clock.

If it's off, it compensates and makes it correct.

There's a pll on the mobo for this, on the left hand sie of the mmeory slots.

In the box labled neuro ic pad.

That's a pll chip I'm pretty sure.

Both my memory stick, matter of fact, all sticks of memory since sdram I've seen pll chips on them.

So I dn why they were disabled stock...

 

I enabled them so later on, I can modify the heck out of one stick, without having to mod the other.

Because if I mod only one stick's clock reference timer, it gets so fast that the other stick falls behind and sometimes dissapears, no joke.

It makes my adata more stable at 280 anyways.

I checked when I actually had 280 prime stable and s&m quick tests stable.

 

What else...

Oh, was priming, dual priming, 1024-1024k and 4096-4096k setups for 4 hours.

Meaning 8hrs each.

I logged out though after that time peroid to try some windows mods to find that it exited those and my dialup connection...

Did it at 266x9 @ 1.65v .

I forgot if I verified this vcore or not, so I'm doing it.

I want lower vcore.

And I want my system stable...

 

I think my latest bios sucks or something I dn, I don't have my burner hooked up so I can't flash to an older bios to check.

[Clay]

Usually memtest will run a few more mhzs stable than windows will. Usually my problem with prime is vcore when you get to that point.(Sometimes heat)

[skinnie]

it is so strange..in my email....appeared a notifications of reply to this posts..and a big psot of neo...but here there is nothing...but as he said..I'm going slow..keeping the 250fsb but @2000mhz...1.45vcore...now i'll prime to see...

[skinnie]

this was what neo said:

Hey dude, back off the cpu multi.

 

Goto 8.5x, which is around 2125mhz.

For that should only need 1.45v vcore for.

If you need more, then by all means, you shuoold'nt need more then 1.65v

absolute max.

 

From there, which everything getting less hot, and less cpu probs, and less pull

from the cpu, it'll be easier on you.

 

Why you guys allways wanna max it out lol...

I mean from the get go.

 

You gotta start low and work your way up .

 

So work on an everyday use setting, something with the stock vcore for that cpu,

not the bios stock, but your cpu's rated vcore.

 

 

Let it prime.

Once that's all settled, go up a multi or 2 until you reach around 10x or more.

Then lower it and go up the fsb.

 

If you have to, to get a feal for it.

Go down to 200mhz fsb, and try 12x and 12.5x.

To check the cpu...

 

 

This part is the hardest to explain...

When you get yourself into trouble, the system stability will go down the drain.

It will never recover.

I mean it could but...

It's the cmos, it gets corrupted somehow majorly.

 

This is the hard to explain part.

You have to clear the cmos.

Seems easy right?

Well it's not.

The cmos is finiky.

You may have to clea that sucker many times before it's right again.

So how do you tell it's corrupted?

Well...

 

Look for the vcore, or vmem, that's one sign.

If it's higher or lower then the bios'es stock, then it's a bad cmos after

clear.

 

Other ways to tell are by jumping to something that's tight, like 266x8 maybe or

whatever.

It may not boot right after a clear, but it should(just a possible example).

Well, clear it again and try that fsb setup again, it's supposed to boot.

It may be 250 in your case, stuff like that.

For example, you know it's memtest stable, and prime stable...(say it was).

Well it shoudl boot, but it does'nt.

Clear that cmos, don't even try forcing it, it'll be problematic in the long

run.

For example you'll probably have some errors in s&m when there should be none.

That's how I've caught that one.

 

Sometimes, even if it seems all good form the get go, it may not be.

Ie the s&m errors.

Clear a few more times and they are gone, multble runs of s&m too.

I no longer bother on that though, I mean clearing to get stable.

I just ensure that stuf seems normal and I go ahead anyways.

 

As long as it boots, and as long as everythign itn eh bios setup seems normal,

continue on.

 

Something I noted today.

Clearing the cmos and holding insert to boot does'nt clear the cmos as good on

avg as compared to just clearing the cmos.

I dn why, like I would know...

I noticed it when modding spd's.

Holding insert 75% of the time allowed me to oot an invlaid spd, and everytime

it had th ewrong stock vmem and vcore.

This would'nt happen everytime, but...

When not holding insert, it did it right the 1st time.

Not saying it will clear correctly 100% at all times this way, but it's got a

betetr avg of doing it right.

That is, if you can boot initally without holding insert, some people can't.

 

 

 

A status update on my part.

Enabled the PLL, phase lock loop on both my sticks of memory.

Tested on my adata, before hand and never realized it.

It's ok.

The samsung I dn.

I will test with memtest and lower cas and such when I get my dvdrw back in,

that should be good enough I would think, the rest needs testing at 280...

 

A PLL is somehting that checks and redoes phase..

Err...

Well, it monitors the crystals, the clock.

If it's off, it compensates and makes it correct.

There's a pll on the mobo for this, on the left hand sie of the mmeory slots.

In the box labled neuro ic pad.

That's a pll chip I'm pretty sure.

Both my memory stick, matter of fact, all sticks of memory since sdram I've seen

pll chips on them.

So I dn why they were disabled stock...

 

I enabled them so later on, I can modify the heck out of one stick, without

having to mod the other.

Because if I mod only one stick's clock reference timer, it gets so fast that

the other stick falls behind and sometimes dissapears, no joke.

It makes my adata more stable at 280 anyways.

I checked when I actually had 280 prime stable and s&m quick tests stable.

 

What else...

Oh, was priming, dual priming, 1024-1024k and 4096-4096k setups for 4 hours.

Meaning 8hrs each.

I logged out though after that time peroid to try some windows mods to find that

it exited those and my dialup connection...

Did it at 266x9 @ 1.65v .

I forgot if I verified this vcore or not, so I'm doing it.

I want lower vcore.

And I want my system stable...

 

I think my latest bios sucks or something I dn, I don't have my burner hooked up

so I can't flash to an older bios to check.