Overclocking Q6600 problem

[Obione]

The thing is that you have a bad chipset, the E4600 with 250 FSB you already put it at 3GHz, the c2q eats more and comes standard with a higher FSB. With a decent P35 you would have 3GHz assured

[Serefor]

@Obione:

The thing is that you have a bad chipset, the E4600 with 250 FSB you already put it at 3GHz, the c2q eats more and comes standard with a higher FSB. With a decent P35 you would have 3GHz secured

That is to say, that with this board I'm forgetting about getting stable 3 GHz, right? right now I have it at 299x9, almost 2.7 GHz, I'll have to settle… Best regards and thanks.

[Serefor]

In this post http://www.xtremesystems.org/forums/showthread.php?173338-FSB-holes-and-bugs-on-650i-SLI-chipset they talk about "holes" in certain FSB frequencies, perhaps I have a "hole" from 300 to who knows where... the truth is that it is a nuisance to test MHz by MHz...

[amd125]

Doesn't it let you touch the voltage of the micro?

[Serefor]

@amd125:

Can't you touch the micro voltage?

If it lets me, I've been testing but I can't get it to start in any way if I put the Vcore on manual.

[amd125]

If it lets you touch the Vcore, keep raising it. You need to know your micro's VID to know if it's good for overclocking or not. You can see it with the Core Tempo program. My VID is 1.3250 but I have it at over 1.4 to reach 3.2. My VID is the worst of the Q6600 :ugly: and look that even so I have it at 3.2. A Q6600 with a good VID can get you up to 3.4 with good dissipation or more.

If you have it with a good heatsink, keep raising the Vcore. Can't you set the FSB to more than 333?

My configuration is FSB 400 * 8 multiplier = 3.200 with Vcore… which in Bios goes over 1.45 but it's that with my VID my micro needs a lot of juice to go up but still goes up. Then in Windows it marks something less, I suppose because of the Vdrop, this is some voltage drop between what the Bios marks and reality, depending on the motherboard.

[Serefor]

@amd125:

If it lets you touch the Vcore, keep raising it. You need to know your CPU's VID to know if it's good for overclocking or not. You can see it with the Core Tempo program. My VID is 1.3250 but I have it at over 1.4 to reach 3.2. My VID is the worst of the Q6600 :ugly: and look that even so I have it at 3.2. A Q6600 with a good VID can reach you 3.4 with good dissipation or more.

If you have it with a good heatsink, keep raising the Vcore. Can't you set the FSB to more than 333?

My configuration is FSB 400 * 8 multiplier = 3.200 with Vcore… which in Bios goes over 1.45 but it's that with my VID my CPU needs a lot of juice to go up but still goes up. Then in Windows it marks something less, I suppose because of the Vdrop, this is some voltage drop between what the Bios marks and reality, depending on the motherboard.

The VID is 1.2125, the FSB from 300 fails, however before trying to lower the multiplier I managed to boot with 4008= 3200 but I got a blue screen shortly after entering Windows, I was with the Vcore on automatic, maybe with 4008 touching the Vcore, could I get it to be stable?
My heatsink is this:
The E4600 I had before kept it well cool, however right now I have the Q6600 at 2.7 GHz, and under load it hovers around 60º, I don't know if it's partly my fault, because today I changed the thermal paste, and my finger got a little messy..and I put a lot, but once applied there was no way to remove it, I spread it and removed some of the excess, but even so I think I put too much.

[Sylver]

That's what I was telling you at the beginning, by lowering the multiplier you can theoretically increase the FSB more and make it stable. Now lower the multiplier to 8 and increase the FSB to 350 for example to see how it turns out, and if it doesn't cause any problems, proceed to run the stress tests. Saludos

[amd125]

I'm afraid your heatsink is not very good, so look, if you're able to set it to 3,000 without the temperature going up much, that's already an achievement. The voltage on automatic can make it go up, it's better to leave it on manual and little by little you go up until you don't get a blue screen. Even so, if you're able to start the computer, the temperature at rest shouldn't be very high, it will go up with some stress test and you'll check if you can really or not raise it a lot with that heatsink, which, by the way, is pretty bad. A Q6600 at 3,000 is not lame either, so don't worry, if you manage to put it at that speed it's still a more than decent micro today.

[Obione]

I thought you had it more or less polished...

Before OCing you can try the Vcore to get a voltage a little above the automatic one, if it doesn't start with stock frequencies it should be due to a lack of Vcore.

