"Paul" <> wrote in message
news:nospam-3107061547170001@192.168.1.178...
> How about trying A64tweaker while in Windows ? I think it has
> a setting for memory clock.
>
> http://www.xtremesystems.org/forums/...t=37345&page=1
> http://www.cranox.com/Software/A64-T...r_V0.6beta.zip
>
> What I cannot tell you, is if all the settings listed in A64tweaker
> really affect the hardware on the fly, while the processor is
> running. All I can suggest is giving A64tweaker a try, and use
> Sandra or some other Windows memory benchmark program, to test the
> results.
>
> There is a three bit register in the processor, which controls
> the memory clock. The AMD 26094.pdf document, only officially
> defines four of the values. But this article was one of the first
> to show what was happening underneath. The Rev.E processors
> added a bit called OddDivisorCorrect, but I don't know how
> that affects this table, or even whether A64tweaker knows
> about that bit setting.
>
> http://xtremesystems.org/forums/show...hlight=divider
>
> Another tool you can check into, is Clockgen. It has a
> setting for memory clock, but I don't know if it is accessing
> that three bit register as well or not.
>
> http://www.cpuid.com/clockgen.php
>
> There are plenty of tools to play with :-)
>
> HTH,
> Paul
Paul, thanks for your reply.
Have been using Clockgen for quite some time for OC, and fiddled a little
with A64-Tweaker some week ago, but only scratched the surface of its
capabilities - until now.
The thread link you provided to Xtremesystems.org was what really opened my
eyes. I read it all (took some time).
It turned out that it is possible with the A64-Tweaker to employ a memory
divider between 166 and 200 MHz, namely 183 MHz, which is what I have been
looking for (in form of a modified Bios flash file). Using this divider
(183) I now have my memory running at 214 MHz instead of earlier 184 MHz,
which is a nice improvement.
In the process I also tried some other little adjustments in the various
memory timings and values that the A64-Tweaker gives acces to, but are not
accessable in Bios. The thread provided very uselful help in this context. I
actually copied and saved the most important info (for me) from the thread
into a text file for further reference.
It is very easy to test the new memory settings adjusted with the
A64-Tweaker, as the altered values are activated on the fly (click SET), and
you can test them immediately with Memtest for Windows and SuperPi or
similar, to check stability and performance. Of course there is the risk of
crashing if you go too far, but then you know the limits.
A good thing with the Tweaker is that you can save your settings to be
enforced at the next system startup, but I got the feature to work only with
version 0.31, which is the latest fully tested version, acc. to the author.
The later versions, like the latest v0.6beta, are experimental and not fully
tested by the author. I made my first experiments with that latest v0.6beta
version, and all went fine except for loading the adjusted values at Windows
startup. It simply crashed and re-booted, and I have to go into safe mode to
stop the loop.
I then downloaded the "official" v0.31 version, and now it loads the new
values at startup with no hickups, and maxed out memory performance. So it's
best to use the stable v0.31.
With that thread at Xtremesystems.org I have been able to achieve my
objective. Thanks for pointing me there.
Uffe