interesting. I skipped the part with the double click in the initial post of yours. Thanks for pointing that out. It is helpful and works, kind of... On the newest driver I have a bug that causes the core clock to become unstable and clocks down wildly to +-800 mhz. (This happens with events related to DXVA.) Disable all states except one, didnt fix the problem, though. The command line utilization is extremely helpful! Thanks for implementing that feature. I made a small workaround with a batch file that applies regularly the clock settings (different profiles) with your tool. A little critic: it would be more helpful if you can add a visual hint that let the user activate/disable the Pstates. Something like a checkbox beside the Pstate. Double click is not really intuitive. This is an excellent tool to apply Wattman setting without the need to open the ugly and slow Wattman UI. I will keep suggest this tool in the future.