Windows 10: CPU at 100% Usage when using Full Scan in Windows Defender

I'm trying to scan for viruses but every time I choose Full Scan or Custom Scan my C: Drive my CPU shoots up to 100% usage and overheats prompting the scan to stop or my PC shuts down. I used Core Temp during a scan and all cores are getting up to 100 degrees Celsius. I've tried excluding Antimalware Service Executable folder from scan but same thing happens.

:)

 

Windows defender advanced scan extreme cpu overload


I routinely do Windows defender advanced scans. Up until about 2 weeks ago, that is.

All of a sudden the scan was completely maxing out my cpu. I wouldn't say it crashed the computer, but if I tried to do the simplest task while it was running, it rendered the machine unusable due to the draining of resources. Not to mention the scan would disappear, but was still running in the background. The only thing I could do at that point was to wait until it was done scanning, or shut down the unit

I found this thread that's about a year old, followed some of the suggestions, but nothing really helps.

I have no problem with the Quick scan.

High CPU usage when Windows Defender perform a Full Scan in Windows 10 - Microsoft Community

Windows Defender is my only virus protection, so there is nothing to create a conflict.

I put my defender installer folders in the excluded list. I changed my power settings from High Performance to Balanced.

I ran chkdsk /scan, sfc /scannow, dism /online /cleanup-image /restorehealth, and a Memory diagnostic. All normal.

Finally, I did a fresh install.

Is anybody else experiencing this?

 

CPU usage 100%





As you can see my CPU usage is always 100%, Due to this CPU fan never stops, even when temperature are normal.

When I turn on pc, it always starts with 100% cpu usage. I also ran malware and antivirus scans, couldn't help (Quick Heal antivirus).

Using Windows 10 updated to latest version.

 

cpu usage at 100%

CPU usage at 100% from start up for no apparently good reason. Service Host appears to be the problem but I cant narrow it down more than that at present.

Any suggestions?

I am using Windows 10 full release version 64 bit.