What does Windows error code 105 (ERROR_SEM_OWNER_DIED) mean?

ERROR_SEM_OWNER_DIED

What ERROR_SEM_OWNER_DIED means

The previous owner of an exclusive semaphore terminated or otherwise ended ownership without completing normal release. The result signals abandoned synchronization state. Another participant may acquire the object, but data protected by it can be inconsistent because the former owner stopped in the middle of an update.

Common causes

• The owning process crashed while holding the semaphore
• A thread was forcibly terminated inside the protected region
• The service was killed during a multi-step state update
• A watchdog aborted the owner after a timeout

How to investigate

1. Find the crash, termination, or watchdog event for the former owner
2. Determine which data structures were protected at the time
3. Run integrity checks before allowing normal processing to resume
4. Capture the new owner path to ensure it recognizes abandoned state

Developer guidance

Handle abandonment explicitly. Recovery code should validate or roll back protected state before treating the acquisition as ordinary success. Avoid forcefully terminating threads that may own synchronization primitives.

Administrator and support guidance

Do not assume that restarting only the consumer is sufficient. Check persistent files, shared memory, and transactional state modified by the dead owner.

How this code differs from related results

Unlike ERROR_EXCL_SEM_ALREADY_OWNED, the earlier owner is no longer healthy. The key issue is possible state corruption, not merely contention.

References

• Microsoft: System error codes 0–499