Striker Extreme & Q6600 GO - OC'ing issues and help requested.

Yea 1.275 is set in BIOS. If I leave Vcore on Auto and set the FSB to 1333, the Vcore jmps up to 1.325. I just dropped it to 1.275 to test it overnight and it was still running nicely this morning.

Cooler is looking good, Idlilng around 30-35 and Load around 48-52. Although it may have been a pointless waste of cash if I can't get it over 3.0Ghz LOL.
 
Struggled to post at first but I increased the NB to 1.45 and that was fine. However, it wouldn't even load Vista. Increasing the NB to 1.55 made no difference and neither did increasing the Vcore to 1.50.

The only other thing I can think to try which I didn't really experiment much with the first time, is flashing to the 1301 BIOS. A few in the guide you posted above seem to have had some success with that.

One other thing I've noticed, but don't know if it's normal or not. Baring in mind that my FSB and MEM are unlinked, when I enter certain figures into the FSB but don't touch the MEM setting, the Actual MEM reading sometimes changes, i.e.

FSB (QDR), Mhz: 1492
Actual FSB (QDR), Mhz: 1492
MEM (DDR), Mhz: 800
Actual MEM (DDR), Mhz: 799.3

Depending on what I set the FSB too, the Actual MEM reading can drop by as much as 10.
 
Last edited:
From reading through the first few links you posted, it would seem that RAM dividers against the FSB seem to make a big difference to stability. However, that just looks to me like an extra variable on top of voltages, that makes OC'ing worse than trying to win the National Lottery!

Think I'll go buy some lottery tickets and hope I win, can afford a new motherboard then LOL.
 
truthfully flea bay it you will still make a nice earner on it (almost what you paid for it)

Abit IP Pro or the Asus Maximus motherboards are the over clocking flavour;)

http://www.overclockers.co.uk/showproduct.php?prodid=MB-135-AB


http://www.overclockers.co.uk/showproduct.php?prodid=MB-253-AS&groupid=701&catid=5&subcat=946


*****Official ASUS MAXIMUS FORMULA thread*****

http://forums.overclockers.co.uk/showthread.php?t=17789878



**Official ABIT IP-35 Pro Review/Overclock/Guide Thread**

http://forums.overclockers.co.uk/showthread.php?t=17739133
 
Last edited:
Well, when I bought this set up I was aiming for an OC to 3.2, but after reading up I got that craving for more :)

I shouldn't be disappointed that I have a [email protected] as it means I'm getting the same performance as I would get from a QX6850 but only having paid a quarter of the price. However, I am disappointed because I know this Q6600 could be so much more on a different board (btw had it in Windows @3.825.... for about 30 seconds lol).

I might continue experimenting with this board for a little while and ebay it later.

Any recommendations for which of the two boards (or any others for that matter) that would most suit OC'ing a Q6600?
 
Last edited:
From what I can remember, the only programs running were Core Temp and Prime95. Prime95 failed on 1 core within about 3 seconds, failed another core about 15 seconds later, I then went to end the test and close, but Windows hard locked.

I had trouble getting back into the BIOS afterwards too, eventually got back in on my second or third cold boot.

I'm pretty sure the settings were as follows:

FSB: 1700
Memory: 850

Vcore:1.5
Memory:2.05
1.2v HT:1.65
NB Core:1.5
SB Core:1.65
CPU VTT:1.4

RAM was at 4-4-4-12 / 2T
 
Only had 2x1GB sticks in at the time and was using Small FFT stress test, that should mean I wasn't testing the RAM at all, or would it still have an effect?
 
if you are getting rounding errors then 90% of the time is the RAM failing.. it still has to work at the higher FSB speed whilst your CPU is doing the work and as I understand it although the actual calculation is being held in the CPU cache it passes through the RAM? (someone can correct me on this)... anyways! either way trust me on this one :)

Is way easier to get you clock stable first and then come back and speed the RAM up later.. that way you know when you fail a prime test it can only be the CPU failing and is a case of vcore increase

your clock looks like its failing from lack of vcore if thats the BIOS vcore you state there?
 
Vcore in BIOS is 1.5 and is reading as 1.42 under load in Everest.

My problem so far has been that I can't get into Windows with an OC anywhere above 3.0. Whilst those voltages may affect the stability of a 3.825 OC, they should be fine for an OC of 3.2 to 3.4. I honestly don't think voltages are the issue and my RAM passes 2 hours of Memtest86 when running at 4-4-4-12 / 2T, with the 3.0Ghz OC and pretty much stock voltages.

But I do intend to play some more and I'll try your suggestion :)
 
That striker is a frustrating board, i have been sitting with me rosie lee, re-reading this thread trying to work out what is preventing above 3Ghz.

And i am stumped to an extent....... hmm digestive biscuits.....
 
Could the LDT Frequency setting have any effect to the stability of an overclock? It's about the only thing in the BIOS that I haven't tried changing whilst OC'ing.

From what I've read it seems to be some sort of multiplier between the NB and SB.
 
LDT Frequency (HyperTransport bus multiplier on the section between the NB and CPU):

seems to be a leftover from when this BIOS was used for AMD CPUs, it has no effect whatsoever on Intel chips.

I am sure, adamant the problem is the unseen memory dividers on this mother board combined with the FSB holes.
 
Last edited:
That would be my assessment as well. In fact it makes sense because when I had my FSB at 1333 it wouldn't post unless my Memory was at 800.

I think what I need to do is settle on an acceptable level for the FSB, set my voltages above what should be required for that FSB and then just try different Memory levels. See if that makes any difference.
 
you could try manually setting the PLL? do you have that option, normally only required on very high clocks but could give you some stability
 
I don't appear to have an option within the BIOS for setting the CPU PLL and there's no reading for it under the voltages either. I don't think it's available.
 
Back
Top Bottom