Name: B2K24 Date: August 28, 2006 at 14:11:06 Pacific Subject: CPU config Locked in BIOS OS: winXP pro CPU/Ram: P4 2.8GHZ
Comment:
My mobo is P4v533-mx I had a processor professional installed today but now I can't seem to take advantage of it. My bios reconizes the new 2.8 as does CPU-Z but due to the cpu config being locked its still running at 1400 MHZ frequency!!!!
The info in clocks part of cpu-z has not changed from using the old processor
I should be getting a hell of alot better with a P4 2.8 GHZ 800 bus processor and 533/400 bus mobo.
I flashed the bios and updated to the latest and the cpu config section is still dammed locked Can anyone help please. bios american megatrends inc. 1010.003
P4V533 means 533Mhz FSB max, buying a 800Mhz FSB CPU and put it into a 533Mhz FSB max mobo get you no where. The max you can run would be 133 x 14 = 1862Mhz...
TMP-Man
Asus P5P800-SE PAT P4 506 @ 4009Mhz 1.3625v Thermaltake CLP0024 w/ 1700RPM 92MM + AS5 2GB OCZ 2-3-2-5 DDR400 120GB/300GB 7200RPM HD MSI 6600GT AGP 565/1100 VF700 ALCU AS5
Dude, there's nothing to unlock. Your 2.8GHz (2800MHz) CPU is supposed to run at 14 x 200MHz, but your motherboard doesn't support it. The fastest FSB a 533 board can support is 133MHz, so as was stated above, 14 x 133MHz = 1.86GHz. Your FSB is currently set at 100MHz, that 's why your CPU is running at 1.4GHz. There's probably a FSB jumper on the motherboard that has to be changed to set it to 133MHz. But with your current board, you will NOT be able to run the CPU at 2.8GHz...you'll have to get a board that supports 200MHz (800FSB)
ok thanks alot for clearing it up im sorta new and the numbers are damn confusing. They don't make that clear on the site
(Specification CPU Socket 478 for Intel Pentium 4/ Celeron up to 2.8GHz+ Intel Hyper-Threading Technology ready Chipset
VIA VT8751 (P4M266A) VIA VT8235 Front Side Bus
533/400MHz)
I didn't quite understand the 533/400 concept anyway ill look through the manual for the jumper is there by chance a program that will change it to 133 sorry for being dumb
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