Name: pcnooby Date: April 15, 2008 at 01:03:17 Pacific Subject: ram mhz and fsb OS: winxp pro CPU/Ram: 2 x1gb geil/ intel core 2 Model/Manufacturer: think.. ASrock 4coredual-
Comment:
on cpu-z it says my ram is running at 200mhz freq it should be running at 400mhz, both of them and my bus speed is running at 255mhz should be 266mhz :P not much but yh and i want my ram to run at 400mhz but i cant overclock my bus over 280mhz because my mobo is poo so is there anything i can do other then get a new pc to get my ram to run at its max. if anyone can help would be great i have been looking around google etc i probz didnt look hard but had a little look tom get help couldnt really so i came to this website. also im new to overclocking :P so i dont know much.
With a Core 2 system, you should keep the RAM frequency in sync with the CPU frequency. So even though your DDR2-800 RAM is rated to run at 400MHz, it should be run at 266MHz to match your CPU. Try manually configuring your BIOS settings.
Your ram is ddr so 200 is 400mhz effective, follow Jams advice and set it to 266 which would be 533 effective.Your ram is not running 1:1...this equals a performance penalty
The difference is that normal ddr ram goes as fast as 400MHz (real 200MHz) and your ddr2 ram is build for up to 800MHz (real 400MHz).
The others are right that you should run your ram in sync with the cpu. The problem is to know the right frequency. For example, if your intel core 2 duo or quad cpu has a fsb of 1066MHz then the ram should run with 533MHz (real 266MHz). Two ram sticks together in a dual channel ram setting give you the 1066MHz to run in sync with the cpu.
Yes, I know it's not totally exact to add those ram frequencies but that's one of the ways to figure it out! ;)
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE