-
1700+ at the limit
ok so i admit in this field im a bit of a noob
i have a athlon 1700+ on a asus a78v8x-x mbo
adn 256mb of ram
i read a bit about over clocking, and decided to experiment
the fsb was 133 wen i started and the cpu speed was 1.47ghz
ive been putting it up in increments and im now at 180 and the cpu is at 1.98ghz
i think this si as far as i can go, but what is this multiplier stuff, can it ssraise the speed, what should i do next, or is there nething i have missed out?
please help
richard evans
-
1) What RAM are you running.
2) Try and get another 256mb of the same RAM as you have now.
Lower the mutlipler to 9.5, and the FSB:RAM is set to 6:6. Then try and get the FSB as far as you can go. If the RAM is PC2700 i would suggest putting 2.7v at about 185mhz (FSB.) But if it is PC3200 then dont worry about it, as that is designed to run at 200mhz anyway.
Once you have got the FSB as far as possible, try and increase the Multipler. This will probably involve upping the volts. Dont go above 1.85v, go until the volts dont make a large difference ~100mhz as any less you wont really notice.
Summary:
Lower multipler
Up FSB
Up volts (RAM)
Up mutlipler
Up volts (CPU)
...........and see how far you get :)
Hope that is of some help.
Will
p.s. is it possible to post the code on the chip?
-
256 mb 333mhz pc2700 dimm
thats wot the ram is
i understood all u said apart from thsi bit
"If the RAM is PC2700 i would suggest putting 2.7v "
wot dose that mean, im gonna decreae ther multiplier to 9.5 to see if it makes a dfference
-
ok rubbishrubbishrubbishrubbishttttttttttttt
when i restarted to change he multiplier, in my bios i find sum things greyed out, and the cpu speed is 1916 and i cant change thee multiplier or the fsb or the vcore setting, hat the fcuk, please help asap
-
ok restarted and i can change it
sorry ive put the multiplier down to 9.5 and its booted up, ill try changed the fsb now
-
Well pc2700 is designed to run at 333mhz (or 166mhz FSB [as DDR is 2xFSB]) so to get the RAM to 400mhz (pc3200) i would suggest putting 2.7v through it when you hit 185mhz FSB. Otherwise you may find that you cant boot before you get to 200mhz FSB.
-
w8 i have a grweater problem now
i did like u said
took the multiplier from 11 down to 9
got the fsb up to 200, IT WOODNT TAKE NE MORE
so i then upeed the multiplier to 10x and the vlotage to 1.65, and it sorta crashed, lol and now it wont boot at original settings, fsb = 133 mul = 11 vol =1.6,
so im wating for it to cool, cos its pretty warm atm, ne advice?
-
if it doesnt boot, turn the comp on and hold the Insert button on the keyboard.. failing that, unplug it from the wall, plug it back in, and try again.. and finally, failing that, reset the cmos by either connecting the 2 pins, or remove the battery (check your manual first tho)...
good luck with the overclocking :)
mark
-
ok ive tried your advice and ive done what you said, it still doesnt make a differnece,
i took it in to my network administrator at school and he said it probly isnt and hardware damaged, but that the operating sytem just threw a wobbler.
maybe this is a newb question but what should i do, as i cant currently get hold of an xp cd to put in and repair the os (win xp pro)
can i make a boot disk or something?
i tried making one from my winn2000pro laptop but it wouldnt work in it,
ne help wouldnt be greatly apreciated
cos i have a hell of a lot of coursewrok to do, and its all on the pc thats down atm
thanks
richard evans
-
Ask a mate if you can borrow their XP disc? And use your own CD Key of course.
Better get working on that coursework also, its gonna take a hell of a lot for you to pass english.
Cr4iG
-
lol,
thats the gay bit, my mate who installed xp and has the xp cd and product key, has buggered off on holiday, is there any other alternatives?
-
u sure u reset cmos mr anderson, cause ur damn unlucky if u managed to damage software/hardware because of boot up failure, cmos usually sorts it.
-
definitly, 100%
what happens is after it shows the post krap, it gives me a list of options, safe mode, safe mode with comadn prompt, last known configuration, or start windows normally, i pick normally, and it brings me to the windows xp loading screen for 1 second, the flashed white and the computer restarts,can anyone confirm that these actions, are most likely the os throwing a wobbler?
-
i havent read this thread properly, but it seems youve just managed to corupt your windows install..... this would be caused by runing your ram or northbridge to fast - they get unstable andwill corrupt everything sent to them...
next time use memtest86 to make sure its compleatly stable before booting windows. i would get that app and run it anyway, find out what your max stable is, then resinstall windows over the top of what youve got, it should fix all the important windows files, and youll be able to recover whats left... or maybe a better way if youve got a spare hdd would be to install onto that, which would leave your corrupted install as-is so that you can get any important files back. if the filesystem has got b0rked then you dont have much chance of getting any files back...
-
Yeah, sounds like your windows install is screwed. When you get the disc/key, do a repair install. They've always worked well for me.
Guys, you're giving him poor advice here IMO. He's got a KT400 chipset board, so it's not going to like FSBs of 180+ much. My advice mate would be to set the FSB to 166, and then increase the multiplier as far as you can (more than likely you won't be able to go above 12.5 with the chip as is). Then, if it's still stable at 2.083GHz (which is 12.5x166), raise the FSB in small increments. If you can get to 180 you'll be running at 2.25GHz which is a pretty nifty overclock. Then, run Memtest85 and the Prime95 Torture Test to make sure your system is stable. Loop 3DMark2001 to make sure your video card is happy running at a high PCI bus speed.
Rich :¬)
-
wouldnt bother with 3dm2k1 for benching really... well depends on the card. ive only ever used it for testing overclocked gfx cards, but 3dm2k3 is better for finding p/s or v/s errors. i would suggest finding the max fsb with your mobo, but maybe not as pci will cause loads of problems if you go too high....... so best run the pci within 5% of spec and use max fsb you can with that...