Quote:
|
Originally Posted by MrMsyvc
Another lengthy WoW session, 4-6 hours (cough), best temps yet. 68-70C at 2Ghz. Max res using lappie LCD, max game settings. Temp and cpu sinks like a stone as soon as the game is off.
|
RMClock is indeed a catch!
Apart from not being able to monitor the CPU load correctly and a minor MFC bug when switching to Monitor tab after some time (btw, both bugs are logged now on the author's forum so let's hope we'll get a fix soon) the program makes wonders when it comes to CPU temps.
I set mine to do Automatic management between FID/VID: x6/0.812 - x15/1.212
Running a quite old 3D application (called TLWater btw) which brings my CPU at 85C after only 10-15 minutes I was surprised to see that RMClock manages to lower it with 10C, stabilizing it at 75C.
I've read that some people managed to run RMClock as low as 1.1V at x15 but others had problems with these settings so I decided to play safe.
According to Intel, the VID values for x15 (2.0GHz) can vary between 1.260 (min) and 1.356 (max).
I set then the maximum to x12 (1.6GHz) / VID 1.084 and loaded Warcraft III which is not a very demanding game. I played a single player mission at 1152 x 864 with all settings at high. The game run very smooth and the temperature was below 70C. Wonderful!
I still don't know what impact it has setting the VID to 0.700 at x6 (800MHz) or setting it at 0.988 which I think it's the default.
And another thing: RMClock does work with ePM loaded (CPU set at High in ePM) and it overrides ePM CPU control. MobileMeter's CPU frequency monitor also works if set to "Measure actual".
Cheers,
_EnF_