I did, but I found something even more interesting. Last night It would not work, but now after a reboot (the next day), it seems to be working. There seems to be some sort of a "trigger" that causes this kind of behavior to happen, since late last night when I was troubleshooting the cores would be constantly at P2 voltages/frequencies even when "idling" in desktop when CTR was running, even after restarting CTR multiple times and closing any other applications. The CCX usage min/max settings are really confusing/misleading and need some explaining(and for future reference, could use CPU based recommendations in application). At first glance, having P1 CPU usage at 75% and P2 CCX usage at 25 - 75% gives the impression that these are simple CPU usage parameters, but I need around 55 - 60% on P2 CCX Min for optimal (PB) clock speeds at 3 thread CB20. Which gives the impression that CCX Min is based on actual CCX usage, but on 6 threads the P2 activates even though the threads are split evenly among 6 cores across 2 CCXs, in which case neither of the CCXs should above the P2 minimum threshold. You can see the confusion I am having here right?