Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Windows IT Technology

Windows 11 CPU Usage Reporting is Apparently Buggy, Including on Task Manager (neowin.net) 41

An anonymous reader shares a report: While not every user is actively monitoring hardware resource usage when gaming, enthusiasts and reviewers often turn the stats on to see how certain games and other applications are being handled by the hardware. During such a test run, CapFrameX, which developed a useful frametime analysis tool, noticed a weird anomaly when gauging the performance of the Ryzen 7 5800X3D on Lara Croft Shadow of the Tomb Raider (SotTR). The processor usage reported on Windows 11 is seemingly unusually low in one of the scenes in the game which is typically known to be quite intense on the CPU. Only one out the 16 threads seem to be reporting the correct usage whereas all the other threads are under 10% utilization. CapFrameX notes the issue though it isn't sure what could be causing it: " The core usage reporting on Window 11 is completely broken. Should be >80% for SotTR + this particular scene and settings. What happened? Did the recent update change the timer behavior?"
This discussion has been archived. No new comments can be posted.

Windows 11 CPU Usage Reporting is Apparently Buggy, Including on Task Manager

Comments Filter:
  • by wakeboarder ( 2695839 ) on Monday May 23, 2022 @04:52PM (#62559716)

    Is tell all your friends and relatives not to use it. Not using it usually lets microsoft know that they suck, they've been getting every other version of windows wrong since the beginning of time.

    • They'll just start posting huge warnings saying that your computer is at risk and force people to upgrade again. Just like Windows XP, 7, 8...
      • by jmccue ( 834797 )

        They'll just start posting huge warnings saying that your computer is at risk

        Shouldn't this be the case for all Wondows versions ? Maybe post warnings similar to what cigarette companies need to put on their packs.

  • This is the 'refresh' of win10. It's not a bad OS, compared to Win10. It preserves many of the same problems, but does not introduce many NEW problems. The worst windows versions are the ones that introduce a ton of new crap - this isn't apparently one of those
    • Is this not an example of a new problem?

      • Not on my end. Win10 misreported my 3900X's clockspeed chronically, reporting it @3.8 GHz when it was running at speeds between 4.0 GHz and 4.35 GHz. Or rarely higher.

        Win11 does the same thing.

        It's an old bug.

        • Windows is probably just displaying the base clock speed. 3.8 GHz is the base clock for the 3900X It can boost all the way up to 4.6 with the proper power delivery and cooling.
    • by jwhyche ( 6192 )

      This, exactly. Windows 11 is hardly more than Windows 10 with a slight face lift. A little work and you can make Win11 look almost like Win10. I tell most people that ask me if they should upgrade from Win10 to Win11, if they are happy with Win10 not to bother.

    • Didn't Windows 11 fuck the start menu even more (and it's *bad* in 10; whoever decided only 1 level of subfolders was allowed should be tried in The Hague for crimes against humanity)? And make it nigh impossible for all but the most sophisticated tech users to create purely local accounts? And repeatedly start uploading shit to OneDrive without permission? Also there's no de-crapified edition like LTSC yet, and it still seems far off. My bet is it will be even less de-crapified too, and Windows 10 has re-a
  • by malxau ( 533231 ) on Monday May 23, 2022 @05:13PM (#62559788) Homepage
    Important context for anyone trying to reason about those numbers: https://aaron-margosis.medium.... [medium.com]
    • Thanks, I'll check that out. I've long known that Windows analytics don't measure certain things right, and estimate other things that are too expensive to measure, but I haven't studied that for a while.

      But, as anecdotal evidence goes, I just got a new laptop with W11. A few strange glitches, but I'm getting used to it. F'rinstance, I started a program that I had just downloaded, it appeared then hung. Tried to kill the window, then looked in TM to kill it. Nope, not there.

      I guess the three-finger salute c

      • by jeffs72 ( 711141 )
        Ah yeah, AAron and I wrote about this a while back, it impacts more than 11. The core of the issue is that taskman isn't watching util as a measure of frequency / core. We talked to some folks at MSFT about it, procexp had the same issue at the time fwiw.
  • He was using a beta OS build. Not really news for betas to have bugs. If it was in stable (is it?) that would be more interesting.

    Also Task Manager is being completely rewritten so that's another wrinkle (does that one have the same problem?)

  • by t0qer ( 230538 ) on Monday May 23, 2022 @05:31PM (#62559832) Homepage Journal

    get-process - see all your processes
    get-process | sort cpu - sort by CPU
    stop-process -name - specify a name of a process to stop.

    You can even do fun partials

    get-process | where {$_.name -like"MS*"}

    or pipe them into stop process.

  • in older Windows??

  • I have noticed that Windows virtual machines tend to show much less processor activity than the host (KVM) shows for all flavors of Windows.

  • Windows is done & dusted as far as a personal computer O/S is concerned.

    It's a piis poor pile of dogshit.

  • It's been known for a while that Task Manager (the "new" Process Explorer) under-reports CPU utilization. If you use old versions of Process Explorer (by SysInternals, before Microsoft bought them out), you'll see lost of extra stuff and higher utilization numbers that aren't shown in the Microsoft version. This applies to disk utilization and which background tasks are visible, as well.

    Granted, I've only done these experiments under Windows 10, and haven't even touched Windows 11 yet. However, we all kn

  • Microsoft is just testing out if they can hide cryptomining from the user.

Beware the new TTY code!

Working...