quick question

[patcheney]

i have just built this new system:

amd64 3200+ winchester 2.0G 512k L2cache
Crucial CT6464Z40B 512mb DDR 400MHz PC3200 CL=3 Memory Module *2
asus a8v deluxe mobo
.....

i have only manually set cpu fsb to 220mhz and disabled 2T, with everything else set to automatic. and memory was automaticlly oc ed to 220mhz as well by mobo.
everything seems to be working fine in xp , except when im running stability test, super pi would gimme some sort of error after a few loops(32M), and prime95 would gimme a error too
as far as i'm concerned, my setting should all be okay and and stability test should survive.
any ideas what's causing the problem? and what should i try to do to get my system stable?
thanks for your help!!

 

[o1die]

I would set your cpu voltage to 1.55 and your cpu fsb to 250. 250 seems to be the sweet spot for both p4 and athlon 64 systems with a good overclocker.

 

[patcheney]

Originally posted by: o1die
I would set your cpu voltage to 1.55 and your cpu fsb to 250. 250 seems to be the sweet spot for both p4 and athlon 64 systems with a good overclocker.

lol, i wouldnt wanna push my cpu tpp much czo last night i had some scary moment when cpu temp just goes up like rocket and i had to turn it off quick.....

 

[patcheney]

well, switch to 2T decreases my performance while system still is unstable.....
perhaps i should try down the multiplier and having the cpu to work at the speed it should only with a little bit higher FSB

 

[Yanagi]

First off you try to isolate the problems. Using the ram dividers in your BIOS set it to 133 (sometimes called 2:3 or something like that)

Make sure you up the vcore a notch if you're still getting error.. If it passes now with the RAM divider set to 133 MHz then it is your CPU. Up the VCore a notch to see if that helps (Watch the temps though)

Now Lower the multiplier and UP the FSB (or is it called HTT on the A64s?) When stablilty tests fails you know you've achieved your rams max.

Have you tried running stability tests at stock? Do you get these errors at stock?


It might be the ram. It might also be the CPU. Its all about isolating the problem