| Previous | Next |
| STATUS_VIRUS_DELETED | STATUS_CANNOT_BREAK_OPLOCK |
STATUS_BAD_MCFG_TABLE
The conflict is in PCI Express configuration-space description
STATUS_BAD_MCFG_TABLE refers to the ACPI MCFG table, which describes PCI Express memory-mapped configuration space. Windows documents MCFG-based access as one of the supported mechanisms for PCI configuration space. A resource conflict with this table is therefore a firmware/platform integration problem, not a malformed PCI configuration register written by an application.
The useful data is the MCFG allocation information together with the device's assigned memory resources and PCI segment/bus topology. ACPI defines the MCFG table as the description of memory-mapped configuration-space base addresses. Windows PnP resource lists separately describe resources assigned to devices. Overlap or inconsistency between these views can make the configuration-space region unsafe to use.
What to inspect
- The raw MCFG table, OEM/table revisions and every allocation entry relevant to the PCI segment.
- Segment group, start/end bus numbers and configuration-space base address.
- The device's raw and translated memory resource descriptors from PnP start.
- Whether the conflict began after a BIOS/UEFI update or a hardware/topology change.
Do not patch the MCFG address or reserve memory by guesswork. Firmware tables and PCI topology must describe the same platform. Compare against the system vendor's firmware update and the actual PCI hierarchy before changing driver resource handling.
References
- UEFI Forum: ACPI MCFG table
- Microsoft: Accessing PCI device configuration space
- Microsoft WDK: CM_PARTIAL_RESOURCE_DESCRIPTOR
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.