• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

OC problem

T

Tanatz

Limp Gawd
Joined
Jan 13, 2006
Messages
271
I've had the system in my sig going strong for a good 9 months now, love it to death. I've been at 3.6ghz since forever, happily, but I'm getting an itch so I'm trying to fine tune, lower some voltages and getting a few more clocks out of my rig in the meantime.

My current, stable OC is very simple:
FSB bumped to 400, PCI manually set to 100 and DDR multy manually set to 2.0. I left my DRAM timings set to auto (5-5-5-18) as well as all my system voltages set to auto. It should be noted that my system automatically sets v-core to 1.225, which I think is high. Real temp shows both cores to be running at 33 idle, 41 under load. Fine.

Now for my fine-tuning:
I started by tightening my ram up, manually setting the timings to 4-4-4-12, which is what this ram is rated at. Reboot, computer posts just fine, however, I notice my Real temps soar to 38-39 idle. Didn't even try to run prime95 so no idea what temps would be under load. So I try to manually lower my v-core, and the PC fails to post. Even manually setting the v-core to the system default of 1.225 causes it to fail post. I don't understand why tightening the ram raises the core temps?

I thought it was a BIOS issue so I updated to the newest BIOS with no improvements. Admittedly, I am a OC newb somewhat, but what could it be?

- Tightening RAM timings raises CPU temps.
- Manually setting v-core causes system to fail POST, regardless of what I set it at.

Do I need to raise the RAM voltage and not the v-core?
Why would manually setting v-core, even set to match the system default under the "auto" setting, cause the system not to post?

Thanks in advance.
 
ok going to make one more attempt to type this whole thing out again.. forum better not go down again to be fixed or ill be really pissed..

first.. do not ever use auto settings on your cpu when overclocking.. unless you want to kill your cpu..
secondly.. loosen your memory timing while overclocking and set the memory to 1:1 timing with the FSB.. some boards will sat 2.00 or 1:1.. just depends.. but its the lowest possible setting you can put it.. basicly it makes the memory run at the same speed as your FSB settings.. example.. fsb is 300 your memory will run at 300mhz or ddr2 600.. once you have completed your stable overclocking then you can raise the memory timing back to its stock speeds..

third.. since you said you were having issues with the overclock not being stable with your manual settings.. (i know im contradicting my self here but try it) set your cpu voltage back to auto.. boot into windows.. load up the processor and check what the voltages are in cpu-z.. then go back to your bios and manually set the voltage to that.. boot into windows.. run prime for about 30 minutes.. if its stable.. go back drop the voltage down 1 more step.. go in test it for about 30 minutes.. if its stable.. go back to the bios and drop it again.. do this until it becomes unstable.. then set it 1 higher and run prime95 for an hour or Intel burn test for about 20 runs.. if its stable.. then you have found the stable voltage setting..

also make sure you have load line calibration turned on.. might help you..

once you have gotten to the overclock you want.. you can now go ahead and start raising the timing on your memory til its back to its stock speed.. also make sure the voltage is set to 2.0 or 2.1v which im sure that memory is suppose to run at.. if its on auto, its most likely running at 1.85v..
 
I've bumped up the FSB to 400, leaving all DRAM timings set to auto, all voltages set to auto and it worked ok for the moment. However, when running prime95 I Realtemp reported temps of 65, which is way too high for my tastes. Idle temps were fine (33 degrees). I immediately loaded optimized defaults until I can figure out why I'm having a hard time getting my v-core to go lower than the default 1.225.

I tried to loosen the ram timings and the loosest it seems to go is 2.0xFSB, or auto, either way I can't get any lower than 800 (aside from 2.0x the stock 333 equaling 667).
 
remember the temps you see running prime95 are usually 5-10C higher then what you would see running any other applications.. so it make seem high but realistically you should never see those temps running standard multi-threaded applications..

1.552v is very high.. but like i said.. work your way down step by step from 1.552v til you find the lowest stable voltage possible.. (start off at 1.4v so that your within the safezone and work your way down.. 1.55v is way to high..)

so im guessing your using ddr2 800? if so thats not going to give you a lot of headroom with overclocking.. may want to look into some ddr2 1066 or 1200 which will give you plenty of headroom.. what id do is leave everything on auto, timing wise and set the dram timing as low as possible until you have it stable.. then raise the timing on the memory after.. but the lowest setting allowed on an intel board is 1:1 or 1xFSB.. so if your fsb is 400 your memory is running at 400mhz x 2 = ddr2 800 which is your rated speed.. and like i said before set the dram voltage to either 2.0 or 2.1v though id pick 2.1v if you are trying to go over 800mhz(just check your manufacture voltage specs for this information).. if you do have decent memory it should run at 1066 5-5-5-15 or 5-5-5-18..

also with the default 1.225 what is the VID voltage on that processor? im guessing its 1.2v? if so its probably not going to let you go any lower then that..
 
then its probably not letting you go below that due to to much vdroop in the motherboard.. even though you set your board at 1.225v doesnt actually mean thats how much the cpu's getting.. its probably along the lines of 1.19-1.20v which might be to low for that exact processor.. remember not every processor is the same and not every motherboard is the same.. so when comparing it to others overclocks you have to take their numbers with a grain of sand because they may not work with your exact setup.. try bumping the voltage up to 1.24 or 1.25v some where around there and see if it becomes stable..
 
You must log in or register to reply here.
Back
Top