CPU scores inconsistent during a video call? Checks

Your CPU test score changes while you are on a video call, or drops between runs on the same PC. The call may be using some of the processor for video, effects, and other tasks, but a changing score does not automatically mean the CPU is faulty.

Compare results under similar conditions with the Processor Test. It measures single-core and all-core speed and gives each a score out of 100. These checks can help you separate ordinary workload changes from heat, power settings, or a persistent performance problem.

Compare CPU scores before and during a call

1. Open the Processor Test before starting a call. Close unnecessary apps and browser tabs, and let the PC sit idle for a moment.
2. Run the single-core and all-core tests. Note both scores and whether the PC is plugged in. Keep the test browser in the foreground while it runs.
3. Join a nonessential call, or use a test call. Once the video and audio are active, run the tests again. A CPU test adds work and can briefly affect call quality, so do not do this during an important meeting.
4. Repeat the comparison once after the call ends. Keep the same power source, browser, and other open apps so the scores are easier to compare.

Do not compare a result from a quiet, cool PC on wall power with one from a warm PC running on battery and several apps. That changes too many things at once. You can also compare a run with the call's background blur or other video effects off, then on.

What the results mean

The scores drop during the call, then recover afterward

The call is likely sharing processor time with the test. Video decoding, encoding, background blur, noise processing, and browser activity can all add work. A lower score during the call is not by itself evidence of a damaged CPU. If the call remains smooth and the score returns to its earlier range afterward, this is usually a workload effect.

The all-core score changes more than the single-core score

An all-core test keeps more of the processor busy at once, so other tasks have less room to run and heat or power limits can matter more. If the change only appears while the call is active, check what else is running before assuming there is a hardware fault.

Both scores stay low after the call ends

Look for background apps that stayed busy, a power-saving mode, or heat that has not yet cleared. Let the computer cool and become idle, then retest under the same conditions as your first run. A browser score is a comparison, not a direct reading of CPU temperature or a full hardware diagnosis.

The scores vary even when the PC is idle

Small changes between runs can happen because background work starts and stops, or because the browser and operating system schedule tasks differently. Large or persistent drops deserve a closer look. For more on background activity and benchmark variation, see How background tasks affect CPU benchmark results.

How to reduce score changes

1. Close extra workloads. Quit downloads, file conversions, games, and unused browser tabs before testing. On Windows 11, press Ctrl + Shift + Esc to open Task Manager and check which processes are using the CPU. On macOS, open Activity Monitor and select its CPU view.
2. Keep power conditions consistent. If it is safe and practical, connect a laptop to its charger for each comparison. On Windows 11, check Settings › System › Power & battery › Power mode. On a Mac laptop, check System Settings › Battery and whether Low Power Mode is enabled.
3. Turn off call effects for a comparison. Background blur and virtual backgrounds may add processing work. Disable them in the call app, then compare again. The exact setting name and location depend on the app.
4. Check for heat-related slowdown. Put the PC on a hard, flat surface and make sure vents are not blocked. If the fans are loud or the case feels unusually hot, stop repeated all-core tests and give the computer time to cool. A browser test cannot show the exact CPU temperature.
5. Restart and retest. If scores remain low after you close busy apps and let the PC cool, restart it. Then test once with only the browser open. Avoid running repeated stress tests back to back, especially if the machine is already hot.
6. Update or check the call software. If the slowdown happens only in one call app, update it and test with its video effects off. If the whole computer remains unusually slow across apps, check for an operating system update or ask the computer manufacturer for support.

Why the call and the score can affect each other

A CPU score is produced while the browser runs a workload. A video call is another workload, and the system has to share its available processor time between them. Depending on the PC and browser, some video work may use the graphics processor instead, so the CPU impact can differ from one setup to another.

The score also does not measure the quality of your internet connection. A call can freeze because of network problems even when the CPU score is steady. If the call is choppy but the computer stays responsive, check the connection separately rather than treating the CPU result as the cause.