In short: HT/FSB will not go above 225 MHz

Even if I underclock my memory using a divider and underclock the CPU
using a low multiplier, I can't get HT above 225 MHz without the system
freezing!

Since I am underclocking both memory and CPU, I guess none of these
could be at fault. Or what? I am using some really cheap and crappy
Elixir RAM (2x512MB in Dual Channel mode), but since I am underclocking
it I thought it wouldn't be an issue. But maybe it is?

Or is my system (motherboard I guess) just so crappy that HT wont go
above 225 MHz?

Can this be solved, or was I just unlucky with my motherboard, I got a
crap one?

/David

On Mon, 09 May 2005 21:59:27 +0200, David Rasmussen
<(E-Mail Removed)> wrote:

>In short: HT/FSB will not go above 225 MHz
>
>Even if I underclock my memory using a divider and underclock the CPU
>using a low multiplier, I can't get HT above 225 MHz without the system
>freezing!
>
>Since I am underclocking both memory and CPU, I guess none of these
>could be at fault. Or what? I am using some really cheap and crappy
>Elixir RAM (2x512MB in Dual Channel mode), but since I am underclocking
>it I thought it wouldn't be an issue. But maybe it is?
>
>Or is my system (motherboard I guess) just so crappy that HT wont go
>above 225 MHz?
>
>Can this be solved, or was I just unlucky with my motherboard, I got a
>crap one?
>
>/David

I also have a 3000+ but in an asus a8v deluxe board. I cant get past
220FSB before it crashes. Cant be the memory because i ran a divider
so the memory was well below 400mhz even at 220 HT/FSB. I think it
must be cooling, maybe i need better cooling.

On Mon, 09 May 2005 21:59:27 +0200, David Rasmussen wrote:

> Or is my system (motherboard I guess) just so crappy that HT wont go
> above 225 MHz?
>
> Can this be solved, or was I just unlucky with my motherboard, I got a
> crap one?
>
Setting the HT link multiplier lower will allow you to raise the system
clock past 225Mhz, and probably past 300MHz

--
Abit KT7-Raid (KT133) Tbred B core CPU @2400MHz (24x100FSB)
My server http://wesnewell.no-ip.com/cpu.php
Verizon server http://mysite.verizon.net/res0exft/cpu.htm

In article <(E-Mail Removed)>, paul berry
<(E-Mail Removed)> wrote:

> On Mon, 09 May 2005 21:59:27 +0200, David Rasmussen
> <(E-Mail Removed)> wrote:
>
> >In short: HT/FSB will not go above 225 MHz
> >
> >Even if I underclock my memory using a divider and underclock the CPU
> >using a low multiplier, I can't get HT above 225 MHz without the system
> >freezing!
> >
> >Since I am underclocking both memory and CPU, I guess none of these
> >could be at fault. Or what? I am using some really cheap and crappy
> >Elixir RAM (2x512MB in Dual Channel mode), but since I am underclocking
> >it I thought it wouldn't be an issue. But maybe it is?
> >
> >Or is my system (motherboard I guess) just so crappy that HT wont go
> >above 225 MHz?
> >
> >Can this be solved, or was I just unlucky with my motherboard, I got a
> >crap one?
> >
> >/David
>
> I also have a 3000+ but in an asus a8v deluxe board. I cant get past
> 220FSB before it crashes. Cant be the memory because i ran a divider
> so the memory was well below 400mhz even at 220 HT/FSB. I think it
> must be cooling, maybe i need better cooling.

With A8V, one issue is whether you have revision 1 (no PCI lock)
or revision 2 (PCI lock). With no PCI lock, expect trouble above
227MHz or so (like you would expect on a K8V SE).

Wesley got the A8N-SLI up to 255MHz:
http://www.anandtech.com/mb/showdoc.aspx?i=2358&p=5

Wesley got the A8V Rev2 up to 289MHz:
http://www.anandtech.com/mb/showdoc.aspx?i=2128&p=5

Also, read a few review articles, and find out which ports and
what frequency choices cause disk corruption. Some SATA ports
are not locked, and can be lifted too high in frequency. When
doing the overclocking experiments, use a "disposable" boot
disk that can easily be restored from backups.

Paul

On Tue, 10 May 2005 07:58:36 +0000, paul berry wrote:

> I also have a 3000+ but in an asus a8v deluxe board. I cant get past
> 220FSB before it crashes. Cant be the memory because i ran a divider
> so the memory was well below 400mhz even at 220 HT/FSB. I think it
> must be cooling, maybe i need better cooling.

Just like the OP, you need to lower the HT link speed. The HT link speed
is determined by the HT link multiplier times the system clock (FSB
clock). Normal multiplier is 4 for 754 cpu's and 5 for 939 cpu's. That's
800MHz for the 754 and 1000MHz for the 939. The bios on my old 754 board
shows this as 400, 600, and 800MHz instead of by the divider number, but
it's the same thing, 400=2x, 600=3x, and 800=4x. On the 939 board you need
to lower it to a multiplier of 4 (800MHz) before overclocking the cpu. As
you know, you also need to lower the ram speed to keep your ram within
specs, and usually you'll need to raise vcore too if you are planning
much of an overclock. Since the memory data no longer goes over the FSB
(Ht Link), it's speed really isn't critical to system performance any
longer. You can set it to it's lowest settings without any noticable loss
of performance, but you will have to go down at least 1 notch. For the 939
system that would allow a system clock of 250MHz to get the HT link back
to it's mormal speed of 1000MHZ (4x250). If you plan on going to 266MHz or
more, set the HT link multiplier to 3x. Well, just do the math to keep the
HT link speed at or under 1000Mhz and you will be safe. My old 754 3000+
defualt speed is 2.0GHz, and my old 754 board has a max system clock
setting of 233MH and it's easy to get 233Mhz system clock for a cpu speed
of 2.33GHz. The default speed of the 3000+ 939 is 1.8 GHz (9x200) and it
should be easy to get at least 9*266 with it if done properly.

