Am I just unlucky with Quads or an Idiot with clocking them?????

[JNav89GT]

Frustrated with the 4th quad I've tried. First 2 were B3 6600's, 2nd two were GO. The B3's I could get to about 3.2-3.3ghz on water(swiftech setup with Apogee GT block and dual 120 rad), the first GO topped at 3.2ghz. That was on an Asus P5E board. Now I have an Asus P5Q-E with latest official bios. I can't break 3.3-3.4ghz, and I'm at about 1.4v give or take. 1.4 FSB term voltage, 1.20-1.3 NB voltage doesn't seem to matter. Ram I'm running 4x 2 GB Mushkin PC8000 Redline loose at 5-5-4-14 everything else auto including charging modes etc... 2.0v <940mhz. Ram is tested in P5E >1050mhz. I've tried just 2 sticks as well and no diff. OS is vista 64 ultimate.
If anyone can give me the key to unlocking this beast I would be much appreciative. I've kinda fallen by the wayside in Oc'ing information in the past year due to work, kids, and my new crack(RC Helicopters hehe!.). BTW Wolfdales on my P5E clocked great to 4.15ghz on water w/out problem and FSB wasn't an issue, so I'm assuming(yeah I know) that it's the same with this P5Q-E. BTW nice board for the $$$ VEry nice bios options although I have no idea what half of them do yet.

[WoZZeR999]

Try upping the FSB/NB/Core voltages. I use 1.6 for NB, VTT I had at 1.4, but it took lots of GTL tweaking (you could try a little higher), and my core is just above 1.42 with C1E mode.

[Avman]

Keeping an eye on temps - what happens when you up the volts? On water you should be able to get to 1.5v without too much trouble.

[WrigleyVillain]

That does sound strange especially considering your setup and everything you've tried.

I havent played with a P45 yet but what are your other voltage options at including vtt? Can you take screenies of your bios? Other will chime in too of course...

[WoZZeR999]

If you have more GTL settings, then you may want to try to play around with those. My quad likes around 69% (maybe higher, DFI makes me use numbers that don't correspond to anything), maybe higher.

[JNav89GT]

pretty sure there are 2 GTL settings, but I've left them at auto. Like I said, I've pretty much went dumb in regards to oc'ing in the past year or so. Used to be so on top of everything but it's passing me by and I've got to play catchup now.

My temps max at 47-50C loaded running Prime95.

Another thing is I can prime for 1-2hrs and it might error there, but it won't even run 1 bench of 3dmark 2005, or might error on 1m super pi. My OS might be hosed so that might be part of that. What I was chaulking that wierdness up to anyway, but if it gives someone a clue thought I'd throw that in there.

I'm at work now, so can't give bios screenies till later tonight

thx for the help guys :)

[Eldonko]

Try GTLREF=0.67xVTT if GTL is set up like that on your board. Im just guessing as I am not familiar with that particular board.

Also when you come to the limit, drop the multi and see if stability comes. That will tell you if its a FSB issue.

[JNav89GT]

Try GTLREF=0.67xVTT if GTL is set up like that on your board. Im just guessing as I am not familiar with that particular board.

Also when you come to the limit, drop the multi and see if stability comes. That will tell you if its a FSB issue.

thx bro will give it a try :)

[JNav89GT]

copied this from a post by tdenton1138 and his bios setup so I could use it as reference
I changed what's applicable to me

JumperFree Configuration Settings
AI Overclock tuner: MANUAL
CPU Ratio Setting: auto
FSB Frequency: 380
PCI-E Frequency: 101
FSB Strap to North Bridge: AUTO/Tried 266/333/400 no diff
DRAM Frequency: ~951/tried diff dividers no diff
DRAM CLK Skew on Channel A1: AUTO
DRAM CLK Skew on Channel A2: AUTO
DRAM CLK Skew on Channel B1: AUTO
DRAM CLK Skew on Channel B2: AUTO
DRAM Timing Control: MANUAL

1st Information
CAS# Latency: 5
DRAM RAS# to CAS# Delay: 5
DRAM RAS# Precharge: 4
DRAM RAS# Activate to Precharge: 14
RAS# to RAS# Delay : 5
Row Refresh Cycle Time: 60
Write Recovery Time: AUTO
Read to Precharge Time: AUTO

