Speedfan

Associate
Joined
21 Jun 2009
Posts
1,668
Location
Chester/Loughborough
Ive decided to see how far my Q9550 will go, got a couple of hours free ;)

Im currently running at 3.3GHz stable with no voltage changes.

I usually use CoreTemp to monitor my temps but have Speedfan . . . just because + am wondering what the different temps are ?

Speedfan.jpg


Inparticular: System and Temp both sitting at 90C
They only ever change about 2-3C even under load during that heatwave a couple of weeks back.
They are always the same too.

Im pretty sure the temp labelled CPU is my northbridge as the fan listed as CPU1 Fan is actually the northbridge cooler as it only ever turns on when the 'CPU' temp is high (35C i think).

Any ideas ?
 
Well im gonna have to step out of stock voltages now, just got an error on core 1 at 395x8.5.

How much of a step up should I make ?
Im on 1.2375V now. Im thinking of going around 1.25V, see how that works out.

18.6% overclock on stock voltages aint bad =]
 
Last edited:
Looks good so far. Dont know much about intel but 1.25 sounds fine. That should give you a nice stable overclock.

Have you tried Real Temp?
 
Bump the Volts to 1.25 and see how far you can go from there.

The NB might need a bit more (0.1 or so) so deal with the higher FSB.
 
Try clicking on 'Configure' to see what speedfan is ,allegedly, reading. I've read that if speedfan cannot find a sensor it may well give an erroneus reading.

Whats your chips 'vid' ?
 
Alright, I did 1.25v and got 395x8.5 seemingly stable (3.3575GHz)
Then tried for 3.4GHz and it hung on windows loading screen, so i tried 1.25625 and it BSOD before windows loaded and the same for 1.2625.

Is it likely to be the northbridge limiting it now (memory is unlinked and currently underclocked at 800MHz) ?

If so what are safe voltages to bump it up to ?

Heres Intels spec sheet for the Q9550 which displays the VID range : 0.85V – 1.3625V. Although I have read of people going up to and just over 1.4V on these chips.
 
I have CoreTemp, use it to monitor temps.
Displays the VID as 1.2375v . . .
And OCCT displays (VCore) as 1.22 (is that supposed to be the same thing ?)

EDIT:
I have these voltages available to me in BIOS-
CPU CORE
CPU FSB
Memory
nForce SPP
NF200 Voltage Level

set the CPU CORE to 1.25 and CPU FSB to 1.2 and booted into windows, OCCT flags an error on core 2 tho.

any explenation as to what those voltages refer to would be appreciated.
 
Last edited:
My Q9550 has the same vid and is stable @ 3.4 (400fsb) when running 1.1875v (slightly undervolted).

I am not saying that your chip will be as good - it could be better or worse !

BUT would not , yet , start slinging increased voltages at the chip - it may be something else that is causing your problems.

Got to say I have no experience of your board/chipset so am working a little in the dark.:(

I have read that if you use all 4 memory slots then you may have to increase the northbridge voltage a little to get stability. I have no experience of this myself but it might well be worth some research.

BTW it's not unusual to see a drop in voltage comparing what you entered in the Bios and what OCCT/Real Temp show as the volts - known as vdroop - I think.
 
Ah alright cheers for that, yeah Ive heard about the memory drawing more volts.
Which setting is it im increasing for the northbridge then ?
CPU FSB upto 1.15(not 1.2 as i said before) helped it boot into windows but is still not stable.
Ive heard that NF200 is related to SLI + RAID configurations, is that right ?
is it CPU FSB for northbridge or nForce SPP ?
 
Cheers Ill take a read =]
Im pretty sure its nForce SPP; whacked that up a notch and everything else back down to stock and it lasted longer in OCCT than before, tho still flagging an error.

EDIT: Heres the relevant text for reference :
-SYS VOLTAGES
-CPU CORE: This will take some working on your own. Start in the green area for 3.6ghz and work way down. For 4.0ghz and above I would say start at 1.225v for later batches of E8000 series procs. For older batches like my Q746 start with 1.3 for 4.05ghz. I am sitting at 1.39 in bios and 1.344 in CPUID.
-CPU FSB: 1.3 (I dont recommend going any higher)
-MEM: This is where I always say give as much as you can that the warranty will cover. OCZ has Extended Voltage protection or EVP that allow overclockers to give em a ton of voltage. I set mine to the max that they warranty will cover which is 2.2v
-SPP: 1.4 You may go higher but I dont recommend it for modest overclockers
-MCP: 1.6 You are pretty safe here, if you run into stability issues I dont see higher voltage here helping.
-HT: You might have luck by leaving it in auto... otherwise 1.3 should get you there.
GTLVREF lanes 0-3: Auto for now. I have found no benefit with these settings. Maybe someone can elaborate on their experiences here.
 
Last edited:
Try clicking on 'Configure' to see what speedfan is ,allegedly, reading. I've read that if speedfan cannot find a sensor it may well give an erroneus reading.

Whats your chips 'vid' ?

sorry, did not mean to overlook this post -

speedfanconfigure.jpg


Got things running stable at 3.5GHz atm, not sure how much further it will go though. seems heavily Northbridge limited. Might take 2GB out just to see how far it could go.
 
I would guess (and hope:D:D) that the two entries showing 92c are faulty.

Unfortunately I am not able to state with absolute certainty that this is the case - Would suggest you 'google' a bit ; such might provide the reassurance needed.

Good to hear you've got to 3.5 - No idea what volts your putting through your cpu but whatever it is you might try with lower. IMO best clock is a nice balance between performance/volts/heat.
 
It would appear that LM78 is a sensor chip and Winbond has something to do with aux inouts/outputs. lots of people reporting radiculous temps on these sensors through SpeedFan which would appear to be misinterpreting data or something.

I got 3.6GHz last night before I went to bed still on CPU stock voltages (1.2375 i think), had to up the nForceSPP to 1.45v which the mobo BIOS considered safe but I wasnt sure so turned things back down.

Have recorded all settings at different clocks though so I should be able to carry on later relatively easily.
 
Back
Top Bottom