CPUgenie - New Undervolting Tool

How can I use IDA state with CPUgenie? It doesn't appear in CPU states!


Thank you in advance.

[[]]

 

Just purchased this (still not receive key yet).
Don't know why people forget this excellent tool.

 

you can use RM clock with core 2 duo and even with half multipliers core 2 duos... free and don't need to pay... i got lots of problems with CPUgenie so that's why RM clock.. IMO , not worth buying it unless u got a core 2 quad or core i series processors....

 

been using it since I switch my FX to Windows 7 (about 7 months). Its a great tool and don't mind the price

 

tried RMClock, but it cannot recognize CPU Vcore properly. When CoreTemp, CPU-z, everest show that CPU Vcore is 0.925v, RMClock still shows 1.0375v. That's why I've chosen CPUGenie. Satisfied with it

 

Hi everyone,
I used RMClock for more than one year to undervolt my T5800. it produced good result but the lowest voltage i can assign was 1.050 V. which i used for all 6 multipliers without any problem.
CPUgenie unable me to use 1.00 V. (which is the lowest possible voltage) for all multipliers without any problem also.
i wonder if anyone succeeded in using less voltage.
____________________
hp pavilion dv5: CPU T5800 undervolted to 1.00 V., 4GB Ram, 5400 Hitachi 250G., 1280x800 screen, Nvidia 9600GT

 

Does CPUgenie not work with CULV cpu's? I've got an Intel SU3500 that I'm trying to undervolt with no luck.

When I open CPUgenie it shows 3 voltages I can change for each multiplier (.875,.887, & .900) & when I change those the CPU Monitor shows the cpu running at the correct voltage.

The problem is when I click "Unlock Voltages" it shows several more voltages to select from, but when I select any of them & go into CPU Monitor the cpu still runs at the stock voltage.

Is anybody successfully using CPUgenie with an Intel CULV cpu?

 

Hi Everyone,

I've been using CPUgenie for the last couple of weeks, really like it actually, but I’m having this funny problem. After a while, with CPUgenie running, my laptop suddenly maxes out 1 core of its CPU. According to process explorer wlanext.exe is the guilty processes, which is windows wireless service. So I tried reinstalling my wireless driver, killing the service…all the usual things, none of which solved the problem

The solution I found was to kill CPUgenie and then the problem magically went away and doesn’t come back! Once CPUgenie is restarted though the problem reappears…strange! I was wondering if anyone else has been having this or a similar problem?

Probably should mention my CPU is a Core 2 DUO P9300 and I'm running Windows 7 64-bit

Thanks in advance.

 

Complete tangent: try Throttlestop instead. It's, small and free, will unlock SLFM undervolting voltage ranges. If you've got a Dell system then you'll get dualIDA overclock too. Best of all, the author, unclewebb, is on this forum and accepts enhancement requests. A great replacement for rmclock.

 

Thanks for the suggestion, I've just taken a look at it - a very nice tool. Unfortunately it doesn't seem to allow me to set the VID for each multiplier which is what I'm trying to do with CPUGenie.

 

Not really necessary imho. For highest battery power saving just lock the highest multiplier on the lowest voltage, then 'exit' Throttlestop ensuring the 'restore VID/DID' isn't selected so it's monitoring doesn't take up CPU cycles. Works a treat.

For AC, I just set the highest multipler to use the lowest stable voltage, enabling EIST and C-states.

 

That works except my CPU seems to spend about 12% of its time in the second lowest multiplier, which isn't set at the lowest voltage it can run at. CPUGenie allows me to control that multipliers voltage as well as the top one – it also allows my to set some more advanced power plan settings governing when the CPU will switch up and down multipliers which Throttlestop doesn’t seem to support.

Does anyone know how to do that with Throttlestop? Or has anyone seen the problem I’m having with CPUGenie maxing out one core of my CPU – CPUGenie support doesn’t seem to be contactable.