Windows 10: Windows Camera Frame Server excessive CPU

I just noticed that the light for my Webcam is showing the camera on after a reboot. It never did this before. In Task Manager the Windows Camera Frame Server is using 10-13% of the CPU after a reboot before I started any applications other than the autostart Apps including MS-Teams and To-Do. Any idea what could be causing the camera to be on and using such high CPU.

:)

 

Windows Camera Frame Server turns on on its own

I have a 2017 Surface Pro, recently my computer has been making a sound like the ticking of a watch. When I check my task manager

Windows Camera Frame Server is turned on, when I force quit this program the clicking stops. This happens when I haven't been using my camera or anything with video capture, so this program shouldn't be on. After I force quit the program, it often turns
itself back on, sometimes immediately. One of my computers cameras also turned itself on recently, noticed by the red light, and I had to restart my computer to get it to turn off. The Windows Camera Frame Server takes up a significant chunk of my memory.
This is a problem because I've been having trouble with programs crashing, even Google Chrome crashes saying I don't have enough memory. When this started happening I deleted unused files and programs, so I don't think I've actually run out of memory. What
can I do to stop Windows Camera Frame Server from turning itself on?

***Moved from: Windows 10 / Performance & system failures***

 

File Explorer Excessive CPU

Hi,

To address your concern, we suggest that you disable sdclt.exe in Task Scheduler. To do that, follow these steps:

• Type task scheduler in the search box.
• Click on Task Scheduler.
• Expand it to: Task Scheduler > Microsoft > Windows > WindowsBackup.
• Disable ConfigNotification.

Let us know how it goes.

 

SPOOLSV.EXE - Excessive CPU time Solution

Suggestions in several posts for excessive processor usage by SPOOLSV.EXE indicate the C:\Windows\System32\spool\PRINTERS folder should be emptied to solve the problem.

I have found another solution that solved my excessive SPOOOLSV.EXE processor usage issue.

Using Task Manager's Resource Manager, I found that SPOOLSV.EXE would continually try to connect to printers that are not attached to my
current local network. These printers are located on the local network in another office which I rarely visit. To solve the excessive CPU usage issue, I opened the print spooler queue window for each
off network printer, clicked on the
Printer menu item, then clicked Pause Printing. Immediately, SPOOLSV.EXE stopped using processor time. I will just have to remember to click on
Resume Printing should I need to use that printer if I am in the other office in the future.