Sign-in / Sign-up
Your question

P5B Deluxe, C2D 6400, Corsair PC6400 C4, 400+ FSB voltages?

Tags:
  • Corsair
  • Overclocking
Last response: in Overclocking
January 4, 2007 3:38:06 PM

Hey everyone. Thanks to all who've helped me along the way. Just starting a new thread for myself and anyone who plans on getting the same setup so we can all OC together like one big happy family. Here are my main components:

Asus P5B Deluxe
C2D e6400
Corsair 2GB PC6400 C4

I seem to top out at 400 FSB with these voltages:

Vcore: 1.375v (runs fine at 1.3375)
Vdimm: 2.1v

If anyone has this board/cpu/ram combo (or very close to) can you tell me your current OC with temps and ALL your voltage settings? Do I need to go up to 1.4v+ on the vcore or 2.2v on the vdimm to go any further? What about Mobo voltages (for this specific board)?

Relaxing my timings on the ram doesn't do the job and I can run stable at 400 FSB at 1.3375 up through 1.375. Is there something I'm overlooking? I see other people with roughly the sam settings getting much better OC's. It's not my temps. I have a Thermalright XP-120 keeping my temps (at 3.2Ghz) around 38 idle and 50 max load (during Orthos testing)

Thanks guys!

More about : p5b deluxe c2d 6400 corsair pc6400 400 fsb voltages

January 4, 2007 4:44:33 PM

I was thinking the same thing, but shouldn't have loosening my timings to 5-5-5-15 have roughly the same effect at 2.1? Will 2.2v cause any warranty issues? Thanks.
Anonymous
a b K Overclocking
January 4, 2007 6:59:29 PM

If you are running on the 8X multiplier, your CPU is at 3.2ghz it might need a bit more voltage, depending on your cooling you can probably push it further. The retail heatsink might not cut it though.

You can check in my post I got all my voltage

Edit:o h and the ram might not be able to run at faster speed even with looser timing. Usually has to do with the IC used in the ram.
Related resources
January 4, 2007 7:48:30 PM

Thanks.

Checked out your thread. Good info. What about my ram voltage? would 2.2v be a bad thing?
January 4, 2007 8:18:24 PM

Quote:
Will 2.2v cause any warranty issues?


I dont think overclocking is for you
January 4, 2007 8:35:43 PM

ugh....I'm more concerned about burning out the ram.

I've OC'ed my C2D 6400 to 3.2Ghz stable already.

(brief history)
X2 3800 2Ghz to 2.6Ghz
P4 2.6Ghz to 3.25Ghz
P4 3Ghz to 3.5Ghz
and my 7900GT is at 560/1500 with a modified NV5 cooler on it.

Care to make any other assumptions?

I have the experience. I'm just new to the DDR2 (and they're lower voltages) and wanting to know what these babies can handle before it's too much/too late. That's all.
January 4, 2007 9:05:09 PM

easy way to tell if you have to much voltage to your ram is feel them...
if they feel warm then cool them with a fan.
if smoke is coming out of them... then good chance you have to much voltage.

raising your voltage to 2.2 should be fine though...
airflow never hurts though
January 5, 2007 3:35:58 AM

lol...nice.

alright. well, if 2.2v doesn't work, I'll still be happy with 3.2 for now.

Thanks!
January 5, 2007 10:18:38 AM

well, i have an ASUS P5B-Delux C2D E6600 and 2GB OCZ Plantinum,
i can overclock to 2.88Ghz with FSB 320 and Vcore at around 1.2V, the problem is that i cant go any higher even with Vcore to 1.4V , ive tried NB 1.55, FSB termination voltage?? gont know..., I set up DDR2 speed with the dividers allways to 800 or under it, can you tell me all the things a i have to set up to go higher?? i never can go up more than 320FSB, CE1 diabled, speed step diabled....
PCI-E 100Mhz, PCI 33 Mhz.....
i dont know what else to do, maybe i have to overclock the memory too? using dividers it becomes inestable?? :?:
January 5, 2007 3:41:30 PM

