STATUS_PNP_IRQ_TRANSLATION_FAILED (0XC0040037) Fix Guide

The 30-Second Fix: Simple Reboot

I know it sounds dumb, but a full shutdown and restart clears temporary IRQ resource assignments. This error often happens after a driver update or hardware change where Windows didn't re-evaluate the IRQ table properly. Do a full shutdown — not a restart — by holding Shift and clicking Shut Down in the Start menu. That bypasses Fast Startup. Boot back up. If the error's gone, congrats. If not, keep reading.

The 5-Minute Fix: Remove the Culprit Device

If the error persists, the culprit is almost always a specific device with a bad IRQ mapping. Open Device Manager (devmgmt.msc). Look for devices with a yellow exclamation mark or that show an error in their status. Right-click them and select Uninstall device. Check the box that says "Delete the driver software for this device" if it shows up. Then reboot. Windows will reinstall the drivers and re-assign IRQs fresh. Nine times out of ten, this fixes it.

Common Trigger: PCIe Devices

This error loves to hit PCI Express devices — graphics cards, NVMe SSDs, network cards. If you just installed a new GPU or an M.2 drive and got this error, it's the IRQ translator failing because the BIOS didn't reserve enough interrupt lines. Uninstalling the device from Device Manager forces a renegotiation.

The 15+ Minute Fix: Advanced BIOS and ACPI Tuning

Still broken? You've got a deeper problem — likely a BIOS bug, outdated ACPI tables, or a hardware conflict. Here's the real workflow.

Step 1: Check BIOS Versions

Update your motherboard BIOS to the latest version. This is the number one cause of IRQ translation failures on modern boards. Go to your board manufacturer's site, grab the BIOS file, and flash it. Don't bother with beta versions — stick to the stable release. On systems from Dell, HP, or Lenovo, use their tools (e.g., Dell Command Update) to get the latest UEFI firmware.

Step 2: Disable Windows Fast Startup

Fast Startup screws with device initialization. Go to Control Panel > Power Options > Choose what the power buttons do. Click "Change settings that are currently unavailable." Uncheck Turn on fast startup. Shut down completely, then boot back up. This forces the PNP manager to re-enumerate all devices from scratch.

Step 3: Reset ACPI Driver in Safe Mode

If it still fails, the ACPI.sys driver might have a stale IRQ mapping. Boot into Safe Mode (hold Shift while clicking Restart in the sign-in screen). Open Command Prompt as admin:

sc config acpi start= disabled

Yes, seriously. Reboot normally — Windows will complain about missing ACPI, but it will also load a default IRQ handler. Then reboot again, go back to Safe Mode, and re-enable it:

sc config acpi start= system

Reboot normally. This resets the ACPI driver's cached IRQ assignments. I've fixed 0XC0040037 on Lenovo ThinkPads doing exactly this.

Step 4: Manual IRQ Assignment in BIOS

If you're on an older system (pre-UEFI, or a server board), you can manually assign IRQs per PCI slot. Enter BIOS setup, look for PCI/PnP Configuration or IRQ Resources. Set IRQ 10 and 11 to Available or Legacy. Save and exit. This forces the OS to use software IRQ translation instead of hardware. It's ugly but works.

Pro tip: If you have a Thunderbolt dock or USB-C hub connected, unplug it before booting. Those things cause IRQ conflicts like crazy. Boot without it, let Windows settle, then plug it back in.

When to Replace Hardware

If none of this works, the error is hardware-level. The device that's failing has a physical IRQ line shorting or a dead ACPI controller. Swap out the PCIe card (try a different slot first), or replace the motherboard. I've seen one case where a bad keyboard controller on a Dell laptop caused this error — the keyboard was sending bogus interrupts. Unlikely, but don't rule out flaky peripherals.

Quick Reference Table

That's it. Start at the top, work your way down. Most people stop at Step 2. You won't need Step 6 unless you're running a museum piece. Error 0XC0040037 is stubborn but fixable.