Name: protohunter Date: November 11, 2007 at 03:59:06 Pacific Subject: Ram FSB question OS: XP CPU/Ram: Pentium D 3.0GHz/1GB
Comment:
I have a question, I have a Pentium D said to run on an 800mhz fsb however my ram is DDR2 PC2-4300 rated at 533mhz. Does this mean that my cpu is not running at the right fsb also?
Sorry if I sound like a noob I just don't understand DDR that much. I'm too used to the old P3 days where the cpu fsb and ram ran at the same speed.
"I'm too used to the old P3 days where the cpu fsb and ram ran at the same speed"
The CPU & RAM should run at the same frequency. Your Pentium D actually runs at 200MHz, not 800MHz. 800MHz is the effective speed due to "quad pumping". If you check the settings, you'll find your CPU is clocked at 15 x 200MHz.
Your DDR2-533 RAM actually runs at 266MHz, not 533MHz, with 533MHz being the effective speed due to "double pumping".
In other words, your RAM frequency is running faster than your CPU frequency. Your current CPU:DRAM ratio is 200:266, or 3:4. A 1:1 ratio is considered optimal.
Well I can't change anything like that in the bios because I have a Comcrap computer, however I did read the manual and it said that it does support Core 2 duo Cpus.
I sometimes wonder if this is why I never quite got the speed I expected out of my new machine (new in 2005 anyway).
HP shipped it from the factory with PC3200 memory that gives me an fsb:dram ratio of 4:5. It's a moot point now because I'm not about to change out the modules, but I have often wondered if my performance suffered slightly as a result.
I realize these manufacturers throw in whatever bulk memory is cheapest at the time and I've never had a problem with the machine. But I've often felt it should be running faster.
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