Zog1971
Active Member
So, I am just figuring out an issue that I've been experiencing today and I think this may be affecting others.
I happened to be sitting right next to my SP3 8gb Ram, 256, i7 and working at me desktop. The SP3 had no programs running at all and had just booted up from being shut off for a few hours so was nice and cool. It sat for about 10 minutes and all of the sudden I noticed the fan come on. I felt the unit and it was very warm. I opened up my task manager and CPU was at 1% and under 1ghz. After a few minutes the unit cooled and the fan turned off. Weird.
I decided to leave the task manager up full screen to monitor cpu usage and processes. After several minutes, I noticed the CPU usage jumping to 30-35% and and 2.8-3.1ghz. As soon as I would engage the device in anyway (the touchscreen, touchpad, keyboard) the processes would go back to 1%, the unit would cool and fan would go off within a few minutes. This is now happening every time the system sits idle for more that 5-10 minutes. I finally (and it was kinda difficult since it would stop once you move the cursor) found the process that is causing this is Antimalware Service Executable which is part of Windows Defender, the only anti-virus I have running on the system. Interesting to note, I have had the SP3 for over a week without this issue whatsoever, but did manually run a quick virus scan in the SP3 today for the first time. This was the first time Defender had run the scan. In doing more tests, I let it go ahead and run for over 45 minutes without touching the screen hoping that it was maybe just a process that needs to run once for Defender or something. I touched the screen at 45 mins to make it stop, but thinking this would just run until it exits idle status.
Anyway, I bet this affecting more people than just me and I bet it can contribute to some peoples heat/excessive fan running issues as well as battery issues. I had my unit plugged in, but bet the batter will drain quick with the fan constantly on turbo.
Any ideas besides turning off Windows Defender for making this stop? The unit just started doing it again.....
I happened to be sitting right next to my SP3 8gb Ram, 256, i7 and working at me desktop. The SP3 had no programs running at all and had just booted up from being shut off for a few hours so was nice and cool. It sat for about 10 minutes and all of the sudden I noticed the fan come on. I felt the unit and it was very warm. I opened up my task manager and CPU was at 1% and under 1ghz. After a few minutes the unit cooled and the fan turned off. Weird.
I decided to leave the task manager up full screen to monitor cpu usage and processes. After several minutes, I noticed the CPU usage jumping to 30-35% and and 2.8-3.1ghz. As soon as I would engage the device in anyway (the touchscreen, touchpad, keyboard) the processes would go back to 1%, the unit would cool and fan would go off within a few minutes. This is now happening every time the system sits idle for more that 5-10 minutes. I finally (and it was kinda difficult since it would stop once you move the cursor) found the process that is causing this is Antimalware Service Executable which is part of Windows Defender, the only anti-virus I have running on the system. Interesting to note, I have had the SP3 for over a week without this issue whatsoever, but did manually run a quick virus scan in the SP3 today for the first time. This was the first time Defender had run the scan. In doing more tests, I let it go ahead and run for over 45 minutes without touching the screen hoping that it was maybe just a process that needs to run once for Defender or something. I touched the screen at 45 mins to make it stop, but thinking this would just run until it exits idle status.
Anyway, I bet this affecting more people than just me and I bet it can contribute to some peoples heat/excessive fan running issues as well as battery issues. I had my unit plugged in, but bet the batter will drain quick with the fan constantly on turbo.
Any ideas besides turning off Windows Defender for making this stop? The unit just started doing it again.....