What does NTSTATUS 0xC0000114 (STATUS_ABIOS_INVALID_LID) mean?

 
Previous Next
STATUS_ABIOS_INVALID_COMMAND STATUS_ABIOS_SELECTOR_NOT_AVAILABLE

STATUS_ABIOS_INVALID_LID

The LID field selects the device context used to interpret an ABIOS request

STATUS_ABIOS_INVALID_LID belongs to the request-addressing side of ABIOS. IBM describes the Logical ID field in the request block as identifying the particular device addressed by the function request, and the initialized common data area uses LIDs as indices for device information. The value must therefore be interpreted against the ABIOS state built for the current machine and boot.

The public Windows status list also contains STATUS_ABIOS_LID_NOT_EXIST. Microsoft does not publish the internal Windows test that separates those two results, so it would be unsafe to invent a specific numeric range or reserved-bit rule. A practical investigation should instead preserve whether the LID value itself is structurally acceptable to the caller and whether an initialized common-data-area entry exists. That allows the producer-specific distinction to be observed rather than guessed.

Look for uninitialized request blocks, truncated field writes, stale LIDs copied from another boot, or 16/32-bit structure-layout mistakes in old compatibility code. The request block should be captured before the failing call because later error handling may overwrite the return-code field or reuse the buffer. If the LID is correct for the current table, retain the exact firmware/model context and examine the producer that returned this status; the symbolic name alone cannot reveal the undocumented validation predicate.

What to inspect

  • Capture the raw LID value before error handling reuses the request block.
  • Compare structure packing and field initialization in 16/32-bit compatibility code.
  • Check the current initialized ABIOS table rather than a LID remembered from another boot.

References

Looking for a different code? Search another status or error code.