[SOLVED] Core pegged at 100%

[McSlash]

I've got an issue I haven't seen before . . . Task Manager is constantly pegged at 100%, and games have been crashing my display. On the other hand, the Core Temp app gives different numbers, and right now, while I'm typing, is showing 5%-7%. Task Manager is still pegged at 100%.
I have tried a couple of Windows 10 DeBloaters to no avail, and if I "end task" on a consumptive process, another process will jump up and become as consumptive!?

View: https://youtu.be/7UM707bYi5w

i5-8600K
MSI z370 Gaming Plus MB
GEForce GTX 1660 Ti
MSI MAG341CQ

Up for any ideas.

 

[McSlash]

Currently at idle;

 

[SamirD]

Boot a linux live cd and see what the 'top' command shows in terms of cpu usage. If it's 100% there then it's probably a hardware issue, and if it doesn't--windows issue.

You may have to reinstall windows as you may have a cryptovirus that mines on your system. I wish cryptocurrancy and that whole illegal underground world would just vanish...

 

[McSlash]

Boot a linux live cd and see what the 'top' command shows in terms of cpu usage. If it's 100% there then it's probably a hardware issue, and if it doesn't--windows issue.

You may have to reinstall windows as you may have a cryptovirus that mines on your system. I wish cryptocurrancy and that whole illegal underground world would just vanish...

That would be a drag . . . Uh, I know nothing of, and have no Linus CD, any other ideas?

 

[uWebb429]

@McSlash - The Task Manager Processes tab, CPU % data, is bugged. On CPUs that use a high percentage of turbo boost, this data will over estimate the CPU percentages. When this says 100%, switch to the Details tab and see how it compares. The Details tab is usually correct.

Try running ThrottleStop. Sometimes all of the C states get disabled. This might be what is screwing with the Task Manager. ThrottleStop should show 1% or less in the C0 state when your computer is idle. Post some screenshots of this program if you need help.

https://www.techpowerup.com/download/techpowerup-throttlestop/

 

[McSlash]

98% Idle!

 

[McSlash]

But Throttle Stop agrees with the Task Master . . .

 

[uWebb429]

@McSlash - ThrottleStop does not report CPU usage. It reports the percentage of time that your CPU is in the C0 state.

When the CPU is actively working on a task, it will be in the C0 state. When a task is finished, that core will usually go into the C1 state to save power. If you have C1E enabled, it will go into that state to save more power. If you have C3, C6 or C7 enabled, the cores will go into one of those states to save even more power.

When your computer is idle, it is not using any of these low power C states. A computer that does not go into at least C1 is highly unusual. There are some registry hacks and power plan tricks you can use to disable all of the C states. Some people like to do this to minimize latency. The tiny improvement is not worth the extra power consumption and heat created when you do this.

Do you remember doing any mods like this? Try switching to a different Windows power plan. You can use ThrottleStop to switch from the Windows High Performance power plan to the Balanced power plan. Watch ThrottleStop to see if the C0% suddenly decreases.

If that does not work, click on the C1 button in ThrottleStop to open up the C States window. Push the > > button to open up the entire window. In ThrottleStop 9.3.1 there is a new option to adjust the C states. Check the C States - AC option, select the On option and then press the Apply button. That might get your C states working properly.

If you have disabled all of the C states in the BIOS, this is not really working correctly. The CPU should always have access to C0 and C1.

Edit - Here is what I get with 10 cores running at 5000 MHz with the C states enabled.

 

[McSlash]

Okay, Process Explorer, like Systems Details is telling me Task Manager is wrong . . . However games are crashing as if they are believing Task Manager.

 

[McSlash]

Malwarebytes found these . . . let's see what happens.

 

[McSlash]

Nothing changed, going for reinstall.

 

[uWebb429]

@McSlash - You have a problem with your C states. Are you using the most recent BIOS version for your motherboard? It might not be enabling C1 like it is supposed to do.

Did you try changing to different Windows power plans? If they are all showing the same problem, it is likely the BIOS.

Next time you have a problem like this, before reinstalling Windows, open the Power Options and press the Restore plan defaults button.

Task Manager is wrong

It is not wrong. The Processes tab does not display CPU Usage. Everyone assumes that it does. The Task Manager shows you that there is a problem. ThrottleStop shows you that the problem is because of the C states. Your CPU does not have access to any C states beyond C0 so the CPU never gets a chance to go idle.

 

[McSlash]

So . . . reinstall did nothing except create a boatload of work . . .
Restoring Plan Defaults got me this;

I'll listen to anything, checking bios drivers . . .

 

[John Chesterfield]

I'll listen to anything

I'm not so sure, you didn't listen to the poster who suggested you make a Linux live CD/USB which you dismissed as being "a drag". It was a very good suggestion, especially given you've reinstalled Windows and nothing's changed..

 

[uWebb429]

