Problems with new memory (2x256 BH-5 Buffalo ddr400)

Brule

Golden Member
Apr 23, 2004
1,358
0
76
I just bought 2 sticks of RAM listed in the title off of a forum. The stickers clearly state Buffalo pc3200 cls 2.5 2x256 matched pair. The ram itself is imprinted with Winbond 252WE W942508BH-5 and are in great shape. To take advantage of my newly aquired Soltek A64 board I bought these to run at pc3200 speeds with the ability (down the road) to tweak and OC, replacing the pc2700 I previously had installed.

Now the problem. I cannot get the RAM recognized as pc3200. The BIOS options include max memclock which is 100, 133, 166, or auto. (200 tops according to specs before any tweaking) I can't seem to get the ram to run at 1:1 although through OCing the A64's FSB (or HTT I guess) it runs fine at higher speeds. All diagnostic software reads it as pc2700 ram. (BIOS, Sandra, Everest, CPUID)

CPU-Z speed
CPU-Z memory

I've tried both sticks at once as well as either stick at a time. I know that this CPU and/or board has been somewhat picky concerning RAM before from other posts. Is it just a compatibility problem or some setting? (everything's auto configured, HT at 4) Or am I just an A64 noob and should be beat for making an obvious mistake? Any help would be greatly appreciated.
 

montag451

Diamond Member
Dec 17, 2004
4,587
0
0
wait for other replies before you do this:
reflashing bios with newer version may help
 

Brule

Golden Member
Apr 23, 2004
1,358
0
76
Originally posted by: montag451
wait for other replies before you do this:
reflashing bios with newer version may help

I have v. 1.2, which is the latest BIOS I can find. Reflashing it is certainly an option, but (as you said) if there's something else I'm missing I'd rather not risk reflashing it. Thanks for the response, I finally have some BH-5 to try out (with all its hype) and it doesn't work as well as Backwood Bubba's generic pc3200 at this point. :(
 

Brule

Golden Member
Apr 23, 2004
1,358
0
76
About ready to ditch the RAM and move on. Before I do, any advice? Would there be hope in a (near) future BIOS update that would help out?