You turn on background blur or portrait light for a call, and your video starts strobing — frames freezing, the background pulsing, your face flashing in and out of the effect. Turn the effects off and the picture is perfectly smooth. That contrast is actually good news: it tells you the camera is fine and the problem lives in the Studio Effects pipeline.

Flickering is a timing problem. The NPU processes each frame through the effect model, and if frames arrive late, get dropped, or get processed twice, you see it as flicker. The usual suspects are an overloaded or throttled NPU, a flaky camera driver, two apps wrestling for the camera, or aggressive power saving that starves the neural processor mid-call.

This guide isolates the cause fast — one effect at a time, one layer at a time — then fixes it. If the flicker happens with effects off too, start instead with our Copilot+ PC camera guide , which covers camera-level faults this guide does not.

Why this happens

  • NPU overloaded by stacked effects: Running background blur plus portrait light plus a creative filter at once can exceed what the NPU sustains, and dropped frames show as flicker.
  • Camera driver dropping frames: An unstable camera driver delivers frames irregularly; the effect model then reprocesses or skips frames, producing visible strobing.
  • Two apps sharing the camera: When two apps open the camera simultaneously, the frame server splits the stream and the effect pipeline can process frames out of order.
  • Power throttling the NPU: Battery-saver and aggressive PCIe power management can downclock the NPU mid-call, so it suddenly cannot keep up with the frame rate.
  • Conflicting app-side filters: A calling app applying its own background or touch-up on top of the Windows effect doubles the processing and causes pulsing.
  • Bad driver after an update: A Windows or OEM update replacing a stable NPU or camera driver with a buggier one is the classic “it worked last week” cause.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Find the flickering effect by disabling them one by one

Do not turn everything off and declare victory — you want to know which effect flickers so you can keep using the rest. This two-minute test narrows the whole problem to one model.

  1. During a camera preview, open Quick Settings (Win + A) and the Studio Effects panel.
  2. Turn all effects off and confirm the video is smooth — this proves the effect stack is the cause.
  3. Enable effects one at a time, watching 10 seconds each: background blur first, then portrait light, eye contact, automatic framing.
  4. Note exactly which effect introduces flicker — background blur and creative filters are the usual culprits.
  5. Leave the flickering effect off and keep the rest; continue below only if you need that specific effect back.
  6. If every effect flickers individually, the problem is the pipeline itself — continue to Fix 2.

Fix 2: Stop power management from starving the NPU

On battery or power-saver plans, Windows can throttle the NPU mid-call — the effect starts smooth on a full-power machine and begins flickering minutes in as clocks drop. This is the top cause of flicker that appears partway through calls.

  1. Plug in the charger and set the power mode to Best performance (Settings > System > Power & battery).
  2. Open Control Panel > Power Options > Change advanced power settings, expand PCI Express > Link State Power Management, and set it to Off for both battery and plugged in.
  3. In Device Manager, open the NPU’s Properties > Power Management and uncheck “Allow the computer to turn off this device to save power” if present.
  4. Restart and retest the flickering effect on the charger.
  5. If the flicker is gone, you found it — consider a custom power plan for calls rather than leaving maximum performance on all day.

Fix 3: Update the camera driver

The effect pipeline can only be as smooth as the frames feeding it. A camera driver that delivers frames with irregular timing makes even a healthy NPU produce strobing output, and camera drivers are updated far less visibly than other drivers.

  1. In Device Manager > Cameras, right-click your camera and choose Update driver > Search automatically.
  2. Then check your laptop maker’s support page for a newer camera driver — OEM camera drivers often fix frame-timing bugs the generic one has.
  3. Install as administrator, restart, and retest the previously flickering effect.
  4. If the flicker started after a recent update, try Roll Back Driver on the camera device instead.
  5. Test in the built-in Camera app, not inside a call, so no app-side processing muddies the result. On Surface hardware with broader system quirks, our Surface Pro 11 Recall issues guide covers related platform-level fixes.

Fix 4: Repair or update the NPU driver

If the camera feed is smooth with effects off but flickers with any single effect on, the NPU side of the pipeline is struggling — a corrupt or mismatched NPU driver is the next suspect. See Microsoft’s Windows support page for official driver-troubleshooting context.

  1. In Device Manager > Neural processors, update the NPU driver automatically first.
  2. If nothing changes, uninstall the NPU device with “Attempt to remove the driver for this device” checked, then restart.
  3. Install the latest NPU/chipset driver from your laptop maker’s support page as administrator and restart again.
  4. Verify the NPU shows healthy with no warning icon, then retest the effect that flickered.
  5. Confirm with Task Manager’s NPU tab that utilization during the effect looks sane — pegged at 100% with flicker suggests the model itself is too heavy for sustained use on your chip.

Fix 5: Eliminate camera contention and double processing

Two programs touching the camera at once — or one app stacking its own filter over the Windows effect — is a classic flicker recipe. The frame server was not designed for two effect stacks at once.

  1. Close every app that might use the camera: Teams, Zoom, Discord, OBS, browser tabs with camera permission — check the system tray.
  2. In your calling app, disable its own background effects, blur, filters, and “touch up my appearance” features.
  3. Disable virtual camera software temporarily (OBS virtual camera, etc.).
  4. Retest with only the Camera app running and the Windows effect on.
  5. Reopen your calling app alone and retest — if flicker returns only there, the app’s own processing is the conflict, so leave its filters off permanently.
  6. On ARM laptops where app compatibility itself is flaky, check our guide to x64 emulation on Windows 11 ARM — an emulated calling app can starve the effect pipeline of frames.

Fix 6: Reduce the load — lighter effect settings

Sometimes the honest fix is that your NPU cannot sustain the heaviest effect at full camera resolution. Lowering the load slightly eliminates flicker with barely visible quality loss.

  1. In the calling app’s video settings, lower the camera resolution (720p instead of 1080p) — the effect model processes fewer pixels per frame.
  2. Improve room lighting — the effect models work harder and less predictably on noisy low-light frames, which amplifies flicker.
  3. Use one heavy effect at a time instead of stacking blur plus filters plus portrait light.
  4. Close heavy background apps during calls to free thermal and power headroom for the NPU.
  5. Retest the previously flickering effect for a full minute — flicker that only appears after warm-up points back to Fix 2’s throttling.

Closing

Studio Effects flicker is a pipeline timing problem, not a dying camera or NPU: find which effect flickers, make sure power management is not throttling the NPU mid-call, get the camera and NPU drivers healthy, and stop apps from double-processing the feed. Worked through in that order, flicker resolves at one of those layers — and you keep every effect that was never the problem.

Frequently asked questions

Why does my video flicker when Studio Effects are on?
Flickering usually means the effect pipeline is dropping or reprocessing frames — the NPU is overloaded, the camera driver is unstable, or two apps are fighting over the camera. Turning effects off and seeing the flicker stop proves the effect stack, not the camera, is at fault.
Which Studio Effect causes flickering most often?
Background blur and creative filters are the heaviest effects and the most common flicker sources, especially combined with low light. Eye contact and automatic framing are lighter. Disable effects one by one to identify the culprit.
Can a Windows update cause Studio Effects flickering?
Yes. Updates can replace a stable NPU or camera driver with a newer but buggier one, or change power policies that throttle the NPU mid-call. If flickering started right after Patch Tuesday, suspect the update first.
Does flickering mean my NPU is failing?
Almost never. NPU hardware failure is rare and usually shows as the effect vanishing entirely or a Device Manager error, not flicker. Flicker is a software timing problem — drivers, app conflicts, or power management — and it responds to software fixes.