a8n-sli and 3000+

[Loki726]

Ok, I've had an a64 3000 sitting on my desk for about a month waiting for the new dfi nforce4 board. However, after seeing some of the overclocks people have been hitting and the a8n go below $180 I figured what the hell.

Heres my setup so far

a8n-sli 1004
a64-3000+ Stepping: 0 Revision: DH8-DO
Zalman cnps 7700 heatsink
1x 512mb CorsairXL3200 (just one so far one more in the mail)
2x leadtek 6600gt

Everything listed is prime stable for at least 2 hours ( I will do more stability testing when I hit a wall)

UPDATE 1/26/05 1:45 am
Right now I am running async 2:3 to get the max for the cpu and mobo

HT is 3x
HTT is 278
Multiplier is 9x
Resulting clock is 2506.7
DDR voltage is 2.75
cpu voltage is 1.45

UPDATE 1/27/05 9:25 am

Still running async 2:3

HT is 3x
HTT is 292 (set to 290 in bios though)
Multiplier is 9x
Resulting clock is 2627
DDR voltage is 2.75
cpu voltage is 1.45

UPDATE 1/27/05 3:53pm

Looks like 2627mhz is the max. I get errors in prime95 with anything higher no matter what voltage. Adding more voltage just increases the temp. Here are some numbers for full load temps and voltages if anyone cares.

1.45v = 47C
1.475v = 49C
1.5v = 53C
1.525v = 55C
1.55v = 57C


Now I'm gonna see how high my ram can go with 3v.

UPDATE 1/29/05 7:42pm

I guess the a8n won't go over 240 for the memory frequency at 1T so I had to drop the htt to 289 and run at 5:6. here's the final clock

HT is 3x
HTT is 289
Multiplier is 9x
Resulting clock is 2607
DDR voltage is 2.75
cpu voltage is 1.45
Memory fequency is 237 at 2 3 2 11
Memory volatge is 3.0v

I'll be back later with more and some benches when I get the rest of my ram

 

[steady602]

looking forward to it.
my wall is sofar @ 2655 (295x9)

here my setup:
http://forums.anandtech.com/me...id=1503573&STARTPAGE=1

 

[TantrumusMaximus]

HOW are you guys setting your divider in this BIOS without it screwing up your custom CPU settings. I have the same board and when I set the "MAX DDR Frequency" to anything other than AUTO...my "Jumperfree" Section all defaults back to AUTO!!! Then if I set anything manual in the Jumperfree section the MAX DDR Frequency goes back to AUTO.

Am I missing something? I am getting a very good overclock now but would like to play further. It always says DDR200 when I boot too, so I think something is wrong.

 

[GuitarDaddy]

If you use DDR400 or lower, when you initially change it it resets the jumperfree section, but if you go back to the jumperfree section before leaving bios, you can change it back to manual and change all the settings and it will not reset the ramclock to AUTO

The DDR433 or higher settings work as you described. IMHO these settings are worthless

At least thats the way it works for all the 1003 bios, I never used the 1002 bios so I'm not sure about that one. Before I figured this out, I would set my DDR settings in bios then boot to windows and use AI booster to increase HTT a few mhz, then reboot and you can change the jumperfree settings without reseting the ramclock. I beleive this method works for all DDR settings but it requires a reboot.

 

[Loki726]

Originally posted by: GuitarDaddy
If you use DDR400 or lower, when you initially change it it resets the jumperfree section, but if you go back to the jumperfree section before leaving bios, you can change it back to manual and change all the settings and it will not reset the ramclock to AUTO

The DDR433 or higher settings work as you described. IMHO these settings are worthless

At least thats the way it works for all the 1003 bios, I never used the 1002 bios so I'm not sure about that one. Before I figured this out, I would set my DDR settings in bios then boot to windows and use AI booster to increase HTT a few mhz, then reboot and you can change the jumperfree settings without reseting the ramclock. I beleive this method works for all DDR settings but it requires a reboot.

This totally confused me when I first got the board. Thanks for explaining, it was very frustrating having to enter everything in again every time I change the divider.

 

[fireontheway]

Originally posted by: Loki726
Ok, I've had an a64 3000 sitting on my desk for about a month waiting for the new dfi nforce4 board. However, after seeing some of the overclocks people have been hitting and the a8n go below $180 I figured what the hell.

Heres my setup so far

a8n-sli 1004
a64-3000+ Stepping: 0 Revision: DH8-DO
Zalman cnps 7700 heatsink
1x 512mb CorsairXL3200 (just one so far one more in the mail)
2x leadtek 6600gt

Everything listed is prime stable for at least 2 hours ( I will do more stability testing when I hit a wall)

UPDATE 1/26/05 1:45 am
Right now I am running async 2:3 to get the max for the cpu and mobo

HT is 3x
HTT is 278
Multiplier is 9x
Resulting clock is 2506.7
DDR voltage is 2.75
cpu voltage is 1.45

UPDATE 1/26/05 9:25 am

Still running async 2:3

HT is 3x
HTT is 292 (set to 290 in bios though)
Multiplier is 9x
Resulting clock is 2627
DDR voltage is 2.75
cpu voltage is 1.45

UPDATE 1/26/05 3:53pm

Looks like 2627mhz is the max. I get errors in prime95 with anything higher no matter what voltage. Adding more voltage just increases the temp. Here are some numbers for full load temps and voltages if anyone cares.

1.45v = 47C
1.475v = 49C
1.5v = 53C
1.525v = 55C
1.55v = 57C


Now I'm gonna see how high my ram can go with 3v.

I'll be back later with more and some benches when I can't go any higher (and when I get the rest of my ram)

i'm jealous, i can only do 2.8 vdimm

Goog Luck .....

 

[DVad3r]

Wow I'm stupid, I still don't understand how you guys are preventing the jumperfree settings from being reset when going above 400 mhz DDR ?

 

[GuitarDaddy]

You don't use the settings above DDR400 regardless of the rated speed of your ram

You use either DDR400 or DDR333 and increase your HTT and the ramspeed increases with it.
I am using the DDR333 setting but my HTT is 289 , my ram is running 236mhz = DDR472

As reported by everyone using this board the maximum ramspeed that will currently run stable is 240mhz = DDR480, regardless of the speed ratting on your ram. Hopefully a bios update will fix this.