Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Subject: MOBO FSB vs CPU bus

Original Message
Name: LeBabouin
Date: July 14, 2007 at 12:48:09 Pacific
Subject: MOBO FSB vs CPU bus
OS: pro sp2
CPU/Ram: E6700/PC6400X2
Model/Manufacturer: me
Comment:
I though I would have to increase the motherboard FSB first to then be able to increase CPU frequency to get a CPU bus speed minor or equal to mobo FSB.

I think I'm wrong because increasing CPU MHz automatically increases mobo FSB.

Also motherboard is compatible 1066MHz and after 13% CPU oc'ing I get a 1204MHz FSB value and everything runs well (not better though).

I think I need some explainations. Would you please help me to understand the relations and actions between mobo FSB and CPU bus speed.

Thanks a lot!

GigaByte 3D Aurora
Asus P5WDHDeluxe RAID 0
Intel Core 2 Duo E6700
2GB DDR2 Twin2X 800MHz
nVidia GeForce 7900 GTX


Report Offensive Message For Removal

Response Number 1
Name: jam
Date: July 14, 2007 at 13:03:20 Pacific
Subject: MOBO FSB vs CPU bus
Reply: (edit)
They're basically the same thing, but it's much less confusing if you refer to them as they're actual clock settings, rather than the double-pumped or quad-pumped numbers.

For Intel CPUs:

533MHz FSB = 133MHz
800MHz FSB = 200MHz
1066MHz FSB = 266MHz
1333MHz FSB = 333MHz

For RAM:

DDR266 = 133MHz
DDR333 = 166MHz
DDR400 = 200MHz
DDR2-533 = 266MHz
DDR2-667 = 333MHz
DDR2-800 = 400MHz

You should always strive for a 1:1 CPU:DRAM ratio. If you have an Intel 1066MHz FSB CPU, your RAM should run at 266MHz. So if you have DDR2-667 or DDR2-800, you should change the RAM settings in the BIOS to match the CPU freq of 266MHz.

You've increased the CPU freq from 266MHz to 301MHz, therefore your RAM should also be set to run at 301MHz.


Report Offensive Follow Up For Removal

Response Number 2
Name: LeBabouin
Date: July 14, 2007 at 14:53:44 Pacific
Subject: MOBO FSB vs CPU bus
Reply: (edit)
Thanks for your answer.

Yes BIOS turned RAM speed automatically to the 1:1 ratio right to 301MHz.

How can I be sure that the other components such as DVD writer won't take disadvantage from the FSB increase?

GigaByte 3D Aurora
Asus P5WDHDeluxe RAID 0
Intel Core 2 Duo E6700
2GB DDR2 Twin2X 800MHz
nVidia GeForce 7900 GTX


Report Offensive Follow Up For Removal

Response Number 3
Name: LeBabouin
Date: July 14, 2007 at 14:57:11 Pacific
Subject: MOBO FSB vs CPU bus
Reply: (edit)
Sorry for double post, I forgot to mention I stuck the PCI and PCI-express speed to 33 & 100 MHz.

GigaByte 3D Aurora
Asus P5WDHDeluxe RAID 0
Intel Core 2 Duo E6700
2GB DDR2 Twin2X 800MHz
nVidia GeForce 7900 GTX


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: MOBO FSB vs CPU bus

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software



Version Tracker Pro
Keep your software current and secure, effortlessly

Click Here for a Free Scan

Driver Agent
Automatically find the latest drivers for your computer.
Click Here for a Free Scan



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

All content ©1996-2007 Computing.Net, LLC