Upon fresh boot, 4 CPU core is running at 100% for 65 min?

[MDRI]

Upon fresh boot, 4 CPU is running at 100% for 65 min?
Thanks for suggestions to my postings!

When I start up my computer, I notice that the HDD LED is constantly in the ON state, as oppose to the usual blinking. When the HDD LED stays on constantly, it pretty much indicates, to me, that the CPU running at 100%. At this point, Key board/mouse won't respond.

I opened Task Manager and no other programs were active at this time. I find all (4 core) CPU at 100%. I find task manager at high CPU use. Even if I close task manager CPU usage is not coming down.

I did adjust the affinity for task manager, but no improvement.

I ran sfc /scannow, chkdsk. Nothing reported .

What am I missing here?

Is there a way to get memory dump/memory snapshot to figure out, what is going on?

Is it possible for some programs to run without showing up in task manager?

Thanks for sharing.

 

[profdlp]

...Is it possible for some programs to run without showing up in task manager?...

Have you checked the box "Show processes from all users"?

 

[MDRI]

Yes, I did. Nothing showing as high CPU use.

 

[profdlp]

Try using msconfig to disable all the extra stuff loading at startup. Reboot and see if the high CPU usage continues. If not, add the things you disabled in msconfig back in one at a time until you find the culprit.

If you've disabled everything via msconfig and you are still getting the high CPU usage I would look through the Windows logs. I'd also do a couple of different malware scans.

 

[ThrashZone]

Hi,
I noticed a lot of activity after startup too or at least more than usual,
Of course windows updates checks for updates shortly after startup and I'm pretty sure it's the cause in my case
It isn't using 100% but does spike to 50% and that is higher than in the past
See if you have installed the newest update client which was included in KB3161608

If so the easiest test would be switch your update settings to Never check for updates and restart the machine.
Verify the services are not running if the issue remains.
Background intelligent transfer services
Cryptographic
Windows installer
Windows update

 

[MDRI]

Try using msconfig to disable all the extra stuff loading at startup. Reboot and see if the high CPU usage continues. If not, add the things you disabled in msconfig back in one at a time until you find the culprit.

How/where can I find the stuff loading at startup?

Are there any list available under windows folders, that list all startup loading programs?

Thanks for sharing.

 

[tommyg562000]

The best fix for this issue is upgrading to Windows 10.

 

[profdlp]

...How/where can I find the stuff loading at startup?

Are there any list available under windows folders, that list all startup loading programs?...

Go here: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Once there, scroll down to Method Three.

The best fix for this issue is upgrading to Windows 10.

Don't you think the poor guy has enough troubles?

 

[MDRI]

Thanks. I find Windows update service is already stopped. I reviewed startup programs change ==> Method Three

Step 10. Click on the Boot tab, then check the Make all boot settings permanent box and click on OK. (See screenshot below)

It says I cannot do undo after choosing this option.

How do I test, which one (startup program) causing the issue in my situation?

If the picked one did not resolve my cpu 100% issue, I need to bring it back and pick the next one etc.

Thanks for sharing.

 

[profdlp]

Just stop after Step 9.

The streamlined version:

Uncheck everything in the Startup tab. Apply and reboot. You will get a noticed that you disabled some stuff. Just say OK.

Check to see if your problem has gone away. If it hasn't, go back to msconfig and re-enable everything. (Because if it was one of your startup programs, the problem would not still be there.) At this point we'll have to try something else.

If the problem is gone with all startup stuff disabled, we need to find out which one(s) are the culprit. Go back into msconfig and re-enable ONE of them. Apply and reboot.

Repeat the process until the stinker reveals itself.