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.

[RRe22]

1. NPU driver version currently active → Neither — the NPU driver (npu_kmd.sys) has been fully removed from the DriverStore using pnputil. Both versions appeared across multiple crash dumps: 32.0.100.4512 in dumps 1 and 4, 32.0.100.4724 in dumps 2 and 3. The driver is no longer installed.

2. See file attached intel_report.txt.

3. I cannot attach dump files. You can follow this link : https://filebin.net/zyw82cochsrpyeae

4. Crash dump analysis key findings → All dumps show the same root cause logged by the NPU driver itself:

npu_kmd!__KmGetSupportedWDDMVersion: [ERROR] Unsupported WDDM version 69639npu_kmd!OSGetVersionInfo: OS Version 10.0 Build 26200 UBR 8328 / 8457npu_kmd!VpuBugcheckSecondaryDumpDataCallback: Driver build 32.0.100.4512 / 32.0.100.4724

The NPU driver receives an invalid WDDM version (69639) from the OS and triggers a TDR, killing csrss.exe.

5. Windows Insider build or regular Windows Update? → Regular Windows Update. The machine was never enrolled in the Windows Insider Program (confirmed in Settings → Windows Update → Windows Insider Program, which shows "Join" not "Leave"). Build 26200 was pushed automatically without any Insider enrollment.

6. Build 26200 was first installed on November 7, 2025 via regular Windows Update (Windows 11 version 25H2 feature update). On May 4, 2026, KB5083631 labeled "pre-release update" (26200.8328) was pushed automatically — this is the update that appears to have introduced the WDDM incompatibility with the NPU driver. The machine was never enrolled in the Windows Insider Program.

7. Where was the Intel NPU driver downloaded from? → The NPU driver was never manually installed. It was pushed automatically via Windows Update alongside build 26200. No manual download from Intel Download Center was performed.

8. Have you tried previous NPU driver versions? → No previous versions were tested. The decision was made to fully remove the driver rather than downgrade it, since the root cause appears to be an OS-level WDDM version incompatibility on build 26200, not a specific driver version issue.

9. Can you access Windows Safe Mode without BSOD? → Yes. Safe Mode works without any BSOD. The Avast uninstall utility was successfully run in Safe Mode with no issues.

10. Exact sequence of events →

• ~May 6, 2025: Dell BIOS updated from 1.18 to 1.19 (exact date to confirm in BIOS System Logs)
• Unknown date before May 12, 2026: Windows build 26200 pushed via regular Windows Update (not Insider)
• May 12, 2026: BSODs first noticed and crash dumps collected
• May 12-13, 2026: Multiple workarounds attempted (BIOS rollback, NPU driver removal, Avast removal, ProtonVPN removal) — BSODs continue on build 26200

[SesanN_Intel]

Hi RRe22,

Could you please send us another log from the crash dump since we're unable to access the link you previously provided? Additionally, please include Event Viewer logs in your next response to help us conduct a comprehensive analysis.

You can zip all the files together before attaching them to this thread if needed to manage file sizes or organize the information better.

If you need anything else, please let me know immediately. I will be waiting for your response.

Best regards,

Sesan N.

Intel Customer Support Technician

[RRe22]

Please find attached the archive file containing dumps.

RRe

[RRe22]

And the Windows Event Log attached.

RRe

[SesanN_Intel]

Hi RRe22,

Thank you for providing this information. We noticed that you haven't attempted installing the NPU drivers yet, which could be contributing to your current concern.

Please proceed with installing the NPU drivers from your OEM, Alienware[DELL], as these drivers are specifically optimized for your system configuration and will ensure proper functionality.

I want to ensure you have the most reliable solution for your system. The best and most compatible driver for your device is the OEM (Original Equipment Manufacturer) version, as it's specifically optimized for your hardware. You can download the driver for your OEM device here on this link: https://www.dell.com/support/product-details/en-us/product/alienware-m16-r2-laptop/drivers

Let me know how it goes, if you have any questions, please do not hesitate to reach out.

Best regards,

Sesan N.

Intel Customer Support Technician

[RRe22]

I have installed the latest Intel-AI-Boost-Driver_8PF4J_WIN64_32.0.100.4512_A06_02 from dell support, but it did not changed anything.

RRe

[Bailio_Intel]

Hello Steven,

Thank you for response, and we appreciate your time providing the needed details for this matter

I will now coordinate this with our team, and update you on or before May 22.

Have a great day and keep safe!

Best regards,

Jennifer B

[RRe22]

I rollbacked my Windows build version to 22631 as the computer was not usable by rebooting every 20 minutes. I still do not understand how Microsoft can a push test build into non insider computers.

The issue is resolved by downgrading the Windows build.

RRe

[Bailio_Intel]

Hello Steven,

Thank you for your response, and we received your confirmation for the downgrading the Windows build that resolved your issue.

I will make sure to inform our team regarding this feedback. Allow us to update you on or before May 26.

Again, we apologize for any inconvenience. Have a great day and always keep safe!

Best regards,

Jennifer B

[Bailio_Intel]

Hello RRe22,

I hope this email finds you well.

I'm writing to provide you with an update regarding the technical issue you recently experienced with your system.

We are pleased to know that the issue has been successfully resolved after downgrading the Windows build. The system is now functioning normally, and the problem has been eliminated.

Based on our investigation and the successful resolution following the Windows build downgrade, we have determined that this was an operating system-level issue.

Since this appears to be related to a Windows OS compatibility issue, we recommend contacting Microsoft Support directly for:

• Further guidance regarding the Windows build that caused the issue
• Assistance with safely upgrading to a stable Windows version in the future

As no further assistance is currently required from our team, we will proceed with closing this case.

Thank you, and please stay safe at all times.

Best regards,

Jennifer B