Your AI PC has both an NPU and a discrete GPU, and they are supposed to cooperate — the NPU handling efficient AI work, the GPU handling heavy graphics and larger models. Instead, one of them shows a warning in Device Manager, Copilot+ features fail when the GPU is busy, or games and AI apps crash each other. Sometimes the NPU disappears entirely until the GPU driver is removed.

This is a coordination failure, not a sign that one chip is bad. Windows, the BIOS, and three drivers — chipset, NPU, and GPU — must agree on resources, power states, and which processor handles which workload. When they disagree, the symptom looks like a broken NPU or a broken GPU.

This guide gives you six fixes in order: identify which device is actually failing, fix the driver set as a matched group, then correct graphics and power settings so both processors work together.

Why this happens

  • Mismatched driver set: A new GPU driver paired with an old NPU or chipset driver can break the shared platform services both devices rely on.
  • GPU driver installed over the maker’s package: A direct download from the GPU vendor can overwrite maker-specific integration that coordinates the NPU and GPU.
  • Wrong graphics preference for AI apps: Windows may route an AI app to the discrete GPU, or a graphics app to the NPU path, causing failures neither device causes alone.
  • BIOS hybrid graphics setting: A BIOS mode that forces discrete-only or integrated-only graphics can hide or starve the NPU, especially on laptops with switchable graphics.
  • Power management conflict: Aggressive power saving can power down the NPU while the GPU is active, or keep the GPU awake in a state that blocks NPU initialisation.
  • Resource contention after resume: After sleep or hibernation, the GPU may reclaim shared resources before the NPU reinitialises, leaving the NPU flagged or missing. Newer Windows builds can add their own driver complications, as with NPU issues on Windows 11 25H2 .

How to fix it

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

Fix 1: Identify which device is actually failing

Treating the wrong device wastes every later step. A few minutes of diagnosis shows whether the NPU, the GPU, or their interaction is at fault.

  1. Open Device Manager and note warnings on the NPU, the display adapters, and any system devices.
  2. Open the properties of each flagged device and record its exact status code.
  3. Test the GPU alone with a graphics-heavy app, then test the NPU alone with a Copilot+ feature such as live captions.
  4. If only one device fails in isolation, focus on its driver; if both fail together, suspect the chipset driver or BIOS.
  5. Note whether the fault appears only after sleep, only under load, or at every boot — timing points at power, load, or driver causes respectively.

Fix 2: Install the matched driver set in the right order

Drivers for these devices are a set, not three independent downloads. Installing them in chipset, NPU, then GPU order restores the coordination the maker validated.

  1. Download the latest chipset, NPU, and GPU drivers for your exact model from Dell , HP , or Lenovo support.
  2. Uninstall the GPU driver and the NPU driver in Device Manager, with driver removal checked for both.
  3. Restart, install the chipset driver first, then the NPU driver, restarting when asked.
  4. Install the GPU driver last, as administrator, and restart again.
  5. Check Device Manager for clean entries on all three devices before testing any app.

Fix 3: Use the laptop maker’s GPU driver, not a generic vendor build

A direct GPU vendor driver is often newer, but it can lack the maker integration that manages switching between the NPU, integrated graphics, and discrete GPU on your specific laptop.

  1. If you installed a GPU driver directly from the vendor, note its version, then uninstall it with driver removal checked.
  2. Install the GPU driver from your laptop maker’s support page instead, even if its version number is older.
  3. Restart and check Device Manager for both the GPU and the NPU.
  4. Test an AI feature and a graphics-heavy app back to back to confirm both work.
  5. Only return to a vendor driver if your maker explicitly supports it for your model and the maker’s driver reproduces the conflict. For vendor-specific checks, NVIDIA’s driver download page can confirm the correct GPU family for comparison.

Fix 4: Correct Windows graphics preferences for AI and graphics apps

Windows lets you assign each app a preferred GPU. A wrong assignment can send AI work to the discrete GPU or graphics work down an NPU path, producing crashes that look like hardware faults.

  1. Open Settings > System > Display > Graphics and review the apps listed there.
  2. For Copilot+ and AI apps, set the preference to Let Windows decide or the system default, rather than forcing High performance.
  3. For games and graphics apps, set High performance so they use the discrete GPU explicitly.
  4. Remove any app entry you do not recognise, then re-add the app fresh if needed.
  5. Restart the affected apps and test both an AI feature and a game to confirm the conflict is gone.

Fix 5: Check BIOS graphics mode and power settings

The BIOS decides how the NPU and GPU share the platform. A forced graphics mode or an outdated BIOS can make a software fix impossible until the firmware setting is corrected.

  1. Restart into BIOS setup and find the graphics, hybrid graphics, or switchable graphics setting.
  2. Set it to Hybrid, Switchable, or MSHybrid mode rather than discrete-only, unless your maker advises otherwise.
  3. Confirm the NPU or AI engine is enabled in the BIOS if a separate setting exists.
  4. Save, boot into Windows, and check Device Manager for both devices.
  5. In Settings > System > Power & battery, use Balanced for testing, since Best power efficiency can park the NPU while the GPU runs. A similar power and app interaction appears in 7-Zip on ARM64 Windows , where defaults, not hardware, cause the visible fault.

Fix 6: Test with the GPU disabled, then restore it cleanly

Temporarily disabling the GPU proves whether the conflict is real or coincidental. This is a diagnostic step, not a permanent workaround — the goal is to restore both devices working together.

  1. In Device Manager, disable the discrete GPU device only, leaving the NPU enabled.
  2. Restart and test Copilot+ features; if the NPU now works perfectly, the interaction is confirmed.
  3. Re-enable the GPU, restart, and reinstall the matched driver set from Fix 2.
  4. Test both devices again, this time under load, to confirm the fix holds when both are busy.
  5. If the NPU fails only when the GPU is enabled, even with matched drivers and hybrid BIOS mode, contact your maker’s support with your test notes — that pattern may need a firmware fix. Before concluding, rule out an unrelated AI-component fault such as a Photos erase-object failure .

Closing

An NPU and a discrete GPU are meant to share work, not fight over it. Diagnose which device actually fails, install your laptop maker’s chipset, NPU, and GPU drivers as a matched set in that order, and correct the BIOS graphics mode and Windows graphics preferences. That combination resolves most conflicts, and a fault that survives it — with clear test notes — is exactly what maker support needs to escalate.

Frequently asked questions

Why would an NPU conflict with a discrete GPU?
Both devices share platform resources, power management, and driver services. A mismatched GPU driver, a BIOS setting, or a Windows graphics preference can make Windows assign work or resources incorrectly, breaking one or both devices.
Should I disable the discrete GPU to fix the NPU?
No, not permanently. Disabling the GPU is a useful diagnostic test, but the real fix is correct drivers and graphics settings so both devices work together as designed.
Can graphics settings send AI work to the wrong processor?
Yes. Windows graphics preferences and app settings can route an app to the discrete GPU when it should use the NPU, or vice versa, causing failures, slowness, or crashes in AI features.
Will updating only the GPU driver fix the conflict?
Sometimes, but usually you need the matched set: chipset, NPU, and GPU drivers from your laptop maker, installed in the right order, plus a BIOS that supports both devices.