New to AMDx2 overclocking - Updated alot so please look

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Hacka

Senior member
Feb 20, 2006
248
0
0
i posted the old screenshot lol.. i can run 14x240 easy... but my htt is messed up i think so someone told me to stop doing it.

cpu-z shows 3.0-3.4 and moves in between.
 

Hacka

Senior member
Feb 20, 2006
248
0
0
ok so i will first try to get 230x14 = 3220
I will raise the cpu vcore to 1.55
ddr2 vcore = ?
k8<->htt = ?
ht spread spectrum = ?
ht width = ?

sorry if i sound noob.. its just alot of learning right now and once i learn it.. i will be fine :) or once you can recommend me all my settings.. i can tweak them and understand them more after ;]
 

Hacka

Senior member
Feb 20, 2006
248
0
0
ok sorry im a stupid noob lol....

i got my fsb to 230x14 and my k8<->ht is at 4... so 4x230=920 HTT correct?



Heres my cpu-z report so far.... im at 3.2 ;]


CPU-Z Report
CPU-Z version 1.32.

CPU(s)
Number of CPUs 2
CPU#1 APIC ID = 0
Name AMD Athlon 64 FX-53
Code Name
Specification AMD Athlon(tm) 64 X2 Dual Core Processor 5400+
Family / Model / Stepping F 3 3
Extended Family / Model F 43
Brand ID 36
Supported Instructions Sets MMX, Extended MMX, 3DNow!, Extended 3DNow!, SSE, SSE2, SSE3, x86-64
CPU Clock Speed 3208.3 MHz
Clock multiplier x 14.0
HTT Bus Frequency 229.2 MHz
L1 Data Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L1 Instruction Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L2 Cache 512 KBytes, 16-way set associative, 64 Bytes line size
L2 Speed 3208.3 MHz (Full)
L2 Location On Chip
L2 Data Prefetch Logic yes
L2 Bus Width 128 bits
CPU#2 APIC ID = 1
Name AMD Athlon 64 FX-53
Code Name
Specification AMD Athlon(tm) 64 X2 Dual Core Processor 5400+
Family / Model / Stepping F 3 3
Extended Family / Model F 43
Brand ID 36
Supported Instructions Sets MMX, Extended MMX, 3DNow!, Extended 3DNow!, SSE, SSE2, SSE3, x86-64
CPU Clock Speed 3208.3 MHz
Clock multiplier x 14.0
HTT Bus Frequency 229.2 MHz
L1 Data Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L1 Instruction Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L2 Cache 512 KBytes, 16-way set associative, 64 Bytes line size
L2 Speed 3208.3 MHz (Full)
L2 Location On Chip
L2 Data Prefetch Logic yes
L2 Bus Width 128 bits

Mainboard and chipset
Motherboard manufacturer Gigabyte Technology Co., Ltd.
Motherboard model M61P-S3, x.x
BIOS vendor Award Software International, Inc.
BIOS revision F2
BIOS release date 12/26/2006
Chipset nVidia ID03EA rev. A1
Southbridge nVidia ID03E0 rev. A2
Sensor chip ITE 8716
Graphic Interface PCI-Express
PCI-E Link Width x16
PCI-E Max Link Width x16

Memory
DRAM Type DDR-SDRAM
DRAM Size 2048 MBytes
DRAM Frequency 160.4 MHz
FSB:DRAM CPU/20
RAS# to CAS# 4 clocks
RAS# Precharge 5 clocks
Cycle Time (TRAS) 7 clocks
Bank Cycle Time (TRC) 9 clocks

Software
Windows version Microsoft Windows Vista (6.0) Professional (Build 6000)
DirectX version 10.0
 

Hacka

Senior member
Feb 20, 2006
248
0
0
anything else im missing? i dont think this is super stable.. i havent messed with the memory at all yet..

230x14
230x4=920 htt
cpu vcore 1.55
ddr800? stock volts?
 

BadBrad

Member
Aug 30, 2000
195
0
71
Pretty good so far....

Just like your CPU, you can up the voltage on the memory. I'm not familiar with the gskill but the Corsair XMS I use will only start to really overclock when set to at least 2.2volts.

