View Full Version : hahah, It works!!! hook me up with some info?
shotclock
06-22-01, 02:24 PM
I just overclocked my Duron 750, just bought some thermal grease and went to put it on, didn't plan to overclock but what's the worst that could happen? 42$ cpu, so I grabbed a pencil and just started stroken....
was a little worried at first since my mobo started to make funny noises, the memery must of been loose fixed it then went to bios and started messing around....
I got a KA266-r which is can be easiely OC had it up to 910 140X6.5 but ME crashed on me (which it does at under normal conditions anyway) so I decided to lower the FSB to 133X6.5... with temps steady at 42
I'm not sure what I settings I should have? i.e. VMEM, CPU votage, mutipliers, cpu/sys temps and all that other stuff...
so give me some reccomendations, I want to OC to where it improves the sys performance but still want the chip have a life span to a year or more....
and someone tell me what good does it do to overclock? It shortens your CPU lifespan, and 100-200 mhz how much of a difference does that make?
go read the begginers section on the main page ..........WELCOME
Rob Cork
06-22-01, 04:09 PM
Actually there's some good questions here that I'm not sure can be answered properly in the beginner's section - namely those regarding the point of ocing, and its effectiveness. For most applications the bottleneck is some part of the system other than the cpu - for example, in games the 3d card is normally the bottleneck. My GF DDR is in my computer, so ocing the cpu from 600-1000 only gets me an extra 100 or so 3dMark points - but ocing the GF core by 20MHz gets about 600 points increase. Overclocking the cpu really helps though in encoding operations - at 600MHz, my FlaskMPEG times are over 10hrs, but at 1000MHz they drop to around 5 - quite an improvement!
As for the comment that your cpu's lifespan is reduced, this is probably the case, although in some cases (not extreme ocing) it may actually help increase the lifespan of the chip, as we ocers like to keep our chips a lot cooler than those in OEM machines. But either way, you will probably replace your cpu within a year or two, and given that the MTBF is about 5 years it shouldn't matter if you halve its lifespan :)
To answer your specific questions for your oc briefly:
VMEM is presumably the same as VI/O, (supplied to memory and PCI cards in particular) which should be 3.3V at default, though Asus set the default on my board (the A7V) to 3.54, so anything up to 3.55-ish can be considered safe. Raising it may help stability when FSB ocing.
VCORE can be raised to the max of 1.85 on your board safely as long as your cooling is good (I'd say temps below 50C and you should be fine - just look at my voltage!).
You've got the right idea running 133MHz fsb with a lower multiplier - just keep trying with that fsb - why not try somewhere between 133 and 140 (maybe you have).
Hope all of that helps a little bit... :-)
Well that was some pretty good advice and i have to agree. First of all you do definatly want to spend more time on the fsb then the multiplier. Heres my advice, first of all pick up a good hsf, OCZ Gladiator for example, then raise your voltage up to as high as you can while keeping your load temps around 50* celcius. As far as VIO i would think 3.6 or 3.7 is pretty safe. Take a look at this hsf roundup from Athlon OC (http://www.athlonoc.com/hsfroundup1.php) and decide for yourself what is a good hsf.
shotclock
06-24-01, 03:52 PM
Thanks for all the info....
I had it at 910 but it only worked half of the time, I lowered it to 890 it worked 90% of the time but I noticed that if I used any video apps i.e. Real player or Windows Media Player the system would crash....
It also crashes when I go to a webpage that has and video content.... tested it at normal speeds and everything works fine.
Anyone know why this happens?
Up the CPU core voltage to 1.85v and you can probly hit 950 mhz stable. You got a WBK i see so your cooling should be plenty enough for that.
Aaron
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.