Troubleshooting Guide: Error 673 – “A IRQ Translator Failed to Translate Resources”

Why This Error Happens

This error occurs when the Windows Plug and Play (PnP) Manager cannot properly map an IRQ (Interrupt Request) resource from a device to its parent bus controller, typically due to a resource conflict in ACPI’s interrupt routing table. It commonly happens after a BIOS/UEFI update, driver installation, or hardware change that disrupts the IRQ allocation between the PCI bus and the affected device. Corrupted or outdated bus/chipset drivers, as well as manually assigned static resources (IRQ, DMA, or memory ranges) in Device Manager, can also trigger this translation failure.

Step-by-Step Resolution Guide

1. Identify the Affected Device
   Open Device Manager (Win + X → Device Manager), look for devices with a yellow warning icon. Right-click the problematic device → Properties → Events tab to confirm Error 673 is listed, and note the exact hardware ID.

2. Reset Manual Resource Assignments
   In Device Manager, right-click the device → Properties → Resources tab. If “Use automatic settings” is unchecked, re-enable it. If greyed out, uninstall the device (check “Delete the driver software for this device” if a driver update is also needed), then reboot to let Windows re-enumerate and auto-assign resources.

3. Update the Chipset and Bus Drivers
   Go to your motherboard/laptop manufacturer’s support site and download the latest Chipset Driver and PCI/ACPI drivers for Windows 11. Install these before any peripheral drivers, as they govern IRQ routing at the bus level.

4. Update BIOS/UEFI Firmware
   Check your manufacturer’s site for a BIOS/UEFI update. Many Error 673 cases stem from outdated ACPI tables in firmware; flashing the latest version corrects malformed IRQ routing definitions.

5. Disable Legacy/APIC Conflicts (Advanced)
   In BIOS/UEFI settings, ensure ACPI mode is enabled (not Legacy/CSM) and, if available, toggle IOAPIC/MSI mode for the affected controller (common with USB, storage, or network controllers). Save changes and reboot.

Alternative or Verification Steps

• Verify the fix: Reopen Device Manager and confirm the yellow warning icon is gone; also check Event Viewer → Windows Logs → System to ensure Error 673 no longer appears after a fresh reboot.
• Alternative fix: If the issue persists, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt to repair corrupted system files that may be interfering with PnP resource allocation.