Well actually I don't think it is a power monitor mistake. CPU-Z has a much slower update rate, but on my machine it still reports 1.200 volt sometimes.
To be sure about readings I made a monitoring feature in my software that tracks realtime pstate changes asking directly to the processor's Machine State Registers every 50ms and registers transistion to other pstates than 0, 1 and 2. A one minute monitoring reports this:
Code:
Turion Power States Optimization and Control - by blackshard
Detected CPU:
Family: 0xf Model: 0x3 Stepping: 0x1
Extended Family: 0x11 Extended Model: 0x3
Processor has 3 Power Planes
Monitoring...
pstates:6
Detected pstate 6 on core 0
pstates:1 6
Detected pstate 6 on core 1
pstates:1 6
Detected pstate 6 on core 1
pstates:2 6
Detected pstate 6 on core 1
pstates:1 6
Detected pstate 6 on core 1
pstates:2 6
Detected pstate 6 on core 1
pstates:2 6
Detected pstate 6 on core 1
pstates:1 6
Detected pstate 6 on core 1
pstates:1 6
Detected pstate 6 on core 1
pstates:2 2 ^C
Attached to this post there's the application for Win32 targets. It requires admin privileges and visual studio 2008 runtimes.
Trying to launch the app without any flag shows accepted command switches.
Launching the app with -CM will start monitoring sequence (use CTRL+C to terminate the session), while using -l switch will show pstates table.