Having problem overclocking A64 venice 3000(939) + asus a8n-e

B

bpr7

n00b
Joined
May 30, 2007
Messages
9
When I am setting the mem divider at 166Mhz
I am able to go till 256 HTT(FSB)(reaches my mem limit 209.5Mhz),
But When I set the mem divider at 133 Mhz I am not able to go past 237/239 HTT.
My PCIe and PCI bus are not locked, checked in clockgen.
HT link set to 3x. CPU multi is 9x
Can anybody tell me what is the reason for this?
If I set the DRAM frequency to auto it is set to 166 MHz by default so no use .

But If I boot using mem divider 166Mhz and then using A64Tweaker change it to 133 Mhz, I am able to go till 280 HTT in clockgen.

Another question
what is the ideal temp at full load for this processor If I am using stock cooling?
At 280HTT Coretemp shows 60'C tempwhere as ASUS Probe shows 55'C
Which is correct?
 
PCIe and PCI are not locked? You might want to start there. Drop the multi on your chip waay down. Something like x7. Put your RAM divider to 100 (PC1000) and drop the HTT all the way down to 1x. Now see how high you can get your board to go. Also, what are your voltages?
For temps, use a combination of monitoring apps. Throw Speedfan in there too, then average what all three of those tell you. 60C is the MOST A64s should see ever. Definitely don't want to go over that. I assume you're using F@H for load testing (since I know [H] is crazy about that;) ) With the stock cooler you might want to replace the thermal junk with something better.
 
Sorry I got it all confused between locked and not locked.
I mean to say that the PCI and PCIe bus are locked. i.e the frequencies are not changing when I increase the HTT.
I have already tried the following things.
When I set the following,
mem div - 100 Mhz
cpu multi 5x
ht link 3x
I can not go past 233 /235 HTT .
But If I boot using 166Mhz mem divider and then change the frequency to 100 Mhz by A64 Tweaker , I can go till 345 HTT.Probably will go further with HT link 1x not tried yet.
My point is my board is not the limiting factor here.

BTW my vcore voltage was 1.500. @ 60'C at full load.
Now reduced to default 1.400 temp are now around 55'C at full load.But Can't go to that much higher HTT :( .
SpeedFan shows the same temp as Coretemp and ASUS probe shows 5'C less.
Henceforth will use SpeedFan/Coretemp for temp readings.

I use prime95 for CPU stability testing.
I did not get What you mean by "F@H"?
 
are you on the most updated bios... a lot of times newer bioses are fix stange FSB problems like that... also the a8n-e is not a great OCer. that might be the max for that board....

booting is fairly demanding so it could be failing on boot, and so when you are changing it in windows you are not stressing the system and so it works..

what happens if you run orthos or prime95 after you use a64tweaker to OC.

also is there a voltage control on the chipset?
is the chipset passively cooled or actively?

alsoyou might need more volts on the CPU. the memory controller is on the cpu and so if it failing because of stress on the system that **might** help.
 
I am currently using the bios version 1403 beta.(not official got it somewhere from net)
Already tried with 1013(official latest),1011 and 1010.
Will try the rest of the bios version soon ...but I don't think going down the version will help.
there is no voltage control for the chipset in the bios.
and the chipset has a tiny fan on it(stock) so I guess actively cooled.
Adidas4275, you said it could be failing on boot, But I am able to boot using 133/100MHz mem div setting but can't go past 239/233 HTT respectively.
So setting it in bios and setting it in windows has different effect on the overall system.
I guess it is just a hardware bug which is not yet fixed in the bios.:mad:
Is that my RAM is the culprit?:(
Will increase the vcore and let u know If it helps.
 
You need to add more voltages for the ram and cpu. btw you should post your bios settings.
 
Adidas4275 said:
are you on the most updated bios... a lot of times newer bioses are fix stange FSB problems like that... also the a8n-e is not a great OCer. that might be the max for that board....

booting is fairly demanding so it could be failing on boot, and so when you are changing it in windows you are not stressing the system and so it works..

what happens if you run orthos or prime95 after you use a64tweaker to OC.

also is there a voltage control on the chipset?
is the chipset passively cooled or actively?

alsoyou might need more volts on the CPU. the memory controller is on the cpu and so if it failing because of stress on the system that **might** help.
Click to expand...


I'd have to disagree about the A8N-E, my FSB is stable to around 310MHz.
I have read about the newer BIOS's hampering the overclocking experience on the A8N-E for some people.
I'm using version 1008 with a x2 A64 chip and its wonderful, 4200+ running at 2.8GHz.

I agree that boot times are stressful for a PC and can indicate the PSU isnt powerful enough for the system if the boot gives errors or fails.


To the Op:
I'd say the problem is memory related.
Here is the solution :)

When you set your Ram to 133 bus (266 DDR), the timings for it will be drawn from its SPD chip so it can run fast and stabily at DDR266.
This will tighten some timings over DDR400 speeds so when you start clocking you find the ram can no longer clock as high.

To fix it, set everything back to auto in the CMOS and reboot.
Go into the CMOS again and you should find your Ram is running at DDR400 again.
Write down the timings the system has used for the ram at DDR400.

Now set your overclock in motion again but this time manually set the timings for your ram to match that when it was running at DDR400.
You should be home and dry :)
 
Ok So here is What I get with different BIOS
BIOS Memory-Divider PCI
------------------------------------------
1003 200 locked
1003 166 Not locked
1003 133 Not locked
1003 100 Not locked
------------------------------------------
1005 200 locked
1005 166 Not locked
1005 133 Not locked
1005 100 Not locked
------------------------------------------
1006 200 locked
1006 166 Not locked
1006 133 Not locked
1005 100 Not locked
------------------------------------------
1008 200 locked
1008 166 Not locked
1008 133 Not locked
1008 100 Not locked
------------------------------------------
1010 200 locked
1010 166 locked
1010 133 locked
1010 100 locked
------------------------------------------
1011 200 locked
1011 166 locked
1011 133 Not locked
1011 100 Not locked
------------------------------------------
1013 200 locked
1013 166 locked
1013 133 Not locked
1013 100 Not locked
------------------------------------------
1403B 200 locked
1403B 166 locked
1403B 133 locked
1403B 100 locked
For the above details I have used the following BIOS settings
HT link 3x
HTT 200
DDR Voltage Auto Which is 2.6
CPU Voltage Auto which is 1.4
CPU Multi 9x
PCI 33.33
PCIE 100Mhz

DRAM settings(these settings are default when I set the mem to 200MHZ as Nenu suggested)
CAS 3
Tras 8T
Trcd 3T
Trp 3T
Trc 11T
Trfc 14T
Trwt 5T
Twr 3T
Memory Timing 2T


So As u can see Only with bios 1010 and 1403 I am able to get PCI locked at 133 or lower mem setting.

@Nenu
For 1008 I have tried with Ht link 1x/2x/3x along with mem 100/133 all combinations but in all cases PCI is not locked.
It would be very helpful If u could post all the details abt your bios settings Where you managed to get past 240 HTT with mem at 133 Mhz
Also wanted to know what is the revision number of your motherboard.
Mine is showing 2.XX in the motherboard tab of CPU-Z.


@bail_w
tried with 2.65 V mem(from 2.6 stock) and 1.450V (from 1.4Stock) Vcore but it didn't have any effect on the problem I am facing. Should I increase more for memory .Don't know what is the safe limit for memory voltage increase.
 
You must log in or register to reply here.
Back
Top