To test for stability in the X2 processors you need to download Orthos. Orthos is two instances of Prime 95 running in tandem, one on each core. It stresses both the memory and CPU. When you run it, the temps are maxed out so it is a really good stress test. Do a search on Google to find a download site. Install and run. I was able to run WinXP, apparently stable, @ 3.1Ghz. But when I ran Orthos it froze up in about an hour. Once I backed it off to just below 3.0 Ghz it ran Orthos for 36 Hrs straight without a hiccup. You should also open Easy Tune5 to monitor the temps and fan speeds of the system during the stress test.

If the system freezes up lower everything then investigate one item at a time. RAM first to find it's max stable speed. Lower CPU multiplier, then increase CPU frequency until instability is detected. That should be your max stable ram speed. Then work on your CPU. Back the memory way off by using the memory divider, say 533. Then increase your CPU frequency until instability if then detected. Once you know both of those limits you can formulate the best approach to get the max out of the entire system. Just remember, the best performance is obtained by the max CPU speed not memory speed. You can sacrifice a little memory speed to get the most CPU speed.
 

Hacka

Senior member
Feb 20, 2006
248
0
0
im not sure how to overclock the memory though.. it used to be so easy... 5-2-2-2 with 2.8v lol.. now theres so many options... my ram said it runs at 15-5-5-5 or something but cpu-z says its at 9-7-5-4 wtf?

i will lower the ram to 533 and try to raise the fsb as far as i can without it crashing... then work on the memory if you can explian that a little for me :)
 

BadBrad

Member
Aug 30, 2000
195
0
71
Hacka,

First things first..........lets establish where you are right now. From what you've told me you have a really good overclock already, but is it really stable. Try what I suggested, see if you can get Orthos to run for something like 12 hours without freezing up. Because it's not how fast the system will run to just post or load the OS, it's how fast it will run and be fully stable.
 

Hacka

Senior member
Feb 20, 2006
248
0
0
ok but i have only overclocked the fsb and htt... no ddr settings but i will run it overnight :)
 

Hacka

Senior member
Feb 20, 2006
248
0
0
ok well i played some video games and it crashed at 230 and 220 fsb... so i just said fuk it and brought it down to 200 with htt 5

was it crashing from the memory do u think? maybe raise timings, ratio and voltage?
 

BadBrad

Member
Aug 30, 2000
195
0
71
That's probably a good idea. But try 667 first. At that divider, the memory will be running at 192mhz when you clock the CPU frequency at 230.

Are you using Orthos to test? If not, you're making a big mistake because you're only testing one core at a time and not fully testing for true stability. You need to see what the max temp will be when the CPU is fully stressed.
 

f4phantom2500

Platinum Member
Dec 3, 2006
2,284
1
0
your ram's already overclocked. if you leave it at the default value in the bios, it will be overclocked when you raise the fsb. that value is basically a divider. when you pick ddr2 800, that's the speed when the fsb is 200MHz (default). but when you raise the fsb, the ram goes with it. so you have to drop that setting in the bios to like ddr2 667 in order to keep it at stock speed (or underclocked a little), and you haven't changed the mem voltage at all from what i can tell, so basically you're just overclocking the ram with no extra voltage. also know that the k8 architecture maxes out around 3.2ghz, and that's usually with some kind of water cooling. if you can get it there stably, be happy.
 

Hacka

Senior member
Feb 20, 2006
248
0
0
Originally posted by: BadBrad
That's probably a good idea. But try 667 first. At that divider, the memory will be running at 192mhz when you clock the CPU frequency at 230.

Are you using Orthos to test? If not, you're making a big mistake because you're only testing one core at a time and not fully testing for true stability. You need to see what the max temp will be when the CPU is fully stressed.


I havent really had time... i just played a few games and it crashed... once my games play good then i will use orthos to make SURE its stable :)

but after reading what that guy said... i dunno if i need to lower it.. maybe just raise the ram voltage and see if i can get it to 3.2 stable. :)

whats a good voltage for ram?
 

BadBrad

Member
Aug 30, 2000
195
0
71
Like I said in a previous post, the XMS I use is rated for 1.8vdc but really doesn't like to overclock much until you give it 2.2vdc.
 

ASK THE COMMUNITY