E6300 + 965p Ds3

[h0nam]

Hello, I'm new here.
I have googled around but could not find a solution to my problem, so I hope maybe someone here could give me some advice... thanks!

So, as the topic says, I'm using a C2D E6300 on a Gigabyte 965P DS3 3.3 (F12) mobo. Ram is 2GB OCZ Platinum Rev.2 PC-6400, EVGA 8800GTS 640mb for video card, and Vista 32bit. I've had this build for about 4 months now.

Right now, I have my E6300 running at 3.01ghz (430x7). I had to set the PCI-e frequency to 105 in the BIOS and +0.1 volts to PCI-e in order for PCI-e to run at x16; otherwise, it would be running at x1. I have been trying to oc it to 3.2ghz, and the only problem I have now is that the PCI-e stays x1 when I set the PCI-e frequency up to 110 in the BIOS.

Does anyone know how I can get to 3.2ghz while maintaining the PCI-e speed at x16?

Thanks in advance!

[Patriote]

Huh ? I think i get it. On most motherboards, there is a setting that let you lock the PCI-Express frequency so that when you Oc your CPU\FSB, the PCI-Express isn't following. Look for that setting on your mobo. I have never got you mobo personally but im sure there is that feature somewhere.

BTW: Welcome to Hardwarecanucks.com!

[h0nam]

Thanks for your reply! There is a feature to set my PCI-e frequency; the problem is, when I lock it at 100, the PCI-e bus runs at x1 speed instead of x16. It seems that the higher the FSB, the higher the PCI-e frequency needs to be adjusted in order to keep it at x16. I've heard that this may damage the video card though, and so I am no going to try anything above 110 for PCI-e frequency... that's why I was wondering if there was any other way to make it work properly.

[Somed00d]

yeah its a known problem on dfi p965-s boards so probably others too..

did you try every setting between 100-110? or maybe lower?

[h0nam]

Hey thanks for the replies, but I got everything worked out... sort of.
It turns out that I needed to +0.1v to the MCH thing... although I'm really not sure what that is... This way, I could have my PCI-e locked at 100 and still have it running at x16. The only problem now is that I am overclocking my E6300 to 3.2ghz with the vcore at 1.45v, which I would consider extremely high, especially for a C2D. Right now I have it Orthos stable for 13 hours, but anything below 1.45v it becomes unstable.

[Somed00d]

Originally Posted by h0nam

Hey thanks for the replies, but I got everything worked out... sort of.
It turns out that I needed to +0.1v to the MCH thing... although I'm really not sure what that is... This way, I could have my PCI-e locked at 100 and still have it running at x16. The only problem now is that I am overclocking my E6300 to 3.2ghz with the vcore at 1.45v, which I would consider extremely high, especially for a C2D. Right now I have it Orthos stable for 13 hours, but anything below 1.45v it becomes unstable.

thats actually not too high. my E6420 stock volts was 1.35 and needed 1.55 to hit 3.2ghz

as long as your temps are good you shouldn't have any trouble running 24/7

[h0nam]

Thanks for your reply, that's good to know... at least puts me a little bit more at ease lol!

[Delavan]

thats actually not too high. my E6420 stock volts was 1.35 and needed 1.55 to hit 3.2ghz

as long as your temps are good you shouldn't have any trouble running 24/7

Strange..I only needed 1.375V for my E6420 to reach 3.2..and it is with the apparently bad L644G batch!

My settings on my DS3 rev3.3 (on the old F10 BIOS)

MCH +0.1V
FSB forced to 100MHZ
FSB +0.1V
CPU 1.375V
RAM 1:1 @400FSB stock volts

[Eldonko]

Originally Posted by h0nam

Hey thanks for the replies, but I got everything worked out... sort of.
It turns out that I needed to +0.1v to the MCH thing... although I'm really not sure what that is... This way, I could have my PCI-e locked at 100 and still have it running at x16. The only problem now is that I am overclocking my E6300 to 3.2ghz with the vcore at 1.45v, which I would consider extremely high, especially for a C2D. Right now I have it Orthos stable for 13 hours, but anything below 1.45v it becomes unstable.

Vmch = voltage of memory controller hub. It makes sense to raise vmch if you have pcie issues, basically it supports memory and video buses, ie. lets cpu, mem, vid communicate.

1.45v is fine, I wouldnt worry about it. :)