Search results

09 keeps the counter set to 0x330 indefinitely now, even after quitting HWinfo. On my first test I had the curious case of a Defender Full scan getting stuck until cancelled in its early (single-threaded) phase, but I cannot say for sure if that happened shortly before or after starting 09 for...

Maybe you can ask the TS/CC author what he is doing exactly? He specifically mentions HWinfo in the Readme, so maybe he is willing to help!?

Unfortunately still happening here: 2024-04-03 14:25:52 00:01:21 0x330 Normal 2024-04-03 14:25:53 00:00:01 0x222 Defender 2024-04-03 14:25:54 00:00:01 0x330 Normal 2024-04-03 14:25:54 00:00:00 0x222 Defender 2024-04-03 14:25:55 00:00:01 0x000 Not Used 2024-04-03 14:27:52...

Another day, another full virus scan. Build 07 after 12 minutes, 4:30 min of which where running the full scan. Comparing this to the last result seems to suggest that HWinfo is quite fine now with normal Realtime Protection running, full scans (especially the first scan of a day) will have more...

Comparing build 06 vs. 07 after 1 hour of various desktop load - aka not fully controlled - with all C- and P-states disabled ("Disable Idle"). All values below maximum are counters induced (2s polling). vs.

Ok, I think we can rule out that starting Counter Control was the reason for the back and forth. It's likely rather running a full scan that does that. So with that information gained, I will concentrate back more on the usual Realtime Protection combination. 2024-04-02 23:20:25 00:01:56...

I accidentally quit Counter Control, but as you can see in this log there is a time-span where Defender fought harder for control and thus caused multiple back and forth. This was during a full scan, though, so a bit of a different situation. Maybe starting Counter Control did cause, this...

What I don't like about it is that the counters keep switching every second for two minutes when it happens (sometimes multiple times per second, sometimes a few seconds don't switch). So the counters seem to get a bit "bombarded". Does this have a detrimental effect?

Maybe there is a conflict between HWinfo and Counter Control? Here HWinfo - running in the background - did not successfully reset the counters for 4 minutes until I brought the Counter Control app to the foreground (HWinfo still in background): 2024-04-02 20:40:29 00:00:02 0x000 Not Used...

Is the 2 minutes interval expected for your implementation? This fits the 2 minutes it takes for Defender to take over again after Hwinfo has been quit. 2024-04-02 19:42:26 00:00:00 0x222 Defender 2024-04-02 19:42:27 00:00:01 0x332 Warning 2024-04-02 19:42:28 00:00:01 0x000 Not Used...

This single occurrence of prolonged Defender time is rather puzzling, because from what I can see otherwise Defender tries to use the counters exactly every 2 minutes just once and then is promptly - within a second or maybe polling rate? - reset by Hwinfo to take a step back for another 2...

Unfortunately I celebrated too early: 2024-04-02 18:04:58 00:00:23 0x222 Defender 2024-04-02 18:04:59 00:00:01 0x332 Warning 2024-04-02 18:05:00 00:00:01 0x000 Not Used 2024-04-02 18:06:55 00:01:55 0x330 Normal >2024-04-02 18:14:29 00:07:34 0x222 Defender< 2024-04-02...

I will let HWinfo run for a few hours to watch how stable this is over prolonged runtime.

Yep, that worked. Took about 2 minutes for Defender to take over again after closing HWinfo. :)

Unfortunately you cannot just check for the Defender process to know whether Realtime Protection is enabled or not, because the process always stays loaded. Maybe a warning popup would be useful. I knew about this problem already, but then completely forgot about it and practically started at...

Danke für die Mühe! It was worth a try. Unfortunately still switching back and forth between both counter settings. So it seems like Kevin Glynn has another trick up his sleeve to make this stick for Counter Control and Throttlestop. Still good enough for me personally, but obviously this makes...

And even though the behavior of the last build looks rather odd, at least it makes it obvious to users that something is getting in the way of the measurement. Before that it wasn't really visible unless you specifically enforced "Disable Idle" (which many people don't even know about).

Hwinfo runs the counters in 0x330 as long as Defender doesn't fight back. Once Defender pushes its own 0x222 the result is that the counters keep switching between 0x222 and 0x332. Once Counter Control's "Reset Counters" button is used the counters revert back to the same 0x330 HWinfo originally...

The "Reset Counters" button does not spawn an extra thread when it's pushed, though, the whole Counter Control process runs on a single thread with a short load increase from 20-25 mio. cycles delta to 37-40something cycles delta (so basically nothing). The difference is that afterwards it says...

Could you try to reset to 0x330 instead of 0x332, aka did you leave out counter 0 in your reset? I also noticed that resetting via Counter Control takes 3 seconds before the button becomes usable again, so it either is rather busy or it just doesn't want the user to spam the button to fast!?