WPCREDIT tweaks for the A64

[CodeRed]

Glad to hear its working (at least partially)

The IO.DLL problems will all go away when I replace this module with a better one ... hopefully XP64 compliant too

[cpulloverclock]

NF2 tweaker

http://forum.abit-usa.com/showthread.php?threadid=57468

[blass]

how do you guys make the settings stay after reboot.?

[CodeRed]

Originally posted by blass
how do you guys make the settings stay after reboot.?

File -> Apply Settings at Startup


or save the settings top a file and run from Programs->Startup

a64tweaker filename

[blass]

ohh geesh! I didnt see that option lol!! sorry about that nice job code red!!

[blass]

weird I get this message now==> Unable to extract IO.SYS.log in as a user who has such permission

[CodeRed]

Gents,
All your driver problems are about to go away. Franck Delattre (the author of CPU-Z) has kindly provided me with a Windows 64 compatible version of his I/O utiltities (which is way more than just an I/O driver).

Normally these utilities are sold commercially, but Franck has waived any fees for the use with A64 Tweaker. We all owe Franck and his company, http://www.panopsys.com/ , many thanks for this.

V0.3 of A64 Tweaker using Franck's drivers will be available in about a week or so ... just depends on my workload.

@Franck, Ive looked at about 30+ I/O drivers so far (both free and commercial ones) and yours is easily the best. Programming with them will be a pleasure

[ojdr2001]

[blass]

CODERED IS THA MAN!!!!!!!!! lots of THANKS TO Franck too for sharing he knowledge !!

[jess1313]

THANX FRANCK

[Gokou]

So whats the procedure with all this?
normal settings... find max overclock etc then alter the settings with this program to find the most performance / see if it allows higher overclock?

[CodeRed]

Originally posted by Gokou
So whats the procedure with all this?
normal settings... find max overclock etc then alter the settings with this program to find the most performance / see if it allows higher overclock?

Thats how I tuned my rig.

Firstly I found the max stable mem speed using BIOS setting .. 276 MHz.

Then I backed off to a safe speed of 270 MHz and started tweaking the mem timings. Try
2-7-13-2-2-5-2-2-1-1 or 2-8-12-2-2-5-2-2-1-1
Read Write Q Bypass = 16x
Max Async Latency = 6ns
Read Preamble = 5 ns
Bypass Max = 7x


Then I increased the mem speed again to see what it can hit with the more aggressive timings and re-tested. I only lost 1-2 MHz with the more aggressive timings, but gained a lot in performance.

[PlatinumX]

Nice work very nice program. You may have said it already but it I make changes with the 64tweaker does that take affect immediately? Or do you generally have to reboot and add the file to startup to have this work. Also, I'm sort of new to this so please bare with me. If I'm running 1:1 better then 2:1 dividers and if so how can I change the clock ratio to match my memory speed. ie 2:1 ddr 400 under A8V bios settings. 1:1 equals ddr 200. Thanks.

[CodeRed]

Originally posted by PlatinumX
Nice work very nice program. You may have said it already but it I make changes with the 64tweaker does that take affect immediately? Or do you generally have to reboot and add the file to startup to have this work. Also, I'm sort of new to this so please bare with me. If I'm running 1:1 better then 2:1 dividers and if so how can I change the clock ratio to match my memory speed. ie 2:1 ddr 400 under A8V bios settings. 1:1 equals ddr 200. Thanks.

The changes are applied when you click the "Set" button.

[LilGator]

CodeRed, doesn't a Bank Cycle Time (trc) of 10 give you better performance than 5 ?

IE: 2-8-12-2-2-10-2-2-1-1 ?

[CodeRed]

Originally posted by LilGator
CodeRed, doesn't a Bank Cycle Time (trc) of 10 give you better performance than 5 ?

IE: 2-8-12-2-2-10-2-2-1-1 ?

Not in my experience.

Most of my performance testing has been using SuperPi and PiFast. For these programs Trc = 5 (or lower) is best.

Havent done any detailed 3DMark testing yet .. too busy. But Trc=5 looks good here.

Maybe for Sandra Mem benching Trc=10 is best, but I havent checked this.

[swaaye]

There's a thing with NForce2 chipsets that causes higher tRAS to have a positive impact on performance. It's odd, but has been proven in many benchmarks.

I doubt any other chipsets would display that, but I could be wrong.....

[CodeRed]

Gents, V0.31 of A64 Tweaker is now available thanks to Franck Delattre's contribution of the Windows 64 bit drivers (from CPU-Z).

Download: A64 Tweaker V031.zip

Change Log

1. New 64 bit Windows I/O drivers - now works with Win 2003 Server 64 bit
2. Added AMD64 processor ID check
3. Corrected compatibility issues with MBM5
4. Improved startup directory handling

The new drivers are far more robust than the driver I was previously using. I dont expect any more compatibility issues with other software packages incluing Anti Virus S/W, but I havent been able to verify this completely.

Enjoy !!

[jess1313]

NO PROBS here, I am not using 64OS tho.

[bias_hjorth]

Originally posted by CodeRed
Gents, V0.31 of A64 Tweaker is now available thanks to Franck Delattre's contribution of the Windows 64 bit drivers (from CPU-Z).

Download: A64 Tweaker V031.zip

Change Log [list=1][*]New 64 bit Windows I/O drivers - now works with Win 2003 Server 64 bit [*]Added AMD64 processor ID check[*]Corrected compatibility issues with MBM5 [*]Improved startup directory handling[/list=1] The new drivers are far more robust than the driver I was previously using. I dont expect any more compatibility issues with other software packages incluing Anti Virus S/W, but I havent been able to verify this completely.

Enjoy !!

Uhh I´ve been waiting for that number 4 answer !! Will try it ASAP!!

[swaaye]

I'm having a problem here with 3.1. It's not reading the initial settings when I load the program, nor is it applying things when I change them.....

These two screenshots are of both versions on initial loadup with my default bootup settings for the notebook. 0.2 SEEMS to be getting the proper initial settings (though I can't verify anything other than CL, tRCD, tRP, tRAS, and tRC).

[LilGator]

the program indicates the 183* divider to be a reserved value, does it work ?

Clockgen shows the memory being -200MHz when set to that. As HTT goes up, memory goes negative even further

[swaaye]

When I used the 183 with .2, it worked. To verify it I had to use a RAM benchmark, like Everest's. It's odd how everything seems to report a horribly wrong value. In Clockgen I was seeing -200Mhz.....

But, it seems to work.

[LilGator]

Well, does this look normal for 244Mhz (267*183/200) 2-2-2-10 ?

[CodeRed]

183 MHz DRAM setting does NOT mean that you mem is running at 183/200 of your FSB. It is just another method that the core uses to select the memory divider.

To calculate your actual mem frequency using 183 setting use this

mem divider = ceil(CPU Multi * 200/183.3)
mem freq = CPU Freq / mem divider

CPU-Z and clockgen wont recognise the 183 MHz DRAM setting so they will probably report unusual values. This is a reserved setting and is NOT specified by AMD ... thats why it has a * next to the selection.

@swaaye,
I have seen that effect before, it happens when the driver doesnt correctly load. Are you running V0.2 and V0.31 simultaneously? If it continues then you'll have to uninstall the driver by deleting the registry keys

HKLM/SYSTEM/CurrentControlSet/Service/cpuz
and
HKLM/SYSTEM/CurrentControlSet/Service/io.sys <--- old driver

then run A64Tweaker and it will reinstall the CPU-Z driver in the correct directory.

Let me know how it goes.