Reply to thread

Message

<blockquote data-quote="Dex4Sure" data-source="post: 1012822" data-attributes="member: 79841">This is absolutely true and TechPowerUp&#039;s counter control utility does fix the issue for me as well on i9 10900K system. My Cinebench score improved by almost 1000 points after resetting counters.Before resetting counters on counter control:[ATTACH=full]270986[/ATTACH]After resetting counters on counter control:[ATTACH=full]270987[/ATTACH]So yes, the fix does work, absolutely. Anyone here saying otherwise has clearly not tried it themselves, or owns a CPU that&#039;s not affected (likely an AMD CPU). I also noticed when testing that before I reset the counters, Defender used 2% of my CPU during Cinebench run. After I reset the counters, Defender only used 0.1% of the CPU during the Cinebench run. So quite clearly it is Defender causing the issue and this fix does indeed fix the aforementioned problem. Quite pathetic that Microsoft and Intel haven&#039;t fixed this issue by now. This bug must&#039;ve been there for quite long time before it was even found. Light users probably have never noticed it, but under heavy stress its been noticeable for me on many Intel based systems. Its why I kept using ESET, but after this fix I&#039;ve been using Defender again and its now actually very light.You can download counter control from <a href="https://www.techpowerup.com/download/counter-control/" target="_blank">here</a></blockquote>

[QUOTE="Dex4Sure, post: 1012822, member: 79841"] This is absolutely true and TechPowerUp's counter control utility does fix the issue for me as well on i9 10900K system. My Cinebench score improved by almost 1000 points after resetting counters. Before resetting counters on counter control: [ATTACH type="full"]270986[/ATTACH] After resetting counters on counter control: [ATTACH type="full"]270987[/ATTACH] So yes, the fix does work, absolutely. Anyone here saying otherwise has clearly not tried it themselves, or owns a CPU that's not affected (likely an AMD CPU). I also noticed when testing that before I reset the counters, Defender used 2% of my CPU during Cinebench run. After I reset the counters, Defender only used 0.1% of the CPU during the Cinebench run. So quite clearly it is Defender causing the issue and this fix does indeed fix the aforementioned problem. Quite pathetic that Microsoft and Intel haven't fixed this issue by now. This bug must've been there for quite long time before it was even found. Light users probably have never noticed it, but under heavy stress its been noticeable for me on many Intel based systems. Its why I kept using ESET, but after this fix I've been using Defender again and its now actually very light. You can download counter control from [URL='https://www.techpowerup.com/download/counter-control/'][B]here[/B][/URL] [/QUOTE]

Verification