Ok you refreshin' monkeys, here's some BH5 results.

Phil Stanbridge

New member
Just testing my lurvely 3.0c on air, with this BH5 Corsair, now that I have had the volt mods done to the board.

3.0C @ 1.65v - 2x256 3500 Corsair 1.1 BH5 @ 3.3v

1:1 250FSB 2,2,2,5 (tightest timings furthest it will go) DDR500. 6,200mb/s

1:1 255FSB 2,3,3,6 (slacker timings furthest it will go) DDR510.

Not too shabby as you can see. I'm going to try 5:4 bandwidth next and try and find the limit of the cpu.
 
cool look forward to reading where you get with ure CPU, u gonna be sticking a promie on it for fun yet, or just plain air?
 
Phil Stanbridge said:
Just testing my lurvely 3.0c on air, with this BH5 Corsair, now that I have had the volt mods done to the board.

3.0C @ 1.65v - 2x256 3500 Corsair 1.1 BH5 @ 3.3v

1:1 250FSB 2,2,2,5 (tightest timings furthest it will go) DDR500. 6,200mb/s

1:1 255FSB 2,3,3,6 (slacker timings furthest it will go) DDR510.

Not too shabby as you can see. I'm going to try 5:4 bandwidth next and try and find the limit of the cpu.

dayum I want that ram.
 
I'm going to hit it with the GT early next week. The limit of the ram/cpu seemed to be around 255FSB and about 3.88/3.92ghz. Not too bad for an air rig eh?

I'm going to get my OCZ 4200 EL DDR in there now to see what 3.3v makes of it :D
 
hey phill, wen u test out my stuff (im gonna wait to zee greek has time to start sending it here there and everywhere) you think u can test it on air too, test if you could test it with winamp 5 and prime 95 running same time i would be so greatful, as this seems to be the perfect match to crashing winamp :P due to the instability with voltages especially wen prime drops it down
 
Hey... i am jealous....

seems thats someones having some fun today...and that aint me :p

255fsb is what i could max my ocz PC 3500 LE @ 2 2 2 5 8 turbo enabled infinity 64msec etc..

i get 6367mb/sec with sandra and 236fsb with my ram thats using the 5/4 divider :)
 
I think as a rule of thumb as soon as u get past 3200, memory just loves that extra juice. I got some Geil 3500 sticks yesterday and without the vmodd (max 2.85)

it will do 275 fsb (that’s 5:4 memory running @ 216 mhz) but with 3.3 i can get 292 FSB whoooot 4380 mhz :o. and i haven’t had to fiddle with clockgen yet.

cpu specs below :P

to be honest i really didnt think this cpu would get this far

so in short ive had these sticks 4 around 5 mins and want to get rid of them :) and swap fer pc3700. Will 3700 sticks still divide fine?
 
name='Epicurus' said:
god I still have loads to learn about memory setting and stuff...
Isnt that a cool thing ? :)

name='Epicurus' said:
ok.. Does this 1:1 5:4 apply to AMD CPUs as well????
most certainly.

imo with amd's its more important. With amd's to get good clocks u normally drop the multi (if u can) and up the fsb wich will stress ur memory more

wot sticks do you have and what kind of clocka re you getting @ 1:1?
 
ok.. so where are these set from..

I have seen the place that you can change this lot

DRAM Configuration

  • DDR Timing Setting by [Manual / Auto]
  • Max Memclock (MHz) [100, 133, 166, 200]**
  • CAS# Latency [CL=2.0, 2.5, 3.0]
  • RAS# to CAS# Delay (tRCD) [Auto, 2-7 Cycles]
  • Min RAS# Active Time (tRAS) [Auto, 5-15 Cycles]
  • Row precharge Time (tRP) [2 Bus Clocks]
I have Dual Channel TwinMOS 512. how do I know what to set them too??
 
just found this info

The speeds are set as predefined values "DDR200", "DDR266", "DDR333" and "DDR400", which in fact stand for the memory divisors 1\2, 2\3, 5\6 and 1\1, respectively. This means when set to "DDR400" the memory runs in the synchronous mode (which is, by the way, the most productive mode). When overclocking the processor through raising the FSB to 220 MHz, the memory speeds also goes up to 220 MHz (which is equivalent to DDR440). This means to overclock the Athlon64 processor you would have to store up some high-performance memory

bios_select_mem_clock.jpg
 
its more important to have good timings with amd than high speed memory. The higher the speed the worse the timings generally are. and its made the situation worse now BH-5 is no longer in production
 
Epicurus said:
just found this info

The speeds are set as predefined values "DDR200", "DDR266", "DDR333" and "DDR400", which in fact stand for the memory divisors 1\2, 2\3, 5\6 and 1\1, respectively. This means when set to "DDR400" the memory runs in the synchronous mode (which is, by the way, the most productive mode). When overclocking the processor through raising the FSB to 220 MHz, the memory speeds also goes up to 220 MHz (which is equivalent to DDR440). This means to overclock the Athlon64 processor you would have to store up some high-performance memory

bios_select_mem_clock.jpg
Yeah everything there is correct but also consider this. Memory is rated at specific speed's which u can normally get higher than by throwing more V's at it. With pc4000 u have a rated speed of 500 mhz which in the field equates to around 250 fsb 1:1 in your box. The only way to get a higher clock after that is to throw more volts at them mem to get an extra 10 or so, whack a diver on or buy faster memory which costs a small fortune. I could never get my pc4000 sticks to divide I don’t know if the situation is the same when u go higher than that. you are right in saying that 1:1 is the most productive mode but even with the divider on 5:4 @ 292 fsb i have brought the memory around 20 mhz faster than its rated speed. Memory bandwidth wise this is exactly the same as running 1:1 @ 233 FSB but with my current set im on 4.3 ghz instead of 3.4 ghz!
 
Very true Nick, although I've got some OCZ 4200 EL DDR here (Enhanced Latency) that is pretty damn fine. It will do 265FSB 1:1 @ 2.85v @ 2.5,4,4,7 which actually out performs this BH5 believe it or not. This is premium memory however ( = expensive) and not all fast rated memory (pc4000 +) can handle timings as good as these.
 
so how do you know what to set these to

CAS# Latency [CL=2.0, 2.5, 3.0]

RAS# to CAS# Delay (tRCD) [Auto, 2-7 Cycles]

Min RAS# Active Time (tRAS) [Auto, 5-15 Cycles]

Row precharge Time (tRP) [2 Bus Clocks]

or is it a case of looking on the net? and divider???
 
You should only divide if ur cpu can take the extra fsb. When u do, like u said b4 it’s a trade of. What is ur memory rated @ ? I haven’t played with the 64 chips but if 228 fsb is ur limit cpu wise then u shouldn’t bother with the divider. Experiment! find ur highest fsb and tweak the timings your self. Lower is always better but u might find u get an unstable system sometimes despite being able to boot…

my timmings are like this

2 3-3-6
 
so is that

CAS# Latency [CL=2.0, 2.5, 3.0] 2

RAS# to CAS# Delay (tRCD) [Auto, 2-7 Cycles] 3

Min RAS# Active Time (tRAS) [Auto, 5-15 Cycles] 3

Row precharge Time (tRP) [2 Bus Clocks] 6
 
Back
Top