That's device ID register of VRM chip (which is located at I2C bus 2, device 70), and 0A is a proper DeivceID of VT1165 VRM. If there really was "invalid" it means that something else (other monitoring software?) captured I2C bus at that time. If the same capturing will happend during RT startup (when it scans for sensors/VRMs) - it won't see them.

"Just open PowerUser tab, [select "RivaTuner \ NVIDIA\ Overclocking", ] set ShaderClockRatio to -1 and restart RivaTuner. It is the fastest way for beginners to get pre-163.67 clocks on 163.67 and newer drivers."

Click to expand...

Aha ... you see ! that is what Unwinder (& others) mean when they repeatedly redirect you to a sticky: You do can find answers by yourself if you just look good enough.
What his point is: He'd rather wants 1000 people with a problem spend each 15 minutes by looking thoroughly for the answer, than him spending 1000x3 minutes (=50 hours) on answerring and repeating himself ...

P.S. Sticky's are allways on top of the posts list (not that hard to find)
P.P.S.If you never read (windows) help-files: Please try it, there is a lot of useful information available for most programs, the one for RT it is very comprehensive.

The approach you are referring to works very well indeed but it involves starting the RTSS.
While it's not a biggie to start the RTSS, I was also looking for a solution to be able to switch between two overclocking profiles without using it.

In fact, what I want to do is to underclock the card for normal 2D operation and bring it back for 3D gaming.

Then I added a threshold for the Core clock like this:
Frequency: 350
On upward threshold crossing: Launch "ClockHigh3D"
On downward threshold crossing: Launch "ClockLow2D"

This approach is based on the ForceWare drivers switching the core clock between 2D and 3D and going over the "350MHz" threshold which is chosen in between the "Standard 2D" and "Low power 3D" frequencies.

The reason I activated "Low power 3D" in RivaTuner is because I'm not sure
if the ForceWare drivers have a default value for it and despite the fact it's not activated will still try to use it.

While this works switching from ClockLow2D to ClockHigh3D it doesn't work the other way around.
What happens is, it goes from ClockHigh3D to ClockLow2D for just 1 or 2 seconds and then goes back to ClockHigh3D as if when switching profiles it activates "Performance 3D" by default.

There is a certain delay (around 10-15 seconds) between attempts to switch from 3D to 2D which denotes that ForceWare drivers don't switch immediately back from 3D (which is not a problem).

The attempts to switch from 3D to 2D are easily vissible on the monitoring graph and happen regularely every 10 or 15 seconds.

I would appreciate if someone can test this and confirm my findings.
Also, any comments and opinions are welcome.

You can use this approach under XP, but not under Vista. Clock frequencey change in Vista driver always results in temporary switch to 3D performance level (most likely driver does that to stress-test requested clocks), so it won't let you go down.

You can use this approach under XP, but not under Vista. Clock frequencey change in Vista driver always results in temporary switch to 3D performance level (most likely driver does that to stress-test requested clocks), so it won't let you go down.

That's device ID register of VRM chip (which is located at I2C bus 2, device 70), and 0A is a proper DeivceID of VT1165 VRM. If there really was "invalid" it means that something else (other monitoring software?) captured I2C bus at that time. If the same capturing will happend during RT startup (when it scans for sensors/VRMs) - it won't see them.

Click to expand...

after long search i think i figured out the source it's 'ATI tool' driver
(need to be disabled/removed from active hardware drivers)
i guess it activated and then stays activate after i started by mistake ATi Tool ...

anyway really thanks for trying to help me Unwinder ... this was pain to find

That's not true.
ForceWare drivers are switching correctly to 2D on Vista with Aero enabled.

Click to expand...

The Aero interface is 3D (runs DirectX 9Ex) so it can't have the 2D profile. Another fact is, that most cards should have identical "2D" and "Throttle" performance levels (Throttle may also be known as "Low-power 3D") - yes, you guessed it, the card uses the second with Aero.

If you flash your video BIOS, you can set another Throttle profile that's higher than 2D, but uses less watts than performance-3D.

Dear ex-ATI users, spend a few minutes on reading FAQ and studying NVIDIA 2D/3D clock control basics. Everything is working properly, the only malfunctioning thing is your understanding. The answer can be easily found in the forum, and even in this thead.

The Aero interface is 3D (runs DirectX 9Ex) so it can't have the 2D profile. Another fact is, that most cards should have identical "2D" and "Throttle" performance levels (Throttle may also be known as "Low-power 3D") - yes, you guessed it, the card uses the second with Aero.

If you flash your video BIOS, you can set another Throttle profile that's higher than 2D, but uses less watts than performance-3D.

Click to expand...

Well, I know Aero is 3D but the ForceWare drivers are switching back on "Standard 2D" profile on Vista with Aero. I've set all 3 profiles (so, including "Low power 3D") on RivaTuner to have different clocks and this is what happens.

Maybe the ForceWare have a way to detect Aero and use 2D, I don't know...

One limitation is that you cannot use different clocks for memory between 2D and 3D inside a single profile. Forceware drivers switch between 2D and 3D and not RivaTuner. I think, RivaTuner only sends the whole lot to the drivers.
If you want different memory clocks try creating 2 overclocking profiles. See my above post of how I defined 2 profiles.

And btw, one thing - you need to click "Apply" before switching the combo box selection at the top between the 3 power modes.