Do i need to up the CPU FSB voltage went overclocking ??
- Thread starter chaparral
- Start date
Thanks for the reply...darwin said:
I can get to 3200mhz no problem with the CPU voltage at 1.4 and the FSB voltage on auto....But am getting lockups when i try an overclock to 3500mhz and am looking what else i can try to do to get a more stable overclock at 3500mhz..
Last edited:
darwin said:
I just tryed my C2D6600 cpu at 3500mhz with
1.5volt cpu core voltage
1.4volt cpu FSB voltage
2.0volt memory
1.525volt MCP
memory at 800mhz 4-4-4-12 unlinked
But the system auto restarted in the last cpu test in 3dmark05
Last edited:
Associate
- Joined
- 20 Sep 2006
- Posts
- 1,418
- Location
- Southampton, England
what is your NB temp? like with the CPU, under most normal cooling methods the temps kick up well before the volts by themselves become dangerous.
i need 1.55V NB to hit around 450 FSB with my P5K-Dlx, and that 680i is running at 1.4V atm. Not sure how voltage dependant the FSB is, but some mobos can need quite a lot to hit decent speeds.
Another test, drop the CPU multi a notch and re-test, if you are still getting probs then its the NB not the CPU core that's causing probs, it sure as hell wont be the Mem if you are running unlinked. If that is the case, push the vNB up a notch and try and find the max FSB at that setting (watching the NB temps with whatever monitor you use), which will give you a range up to which you can push to explore the overclocking potential of your CPU without getting errors that COULD be CPU or NB based.
Remember overclocking 101; find the INDEPENDANT limits of each component in your system before trying to find the best stable mix of those maximums.
eg:
Step 1: set mem to max safe volts for your DIMMS, with the slackest timings you are prepared (5-5-5-18 is about the furthest i go), up the mem multi, drop the CPU multi, and raise the FSB notch by notch untill you find the max stable mem speed (with raised multi this should not be FSB limited), or for RD600/650i/680i unlink the mem and find the max stable async speed.
Step 2: set mem to 1:1 with loosest timings (or async if poss), raise NB to max safe volts, drop CPU multi, and attempt to find max stable FSB for the board, or the max stable mem speed if 1:1 (may still be CPU limited, as some cpus have an "FSB wall" past which further increases are unstable).
Step 3: set mem to 1:1 with loosest timings (or async), vNB to max safe, vCore to max safe, CPU multi to max and slowly increase FSB untill you either hit your FSB limit, or you get instabilities or unsafe load temps.
Step 4: mix & match, try to get the best mix of CPU speed and mem speed using the avaliable combinations of memory and CPU dividers. Optimum is of course having max mem @ 1:1, with high FSBs/low CPU multi, but you may have to drop the FSB, and increase the CPU multi/Mem divider to hit the optimum mix. Having Async mem can be a real benefit if you want to max your mem, or have poor OCing mem, as you can optimise the CPU independant of the Mem.
Step 5: Long stability test of completed combined OC
Voila..... beautiful stable, maxed out system!
i need 1.55V NB to hit around 450 FSB with my P5K-Dlx, and that 680i is running at 1.4V atm. Not sure how voltage dependant the FSB is, but some mobos can need quite a lot to hit decent speeds.
Another test, drop the CPU multi a notch and re-test, if you are still getting probs then its the NB not the CPU core that's causing probs, it sure as hell wont be the Mem if you are running unlinked. If that is the case, push the vNB up a notch and try and find the max FSB at that setting (watching the NB temps with whatever monitor you use), which will give you a range up to which you can push to explore the overclocking potential of your CPU without getting errors that COULD be CPU or NB based.
Remember overclocking 101; find the INDEPENDANT limits of each component in your system before trying to find the best stable mix of those maximums.
eg:
Step 1: set mem to max safe volts for your DIMMS, with the slackest timings you are prepared (5-5-5-18 is about the furthest i go), up the mem multi, drop the CPU multi, and raise the FSB notch by notch untill you find the max stable mem speed (with raised multi this should not be FSB limited), or for RD600/650i/680i unlink the mem and find the max stable async speed.
Step 2: set mem to 1:1 with loosest timings (or async if poss), raise NB to max safe volts, drop CPU multi, and attempt to find max stable FSB for the board, or the max stable mem speed if 1:1 (may still be CPU limited, as some cpus have an "FSB wall" past which further increases are unstable).
Step 3: set mem to 1:1 with loosest timings (or async), vNB to max safe, vCore to max safe, CPU multi to max and slowly increase FSB untill you either hit your FSB limit, or you get instabilities or unsafe load temps.
Step 4: mix & match, try to get the best mix of CPU speed and mem speed using the avaliable combinations of memory and CPU dividers. Optimum is of course having max mem @ 1:1, with high FSBs/low CPU multi, but you may have to drop the FSB, and increase the CPU multi/Mem divider to hit the optimum mix. Having Async mem can be a real benefit if you want to max your mem, or have poor OCing mem, as you can optimise the CPU independant of the Mem.
Step 5: Long stability test of completed combined OC
Voila..... beautiful stable, maxed out system!
My FSB voltage is still at 1.2v and ive OC'd my e6600 up to 3.2ghz
I have asked about FSB voltage before and no one replyed with an answer as to what it was for
Does this heat the north bridge up?
How can i monitor north bridge temps?
I have asked about FSB voltage before and no one replyed with an answer as to what it was for
Does this heat the north bridge up?
How can i monitor north bridge temps?
ASH1982 said:
Maximum Recommended Voltages
Note: Be very careful when increasing voltages as setting them too high can destroy the
processor and other components on the motherboard.
Below is a list of the safe, maximum voltages that should be used for overclocking.
Any voltages not mentioned are best left at their Auto setting.
CPU Core: 1.58750v
CPU FSB: 1.5v
Memory: 2.3v
nForce SPP: 1.50v
Taken from here http://www.nvidia.com/docs/CP/45121/nforce_680i_sli_overclocking.pdf
The nforce SPP voltage is something to with the northbrige chip..ASH1982 said:what does that mean ive no idea what the nForce SPP is
Taken from here http://enthusiast.hardocp.com/article.html?art=MTIwOSw0LCxoZW50aHVzaWFzdA==
Last edited:
chaparral said:Should be fine as long as you keep the fan running...
That cpu cooler you have looks big there
Dude you are my own personal jesus christ
by posting the link to that overclocking guide up you have enabled me to break through a little problem I was having trying to go above 3.1ghz
I think the only thing I have to worry about now is my temps as they are reaching 55oc at load for 3.3ghz
I think the problem was my north bridge voltage, i restored it to auto like the guide sugguested and its all cool, its hardly even increased the voltage but its more stable!
Also looked at my south bridge voltage 1.5v is my lowest setting
Associate
- Joined
- 20 Sep 2006
- Posts
- 1,418
- Location
- Southampton, England
as i said, keep an eye on temps, as voltage rarely kills components on its own, rather the temps CAUSED by increased voltage do. As long as the temps are good, you are good to go!
Some rare cases (like some reported Micron mem faliures at mid-high voltages) can be contributed to voltage alone, but generaly electromigration, though a negative influence on the life expectancy of a component, will be unlikey to kill it ON ITS OWN before you are likely to replace anyway.
Some rare cases (like some reported Micron mem faliures at mid-high voltages) can be contributed to voltage alone, but generaly electromigration, though a negative influence on the life expectancy of a component, will be unlikey to kill it ON ITS OWN before you are likely to replace anyway.