| Previous | Next |
| STATUS_INVALID_OPLOCK_PROTOCOL | STATUS_INTERNAL_ERROR |
STATUS_INTERNAL_DB_CORRUPTION
An internal database has on-disk corruption
The NTSTATUS description explicitly distinguishes this condition from a routine logical lookup failure: the operation cannot complete because of catastrophic media failure or on-disk structure corruption. When the returning component is LSA, SAM or another system database owner, the database context is essential to interpreting the generic status name.
Preserve the first failing operation and collect storage diagnostics before modifying the database. A restore, component-specific recovery procedure, or system repair may be appropriate only after identifying which database owns the corrupted structure. Do not assume that recreating one missing object repairs structural damage.
What to inspect
- Identify the component and exact database operation that returned the status.
- Check filesystem, storage, WHEA, and component-specific event logs for preceding failures.
- Preserve recovery media and backups before attempting component-specific repair or restore.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Open Specifications: LsarOpenPolicy2
- Microsoft: LsaOpenPolicy
Looking for a different code? Search another status or error code.