Windows 10 task manager weird behaviour

[Gumikacsa]

BEFORE I START:

• I have posted on multiple tech sites already, got no useful answers, let alone getting "HAHAUSELINUX"-ed.

Basically, I've recently bought an Intel Core i7 2700k (Sandy Bridge-DT) system (Gigabyte GA-H61M-S2PV rev 2.2 motherboard, and a Gigabyte GTX 980 Windforce graphics card). It had no installed drives, so I added my own 1TB Toshiba drive to it, did a fresh install of Windows 10 Pro, 64-bit. So far so good, added my MS account, installed my generic software, customized it to my liking a bit with dark mode and stuff. While running Cinebench R20 from Microsoft Store, I decided to pull up task manager to look at the CPU frequency - little to my surprise, the CPU was reported to have a base frequency of 5,9GHz and currently running at 6 GHz, said by task manager. It's most likely some windows related problem, as CPU-Z and Intel XTU both get the proper readings, it's just task manager not getting something right.

 

If anyone has dealt with this kind of stuff before, please let me know if you ever got it fixed.

Task manager screenshot attached below.

 

Thanks for any attemps of help in advance.

[Mira Yurizaki]

CPU speed at the application level can be attained in various ways. CPU-z and Intel's XTU probably have a specific way of probing for CPU speed, whereas Task Manager likely relies on a Windows API call, which has to be generic to support as many processors as possible.

 

So I would argue in this case, something buggered up the way Windows determines CPU speed.

[Gumikacsa]

3 minutes ago, Mira Yurizaki said:

CPU speed at the application level can be attained in various ways. CPU-z and Intel's XTU probably have a specific way of probing for CPU speed, whereas Task Manager likely relies on a Windows API call, which has to be generic to support as many processors as possible.

 

So I would argue in this case, something buggered up the way Windows determines CPU speed.

So basically this issue is redundant, and has no known fix?

[Mira Yurizaki]

Just now, Deathstreams said:

So basically this issue is redundant, and has no known fix?

Well, no known fix in the sense that I don't know exactly what Windows uses to poll for CPU speed. However, even if I did know, I don't think there would be a way to fix it depending on what Windows is using to source data. If there's something wrong with the hardware for instance, then there's nothing Windows can do about it.

[Gumikacsa]

1 minute ago, Mira Yurizaki said:

Well, no known fix in the sense that I don't know exactly what Windows uses to poll for CPU speed. However, even if I did know, I don't think there would be a way to fix it depending on what Windows is using to source data. If there's something wrong with the hardware for instance, then there's nothing Windows can do about it.

Well in that case, thanks anyway for at least letting me know that it's not a mistery error rather it's known, and extra for not HAHAUSELINUX-ing.

[DildorTheDecent]

16 minutes ago, Deathstreams said:

 5,9GHz and currently running at 6 GHz,

I've experienced this error with a 2700K Haven't had it with a 3570K or my current 5820K.

 

Could be something to do with how the 2700K reported it's maximum multiplier. You'll see in CPU-Z that it reports a multiplier up to 59 in the CPU clock speed box whenever you're running stock settings. Unless it's been patched in more recent versions of CPU-Z.

 

Definately was quite the sight to see though.

[Turtle Rig]

10 minutes ago, Mira Yurizaki said:

Well, no known fix in the sense that I don't know exactly what Windows uses to poll for CPU speed. However, even if I did know, I don't think there would be a way to fix it depending on what Windows is using to source data. If there's something wrong with the hardware for instance, then there's nothing Windows can do about it.

Uncle billy doesn't care about his taskman.  It shows incorrectly for lots of people.  Mines has been incorrect since 2015 when blows10 came out........

[Mira Yurizaki]

3 minutes ago, Turtle Rig said:

Uncle billy doesn't care about his taskman.  It shows incorrectly for lots of people.  Mines been in correct since 2015 when blows10 came out........

How many is "lots of people?" Windows has a userbase of like 1 billion users. Even 1 million people is less than a percent.

 

Besides that, it's important to consider something here. What's the name of the application called? Task Manager. I would argue that given its name and the way information is presented, a hardware monitoring/profiling too is a secondary feature it just happens to have simply because it's already pinging a lot of stuff about the hardware already. i.e., it's useful for getting a rough estimate of system health and status, but it shouldn't be used as a deep profiling tool.

 

I mean the biggest tell-tell sign of this is the fact that normal users can run Task Manager without elevating permissions. The only thing that changes when you do run Task Manager with elevated privileges is you can kill other people's tasks. Most other hardware profiling/monitoring tools require elevated privileges to get the complete picture.

[Enderman]

This is why you don't use windows task manager for looking at your CPU frequency.

If you want the real frequency use a proper tool like hwinfo or CPUZ.

[Turtle Rig]

11 minutes ago, Mira Yurizaki said:

How many is "lots of people?" Windows has a userbase of like 1 billion users. Even 1 million people is less than a percent.

 

Besides that, it's important to consider something here. What's the name of the application called? Task Manager. I would argue that given its name and the way information is presented, a hardware monitoring/profiling too is a secondary feature it just happens to have simply because it's already pinging a lot of stuff about the hardware already. i.e., it's useful for getting a rough estimate of system health and status, but it shouldn't be used as a deep profiling tool.

 

I mean the biggest tell-tell sign of this is the fact that normal users can run Task Manager without elevating permissions. The only thing that changes when you do run Task Manager with elevated privileges is you can kill other people's tasks. Most other hardware profiling/monitoring tools require elevated privileges to get the complete picture.

Good one, honestly its like the 1803 bug that would delete files,, and bring back deleted files and they halted the April 1809 and it took them 3 shots to fix the bugs and mess they made and 1809 was solid then.  However there are weird issues still for lots of people when I say a lot Im talking millions of people experienced the horror that was the first 1809 release, second one was pulled.  It brought back deleted files for me lol,, Also people have lots of sleep issues.  I mean I cant say what amount of people experience the incorrect value in taskman because mine shows incorrect and my old mans 9900k rig says it wrong and so did his Sandy Bridge before that.

 

millions upon millions and more millions have their taskman show incorrectly.  

[Mira Yurizaki]

8 minutes ago, Turtle Rig said:

Good one, honestly its like the 1803 bug that would delete files,, and bring back deleted files and they halted the April 1809 and it took them 3 shots to fix the bugs and mess they made and 1809 was solid then.  However there are weird issues still for lots of people when I say a lot Im talking millions of people experienced the horror that was the first 1809 release, second one was pulled.  It brought back deleted files for me lol,, Also people have lots of sleep issues.  I mean I cant say what amount of people experience the incorrect value in taskman because mine shows incorrect and my old mans 9900k rig says it wrong and so did his Sandy Bridge before that.

 

millions upon millions and more millions have their taskman show incorrectly.  

You know, if there are show stopping bugs like that, fixing what Task Manager reads to provide a higher chance of accurate statistics should be on the bottom of the bucket list.

[IdiotDuck]

Have had that issue in the past, too. MSI H81 board and a G3258 would show as running at 7GHz or so