Advice on vcore limit

moggsy

moggsy

moggsy

Associate
Joined
11 Dec 2006
Posts
223
Hi all

My 1st OC going very well :)



If those temps are right, there's room for more too.

Speaking of which - what exactly are these 2 temp readings, working from the top down?
1) That's the system temp I think, yes?
2) This is the one that I've got my eye on - at idle it's about 36*C but as you can see it goes up a lot under load. Is this likely to be the Northbridge (or Southbridge) temp?? What's a safe limit if it is?

Regarding the vcore limits.....I've read Jokesters excellent sticky (and others) on how to begin OCing, and the safe amount on how much to increase the vcore mentions going over by 20% of the default limit.

Now maths has never been my strong point, but I reckon that means if my default is s'posed to be 1.300, I can go up to 1.560v....is that right?

At the minute for this OC, I've got vcore set at 1.3875 in the bios (though spdfn sees it as 1.31)......

It just seems to me that, if my maths is correct (which it usually isnt :) ....) and those core temps are right, there seems room for an awful lot more - and as you can see, I'm at 3.68Ghz on my [email protected]!

My one concern as I said, is the Temp 2 reading.

Thanks for any input ;)
 
Dont be to concerned about the Temp 2 just yet, my proc is the same as yours and on full load hits between 55 and 60 .. not ideal but no to harmful.
 
Logic Zero said:
1.55v is typically regarded as the safe limit for air cooling! Nice overclock there mate, great temps and nice low voltage too, you got a nice chip! :)
Click to expand...
My bubble's just been burst on another forum :rolleyes:

Was told that my temps are probably out by 10-15*C!!

My bios' PC Health page says the CPU is at 36*C when I'm tinkering in the bios and when I've booted up, Speedfan & Coretemp say I'm idling at 25/26*C so he's prolly right :(

Not as much scope as I originally thought...... :eek:
 
cpu temperature is different from core temperatures, Coretemp shows the core temperatures, and motherboard software generally just shows the cpu temperatures
 
another thing, sorry to burst your bubble, but when overclocking, you usually hit a wall when you start overclocking quite high. for example a jump from 3.6 to 3.8, could actually take a massive leap in vcore to achieve, which of course mean massive temperatures
 
young said:
cpu temperature is different from core temperatures, Coretemp shows the core temperatures, and motherboard software generally just shows the cpu temperatures
Click to expand...
......right......:confused:
So which one is the most important one....the core I'd assume?

another thing, sorry to burst your bubble, but when overclocking, you usually hit a wall when you start overclocking quite high. for example a jump from 3.6 to 3.8, could actually take a massive leap in vcore to achieve, which of course mean massive temperatures
Click to expand...
Well I went from 3.6 to 3.68 and only went up one notch in the bios' vcore values so hopefully I haven't got to that wall yet :)

Thanks for your input - it all goes to understanding things a bit better ;)
 
sorry, wasnt said to put you off, just preparing you!

id pay more attention to the seperate cores, your right. I think the CPU temperature is more of a general temperature which never goes above that of the cores. so I doubt you'll come under problems with that before you do with the temperatures of the cores.

nice overclock though so far, you could prob get 3.8-4 with decent temperatures by the looks of it!
 
young said:
sorry, wasnt said to put you off, just preparing you!
Click to expand...
You didnt at all - i was just a bit confused as to the diff between the two of them ;)

On another forum, I've just been pointed towards Everest as the monitoring suite to get the most accurate readings... I've installed the latest version and Core 1&2 are idling at about 45/46 at the mo....I ran Orthos for a few mins and the temps started getting higher and higher - they got to 73*C so I stopped the test, as I was starting to sweat a bit myself looking at those temps :D

Bummer - thought I was going to be getting 3.8 - 4.0 but I'll have to call it a day methinks and knock it back down a notch to 3.6Ghz - still great though :)
 
Great clocks and for a beginner your doing great, you could try reseating the CPU sometimes you can get a 100Mhz or so if you lower the temps with a better contact. Arctic cooling MX2 or Coolaboratory are great tims.
 
sammie377 said:
Great clocks and for a beginner your doing great, you could try reseating the CPU sometimes you can get a 100Mhz or so if you lower the temps with a better contact. Arctic cooling MX2 or Coolaboratory are great tims.
Click to expand...
Thanks ;)

Knowing my usual luck - if I were to reseat the cpu, I'd get a worse contact, so I'll keep it at 3.6Ghz!

Good job the guy on the the other forum pointed out the innaccurate temp readings.... I could've gone on and on till my cpu went pop!! I had Speedfan, Coretemp and TAT all telling me my temps were 15* too low :(
 
I read recently that increasing the FSB over the multiplier improves benchmarks with the Q6600. So you might want to reduce your multiplier and increase the FSB assuming the RAM can cope :)

Mine is at 3.45GHz with an FSB of 430 and a multiplier of 8. However, my RAM keeps crashing Prime95 so I've still got a few tweaks to do :(
 
Well I put it back to 3.6 and everything was sweet....but I cudn't let it rest could I?

I went back in again after an hour or so and had another fiddle.....I dropped the vcore a notch to 1.38125 and re-ran orthos. This time, my temps never went over 60*

3689hrsnn4.jpg


Maybe a few more tweaks?..... :D
 
You must log in or register to reply here.
Back
Top Bottom