Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
Announcements
For support on Altera products please visit the Altera Community Forums.
23485 Discussions

BSOD 0x000000EF CRITICAL_PROCESS_DIED after BIOS update — Alienware m16 R2 / Intel Core Ultra 9 185H

RRe22
New User
7 Views

System: Alienware m16 R2 · Intel Core Ultra 9 185H · 64 GB RAM · NVIDIA RTX 4060 Laptop · NVMe Samsung 2048 GB
OS: Windows 11 25H2 — Build 26200.8328 → 26200.8457 (after KB5089549)
BIOS: Dell 1.18 → 1.19 (trigger) · attempted rollback to 1.18 (reverted to 1.19 automatically)
Driver: npu_kmd.sys 32.0.100.4512 → 32.0.100.4724

Issue

After updating the BIOS from version 1.18 to 1.19, the machine started BSODing randomly with stop code 0x000000EF CRITICAL_PROCESS_DIED. The crash occurs within minutes of booting, with no specific user action triggering it.

Root cause identified from crash dumps

Six crash dumps were analyzed. All point to the same root cause:

npu_kmd!__KmGetSupportedWDDMVersion: [ERROR] Unsupported WDDM version 69639. Falling back to report WDDM 3.2 capability
npu_kmd!OSGetVersionInfo: [INFO] OS Version 10.0 Build 26200 UBR 8328 / 8457
npu_kmd!VpuBugcheckSecondaryDumpDataCallback: [ERROR] Driver build: 32.0.100.4512 / 32.0.100.4724

Analysis

The Intel NPU driver npu_kmd.sys queries the WDDM version from the OS at initialization. On build 26200 (which appears to have been pushed to this non-Insider machine via Windows Update), the driver receives an invalid WDDM version number (69639) that it does not recognize, causing a TDR (Timeout Detection and Recovery) failure which kills csrss.exe, a critical Windows process, resulting in the BSOD. The issue was masked on BIOS 1.18 as the NPU was less aggressively activated at boot. BIOS 1.19 changed NPU initialization behavior, exposing the incompatibility.

Workarounds attempted (all unsuccessful on build 26200)

  • BIOS rollback to 1.18 — reverted automatically by Dell SupportAssist
  • Disabling Intel AI Boost in Device Manager
  • Full removal of npu_kmd.sys + npu_extension.inf from DriverStore (pnputil)
  • Blocking NPU hardware ID via registry (PCI\VEN_8086&DEV_643E)
  • Installing KB5089549 (26200.8457) — no fix
  • Uninstalling Avast antivirus (kernel drivers confirmed removed)
  • Uninstalling ProtonVPN + removing wintun.inf / ovpn-dco.inf

Question

Is build 26200 officially supported with Intel NPU drivers for Meteor Lake (Core Ultra 9 185H)? Is there a known fix or timeline for a corrected NPU driver that supports the WDDM version reported by build 26200? Is there a way to permanently prevent Windows Update from pushing build 26200 on a non-Insider machine and return to the stable 26100 branch without a clean reinstall?

0 Kudos
0 Replies
Reply