memory incompatibility?

Associate
Joined
26 Jun 2006
Posts
38
I noticed the other day in the bios that my memory is running at ddr333 when i have 2 sticks of 512mb geli value i bought from here and 1gb of ddr400 that came with the computer. I havn't overclocked anything and i tryed to set the memory to ddr400 but then it wouldn't post. It says in bios that the 1gb stick is in slot 1, and the geli sticks in 2 and 3. Shouldn't the geli set be installed in 3 and 4 because of the dual channel memory slots, would that be causing the problem? I have a asrock 939NF4G-SATA2 motherboard. Any help would be appreciated. :)
 
Is your 512mb sticks also DDR400? if not then they wont run at that and your 1gb stick will run at the same speed as the 512mb sticks.
 
Using more than 2 memory modules with Winchester or Newcastle cores will cause the system to default to 333Mhz 2T due to limitations of their memory controllers. Newer E revision cores (Opterons, Venices, San Diego and X2s) should default to 400Mhz 2T.

There's nothing you can do about running at 2T, you can try setting your memory back to 400Mhz, most of the time this will work fine.

The difference between 333Mhz 2T and 400Mhz 1T is pretty hefty I would have thought, so getting to 400Mhz even at 2T is worth a shot :)
 
But when i try to set the memory clock to ddr400 the computer refuses to post. Would it work if i set the ma timing to 2t rather than auto? If i reinstall the ram in the correct slots will that help it post?
 
happysappy said:
But when i try to set the memory clock to ddr400 the computer refuses to post. Would it work if i set the ma timing to 2t rather than auto? If i reinstall the ram in the correct slots will that help it post?

Definately try setting 2T.

What core is your CPU (you can use CPU-Z to check).
 
I dont know because i'm using a different computer at the moment but i'll be able to check in a few days. Will it be harder for a cpu with the Winchester or Newcastle core to change the settings? Or are you saying if its a san diego ect it might be because of where the memorys sloted or perhaps even the memory itself? :eek: I'll have another go when i check what core i have, hopefully it'll work this time. Thanks for the help.
 
Back
Top Bottom