My idle temps ok?

Did a Prime test temps were about 76 for a 4 hour test plus tbh honest guys im sick of testing getting obsest with bloody temps:D, keep telling myself stfu and play.;)
 
76c is grand, now stop with the testing:D and play some games:) Tbh, temps in gaming wont get as high as prime etc.
 
Yes your idle temps are fine and if you are only hitting 76 under load you have a bit of headroom now make the most of your system and get on and use the thing
 
I know it throttles the speed of the cpu, any reason why i should turn it on?


Cheers

You should turn it on so that your CPU runs at a lower speed when it's not doing anything/much. Saves energy and money, will reduce your idle temps and will help counteract the reduction in the CPU's lifetime caused by overclocking.

Running at 4 GHz all the time is totally pointless.
 
You should turn it on so that your CPU runs at a lower speed when it's not doing anything/much. Saves energy and money, will reduce your idle temps and will help counteract the reduction in the CPU's lifetime caused by overclocking.

Running at 4 GHz all the time is totally pointless.


Cheers for the info man.;)
 
I don't see how much if anything moneywise is saved tbh. Maybe with multiple pcs in a work environment etc.. but a single pc? As far as overclocking damage, if done right then its neglible, say a few months of a 20 year lifespan. By the time damage would have occured, the cpu would be in the bin already a decade earlier, for example. I've still got a K6-3+ 450 thats been running 24/7 @ 620Mhz 2.4v since god knows when in a friends ancient win98/later windows 2000 CCTV box, only update is a pci card for a 750gb hdd 2 yrs ago when the 8.4GB seagate packed in lol.
 
Last edited:
I don't see how much if anything moneywise is saved tbh. Maybe with multiple pcs in a work environment etc.. but a single pc? As far as overclocking damage, if done right then its neglible, say a few months of a 20 year lifespan. By the time damage would have occured, the cpu would be in the bin already a decade earlier, for example. I've still got a K6-3+ 450 thats been running 24/7 @ 620Mhz 2.4v since god knows when in a friends ancient win98/later windows 2000 CCTV box, only update is a pci card for a 750gb hdd 2 yrs ago when the 8.4GB seagate packed in lol.

It doesn't matter how little money or energy is saved, it's still saved. However, even if this is unimportant to you, you can turn the question on its head - what's the point of turning SpeedStep off?
 
I've had speedstep interfere with overclocks, causing reboots on state change etc.. probably BIOS bug specific but does happen. Also, some boards i have had did not factor in the voltage change at max overclock state, so when the multiplier was reduced during speedstep it also read the specific corresponding VID from the cpu, problem was, the FSB was raised, so instead of say 10x133 it was 10x200 and the speedstep vid was not enough to remain stable, hence an idle freeze or reboot.

On the other hand, if the board keeps the overclocked vcore to the same no matter the multiplier, then i'd guess the reduced frequencies power draw would be darn close to the overclocked frequency as i think the most saving is brought by the reduced vcore, not frequency. Its a totally different game when overclocking as speedstep is tailored to a stock frequency cpu.
 
Last edited:
Well sure, it can affect stability in some cases but then that's what stability testing is for. Having C-states enabled is far more likely to affect stability methinks but if you can have one or both enabled and retain stability then go for it.
 
The problem with stability testing is that it dosen't take idle into account, so the machine might well be stable at o'ced speed and volts but not during idle when voltages drop, hence why i never use speedstep when overclocking. It can be very perplexing when your machine passes numerous tests of IBT, prime etc.. but reboot when browsing a web page.
 
Back
Top Bottom