I'll listen to anything

Are you running the latest BIOS? This has to be an issue with the motherboard not setting the CPU up correctly. This can happen with early BIOS versions. Problems like this are usually corrected with the latest BIOS.

Try going into the BIOS and enable some C states like C1E, C3 or C7.

 

[McSlash]

I'm not so sure, you didn't listen to the poster who suggested you make a Linux live CD/USB which you dismissed as being "a drag". It was a very good suggestion, especially given you've reinstalled Windows and nothing's changed..

My comment "That would be drag" was in reference to his suggestion that I may need to reinstall Windows, which of course I did listen too. I also mentioned, I had no idea what a Linux live CD usb was, and you failed to jump in then and give the old what's what.

 

[McSlash]

Are you running the latest BIOS? This has to be an issue with the motherboard not setting the CPU up correctly. This can happen with early BIOS versions. Problems like this are usually corrected with the latest BIOS.

Try going into the BIOS and enable some C states like C1E, C3 or C7.

That'll be the next thing I check . . . have to reinstall the MSI software.

 

[John Chesterfield]

My comment "That would be drag" was in reference to his suggestion that I may need to reinstall Windows, which of course I did listen too. I also mentioned, I had no idea what a Linux live CD usb was, and you failed to jump in then and give the old what's what.

I don't know what you're on about with the 'old what's what', are you saying I didn't want to help you? I only want to help those who also want to help themselves.

You also mentioned that you had no idea what a Linux live CD or USB was, which is entirely plausible but you've made no effort to try and find that out. People here aren't going to hold your hand through understanding that when there's a thing called Google, so Google that, make one and do what's been suggested. You'll find that less of a drag and had you done it earlier, you might not have had to reinstall Windows.

You were given a good suggestion to try and pinpoint whether or not you have a hardware or software issue, I'd be trying that. Google how to make the bootdisk and how to use it, it really isn't difficult.

 

[McSlash]

Golly, I'm gonna hafta fugure me out hows ta use the Googly Machine.

 

[McSlash]

To Recap;
Reinstalled Windows,
Updated BIOS,
Enabled C states,
Nothing significantly different in Task Manager.

 

[John Chesterfield]

To Recap;
Reinstalled Windows,
Updated BIOS,
Enabled C states,
Nothing significantly different in Task Manager.

But still not tried the Linux live bootdisk? The thing that would potentially tell you if it's a hardware or software issue?

You're going round in circles here, you really do need to try that Linux live environment that @SamirD suggested to see if the behaviour remains. If it does, then you know it's hardware. Just posting that nothing has changed in 24 hours having done nothing further isn't really getting you anywhere.

 

[McSlash]

Sorry I'm not knocking these tests out fast enough 🙄, but with reinstalling everything, updating BIOS, and enabling C states (the nothing further you referred to) and having a life away from my computer (naw, not really) I've been busy. One thing at a time so you don't lose your benchmark.
Speaking of benchmarks, at least User Benchmark no longer tells me I have excessive background processes running.

 

[John Chesterfield]

Why come here for advice if you're not prepared to try it?

Would take 15 minutes and wouldn't be the time wasting you've described above. Well you've wasted enough of my time, figure it out yourself.

 

[SamirD]

That would be a drag . . . Uh, I know nothing of, and have no Linus CD, any other ideas?

Download the TENS live cd, use rufus to write it to an empty usb drive and then boot with the usb drive and then run the 'top' command.

 

[uWebb429]

Reinstalled Windows

Did you try enabling all of the C states in the BIOS; C1E, C3, C6 and C7?

Not sure how running a Linux CD is going to solve anything. Whether Linux confirms that there is a problem or not makes no difference. When you are in Windows, there is obviously a problem. The BIOS is not enabling the C states correctly. The BIOS always needs to enable C1 so an idle CPU core does not have to constantly stay active in the C0 state.

Edit - I found the power plan setting that can cause this problem. Does this look familiar? The System Idle is showing that the CPU is idle 99% of the time but ThrottleStop shows the CPU spending 100% of its time in the C0 state.

Open up a command prompt window and enter this command.

If you are in the Windows Balanced power plan enter this,

powercfg -setacvalueindex SCHEME_BALANCED SUB_PROCESSOR IDLEDISABLE 0

For the Windows High Performance power plan enter this,

powercfg -setacvalueindex SCHEME_MIN SUB_PROCESSOR IDLEDISABLE 0

If you are still having problems, run this command,

powercfg -qh >C:\plan.txt

This will create a text file in your main C directory called plan.txt

-q stands for query
the h option tells the powercfg command to show all of the hidden commands. Copy and paste the info in plan. txt to www.pastebin.com and I will compare your plan to what I have.

After setting IDLEDISABLE to 0, this is what I get.

Enabling the C states dropped idle temps by 30°C and reduced power consumption by more than 100W.