PROCESS_INITIALIZATION_FAILED

Code: 0x60 (96)

As HRESULT:As NTSTATUS:

Description

The PROCESS_INITIALIZATION_FAILED bug check has a value of 0x00000060.

This bug check appears very infrequently.

Important

This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Resolution

The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.

Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.

Associated Modules

ModuleCodeFound inDescription
EventCreate.exe0x6078.11011%1
cipher.exe0x6011Protection status
dsreg.dll0x601011Automatic device join pre-check tasks completed. The device can NOT be joined because a domain controller could not be located. The device must be connected to a network with connectivity to an Active Directory domain controller.
ehepgres.dll0x607%1
hvloader.dll0x6011Hypervisor processor startup failed (APIC ID %1, status %2). Further processors in the system were not started.
hvservice.sys0x6010Hypervisor processor startup failed (APIC ID %1, status %2). Further processors in the system were not started.
nslookup.exe0x6078.11011mail agent
w32time.dll0x601011The time sample was rejected because: The peer is not synchronized, or reachability has been lost in one, or both, directions. This may also indicate that the peer has incorrectly sent an NTP request instead of an NTP response.
webservices.dll0x6078.11011The HTTP request header '%1' was invalid.
wevtutil.exe0x6011Failed to assert changes to one or more publishers and channels (error 0x%1!x!)
win32k.sys0x6078.1MenuDropAlignment
win32kbase.sys0x601011MenuDropAlignment
12 entries