Q6600 new build - high temps?

  • Thread starter Thread starter JHC
  • Start date Start date

JHC

JHC

Associate
Joined
29 Jan 2010
Posts
90
Location
in bed.
Q6600 new build - high temps? Problem solved. Now with added Badger!

Finished my build this afternoon. I feel these are not good temps!

CPUZscr.png


CoreTemp-Scr.png


Other than apalling airflow which I definitely do not have, what would cause these temps? The high-points were reached after running Prime95 for only about 3 minutes.

I guess checking HSF seating/termal paste re-application is the first place to go? :confused:

Edit: I realise those screenies are showing different speeds. I don't know why this happens. </noob>. Some sort of power saving, runs a lower speed when not being pushed? This was my guess as it's back up to 2.4/x9 when I start doing things.
 
Last edited:
I know bumping your own threads is bad etiquette, but I was wondering why I'd get such differring core temps?

DifferringTemps.png


The +12v reading disturbs me a touch, too!

If it helps I'm on 7HP 64bit.

Anyone? :(
 
The difference in the CPU multiplier is due to Intel's SpeedStep doing its job. It is, as you say, a power saving feature. If it isn't causing any other problems then leave it enabled.

Your temperatures do look high. You really need to supply more information about your case, heatsink, fans, ambient temperature, etc.

For reference my Q6600 (@3GHz) doesn't go much over 60 degrees C at this time of year.

The difference in core temps is probably due to the two programs using different values for Tj. Max.

If your +12V rail was really reading 2.05V the PC wouldn't boot, it must be picking up the wrong sensor value.
 
Last edited:
Case is a Lian-Li PC60. HSF is a Coolermaster 212 with the stock fan on it, which is set up to push air over the heatsink towards my rear 120mm Xilence RedWing exhaust fan. I have a 120mm in the front, which was standard with the case, as an intake.

There's absolutely nothing in the way of the intake fan either, it isn't blowing over HDDs or anything at all. I'd snap a pic but it's in my desk now so I'll get one when I get it out tomorrow. Ambient temperature in this room is about 19/20c.

Any ideas about the different readings between programs there?
 
The difference between the temperatures is due to how temperature sensors work and the selected TJ. Max figures.

There's exactly 10 degrees difference between the two programs. You can make them agree by tweaking the TJ. Max figures. You've just got to decide which numbers you want to believe.

You should try reseating the cooler before going looking for more exotic solutions.
 
Yeah, I'll definitely re-seat the HSF and clean and re-apply the thermal paste. I'll get back to you when I do that tomorrow.

Cheers for the help gentlemen!
 
+1 for re seating and re applying thermal paste..

when I first installed my h50 i was idle'ing at 70 degrees...i was like rippoff! lol

re seated it and it was fine.
 
too little/too much paste. heatsink might not be properly clipped onto the board maybe.

87c is pretty high. My Q6600 @ 2.9ghz has reached 65c after 3 hours of prime
 
The temps in speedfan are the correct ones. Tj max for q6600 CPUs is meant to be set at 90c. About 90% of people on this forum will incorrectly tell you it's 100c.
 
Righto fellas - problem solved! I discovered the issue when I was taking the HSF off - one of the four nuts on the back of the motherboard wasn't seated right, so when the bolt from the HSF bracket went into it, it didn't thread properly. I had a loose HSF on one side! D'oh. You'd've thought I'd have noticed that! It became apparent that this was certainly the problem when I lifted off the heatsink and the thermal paste hadn't spread all over, there was a big gap on the corner the loose bolt was on.

Now I've cleaned the old paste off, taken the board out, re-alligned the bolts, re-applied the paste, and got the HSF bolted back firmly into where it's meant to be, I'm getting these temps.

NewTemps-1.png


The CoreTemp readings match my BIOS temps now, so I shall guess that they're right. I'll get some Prime running and see what it maxes out at.


Oh and FWIW, this is the inside of my case, suitably captioned. (lol) This is why I just knew it wasn't an airflow issue, there's nothing in there to obstruct. Ignore the front USB cable floating around in mid air there - it's because the case was on it's side. It sits nicely at the bottom ordinarily!

CasePic.jpg



Thank you kindly for the asisstance gents, I can now OC without panicking! :D

Have a Badger as a reward.

17-FEB-Cute-Badger.jpg
 
Mushroom! Mushroom!

Further to my earlier issues, One overclock and four hours of Prime later and my temps show thus;

CoreTemp-Scr-1.png


Although in the BIOS I upped the voltage to 1.3000, Everything's still showing 1.2125/1.213. Weird.

Clearly stable and nice and cool at 3.06GHz though.

Shall try for 3.2 tomorrow. :D
 
Many Q6600 can achieve 3GHz on stock volts; from there I would increase the volts and clock speed if your CPU is stable on stock volts.

Although in the BIOS I upped the voltage to 1.3000, Everything's still showing 1.2125/1.213. Weird.

D

The variations between voltages are vdroop and vdrop.

vDroop is Idle -> Load

vdrop is the difference between BIOS and Idle.
 
The variations between voltages are vdroop and vdrop.

vDroop is Idle -> Load

vdrop is the difference between BIOS and Idle.

Errm ... this means nothing to me. :confused: Could you maybe explain it for me in words of two syllables or less? I take it something in there is the reason why all my software says 1.2125 whereas I told my BIOS 1.3? There's a Badger in it for you.
 
The BIOS can't accurately set the voltage the CPU gets. I'm not sure of all the reasons for this but it will include things like inefficiencies in the circuit (these will increase at higher temperatures) and this is what's known as vdrop. Every motherboard does it to a certain extent, and some compensate for it better than others.

When the CPU becomes stressed (i.e. under load), simplistically, the power draw changes so the voltage also changes. This is called vdroop, and again every motherboard has it and some compensate for it better than others.

So yes, there's a reason the software says less than the BIOS :)

Do I get a badger? :p
 
Back
Top Bottom