• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

HELPP IM NOOB AT OC :(

G

gcxbrian

Member
omg wtf.

DFI|NF4 LANPARTY UT nF4 Ultra-D
LEADTEK 6800GT
CPU A64 3500+ 939
CORSAIR VALUE SELECT RAM 512x2
ZALMAN 7000b ALCU

why so sux?!?!?!? 🙁
 
Welcome to teh forums. 🙂

First off, are you running a RAM divider?

What have you tried thus far to concede that 2.36 GHz is as far as it will go?
 
o yea im noob 🙁 i dun understand how ram has anythign to do with OC
LOL 🙁 oh i just put down vcore to 1.34 its working fine

lemme get screenshot of my comp
 
Have you tried lowering your Hypertransport multiplier to 4x?
It's also known as the LDT multiplier often. You usually need to so that you don't overclock your HT bus too far past 1000mhz, as it sometimes can't handle it.
 
i dunno. miy hypertransport mulitplyer thing is on auto? so should i change to 4x?

oh ya so this is how its done-
HTTx 215
mulitplyer x11


Ram is
200MHz
2.5-3-3-8






cool! i turned hypertransport to 4x and put mulitplyer to 10 and HTT to 230 and its working! before it wouldnt work
 
i did but i have no idea how to change all that memory stuff.. 🙁
someone halp!

right now currently @ 2.65 GHz
241*11 with hypertransport at 4x vcore 1.488

mem timings at
2-3-2-5-9(i have no idea how to change these)
SPD timings
2.5-3-3-8 @ 200MHz (i haev no idea how to change these
 
That's not going to pass prime 95.

Okay, read the guide above and expect to hit 2.6Ghz or maybe some more. Make sure that you test with prime 95 for 15 minutes between each test and....just read the guide.=)
 
i dunno how to do the following steps in the guide




. Max HTT/FSB should be first ..*only works if motherboard has locks. Most A64 boards do today. Sata 1 and 2 are not locked on some nforce mobos use 3 and 4.
-set CPU multi to 6 or 7, this will take CPU out of equation
-set memory to SPD and 100, this will take memory out of equation
-Increase HTT/FSB up until you fail to boot or there abouts, back down 5%, (HTT * 0.95), this is your max safe HTT.

2. Max Chip capable
- Set multiplier to it's maxium
-Set vcore to 1.6 -1.65 for 130nm chips, 1.50-1.55 for 90nm chips
-Set mem to SPD and 100, this will take memory out of equation
-starting with HTT 200 raise in about 5Mhz increments up to boards max found earlier or until you start failing PRIME95 which will probably happen first..only give it 5 minutes max, that's good enough for now.
-At the point it starts failing within that 5 min time period, back down 5%, (CPU MHZ * 0.95), thats your max CPU speed, now test prime again at 95% for 12 hour for stable.
Prime 95 Link http://www.mersenne.org/freesoft.htm

3. Memory MAX

It depends what you want and type of mem you chose, LL or Bandwidth but must keep 1T (command rate) because A64 suffers big time with 2T.

-For high bandwidth set mem setting to 200 and 2.5-4-3-7 1 T and give it boards max volts, or for LL set mem setting to 200 and 2-2-2-7 1 T and give it boards max volts. (up to 2.9Vdimm is safe with all ram) (i have no idea how to set mem settings
-Set CPUs multi to 6-7, again to take it out of equation.
-Raise HTT up to boards max or until you start failing memtest86 test 5 and 6 http://www.memtest86.com/
-When you start failing memtest86 test 5 and 6, back down 5%, (HTT * 0.95), thats your max MEM speed.
 
ohh yea i know that but. i dont kno what like all the stuff are theres more then just
2-2-2-7 1t
theres like 10 of them 🙁 someone ss or something 🙁(
 
My guess is that most of your problems are due to the fact tha tyou are OCing your RAM past what it can handle.

You say you are at 11*227. That means your RAM is running at 454 MHz, far past the 400 it's designed for.

Try setting the RAM to 166 instead of 200.
 
When you overclock, you raise your FSB (thats what the 227 is). Ram speed is based off of the FSB. Right now, if your FSB is 227, your ram is running at 227mhz, or 454 effectivly. If you lower the divider to 166, the ram will run at a certain fraction of the FSB, 5/6 of it in this case. 5/6 of 227 = 190mhz, which is a speed your ram can handle.
 
btw running @ 2.55GHz 232x11 prime running for maybe 4 hours now ill leave vernight and see how it goes

EDIT: oops i did replay isntead of edit sry
 
Originally posted by: gcxbrian
how do i get a divider?
Click to expand...


Myself & Cheesepoofs just attempted to explain to you how.

I would recommend taking the OCing easy until you have a better grasp of what you are doing.

IOW, do a little research, since you don't seem to understand our help.
 
Okay, what they are saying is that you ram is slow and is holding up the OC process. In order to continue here you need to set up dividers. In otherwords, set your ram to a lower setting as suggested, 166 should be good for now and see where that takes you. You should be between 2.55 and 2.65 GHz on the processor. That mobo supports 300+ mhz fsb. About what you don't understand in the guide, I need you to ask specific questions about what you don't understand cause I'm not going to explain everything that you quote. =) You understand.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top