No prob bro

First, set your mem's rated timings manually. Then set them to 533Mhz. This puts them at a 1:1 ratio with your FSB. as you raise the FSB, your ram speed goes up as well.

So, if you can get your FSB up to 400, then your ram will be running again at it's native ddr-800 speed.

At 333 FSB, your ram will run at ddr-667 speeds.

The reason you're having problems is because you set your ram at ddr-800 but when you raise your FSB, your ram still goes up. So at 320 FSB, you're ram is overclocked at that point. So it's probably your ram that's giving out.

If you put your ram at 533 to start off, you should be able to put your fsb at 333 (667 ddr) without a problem. Then raise it 5-10 Mhz at a time till you top out.

If you're using wacky dividers, it can cause instability. 1:1 works best when overclocking it seems.
January 5, 2007 4:10:51 PM

My setup is,

E6400 at 3.2GHz @ 1.25v
Corsair XMS2 DDR2-800 5-5-5-12 @ 1.9v
P5W DH Delux BISO:1707
Zalman CNPS9700 keeps it all cool at 33C idle 50C full load

Running stable on dual instance of Prime 12 Hours and memtest 12 hours

Tried going higher FSB and reached 413FSB but dropped back to 400 thought to myself that a couple MHz would not be worth more temps and strain on the CPU

Lucatz
January 5, 2007 5:00:52 PM

is that 1.25v set in your bios or what speedfan (or some other monitor) reads? Thanks.
January 5, 2007 8:22:10 PM

you got that!, yes it was the ram timings that wanted to be set up manually, now ive got it to 3.4Ghz estable but with a bit high temps due to stock HSF , 681C full load with TAT. thank you!
January 5, 2007 11:30:36 PM

cool. glad I could help. Now go get a Zalman or Thermalright cooler and you'll be all set. Gotta keep those temps as low as possible. 'specially during the summer!
March 2, 2007 11:45:16 AM

Hi,

I have a similar setup : p5b Delux, c2d 6400, 1gb Corsair XMS 6400) but I can't get past 321 fsb. Not that it crashes at that, but I set 375 say in bios, but when it has booted the fsb is reported as 321 maximum.

I have locked pci-e at 100, pci at 33.33, disabled spread spectrum, set memory to 533 (1:1?) 5-5-5-15 and 2.1v, set core volts to 1.425 (ish).

System boots and runs fine, but cpu-id/cpu-z reports fsb of a fraction over 321 every time. So does Coretemp.

Is there some sort of throttling going on? :?

Or could cpu-id and corecemp both just be wrong??

Any help welcome!

Thanks

Graham
March 6, 2007 5:04:46 PM

Try disabling C1E in your bios. The newest version of CPU-Z (1.39) doesn't like it very much as far as reporting accurate info at idle speeds. It will report accurate speeds at load without disabling C1E. Try right-clicking on My Computer and go to Properties. Is the CPU speed correct there?
a b K Overclocking
March 6, 2007 5:44:40 PM

Quote:
System boots and runs fine, but cpu-id/cpu-z reports fsb of a fraction over 321 every time. So does Coretemp.

I've noticed the 321 FSB glitch on my P5B-Deluxe system too. It only happens after the first bootup after I've OC'd. Doesn't matter if I set FSB to 333, 400, or whatever, it will only go to 321 on the first bootup (notice I say first bootup). What I've found is that after I bootup after an OC and get the 321 FSB, I just reboot and it goes away. The 321 never returns for me, it only happens the first time. Try that and see if it goes away. Post back here if this helps.
March 7, 2007 8:37:41 AM

Thanks for the replies.

KrazyNutz, I have disabled C1E but it makes no difference.

"My computer", properties also reports speed as 2.57 ghz - so 321x8 = 2568.

cpu-z always says fsb is 321.1 as does CoreTemp. Asus Ai Suite also shows 321.1 in the main window, but shows 375 in the Ai Booster window.

