The only purpose of the Counter Control tool is so users can watch to see if Windows Defender is setting the three different timers to mode 2. When that happens, Counter Control will show 0x222 and CPU performance will be reduced.
Most monitoring programs like HWiNFO will set two counters to mode 3 and the other counter is not used. The third counter will usually be left in mode 0. That is when you will see 0x330. That seems to be the most common value.
What does 0x333 Normal means?
That means that the three individual counters are all set to mode 3. I do not think this is as common as 0x330 but it is still perfectly normal. CPU performance should be OK. Windows Defender only reduces performance when the 3 counters are set to 0x222.
During sleep mode, all 3 counters are stopped and reset. That is when they are all set to mode 0. This shows as 0x000. If you have some software running on your computer that is using these counters, as soon as your computer resumes from sleep, that program will automatically turn the three counters back on and set them to mode 3.
On my computer when I resume from sleep, if ThrottleStop is not running in the background, Windows Defender will immediately set the three counters to mode 2 and performance will be reduced. I never realized that was going on until I started using Counter Control to monitor the situation.
You are welcome. Thanks for the feedback. Each counter has 4 bits of information that can be set or cleared. Counter Control 1.1 reported all 4 bits. To monitor for the Windows Defender issue, the upper two bits can be ignored. Counter Control 1.2 only reports the lower two bits. Each counter will only report if it is in mode 0, 1, 2 or 3. That is the important info.
Do you know if you have any Acer software running in the background on your computer? Some Acer program might be setting the three timers to mode 3. This is not an issue. Just curious. When I first boot up and Windows Defender is not doing anything, these counters are not used on my computer so Counter Control reports 0x000. It will stay like that until Windows Defender thinks that no one will notice if it takes over control of all of the system timers. Let's just say that, I noticed!