HOWTO: Overclock C2D Quads and C2D Duals - A Guide v1.0

[graysky]

What do you mean by that pile of nonsense? Meaningless temps? Too high or too low temps..?

[Thorsson]

Two (unknown) temps 127C; some seemed low; fan speeds 8 times too high, although these could be adjusted with a divider; and some voltages weird too. Didn't have any of these issues with the older version I had, but I deleted that.

[GSte]

I get the 127C thing as well.... v. odd

[graysky]

yeah, it overdetects sometimes. I too had a 127C reading. You can disable the erroneous sensors so they aren't even displayed. You must have two that correspond to the core temps, one for your system temp, and one for your "CPU Tcase" in there somewhere.

[Blitzen]

Very good!

One thing that lets this down though. The reference to TomsHardware........as good as it was, the credibilty did slide somewaht after their mention.

[graysky]

Very good!

One thing that lets this down though. The reference to TomsHardware........as good as it was, the credibilty did slide somewaht after their mention.

TH forums aren't creditable in your estimation?

[graysky]

Okay guys, I updated the guide (now version v1.2). It has been streamlined, dead/bad links removed, etc.

[Rosaline]

TH is useful for someone with a passing interest, but I've noticed far too many flawed methods in some of their articles. It's a real shame, they seem to have some very competent writers, and some who seem a little shoddy. Thankfully the articles you now link to are some of the better ones It is worth reading Tomshardware, but never take their material as the final word.

Writing up such guides is hard work, well done on getting it finished!

As with every guide, though, don't expect everyone to find it right for them - that's why there is always room for more guides Some people seem to really like it, thankfully

Personally, I must admit, the tone is a little too harsh for my liking. It does seem aimed at those who quickly want to play with overclocking rather than those who want to get their system to a good everyday stable level. Don't worry about the tone, though, as I said - different people like different writing styles!

I did feel that some of the advice was a bit inconsistent, with parts clearly aimed at beginners, some parts focusing on power saving at too early a stage (I'd say that power saving measures should be left until after you have overclocked), and some parts talking about fairly hardcore steps such as lapping. The advice on ram timings I also felt was a bit strange, as it did not take note of the manufacturer's recommended settings.

Edit: reworded

[Mad-Max]

Graysky if you are going to update this then may I suggest that you put the update information on the first page at the bottom so it looke like this

EDIT:

Update 1: blah blah blah

[graysky]

Thanks for the suggestions, all.

[kinnth]

Thanks for the guide graysky, I personally found it more informative than clunks but both have been useful.

I was wondering how you make the assumption of your core temps? I have been using 2 programs, speedfan and coretemp but at any one time they can be upto 10 degrees c different. Which is correct. Also coretemp seems to always put two of my cores around 3 or 4 degrees higher whereas speedfan rates them all around the same, any ideas why?

At the moment I have a stock q6600 running at 266 and no change to voltage. I have an asus p5n-e sli board. I havnt got any upgraded cooling for my quad but I was wondering if it was possible to remove the stock one provide and place an extreme cooler on it? What would happen to the heat paste, would i damage my quad?

my base temps seem to be around 49 degrees c is at idle, what steps could I take to reduce these?

Thanks again.

here is a pic of my pc 25 mins in with prime 95 running, why are the temps so radically different?

[masscrazy]

For me TAT works, CoreTemp and TAT pretty much run in-sync, one is slightly slower in showing changes but they're both give the same readings of temperatures.

[masscrazy]

Thanks for the guide graysky, I personally found it more informative than clunks but both have been useful.

I was wondering how you make the assumption of your core temps? I have been using 2 programs, speedfan and coretemp but at any one time they can be upto 10 degrees c different. Which is correct. Also coretemp seems to always put two of my cores around 3 or 4 degrees higher whereas speedfan rates them all around the same, any ideas why?

At the moment I have a stock q6600 running at 266 and no change to voltage. I have an asus p5n-e sli board. I havnt got any upgraded cooling for my quad but I was wondering if it was possible to remove the stock one provide and place an extreme cooler on it? What would happen to the heat paste, would i damage my quad?

my base temps seem to be around 49 degrees c is at idle, what steps could I take to reduce these?

Thanks again.

here is a pic of my pc 25 mins in with prime 95 running, why are the temps so radically different?

[IMG]PIC[/IMG]

CoreTemp as this guide says is the one to trust. The difference between my speedfan temps and coretemp temps are about 10C.

If these are your temps on stock then theres something wrong with you HSF or the way you have seated it. The temps are way too high. I think my idle temps were low 30's before overclocking 49C is definitely too high.

Yes you can remove your stock HSF and replace it, once its removed all you have to do is wipe off the thermal paste on the chip. Why do you think the chip would get damaged?

[jjcave]

Good guide

Just as useful as Clunk's, and as you said, it is good to have information from two sources.

[roddines]

Speedfan is another app you can use to measure your temps that is very robust and stable. BEWARE that the core temps speedfan reports (as of version 4.32 anyway) are INCORRECT on C2Q chips! They are too low by 15 °C.

You can go in the software and change the offsets to read +15 degrees for each core (hit the “configure” button, then “Advanced” tab, then select the “INTEL CORE” array from the “Chip” pull down menu and give each of the cores an offsets +15)



I know this through an experiment running both Speedfan and Coretemp at the same time while having each app log a set of load temps. I then meticulously analyzed the log files and averaged the exact time points (down to the last second) from each log to ensure a fair comparison. When I took the difference of the average CoreTemp numbers, and the average Speedfan numbers, I found that the averaged Speedfan numbers were too cold by the following values:

Core 0: 15.002
Core 1: 15.069
Core 2: 15.049
Core 3: 14.979

It would seem to me the above comments are related to the other fact your mention below. ie 100-85 = 15. It seems highly probable the Speedfan software is using the constant for the dual core rather than the quad core thus the 15 degree error you discovered.

All C2D and C2D quad chips have a DTS inside the cores. For non-quad C2D chips, that constant is 85. So your Core Temp = 85 - DTS where DTS is the number the DTS is reporting. For a quad C2D chip, the constant is 100. So Core Temp = 100 - DTS. THIS DOESN'T MEAN THAT THE LIMIT FOR THE CHIP IS 100 °C!

Many thanks for the guide it is appreciated.

[graysky]

It would seem to me the above comments are related to the other fact your mention below. ie 100-85 = 15. It seems highly probable the Speedfan software is using the constant for the dual core rather than the quad core thus the 15 degree error you discovered.

Many thanks for the guide it is appreciated.

Yeah, I believe this is a known bug with speedfan and quad core chips. Also, glad you found the guide useful