Just now I ran some benchmarks with 375 set in bios, and then rebooted and actually set 321 in bios and ran them again. No change, so I guess I really am running at fsb 321(2.57ghz) even when I OC to 375 (3.0ghz) in the bios. :( 

rwpritchett, it doesn't matter how often I reboot - it still shows 321.1

Regards

Graham
March 7, 2007 9:23:53 AM

More testing :

Setting fsb 300 in bios, pc boots up at 266!! (=2.13ghz=standard).
Setting to auto still produces 266.
Setting 400 and I'm back to 321.1
???
a b K Overclocking
March 7, 2007 12:05:57 PM

What BIOS version are you using? Maybe an update is in order.
March 7, 2007 1:29:12 PM

Wait a minute. You're using AI Suite? Could that have something to do with it? I would uninstall/disable ANY Asus OC tools in Windows and your BIOS if you haven't already. I can email you my bios screens tonight (EST 7PM) if you like. Off the top of my head, my main settings are:

FSB: 400
Vcore: 1.325v
DDR: 533 (1:1 = 800 effective with 400 FSB)
Timings: 4-4-4-10-5-35
Dimm V: 2.1v
PCI:33.33Mhz
PEG: 100

I have pretty much everything manually set. If you PM me your email, I'll send you my bios screens tonight or I could upload them to photobucket and send you the link.

BTW, my components are:

Asus P5B-Deluxe
C2D e6400 @ 3.2Ghz
Corsair XMS2 C4 PC6400
Antec Neo 480 PSU
March 8, 2007 10:48:57 AM

Hi Guys,

rwp - bios is 0507 (08/10/2006).

KN - I'm only using AiSuite to look at the speed, but I'll uninstall it from windows and see if it does make any difference.

Thanks for the bios screens offer, I have enabled the email contact button.

Thanks again for taking the time with this. :) 

Regards

Graham

EDIT - have uninstalled AiSuite....................no difference, still 321 :roll:
a b K Overclocking
March 8, 2007 12:41:37 PM

Quote:
rwp - bios is 0507 (08/10/2006).


I remember the release notes for one of the BIOS files saying that it fixed the problem you are referring to (even though it still happens on first boot for me). Update your BIOS, that one is ancient, relatively speaking. Current BIOS is 1004, but that one won't let you roll back to a previous BIOS. Try out BIOS 0910 and see if the problem goes away. BIOS 0910 allows rollback to previous BIOS versions BTW.
March 8, 2007 2:13:10 PM

Tell ya the truth, you'll be fine with either one. I use 1004 without any problems. But I didn't notice any difference betwen 0910 and 1004 so I agree, until your problems are solved, go with 0910 (or whichever is before 1004 on Asus's website.) Try that and if you still need the bios screens, I'll email them. I didn't get a chance to take pics last night due to a 3D animation I'm doing for a local band's website. Good luck and let us know how things go.
March 8, 2007 2:30:46 PM

Quote:
rwp - bios is 0507 (08/10/2006).


I remember the release notes for one of the BIOS files saying that it fixed the problem you are referring to (even though it still happens on first boot for me). Update your BIOS, that one is ancient, relatively speaking. Current BIOS is 1004, but that one won't let you roll back to a previous BIOS. Try out BIOS 0910 and see if the problem goes away. BIOS 0910 allows rollback to previous BIOS versions BTW.

Good call!!

I just updated to 0910 and it booted up at fsb 375.

Ran benchmarks and got expected increase. :D 

Thankyou!

Just need to do final tweaks now to see how far I can push it and still be stable.

KrazyNutz, I'd still like to see your settings if you get round to it, but if it's a pain don't bother.

Thanks again for taking the time to help!!

Regards

Graham
March 8, 2007 2:40:56 PM

well, I'm in the US (EST) currently 11:37 AM and at work. I'll try to get those to you tonight my friend. Glad the BIOS update worked for ya. Good call rwpritchett. Good luck Graham in the meantime!