how do you tell if you have a weak/crappy mem controller?
I know i've got a crappy clocking cpu, but i think the mem controller sucks so bad it's a black hole. (bh-5 known to work at 280+ has a hard time with 245)
is there any way to work around a weak controller?
245 is a known issue on most of the nforce boards... not the cpuOriginally Posted by Otaking71
what mobo?
duploxxx
the dfi lanparty sli-d
i can get to 243 error free in memtest on 3.0v dual channel.
245 and i hit a hard wall at any volts.
i'm on the 704 bios modded by tony.
provide the full mem-settings from bios pls...
also 243 with 3v is not bad at all, pls explain also how you test max mem, because otherwise whe have to start asking about htt multi, cpu multi down etc....
Last edited by duploxxx; 10-20-2005 at 03:49 AM.
well 245 with 3v is already good, so have you tried upping the voltage?
What cooling is on the CPU as well? Might try lowering the drive strength, could help.
Conroe E6300 ES
2x1gb Ballistix PC8000
Asus P5W DH Deluxe (1705)
Manli Geforce 7950GT 512mb
Hiper Type-R 480w
Samsung SP250
"What did the quantam duck say?" "Quark Quark"
guh...i don't want to have to fish all the settings..but basically all the main timings above the bank interleave settings have been tinkered with one at a time ...and verified with a full pass at 200 mhz in mem test (started with 2.9v...i've never run the mem with less)
then I started tinkering with max speed where i could get 25 error free passes in memtest ..test #5. i got errors at 236 (235 stable) at 2.9 v....went to 3.0...got to 243 fine...244 errored...3.1 works at 244 and then nothing I do lets me go any higher.
I know bh-5 isn't supposed to be affected by timings once you get them set....
hrm...i'll pull the settings when I get home later today.
I know the cpu clock to 2.6 ish (just above it) ghz as it's max prime stable speed. (damn 55c max tcase)
The mem testing is done with 8x multi and 4x htt multi.
Last edited by Otaking71; 10-20-2005 at 04:03 AM.
Just kinda disappointed that my first real a64 overclock (i've built quite a few a64s...that run stock....even a few x2s...don't bother with overclocking any computer that's not mine or a good friends) is going so sour. I know my mem is good. It's carried over from my recently retired p4.
AMD overclocking has always been very bad luck for me. Heh.
(been overclocking since the 386 days)
Last edited by Otaking71; 10-20-2005 at 04:49 AM.
200-e-2-2-5-2-7-11-2-2-1-a-e-a-0-a-a-8-n-6-16-d-16-04
bump
Have you tried swapping to the other slots? (ie yellow vs orange and vice versa).
Also, have you tried changing the sticks' position (ie put one in the slot nearer the CPU and the other in the other dual channel slot, then swap them and see which is better).
I have had some WEIRD issues with my BH5 and my Venice 3000 and DFI Ultra D, where I couldn't clock the CPU past 2.5 Ghz with the BH5 in the yellow slots, where I think I remember testing it to be better. When I swapped to the orange slots, hey presto, like a wall had been lifted.
As you probably already know, one stick will ALWAYS be slightly better than the other, so the weaker one should go closer to the CPU (something to do with trace lengths as I understand?).
Anyway, it worked for me (I am a fairly seasoned OCer too).
The only other thing to point out (in case you don't already know) is not to worry too much about the memory clock / speed on the A64 platform. Just get the CPU as high as possible. If you have to sacrifice 1 Mhz of CPU speed for 5 Mhz gain in memory speed, it isn't worth it. (Depends on the application I suppose, since MAJORLY memory-bandwidth limited apps may respond differently.).
See here:
http://math.gogar.com/athlon64.cgi
Last edited by Jimbo Mahoney; 10-21-2005 at 03:44 AM.
:: 3DMark01=66,732 :: 03=71,879 :: 05=26,413 :: 06=18,772 ::
Posting Permissions
Reply With Quote
