View Full Version : Increasing Multiplier
Ok so i finally decided to take the plunge tonight and try OCing my CPU. I've already OCed my graphics card so I was feeling brave. First thing I did tho was try fiddling about with my ram latency speeds before I messed with the FSB at all. My CAS is set to 3, tried to go to 2.5 but even with increasing the voltage to the ram to 2.7v and lowering the FSB no joy. Tried adjusting the other latency settings instead but kept getting errors and lockups when I ran 3dmark05 so I decided to set them back to their defaults and concentrate on the cpu and fsb.
After a while and some very cautious stemps I've increased my athlon64 3200+ from 2000MHz upto 2100MHz with a FSB of 210MHz(mulitplier of 10). So next I thought I would try increasing my multiplier to 10.5 and see if I could go much further with the CPU, if I can work out the CPU's limits then the FSB limits then I can do a balanced OC between both. So changed the multiplier to 10.5 and booted up. First thing I do is open CPU-Z to check the settings but the multiplier is still set to 10. I've checked my motherboard manual and a few sites with info on it but I can't see where im going wrong. Any ideas as to how I can increase the multiplier? Im using a DFI Lanparty UT nF3 250GB.
At 2100GHz my CPU temps don't seem to rise above 45c so im hoping I can still increase it a little way. My system temps are a little high at 40c max tho so I think I'll be looking at replacing that northbridge HS with a HSF, any recomendations on a good one thats also pretty quiet?
TIA
Nick
Any ideas as to how I can increase the multiplier? Im using a DFI Lanparty UT nF3 250GB.
Is that a ClawHammer or a Newcastle?
If it's a Newcastle try 11 (i.e. stock multi) - AMD64 doesn't support 0.5 multis according to AMD.
If it's a Clawhammer 10 is as high as you can go on a 3200+.
Firelord
12-03-2005, 10:11
All non Athlon 64 CPUs are multi locked up but ok going down the range.
It is only Athlon 64 FX (FX51 s940, FX53 s940, FX53 s939 and FX55 s939) that you can go up the multi ranges into the 20s
Is that a ClawHammer or a Newcastle?
If it's a Newcastle try 11 (i.e. stock multi) - AMD64 doesn't support 0.5 multis according to AMD.
If it's a Clawhammer 10 is as high as you can go on a 3200+.
Cheers Buff, it is a clawhammer im using so guess I'll just trey to increase the FSB some more and see what I can get.
I was doin some research and it turns out that with the original BIOS DFI released there was a problem with the temperature readings that they were showing higher than they actually are. DFI haven't releaseda BIOS other than the original so they have no fix...however I found a beta BIOS. It fixes a few bugs in it including the temperature readings and also had a memory test built into the BIOS which makes OCing the ram easier. If anyone is intereseed then you can download the beta BIOS here (http://www.ocforums.com/showthread.php?t=328318). I've installed the forth revision and had absolutely no problems and the temperature is now showing much lower, ~30c idle and the max I've seen it on load is 36c.
I would quite like to reduce the timings on the ram, it isn't the best and im planning on getting better stuff in the near future but I'd like to see what I can get outta this, its timings are 3-3-3-8. The problem is that as soon as I decrease the timings at all I get crashes or memory locks. I've tried increasing the Vdimm to 2.7 volts but it makes no difference. My board allows me to increase the Vdimm upto I think about 3.3v(4v if I modd the 4v rail) but im not really sure how high I should increase it, bit weary about increasing it anymore at all. What would you say was the max safe voltage could really look to up it too?
Cheers
Firelord
12-03-2005, 12:24
You'll be alright running up to 3.2v aslong as you have got a fan blowing over the memory or at least got decent air running through your system :)
You'll be alright running up to 3.2v aslong as you have got a fan blowing over the memory or at least got decent air running through your system :)
Yeh I gots two 92mm fans on my front and rear of my case and got sinks on the RAM
Firelord
12-03-2005, 13:04
It should be ok then :)
Hmm, I wouldn't make such a sweeping statement as that. A lot of Hynix ICs and some Samsung stuff for instance really doesn't like extra voltage. What is the RAM? It's the memory modules on it that count.
Firelord
13-03-2005, 09:03
It may not make any difference to the memory in terms of OCing but it could so it shouldn't be a problem to run it at that. If it was a problem then they wouldn't give you that much voltage to play with!
The DFI nForce 4 boards give you up to 4V. Do you consider that safe since they give you it?
More than 3V will kill some types of Mosel Tech based RAM. DFI boards are enthusiast boards, you're expected to know what you are doing. I'm not saying he shouldn't raise the Vdimm, just that he should be cautious and that if we knew precisely what type of RAM it was then we could give more information. Being cautious won't kill anything.
Firelord
13-03-2005, 15:36
The DFI nForce 4 boards give you up to 4V. Do you consider that safe since they give you it?
More than 3V will kill some types of Mosel Tech based RAM. DFI boards are enthusiast boards, you're expected to know what you are doing. I'm not saying he shouldn't raise the Vdimm, just that he should be cautious and that if we knew precisely what type of RAM it was then we could give more information. Being cautious won't kill anything.
No one said about going up to 4v unless I can't read :confused:
I have overclocked all sorts of memory and stuck all sorts of volts through them and they have all survived.
When it comes to overclocking you raise little by little...you don't just whack it straight up. He asked for a safe limit and thats what was given...
reflex_1
15-03-2005, 13:11
have you changed the HTT to 4x?
Havent changed the HTT multiplier. I've increased the FSB to 210MHz giving me a clock speed of 2100MHz. I did have it higher, but if I increase the FSB much over 210MHz the RAM seems to become instable. At the moment at idle im getting CPU temps of about 28-31c and on load I haven't seen them go over 37-38c. I've tried adjuwsting the RAM latencies but even with the Vdimm upto 3.2v the slightest adjustment of any of the ram settings cause lockups and crashes.
Its a pity I couldnt increase the multiplier, if I could bump the multiplier upto 11 and take the FSB back down to 200MHz, im pretty sure I could still get some more juice out of my CPU. I hope to replace the RAM in the not to distant future, go for something like the crucial ballistics, i've heard that stuff is pretty good, or mabey some crossair xms stuff.
Then when I get my watercooling in the summer I can squeese some more juice outta my machine.
P.S. occording to cpu-z my RAM manufacturer is Nanya Technology, part number is M2U51264DS8HB3G-5T. It was some Kingston stuff I bought off eBay. It's done me well enough so far, just the latencies could be a lil better.
I'd suggest dropping your HTT to 4x, use a ram divider to drop the ram frequency and leave the ram timings set at SPD or auto. This way you're only clocking the CPU and should be able to see what it can do. Once you get to a nice speed (hopefully), then you can play with the ram timings after that.
I hope to replace the RAM in the not to distant future, go for something like the crucial ballistics, i've heard that stuff is pretty good, or mabey some crossair xms stuff.
Well, thats the RAM problem sorted, finally decided to bite the bullet and get myself some decent stuff. Purchased some OCZ4000 EL Gold (2x512MB), so now I can see how good this baby is and not have my RAM holding me back.
Cheers Snowman
Well with a little playing about with the DDR/FSB ratio, I've got my clock speed upto 2200MHZ with the FSB still being at 200MHz. Had to increase my Vcore upto 1.58-1.6V and my Vdimm to 2.9V. Runs at about 32c idle and 42c on load. Once I get my new RAM then im going to try in upping the speed some more but I will also be able to increase my FSB rather than keep it at 200MHz as it is DDR 500 and it has better timings too.
On the timings issue, is there a formula to decide what is best - ie does 2-4-4-8 perform better (with an athlon XP) than 2.5-3-3-6? Is it a simple case of the lowest result when you multiply of all the numbers?
The most important one is the CAS latency.
vBulletin® v3.8.1, Copyright ©2000-2013, Jelsoft Enterprises Ltd.