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

[RRe22]

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?

[Bailio_Intel]

Hello rr,

Greetings from Intel Customer Support!

Thank you for contacting Intel Customer Support regarding the BSOD issue you're experiencing with your Alienware m16 R2 system after the BIOS update. We understand how frustrating this situation must be, and we're committed to helping you resolve this Intel NPU driver compatibility issue.

To provide you with the most accurate assistance and escalate this matter appropriately, we need to gather some additional technical details:

System Information:

1. Please confirm the exact Intel NPU driver version currently installed (you mentioned both 32.0.100.4512 and 32.0.100.4724 - which is currently active?)
2. Please provide a scan of Intel® System Support Utility for Windows* software. After scanning, please save and send the results in your response.

Crash Dump Analysis:

3. Can you share the crash dump files (.dmp) you analyzed? These would typically be located in C:\Windows\Minidump

4. If possible, please provide the complete crash dump analysis report or screenshots of the key findings

Windows Build Information:

5. Can you confirm if this is a Windows Insider build or if it was pushed through regular Windows Update?

6. When did you first notice the Windows build 26200 installation on your system?

Driver Installation History:

7. Where did you download the Intel NPU driver from? (Intel Download Center, Windows Update, OEM, etc.)

8. Have you tried installing any previous versions of the Intel NPU driver?

9. Can you access Windows Safe Mode without experiencing the BSOD?

Timeline Clarification:

10. Can you provide the exact sequence of events? (BIOS update date → Windows update date → when BSODs started)

Please reply with this information at your earliest convenience. This will help us determine the best path forward and potentially escalate this to our specialized NPU driver development team if needed.

We appreciate your detailed technical analysis and patience as we work together to resolve this issue.

Best regards

Jennifer B.