BSOD 282 (EM_INITIALIZATION_ERROR): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Windows failed while initializing an executive or environment-management component.

Could be also:
Constant	Type	OS
ERROR_EAS_NOT_SUPPORTED	Win32 error	Windows

Previous	Next
VIDEO_SCHEDULER_INTERNAL_ERROR	DRIVER_RETURNED_HOLDING_CANCEL_LOCK

EM_INITIALIZATION_ERROR

Executive management initialization failure for EM_INITIALIZATION_ERROR

EM_INITIALIZATION_ERROR is bug check code 0x0000011A. This early initialization code is useful only with the stack and nested status. It points at a core OS management component failing before the system reached normal runtime service startup.

How to read it in a dump

Treat it as boot-phase infrastructure failure.
The component name on the stack is required to distinguish memory, environment, policy, or executive state.
Do not guess from the symbolic name alone.

What to check

Check system file integrity, boot-start drivers, registry hive health, and recent OS updates.
Use boot debugging or a full dump when possible.
Compare with other initialization bug checks on repeated boots.

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