BSOD 51 (UNEXPECTED_INITIALIZATION_CALL): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: An initialization routine was called in an unexpected phase or state.

Could be also:
Constant	Type	OS
ERROR_REM_NOT_LIST	Win32 error	Windows
KERN_POLICY_STATIC	Kern return	Mac
ippStsFeaturesCombination	Intel Ipp Status	Any
EL2HLT	errno	Linux
ENETUNREACH	errno	Mac
EBADR	errno	Solaris

UNEXPECTED_INITIALIZATION_CALL

Unexpected kernel initialization call

UNEXPECTED_INITIALIZATION_CALL is bug check code 0x00000033. This bug check points at initialization sequencing rather than a normal runtime driver error. A component entered an init routine after the expected phase, before prerequisites existed, or in a state that made initialization unsafe.

How to read it in a dump

Identify the initialization phase on the stack: boot loader handoff, kernel init, driver load, subsystem init, or late reinitialization.
A duplicate call can indicate corrupt state, a wrong driver entry path, or incompatible boot/start ordering.
The failing module and phase are more important than the symbolic name alone.

What to check

Check boot-start and system-start drivers, filter load order, and recent kernel or driver updates.
Look for duplicate registration or reinitialization paths.
Compare with neighboring init bug checks if the machine fails early in boot.

References

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