You leave your laptop untouched for a few minutes, glance at Task Manager, and the NPU graph is jumping — 30, 50, sometimes 80 percent — while you are doing absolutely nothing. On a machine sold for efficient AI processing, that phantom activity feels wrong, and it often is: something is running inference behind your back.

Occasional flickers are part of how Windows 11 works now. The OS schedules small AI jobs — search enrichment, thumbnail analysis, background blur readiness — even when you are away. The problem is when those jobs never finish, repeat endlessly, or a buggy driver reports phantom load. If your NPU graph looks busy at idle, it is worth finding out whether that is normal housekeeping or a runaway process like the ones behind chronically high NPU usage at idle .

There is also a knock-on effect on battery. Constant NPU wake-ups prevent the deep sleep states that make Copilot+ laptops sip power, and over a full day that can translate into noticeably shorter runtime — a pattern familiar from high power usage draining the battery . The fixes below help you identify the culprit process, tame Windows background AI, and get the NPU back to a quiet idle.

Why this happens

  • Windows AI background indexing: Search indexer and media analysis services run NPU inference on new files and photos, and can get stuck reprocessing the same items in a loop.
  • A stuck app holding the NPU: Video call apps, browser tabs, or AI utilities sometimes fail to release their NPU session after you close the visible window.
  • Recall snapshots (Copilot+ PCs): If Recall is enabled, it periodically captures and analyzes screen snapshots with the NPU, even when the laptop looks idle.
  • Driver telemetry bugs: Some NPU driver versions misreport usage or fail to power-gate the chip, making idle look busy in Task Manager.
  • Cloud-synced photo libraries: OneDrive or Photos analyzing a large synced library can run NPU inference for hours after new media lands.
  • Scheduled AI tasks: Task Scheduler entries from OEM utilities or third-party AI apps can wake the NPU on timers you never set.

How to fix it

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

Fix 1: Identify the exact process using the NPU

Guessing wastes time. Pin down the culprit process first, then act on it specifically.

  1. Open Task Manager (Ctrl + Shift + Esc) and go to the Performance tab.
  2. Click the NPU graph on the left, then look at the bottom of that pane for per-process NPU usage.
  3. Alternatively, in the Processes tab, right-click a column header, choose the NPU column, and sort by it.
  4. Note the process name and its usage percentage — common offenders include SearchIndexer, Photos, video conferencing apps, and browser GPU processes.
  5. If no process shows meaningful usage yet the graph spikes, suspect a driver reporting bug and skip ahead to Fix 4.

Fix 2: End the stuck process and stop it from returning

A process that grabbed the NPU and never let go will keep spiking until it is killed and its trigger removed.

  1. In Task Manager’s Processes tab, right-click the offending process and choose End task.
  2. Watch the NPU graph for two minutes — it should settle near zero.
  3. If it was a browser tab doing background AI, close that tab and disable the site’s permission or extension responsible.
  4. If it was a conferencing or camera app, check its settings for “background effects always on” or “start with Windows” and turn those off.
  5. For repeat offenders, open Settings > Apps > Startup and disable the app’s startup entry so it cannot grab the NPU after every reboot. This is the same class of issue as AI background processes running amok in Windows 11 , where autostart utilities pile up silently.

Fix 3: Tame Windows background AI services

Windows’ own services are the most common source of legitimate-but-excessive idle NPU work.

  1. Open Settings > Privacy & security > Searching Windows and set “Find my files” to Classic instead of Enhanced to limit indexer scope.
  2. In Settings > Bluetooth & devices > Cameras or in the Photos app settings, turn off automatic media analysis and “people” grouping if you do not use them.
  3. If you use a Copilot+ PC with Recall enabled, open Settings > Privacy & security > Recall & snapshots and pause saving snapshots — test whether idle spikes stop.
  4. Check OneDrive settings and pause photo sync analysis while you observe; large libraries can keep the NPU busy for hours.
  5. Re-enable features one at a time afterward so you know exactly which one caused the spikes. When background AI refuses to release cleanly, users sometimes see Studio Effects report the NPU as unavailable the next time they need it.

Fix 4: Update the NPU driver

Buggy driver versions are a known source of phantom usage reporting and failed power-gating on all three NPU platforms.

  1. Check your current driver version in Device Manager under Neural processors > your NPU > Driver tab.
  2. Run the Intel Driver & Support Assistant on Intel machines, or grab the latest package from AMD’s driver page at amd.com or your laptop maker’s support site.
  3. Install the update and restart — driver-level power management only takes effect after a reboot.
  4. Leave the laptop idle for five minutes, then recheck the NPU graph in Task Manager.
  5. If spikes persist on the newest driver, try the previous driver version from your OEM; occasionally a brand-new driver introduces the regression.

Fix 5: Audit scheduled tasks and OEM utilities

Hidden scheduled tasks can wake the NPU on timers, producing the classic “spikes every few minutes while idle” pattern.

  1. Press Win + R, type taskschd.msc, and press Enter to open Task Scheduler.
  2. Browse Task Scheduler Library for entries from your laptop maker, AI utilities, or photo software with triggers like “at idle” or “every 10 minutes.”
  3. Right-click suspicious tasks, choose Disable, and observe the NPU graph for half an hour.
  4. Also check Settings > Apps > Installed apps for OEM “AI assistant” utilities you never use and uninstall them.
  5. Keep a note of what you disabled so you can re-enable anything you actually miss later.

Fix 6: Reset the AI platform components

If nothing above explains the spikes, the Windows AI stack itself may be in a bad state and need a refresh.

  1. Install all pending Windows updates from Settings > Windows Update — Microsoft regularly ships NPU scheduler and power fixes.
  2. Open an administrator terminal and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, to repair system components.
  3. Restart and leave the machine idle for ten minutes with no apps open, then check the NPU graph again.
  4. As a last resort before contacting support, use Settings > System > Recovery > “Fix problems using Windows Update” to reinstall Windows while keeping files and apps — it refreshes the AI components cleanly. For related rewrite oddities in Click to Do, see Click to Do’s bulleted list rewrite issues for how flaky AI state shows up in practice.

Closing

Idle NPU spikes almost always trace back to one thing: a stuck process, an overeager background service, or a buggy driver — and the Task Manager NPU view tells you which within minutes. Fix the culprit, trim the background AI you do not use, and your NPU should sit near zero when you are not working. If the spikes return after every Windows update, keep the NPU driver pinned to a known-good OEM version rather than chasing the newest release each time.

Frequently asked questions

Is it normal for the NPU to show activity when idle?
Small, brief blips are normal — Windows runs periodic AI housekeeping like search indexing enrichment. But sustained spikes above 20 to 30 percent on an untouched laptop point to a stuck process, a buggy driver, or an app that never releases the NPU. That is worth fixing.
Can idle NPU spikes drain my battery?
Yes. The NPU is efficient compared to the CPU, but constant background inference keeps the chip awake and prevents deep idle states. On a laptop this can quietly cost you an hour or more of standby and active battery life over a day.
Which process is using my NPU right now?
Open Task Manager, go to the Performance tab, click the NPU graph, and Windows 11 shows per-process NPU usage at the bottom of that view. You can also sort the Processes tab by the NPU column to find the culprit quickly.
Will disabling AI features hurt Copilot+ functionality?
Only the features you turn off are affected, and you can re-enable them anytime. Disabling background indexing AI, for example, stops phantom usage but leaves Studio Effects, Live Captions, and Click to Do working whenever you actually call them.