problems undervolting

Hey all

I undervolted my laptop today, its stable at "State 4" at 1.025v, and i checked that with prime 95 and two instances of super pi running in the background and then running two instances of p95 for 4-5 hrs.

Everything seems fine but it doesnt seem like its undervolted. It still feels kinda warm - warmer than when i had my laptop managed by P4G.

Im using RM clock, and according to it when the processor is throttled, at 10x the voltage is 1.025 and when idle its 6x at 0.95.

The problem is when i go to control panel>system it shows the processor running at 1.67GHz! even though RM says its at 1GHz. When my system was managed by P4G it showed 999MHz in the system properties. Even when i uninstalled P4G and used windows to manage the power it showed 999MHz. But now using RM clock it stuck all the time at 1.67GHz.

What am i doing wrong? Has this program been known to be on but not working. If definately starts with windows and in the sys. tray it shows it at 1.00GHz.

I also used cpu-z and it showed the processor at 1000MHz when idle with a throttle of 1000MHz. Does it mean RM clock is working at windows aint reading it right? Or am i doing something wrong? How can i make sure of the clock speed?

Thanks for help.

 

I have no experience undervolting Core Duos, but is probably warmer for the reason that, while the actual CPU is running cooler at full load, the fans are not kicking on as often and thus the heat is being built up.
I took off the undervolting on my machine and it runs noticably cooler at full tilt. At idle, it is about the same temperature, perhaps a bit warmer but not by much.

 

OK, i can see why my laptop may feel hotter but that doesnt explain why windows seems to think the processor is running at 1.67GHz. I know it detected the processor running at 1.0GHz when i wasnt running RM Clock but while using it the processor seems to be at 1.67GHz all the time, well accoring to windows anyway.

Anyone else have this problem? For those of you using RM Clock does windows detect your CPU speed correctly in controlpanel>system?

 

heres a picture to show what i mean.

 

Don't have any real answers for you, although I will theorize a little .

First, I see you are running 2.1 of RMClock, but there was a bugfix version released yesterday. You might ask on their forums as well.

You do realize that a 6.0 multiplier gives you 997 Mhz or 1.0 Ghz and a 10x multiplier gives you 1.67 Ghz (that's where your two numbers are coming from).

You should be able to tell from your system temps.

Unload RMClock and run something like Prime95 or Super PI which will peg the system at 1.67 Ghz and see what the stable temps are.

Then see what the Idle temps are.

Then start RMClock. At idle, your temps should probably be lower than the normal idle temps. If they're near the Prime 95 temps, perhaps the system is running at 1.67Mhz.

I would tend to trust CPU-Z and RMClock more than the Windows screen. What was the yellow readout with system temps (P4G ???)

It is also possible that the Windows system properties kicks the processor out of idle mode, but unlikely since you said it worked correctly in the past.

There are also utilities such as Everest or SiSoftSandra that you can try to get a "second" (fourth, fifth) opinion.

 

Thanks for the reply Tiger-Heli

The small yellow readout is Mobilemeter, its quite a useful tool for showing CPU clock, temp and HD temp.

I figured out that windows is an idiot and cant read the real clock for some reason. Using RM clock the processor is clocking up and down at the new voltage. In mobile meter i found another setting for measuring the cpu clock speed using the windows driver. This gave a real-time reading and it showed the processor clocking up and down fine.

I tested it using windows "Always on" and "laptop" profiles then tested it using RM Clock. Im not worried about it not working anymore, i know it is after the opinions (RM itself, cpu-z and now mobile meter).