| Previous | Next |
| STATUS_PNP_BAD_MPS_TABLE | STATUS_PNP_IRQ_TRANSLATION_FAILED |
STATUS_PNP_TRANSLATION_FAILED
STATUS_PNP_TRANSLATION_FAILED means the resource translator could not turn the bus-relative resources for a device into the translated resources that the driver needs at start time. It is not merely a shortage of resources and it is not a normal driver-ID matching failure.
Windows supplies paired raw and translated resource lists with IRP_MN_START_DEVICE. The corresponding entries describe the same resource before and after platform translation. That pairing is the key evidence: a driver should log both lists and identify the first descriptor that cannot be reconciled.
What to inspect
- The raw and translated resource lists, the parent bus, and any bridge or firmware resource description involved.
- Whether the failure concerns memory, I/O space, DMA, or an interrupt resource; do not collapse them into a single “resource conflict”.
- Whether the device can be reproduced on a different platform or firmware revision before changing the driver.
References
- Microsoft: raw and translated resource mappings
- Microsoft: resources during function-driver start
- UEFI Forum: ACPI platform resource model
Looking for a different code? Search another status or error code.