View Full Version : PII 450 o/c'ing
Longshot421
3rd December 2001, 02:54 AM
I'll try this post again, I fear it may have been buried under off topic material. Not that that's a bad thing...
:confused:
Hello there, I have a rig I'm donating to my girlfriend with an FIC VB601 mobo and a PII 450. The BIOS lets me set the CPU clock speed at 66, 100, 112 or 133. I have successfully o/c'ed to 504 by changing the bus speed to 112. However, I get some little hiccups in the graphics. Can I change the multipler from 4.5 to 5 (selectable with dip swirches on the mobo) and leave the bus speed at 100 to be more gentle to my RAM and graphics card?
Any help much appreciated. :D
bldegle2
3rd December 2001, 02:52 PM
the x's are locked, have been since for years,
all you can do is the FSB adjustment to 504.
the PII's varied all over the map, i have had several that struggled mightly to do the 504, then i got one of the last issues and it did a nice 600 (133 FSB), so it was a PII600EB, if they had made any on purpose.
better cooling and raising the vre (juice to the CPU) just might stabilize the sucker @504.
good luck.
baldy
:cool:
Longshot421
3rd December 2001, 04:20 PM
Thanks baldy. So the multiplier is locked on the CPU itself? Sneeky. Oh well, as you suggest, I will try better cooling (both on the cpu and video card) and see if I can get more Porsche and less VW. ;)
Thanks again
Asha
4th December 2001, 11:37 AM
Try changing the ram timings in the bios and maybe an other graphics card.
Asha
Longshot421
4th December 2001, 03:50 PM
I'm not sure I can change the RAM timings in the BIOS, but maybe I'm not looking the right place. I'll have a look when I get home (boldly wasting work time cruising the Ninja boards right now :D ) I know I can change the speed of the FSB, but where would I find the RAM timings and what kind of changes would you suggest? Thanks for the reply
:xborg:
tripodal
7th December 2001, 07:21 PM
i run a asus p2b ds with 2 p2 450's@504 it is a speed machine for sure, but i am going to move it to another asus board with rambus ram and MANY more settings for over clocking, i will let you know what i get when i am done.
cooling is a HUGE issue in my case, i would definatly reccomend finding all aluminum heatsinks on your processor as they are about 2x as effective as the steel ones, they come with normally.
all and all, i plan to use the 2.2 v, mod. and hit 550mhz minimally.
good luck oc'ing
Longshot421
18th December 2001, 07:32 PM
:confused:
Hey, here's something you might find interesting, I hadn't used my 1.44 in a while (since I o/c'ed actually) and when I went to use it: no workie. I rebooted, no good. Power off check cables, etc., re-start. Still no workie. Reset bus speed to 100 MHz, floppy work. Weird, huh? :)
tripodal
19th December 2001, 04:58 AM
never imagined that. what bus speed were you running at when the floppy stopped working? did you try lowering the mult.. to make it to a full 133.. never thought that the bus speed would also affect the floppy...
though it sounds like that now
Longshot421
19th December 2001, 10:11 PM
OK, re-overclocked (FSB = 112 MHz) and the floppy works OK now. SO I think I just have an intermittently crappy floppy drive and that the FSB speed doesn't affect the floppy, just it's inherent crappiness! :D
tripodal
20th December 2001, 12:40 AM
Originally posted by Longshot421
OK, re-overclocked (FSB = 112 MHz) and the floppy works OK now. SO I think I just have an intermittently crappy floppy drive and that the FSB speed doesn't affect the floppy, just it's inherent crappiness! :D
inherent crappiness... quite a term, it fits in with just about anything really? seems like quite a plague. the first diesease of the new millenium..... "Inherrant Crappiness"
Longshot421
22nd December 2001, 04:55 AM
:D I'd never thought of it as a disease, but from now on, similar problems will be diagnosed as suffering from I/C.
Merry Christmas everyone! :)
tripodal
22nd December 2001, 07:35 AM
oh no ! the new DDR MOBO is suffering from I/C get me the sledge hammer stat!
that'll fix her.
Longshot421
27th December 2001, 04:37 PM
:) Ha! I work with a couple of guys who support that philosophy. "When in doubt, hit it harder. If that doesn't work, get a bigger hammer." Good to hear we're working on a cure for I/C. :D
tripodal
27th December 2001, 10:31 PM
It was only a matter of time really, look at microsoft. at first dos sucked.. but then by dos 6.2 it was bomb.. and then win 3.1, no wait, lets not go there.
win 95! BLAH
win 98 better
win me ok i guess
win 2k finally
win xp... havnt decided yet
seems like microsoft is becoming aware of I/C, and innoculating its products against this disease.
vBulletin® v3.7.3, Copyright ©2000-2008, Jelsoft Enterprises Ltd.