How to fix Error 672 on Windows 11

by

Troubleshooting Guide: Error 672 – “A Translator Failed to Translate Resources” (Windows 11)

Why This Error Happens

Error 672 typically occurs when the Windows resource translator—responsible for mapping hardware resources (IRQs, I/O ports, memory addresses) between the HAL (Hardware Abstraction Layer) and a device driver—encounters a conflict or corruption it cannot resolve. This is most commonly caused by a corrupted or outdated device driver, a resource conflict between two devices sharing the same IRQ/memory range, or corrupted entries in the Windows Registry (specifically under HKEY_LOCAL_MACHINE\HARDWARE\RESOURCEMAP). It can also surface after a BIOS/UEFI update or a botched Plug and Play (PnP) enumeration during boot.

Step-by-Step Resolution Guide

  1. Identify the Offending Device
  • Open Device Manager (Win + X → Device Manager).
  • Look for devices flagged with a yellow warning icon. Right-click the affected device → Properties → check the Events or General tab for Error 672 or resource conflict messages.
  1. Update or Roll Back the Driver
  • In Device Manager, right-click the problematic device → Update driver → Search automatically for drivers.
  • If the issue started after a recent update, instead choose Properties → Driver tab → Roll Back Driver.
  • Alternatively, download the latest driver directly from the manufacturer’s website and install manually.
  1. Check for Resource Conflicts Manually
  • Go to Device Manager → View → Resources by type.
  • Expand Interrupt Request (IRQ) and Memory to check if two devices are sharing resources improperly.
  • If found, disable one conflicting device temporarily (right-click → Disable device) to confirm it resolves the error.
  1. Reset the PnP Resource Cache via Registry
  • Press Win + R, type regedit, and navigate to:
    HKEY_LOCAL_MACHINE\HARDWARE\RESOURCEMAP
  • Back up this key first (right-click → Export).
  • Restart the PC—Windows will automatically rebuild this resource map fresh, often clearing stale conflict data. (Do not manually delete keys here unless following vendor-specific guidance.)
  1. Update BIOS/UEFI Firmware
  • Visit your motherboard or laptop manufacturer’s support page.
  • Download the latest BIOS/UEFI version and follow their update utility instructions carefully (ensure a stable power source during the flash).

Alternative or Verification Steps

  • Verify the Fix: Open Event Viewer (eventvwr.msc) → Windows Logs → System, and filter for Event ID 672. If no new instances appear after a reboot and normal usage, the issue is resolved.
  • Alternative Fix: Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt to repair corrupted system files that may be interfering with resource translation.