BSOD 106 (LPC_INITIALIZATION_FAILED): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Local Procedure Call infrastructure failed during system initialization.

Could be also:
Constant	Type	OS
ERROR_SEM_USER_LIMIT	Win32 error	Windows
EISCONN	errno	Linux
EQFULL	errno	Mac
ELAST	errno	Mac
ECONNABORTED	errno	Windows

Previous	Next
IO1_INITIALIZATION_FAILED	PROCESS1_INITIALIZATION_FAILED

LPC_INITIALIZATION_FAILED

LPC/ALPC startup failure for LPC_INITIALIZATION_FAILED

LPC_INITIALIZATION_FAILED is bug check code 0x0000006A. LPC and ALPC provide kernel communication channels used by core Windows services and subsystems. This bug check means that required local IPC infrastructure did not initialize during startup.

How to read it in a dump

The failure is about local interprocess communication infrastructure, not a network RPC timeout.
The stack may include object manager, security, memory, or port initialization paths.
Subsystem startup can fail later if LPC/ALPC is unavailable.

What to check

Check system file integrity, early security products, and kernel memory corruption.
Compare with MSRPC_STATE_VIOLATION if communication-state failures appear later.
Preserve a full dump when possible because port/object state matters.

References

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 lpc / 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.