Skip to content

Published: April 30, 2016 | Applies to:

See this fix to resolve HAL_INITIALIZATION_FAILED BSOD in Windows 10 by enabling High Precision Event Timer (HPET) in BIOS/UEFI setup.

HAL_INITIALIZATION_FAILED is the another Blue Screen of Death (BSOD) error we just came around on Windows 10. Like other stop errors or BSODs, this error may come into play when a new driver/service is being loaded and likely to happen with new software/hardware. If you face this error on a virtual OS installation, you can reinstall the OS to fix it from frequently happening. While if you’re facing it on a your primary non-virtual OS, you can fix it with a selective approach.

When this error happens, screen displays this message and system may try to reboot itself:

Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you. (x% complete)

If you’d like to know more, you can search online later for this error: HAL_INITIALIZATION_FAILED

FIX - HAL_INITIALIZATION_FAILED BSOD In Windows 10

As soon as this error happens, Windows starts creating its log which you can use for analysis, as its the only hint to solve this issue perfectly. But in general cases, it is seen that some steps are very common to fix this kind of stop errors. So the common steps to fix this issue are as follows:

  • If you got this error on virtual installation, the stop error bug check should follow 0x0000005C code. Remedy to remove this error is discussed in this fix.
  • You should cross check your machine drivers, and update them as soon as computer restarts after this error to suppress further BSODs.
  • If you’ve recently installed a new software and you get this stop error frequently after that, remove the software and check status of issue.
  • You should also run chkdsk /f command in administrative Command Prompt to look for hard drive corruptions and fix them subsequently.

If any of these suggestions helps, you’re good to go. If they doesn’t helps, try this selective fix.

FIX : HAL_INITIALIZATION_FAILED BSOD In Windows 10

To fix HAL_INITIALIZATION_FAILED, we found that enabling High Precision Event Timer (HPET) in BIOS/UEFI may help. HPET is a hardware timer developed by Microsoft and Intel and can be enabled from BIOS/UEFI setup options. However, HPET is not supported by all of the machines. Also, its up to Windows which timer it wants to use, even if you’ve enabled HPET. Enabling HPET may not only solve this stop error but also help to improve your system performance. Here is how you enable it:

1. Boot into System Recovery Options. Hit the Command Prompt entry at following screen:

FIX - DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD In Windows 10

2. Previous step will result in opening of Command Prompt at boot.

FIX - DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD In Windows 10

3. Select your admin account and enter your selected account password to continue.

FIX - DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD In Windows 10

4. Now in the Command Prompt window, type following command and press Enter key:

bcdedit /set useplatformclock true

FIX - HAL_INITIALIZATION_FAILED BSOD In Windows 10

Close Command Prompt and Continue to your OS. If you later upgrade your machine to newer OS/build and if you like to disable HPET, run bcdedit /deletevalue useplatformclock command in Advanced Recovery Command Prompt.

Hope this helps!


SHARE: Facebook Google+ Twitter

Leave a Reply

Your email address will not be published. Required fields are marked *

What's New


Recent Comments

  • frozen nerd : i also tried uninstalling avast, disabling all startup progr...

    2 hours ago

  • frozen nerd : i have a win 10 home OEM from ASUS tried this and got the ...

    2 hours ago

  • Darren : Thank you, Kapil! The first two netsh commands and reboot ju...

    4 hours ago

  • Charles : I followed your steps but got stuck at step 9 since I couldn...

    9 hours ago

  • Barry : Fantastic! You solved my problem with very clear instruction...

    10 hours ago

  • Keith Fessey : Ok, so whats the difference between the "recovery key" and t...

    14 hours ago


Windows Group Policy Troubleshooting