Is there a reason this is happening?

[Funkwagen]

Warning, big image:
http://dl.dropbox.com/u/636616/Throttling.png

I've tried turning off intel speed step, but it appears that the clocks just remain at 2.4ghz regardless. Is the system limiting the clock speeds due to lack of available power? I'm running 2 470s in SLI with an i7 at 4.2ghz on an 875w power supply.. so I'm wondering if it might be that.

http://extreme.outervision.com/psucalculator.jsp This is telling me the minimum spec PSU would be a 750w PSU but I'm not sure.

Anyone know?

EDIT: Throttlestop doesnt work either.

[donmarkoni]

I don't see any throttling.

Unigine Heaven uses so little processor time, that there is no need for the CPU to speed up.



You are fine.

[some_one]

This is just the way TMonitor works which was discussed in detail under the ReaTemp Thread.

TMonitor will only show a true multiplier/frequency if a core is 100% utilized during it's sampling period. In your case once your core(s) drop below ~57% utilization then TMonitor uses 12x (2405MHz) no matter what. Since it's load based you would normally see less than 12x maybe even close to 0 so a fake multi was used so people wouldn't get upset when seeing such a low number.

[fordf250]

I am running an i7 950 at 4.2G ht and 1.4Vcore with two 470's in sli with a 600w 80+ gold psu no problems. I bench at 4480mhz and 1.5vcore. Even with everything at full load there are no problems with psu, it does not get hot and the fan never spins up even with everthing on air and the gfx pcbs an nb at 65C+. The difference in Heaven from 3.07G to 4.4G is only 0.5-1fps so its not using the cpu much.

[unclewebb]

Throttlestop doesnt work either.

Can you explain that further? ThrottleStop is always a work in progress. I've been working on improving Sandy Bridge support. It should report your Core i7 correctly but it can't make your processor do something that Intel did not design it to do.

If there's a problem or something you don't understand, show me what it is so I can fix it or explain it.

ThrottleStop 2.97
http://www.mediafire.com/?c1dla4mk4i9npnq

[[XC] hipno650]

I am running an i7 950 at 4.2G ht and 1.4Vcore with two 470's in sli with a 600w 80+ gold psu no problems. I bench at 4480mhz and 1.5vcore. Even with everything at full load there are no problems with psu, it does not get hot and the fan never spins up even with everthing on air and the gfx pcbs an nb at 65C+. The difference in Heaven from 3.07G to 4.4G is only 0.5-1fps so its not using the cpu much.

thats what I call danger batman... 600w is really pushing it for an OCed GTX 470 SLI IMO

[Funkwagen]

Can you explain that further? ThrottleStop is always a work in progress. I've been working on improving Sandy Bridge support. It should report your Core i7 correctly but it can't make your processor do something that Intel did not design it to do.

If there's a problem or something you don't understand, show me what it is so I can fix it or explain it.

ThrottleStop 2.97
http://www.mediafire.com/?c1dla4mk4i9npnq

It doesnt seem to be an issue with throttlestop after all, as some_one explained its just Tmonitor being sorta funny (thanks for giving me that info, was worried for a bit haha) Other than that, looks like throttlestop DOES work for what its intended to do.

I am running an i7 950 at 4.2G ht and 1.4Vcore with two 470's in sli with a 600w 80+ gold psu no problems. I bench at 4480mhz and 1.5vcore. Even with everything at full load there are no problems with psu, it does not get hot and the fan never spins up even with everthing on air and the gfx pcbs an nb at 65C+. The difference in Heaven from 3.07G to 4.4G is only 0.5-1fps so its not using the cpu much.

Be careful man, I plugged my PC into a killawatt today just to get an idea of what sort of power consumed and at 100% load (GPUs AND CPU, done via furmark and linx) I was drawing up to 864w of power. What sort of power supply make are you using btw?

Anyway guess this solves everything, I was under the belief that the system was throttling itself due to lack of power I guess. Thanks for the help!