[Serefor]

I've been testing it and I've set it to 414x7 = 2.9 GHz with the Vcore on auto. And it's stable, I've been using it all afternoon without any problems, running Orthos and there were no problems, the only problem is the temperature, which reaches 61° on Core 0, I've seen that the Q6600 are quite hot, what do you think? Tomorrow I'll try to increase it to 3.0 GHz to see how it goes. Regards

[amd125]

For the bad heatsink you have, it's not a bad temperature, so don't worry.

[Sylver]

It looks good, that temperature is not bad. Maybe with a better heatsink you could reach 3 Ghz without going over 65º, but you will tell us how it goes tomorrow.

Regards

[Serefor]

@Sylver:

It looks good, that temperature is not bad. Maybe with a better heatsink you could reach 3 GHz without going over 65º, but you'll let us know how it goes tomorrow.

Regards

Well, within what I can do I think I've achieved good results.
380 x 8= 3.04 GHz with Vcore on Auto, because if I set it to manual it wouldn't start in any way.
After 10 minutes of Orthos it reached 66º and so far it seems stable, I'm attaching a screenshot. Regards and thanks to everyone for the advice!

By the way, look at the Orthos, it marks 3.4 GHz and puts the multiplier X9, what will that be? in the properties of the computer in Windows it also shows 3.4

[amd125]

Well, your team is not doing badly. Regarding speed, some programs give you the FSB for the maximum multiplier for example. The edmark marks me as 3600 speed, when I have it at 3200.

Core Temp does not fail for example, so do not worry.

Does the Vcore in manual not let you select the voltage? If you put it in manual what does it indicate you?

[Serefor]

@amd125:

Well, your team is not doing badly. Regarding speed, some programs give you the FSB for the maximum multiplier, for example. My edmark shows me a speed of 3600, when I have it at 3200.

Core Temp doesn't fail, for example, so don't worry.

Doesn't manual Vcore let you select the voltage? If you set it to manual, what does it indicate?

Yes, it lets me select the Vcore, it gives me values from 2.XXXX (An exaggeration) to 0.XXXX, that is, a lot of range, it says that the normal Vcore is at 1.22, so I was selecting from there upwards, but I couldn't get it to start up ever, sometimes it didn't pass the post, other times it got stuck at the motherboard logo and I had to do a Clear CMOS, and other times it got to GRUB, but at the moment of selecting the OS it restarted or gave some error, could it be the motherboard that doesn't like it when you touch the voltages? xD

[amd125]

I see that you don't have a bad VID, mine is 1.325 a chestnut. I would try since you see by Core temp and the other program the voltage at which it works, put it in manual at 1.3 for example and if it doesn't start go up by 0.005 at 0.005

Anyway, the higher the Vcore the higher the temperature, so I think you don't have it at a bad speed for the heatsink you have, and you have some very cool temperatures, so enjoy the micro like this and if in the future you have a better heatsink you already give it more caña until you achieve the 3.2-3.4 but at the speed you have it is a more than cool micro today.

[fjavi]

This post is being processed/translated. The original version will be shown:

@Serefor:

Si, me deja seleccionar el Vcore, me da valores desde 2.XXXX (Una exageración) hasta 0.XXXX, es decir mucho rango, me pone que el Vcore normal esta en 1.22, asi que fui seleccionando de ahí hacia arriba, pero no conseguí que arrancara nunca, algunas veces no pasaba el post, otras veces se quedaba en el logo de la placa y tenia que hacer un Clear CMOS, y otras veces llegaba hasta el GRUB, pero en el momento de seleccionar el S.O se reiniciaba o daba algún error, sera la placa que no le sienta muy bien que le toques los voltajes? xD

tu problema es la placa, ese chipset no es bueno para ocear y menos un quad, por lo menos los duales subirían mejor, los quad no van bien ni en ese ni en el N680, con una P35 o P45 ese CPU debería subir bien fácil a 3400mhz incluso si es bueno el CPU podría hacer los 3600 sin demasiado voltaje.

esa placa además de que no es muy buena en OC debe tener bastante vdroop y asi es mas difícil si no se mete un vcore alto, quizá mejore algo si se hace un mod de vdroop, aunque no se si en esa placa hay algún sitio donde se vea el mod, si ya las p35 de gigabyte tienen vdroop esa debe tener mas.

Quiza te pille mejor el 333x9 serian 3200mhz, lo mismo lo hace con vcore auto aunque según el CPU.

saludos