• 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.

First time C2D OC

sabregen

Fully [H]
Joined
Jun 6, 2005
Messages
19,501
Please don't flame, but I've been on AMD for quite some time (read, since Intel shot themselves in the foot with S478 P4's). At any rate, I just built a C2D based system for someone, and I used the following:

ECS 570SLI SLIT-A
Intel C2D e6400 (retail HSF)
2x1GB PQI Turbo PC2-5400

I know, this isn't best board to learn on OC'ing a C2D system, but WTH. So, the options in BIOS are VERY limited. I am very used to working with high end A64 based boards, so I have quite the grasp on OC'ing those. Same principles apply, of course, but I am not familiar with C2D options. Here's what I see:

FSB 1066 (Current), can range from 400FSB to 1400FSB
RAM Speed 667 (Current), can range from 400-800

Multi on these is locked, correct? This is how Every Intel chip I have ever OC'd was, locked multi...raise the FSB, and there's your OC. Problem is, I dropped the FSB and the RAM to the lowest that BIOS said it allowed, so that I could go into windows, and find my max for board/RAM/CPU, but the damn thing wouldn't POST. I had to clear the CMOS, and go back to FSB 1066 and DDR 667. Anyone have any ideas? I can get it going, if you show what I did wrong, initially. I can OC the hell out of a A64 system...I'm feeling so SMART right now.

Edit: SpeedStep and Spread Spectrum is OFF

Edit #2: 28 Views and no info....good lord. Come on guys!
 
Well I don't have a C2D, and don't know anyone that does have one.. but I do have a 805D, and been using Intel for a bit..

Make sure you have the PCI and PCI-E clock fixed (33MHZ and 90MHZ respectivily iirc). Also, you should be able to boot into windows fine at the stock FSB speed. I always found if I lowered the FSB to below spec it caused issues. And yes, as far as I know most production intel CPU's are multi-locked. I think with the Intel M CPU's you could lower the multiplyer though.

edit: Why are you dropping the FSB to the lowest the MB allows? I can't think of a reason you would want to do that..
 
try going the other direction with the FSB... you'll probably need to raise the mem voltage +1 or +2 to get it stable. i'd set mem timings to 5-5-5-15 so you know that that will generally not be the problem. I assume when you say 1066 mhz FSB you actually mean 266 mhz... i've never ever seen a bios that only posted the quad clocked FSB speed. set FSB to 333... any board should be able to post at that. and go from there... its pretty simple. if you search there is a much more detailed C2D OC guide...
 
strange to me, coming from AMD systems, that going low on the clock causes problems. And yes, the board did list the speed at the quad-clock...strange, I agree. Thanks for the info, I'll give it a run when I get my hands on it tomorrow.
 
Please don't flame, but I've been on AMD for quite some time (read, since Intel shot themselves in the foot with S478 P4's). At any rate, I just built a C2D based system for someone, and I used the following:

ECS 570SLI SLIT-A
Intel C2D e6400 (retail HSF)
2x1GB PQI Turbo PC2-5400

Edit #2: 28 Views and no info....good lord. Come on guys!

Perhaps moving your question to the Overclocking forum would get more responses?


steve
 
perhaps you're right. Mod, can we get a move on this one? Please? TY.
 
Back
Top