Symptoms

Investigate high CPU use on Windows or Mac

Identify which task is using the CPU, separate ordinary workloads from unexplained activity, and choose safe next checks on Windows or Mac.

High CPU use means processing capacity is being used. It does not say whether the work is wanted, malfunctioning, or malicious. Video processing, a game, updates and a security scan can all produce substantial activity. The useful question is which task is responsible, whether it fits what the device is doing, and whether the activity continues without that explanation.

This guide covers Windows and Mac. It does not set a universal “infected above this percentage” rule or ask you to stress the device. If the broader problem is slow storage, memory pressure or startup delay, start with slow-computer diagnosis. Active file damage or unexplained remote control needs urgent triage before performance experiments.

Observe timing and workload before ending a task

Write down the application, activity and time. Is the CPU busy during a known export, immediately after opening a browser, or while no intentional task is underway? Note whether activity falls after a legitimate task finishes or you normally close a known app. A brief burst and recurring sustained activity have different diagnostic value.

A hot case, fan noise or short battery life is context, not a malware finding. Avoid deliberately heating the computer to reproduce the issue. Keep ventilation unobstructed and seek suitable support if thermal problems persist. Do not change firmware, cooling controls or system files based on an unidentified process name.

ObservationEvidence that helpsNext action
A known app is exporting, rendering or processingIts task progress and the CPU view at the same timeLet legitimate work finish or reduce a known workload
An update or security app is busyActual progress, product identity and recorded statusCheck its supported guidance; do not disable protection
The browser accounts for much of the activityTab, extension or browser-task identityInspect known tabs and the browser’s task view
A system task remains busyExact name, timing, platform and associated conditionsUse platform documentation or trusted support
An unfamiliar task recurs without an explanationApp origin, file location, recent changes and security findingsInvestigate identity before removal

No row diagnoses a threat from the percentage alone. When sharing observations for help, remove private paths, document names and account details from screenshots.

Inspect the operating system’s CPU view

On Windows, open Task Manager using Ctrl + Shift + Esc. In Processes, inspect the CPU column and the apps associated with the activity. Use Performance for the broader CPU picture, as described in Microsoft’s performance guidance. Record the reading while the issue occurs and compare it after the known task ends.

On Mac, open Activity Monitor and select CPU. Apple’s CPU guide explains the System, User and Idle summary and activity over time. Identify the app or task associated with the busy period rather than inferring infection from a single summary value.

Compare observations from the same view under similar conditions. Different displays need not represent the same quantity in the same way. Also check whether memory or storage pressure better explains the slow response; reducing CPU use will not automatically repair a different bottleneck.

Do not select “end task” for every unfamiliar entry. An operating system, security product or update can depend on it, and ending a task may discard unsaved work. A task disappearing after forced termination is not proof that its cause has been removed.

Map browser activity to a known tab or extension

A browser can have multiple tasks. A browser name appearing repeatedly does not establish multiple infections. Start with the tabs and work you intentionally opened, including video, calls, large web apps and background downloads.

For Chrome, More → More tools → Task Manager opens its task view. Google’s performance instructions describe inspecting browser tasks and warn that ending a process can lose unsaved work. Use the view to relate activity to a known tab or extension; close a known unnecessary tab normally before using a forced termination.

If activity drops when an ordinary tab closes, that supports investigating its workload. It does not prove that all content on the site is trustworthy. Avoid returning to a suspicious page to test a theory. Browser-based mining is one possible misuse of processing, but sustained CPU activity alone does not establish a cryptominer.

For a legitimate extension with a suspected functional problem, a bounded disable-and-compare check may help. For an unwanted or credibly harmful extension, remove it through supported controls and keep it removed. Do not re-enable suspicious software while logged in to sensitive accounts merely to improve your evidence.

Treat Mac kernel_task as a documented special case

If kernel_task appears prominent on a Mac, read Apple’s explanation before drawing a conclusion. Apple describes a role in managing CPU temperature by reducing availability to other processes. It can respond to thermal conditions even when the Mac does not feel hot to you.

The process name alone is not a reason to remove it or try to stop its system role. Document the conditions and follow Apple or qualified hardware support if the behavior persists. A thermal-management explanation does not settle every performance problem, but it prevents mistaking this specific system behavior for a confirmed infection.

For another unexplained system task, use documentation for that exact platform and component. Do not transfer the kernel_task explanation to every busy process or use a random forum’s deletion command as a general CPU fix.

Investigate an unfamiliar application without executing it

If a supported finding or further evidence points toward unauthorized mining, use the cryptominer investigation. It separates browser activity, installed software, GPU use and remote cloud resources. A busy CPU alone does not justify that diagnosis.

Record the exact task and its apparent application origin. A familiar filename may be copied, while a legitimate program may use an unfamiliar component name. File location, publisher identity, installation history and security findings can help establish context. None is a standalone safety certificate.

On supported Windows systems, Process Explorer offers deeper process inspection for users who need it. Microsoft’s current requirements list Windows 11 and higher for the client version. It is an investigation tool rather than a malware remover, and its Windows instructions should not be applied to Mac. Do not delete an executable based only on a busy row, or upload private files to a public service to obtain a quick verdict.

For a known app that remains busy unexpectedly, save work, close it normally if practical, check updates through its official channel, and consult its publisher. Avoid installing an optimizer offered by an alarming page. If an unexpected installer ran, protection is disabled without explanation, or a security finding is unresolved, use Windows security checks or Mac cleanup guidance.

Verify the change and retain unresolved evidence

After a justified change, compare ordinary use under similar conditions. Check whether the responsible app’s activity changed, whether the original symptom returned, and whether wanted functionality still works. Avoid interrupting an operating-system update or a security action to create a faster-looking result.

If activity returns after every restart or you cannot identify its controller, preserve the observations and get trusted help. A clean scan has limits; recurring unexplained activity remains worth investigating. If account access may have been exposed, use account recovery from a trusted device as a separate task.

The outcome can be “known workload identified,” “app problem requiring support,” or “unexplained activity requiring further investigation.” Do not label every improvement a malware removal. This article is researched guidance; no CPU benchmark, malicious sample test or reader-device diagnosis was performed.

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy