| Previous | Next |
| OBJECT_INITIALIZATION_FAILED | PROCESS_INITIALIZATION_FAILED |
SECURITY_INITIALIZATION_FAILED
Security subsystem initialization failure for SECURITY_INITIALIZATION_FAILED
SECURITY_INITIALIZATION_FAILED is bug check code 0x0000005F. This code indicates that kernel security initialization did not complete. It can involve token, audit, access-check, logon-session, policy, or security descriptor infrastructure during boot.
How to read it in a dump
- The failure occurs before normal user logon; it is not merely an authentication denial.
- Look for security subsystem status codes and early-loaded security or filter drivers.
- System file integrity and registry/security policy state can be relevant.
What to check
- Check early boot security products, credential/security policy changes, and corrupted system files.
- Preserve the nested status code and stack.
- If the system fails repeatedly at boot, compare safe-mode and recovery-environment logs.
References
- Security checks in drivers
- Kernel-mode support routines
- Microsoft Bug Check Code Reference
- Crash dump files and WinDbg
Dump evidence
Preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line. - find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with security / initialization.
- keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.