2nd Information
READ to WRITE Delay (S/D): AUTO
Write to Read Delay (S): AUTO
WRITE to READ Delay (D): AUTO
READ to READ Delay (S): AUTO
READ to READ Delay (D): AUTO
WRITE to WRITE Delay (S): AUTO
WRITE to WRITE Delay (D): AUTO

3rd Information
WRITE to PRE Delay: AUTO
READ to PRE Delay: AUTO
PRE to PRE Delay: AUTO
ALL PRE to ACT Delay: AUTO
ALL PRE to REF Delay: AUTO
DRAM Static Read Control: DISABLED
DRAM Read Training: AUTO
MEM. OC Charger: AUTO
AI Clock Twister: AUTO
AI Transaction Booster: AUTO
Common Performance Level: AUTO
Pull-In of CHA PH1:
Pull-In of CHA PH2:
Pull-In of CHA PH3:
Pull-In of CHA PH4:
Pull-In of CHB PH1:
Pull-In of CHB PH2:
Pull-In of CHB PH3:
Pull-In of CHB PH4:

CPU Voltage: 1.33125-1.425v seems to need 1.3875v for 1+hr of stability in prime blend
CPU GTL Voltage Reference (0/2): auto
CPU GTL Voltage Reference (1/3): auto
CPU PLL Voltage: auto
FSB Termination Voltage: 1.3-1.4v
DRAM Voltage: 2.00
NB Voltage: 1.30
NB GTL Reference: AUTO
SBridge Voltage: auto
PCIE SATA Voltage: AUTO

Load Line Calibration: ENABLED
CPU Spread Spectrum: DISABLED
PCIE Spread Spectrum: DISABLED
CPU Clock Skew : AUTO
NB Clock Skew : AUTO

Advance CPU Settings:
CPU Ratio Setting:auto
C1E Suppport: enabled
Max CPUID Value Limit: auto/default
Intel® Virtualization Tech: DISABLED
CPU TM Function: enabled
Execute Disable Bit: enabled

[JNav89GT]

played with some GTL and pll voltages and got 3.4ghz stable but past that it's getting sketchy.

[Loser777]

Well, you could have a rotten G0, that's no big surprise these days. Batch #/VID?
A lot of the time it's the GTL that needs tweaking. Try adjusting the PLL also...

[JNav89GT]

Well, you could have a rotten G0, that's no big surprise these days. Batch #/VID?
A lot of the time it's the GTL that needs tweaking. Try adjusting the PLL also...

batch I'm not sure, it's an oem from newegg
vid is 1.3125 I believe

[Loser777]

The VID shows that you've got a crummy chip. I wouldn't expect more than 3.5GHz without crazy volts.

[HDCHOPPER]

gtl makes all the differance 67% and up

[Glow9]

Thanks for buying and returning numerous chips I love when people raise prices because they think 200Mhz are really going to matter.

[zanzabar]

this might not help u oc but u need c1e disabled, vitalization enabled, execution disable bit disabled

and try 68-70% gtl for the cpu and 68% for the NB

[Loser777]

He has PLL on AUTO... try raising that.

[Razmatazz]

Clock skew for me is making a big difference in terms of stability. I need delay of 275-350 for my setup in order to be able run superpi. I tested each memory module seperately and used superpi in order to "dial in" the clock skew. If clock skew is off, superpi will crash even though prime will be stable for hours. Haven't played with gtl yet but I'm sure that's coming.

[gillbot]

I'll join the i'm a moron at OC'ing quads. NaeKuh is tired of me already! LOL!

My Q6600 G0 topped at 3.4 and I went through multiple mobo's and air/water trying to get 3.6Ghz. Now i'm having similar issues with my Q9450.

[NaeKuh]

I'll join the i'm a moron at OC'ing quads. NaeKuh is tired of me already! LOL!

My Q6600 G0 topped at 3.4 and I went through multiple mobo's and air/water trying to get 3.6Ghz. Now i'm having similar issues with my Q9450.

no your cursed.

beyond luck my friend. :rofl:

[gillbot]

no your cursed.

beyond luck my friend. :rofl:

Cursed or moronic, I see no difference. ;)

[NaeKuh]

moronic = fixable with help.

cursed = not even overclocking god can help ya here pal.

:rofl:

[Rickpatbrown]

I'm sorry, I know I am not one to be giving voltage advice, but isn't 1.4v pretty low. 65nm should be able to use 1.5v - 1.6v no problem, right?