HAL_INITIALIZATION_FAILED
Code: 0x5c (92)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x005c (92)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x005c (92)
Description
The HAL_INITIALIZATION_FAILED bug check has a value of 0x0000005C.
This indicates that the HAL initialization failed. The hardware abstraction layer is low level code that is intialized early in the Windows start up.
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.
See Also
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
| Module | Code | Found in | Description |
|---|---|---|---|
| EventCreate.exe | 0x5c | 78.11011 | %1 |
| cipher.exe | 0x5c | 11 | Personal Data Encryption |
| dsreg.dll | 0x5c | 1011 | Preparing to send a request to the Web Account Manager silently (no UI mode). Account provider ID: %1 Scope: %2 Client ID: %3 Authority: %4 Resource: %5 CorrelationId: %6 |
| ehepgres.dll | 0x5c | 7 | %1 |
| nslookup.exe | 0x5c | 78.11011 | user ID |
| w32time.dll | 0x5c | 1011 | The peer is unreachable. |
| webservices.dll | 0x5c | 78.11011 | The custom channel callbacks are required for a custom channel but were not specified. |
| wevtutil.exe | 0x5c | 10 | A legacy channel named %1 already exists in the registry. |
| wevtutil.exe | 0x5c | 11 | A legacy channel named %1 already exists in the registry and will be replaced by the one in the manifest. |
| win32k.sys | 0x5c | 78.1 | MouseHoverHeight |
| win32kbase.sys | 0x5c | 1011 | MouseHoverHeight |
| 11 entries | |||