--
Abit KT7-Raid (KT133) Tbred B core CPU @2400MHz (24x100FSB)
My server http://wesnewell.no-ip.com/cpu.php
Verizon server http://mysite.verizon.net/res0exft/cpu.htm

Maybe you used a n.5 multiplier? Like 8.5? Sometimes that does it.


--
Ed Light

Smiley :-/
MS Smiley :-\

Send spam to the FTC at
(E-Mail Removed)
Thanks, robots.

"Wes Newell" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> On Mon, 09 May 2005 21:59:27 +0200, David Rasmussen wrote:
>
> > Or is my system (motherboard I guess) just so crappy that HT wont go
> > above 225 MHz?
> >
> > Can this be solved, or was I just unlucky with my motherboard, I got a
> > crap one?
> >
> Setting the HT link multiplier lower will allow you to raise the system
> clock past 225Mhz, and probably past 300MHz
>
> --
> Abit KT7-Raid (KT133) Tbred B core CPU @2400MHz (24x100FSB)
> My server http://wesnewell.no-ip.com/cpu.php
> Verizon server http://mysite.verizon.net/res0exft/cpu.htm
>

Exactly right. I have a 754 board with a 2800+(1800mhz). With the HTT at x4
I could only get to 218. Lowered HTT to 3 and Mem to 166. Now crusing at 245
FSB, CPU shows 2225mhz!! Stock cooling too. Temps decent at low 50's. Still
it's kinda weird that at boot memory now reads 410. Overcking the A64 is a
bit weirder than the XP's.

Paul wrote:
>
> With A8V, one issue is whether you have revision 1 (no PCI lock)
> or revision 2 (PCI lock). With no PCI lock, expect trouble above
> 227MHz or so (like you would expect on a K8V SE).
>

In my case, the PCI lock is not a (big) problem. It is easy to lock the
PCI frequency on A8N, although choosing it in the BIOS isn't enough for
some reason. You also have to choose at least FSB 201 MHz before PCI
actually locks at 33 MHz. Weird, but true.

Still, it doesn't solve my problem.

/David

Wes Newell wrote:
> On Tue, 10 May 2005 07:58:36 +0000, paul berry wrote:
>
>
>>I also have a 3000+ but in an asus a8v deluxe board. I cant get past
>>220FSB before it crashes. Cant be the memory because i ran a divider
>>so the memory was well below 400mhz even at 220 HT/FSB. I think it
>>must be cooling, maybe i need better cooling.
>
> Just like the OP, you need to lower the HT link speed.

I guess I should have written that also, but I already tried that.

In short: Choosing to run with the lowest memory frequency (by using a
divider), choosing to run a low CPU frequency (by using a low
multiplier), and using a low HTT multiplier (1, 2, 3 and 4 tried) to get
a low FSB/HT/HTT/whatever, none of these helps. When the FSB reaches
appx. 225 MHz, the system crashes. Even if the HT is only running 4x225
= 900 MHz or lower at the time, the memory is running 186.75 MHz instead
of 200 MHz, the CPU is running 225*8 = 1800 MHz or lower, the system
STILL crashes.

> The HT link speed
> is determined by the HT link multiplier times the system clock (FSB
> clock). Normal multiplier is 4 for 754 cpu's and 5 for 939 cpu's. That's
> 800MHz for the 754 and 1000MHz for the 939. The bios on my old 754 board
> shows this as 400, 600, and 800MHz instead of by the divider number, but
> it's the same thing, 400=2x, 600=3x, and 800=4x. On the 939 board you need
> to lower it to a multiplier of 4 (800MHz) before overclocking the cpu. As
> you know, you also need to lower the ram speed to keep your ram within
> specs, and usually you'll need to raise vcore too if you are planning
> much of an overclock. Since the memory data no longer goes over the FSB
> (Ht Link), it's speed really isn't critical to system performance any
> longer. You can set it to it's lowest settings without any noticable loss
> of performance, but you will have to go down at least 1 notch. For the 939
> system that would allow a system clock of 250MHz to get the HT link back
> to it's mormal speed of 1000MHZ (4x250). If you plan on going to 266MHz or
> more, set the HT link multiplier to 3x. Well, just do the math to keep the
> HT link speed at or under 1000Mhz and you will be safe. My old 754 3000+
> defualt speed is 2.0GHz, and my old 754 board has a max system clock
> setting of 233MH and it's easy to get 233Mhz system clock for a cpu speed
> of 2.33GHz. The default speed of the 3000+ 939 is 1.8 GHz (9x200) and it
> should be easy to get at least 9*266 with it if done properly.
>

That's all well and good, but I already knew that

Now! Is there anything I can do? Or have I just been unlucky?

/David

Wes Newell wrote:
>
> Setting the HT link multiplier lower will allow you to raise the system
> clock past 225Mhz, and probably past 300MHz
>

Unfortunately not, no

/David