Question HAL_INITIALIZATION_FAILED BSOD Please solve the problem..T.T

Jun 1, 2020
20
0
10
0
It happens intermittently while using a computer. It is difficult to find out which part is the problem. Can you help me?

HAL_INITIALIZATION_FAILED (5c)
Arguments:
Arg1: 0000000000000110
Arg2: fffff7908002d6f0
Arg3: 0000000000000000
Arg4: ffffffffc0000095

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-P9OP6UA

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 2

Key : Analysis.Memory.CommitPeak.Mb
Value: 90

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 5c

BUGCHECK_P1: 110

BUGCHECK_P2: fffff7908002d6f0

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffc0000095

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
fffff8074cc4b5c8 fffff8074517633b : 000000000000005c 0000000000000110 fffff7908002d6f0 0000000000000000 : nt!KeBugCheckEx
fffff8074cc4b5d0 fffff80745248aa9 : fffff80744259180 00000019ad4c4ed2 0000000000000000 0000000000000000 : hal!HalpTimerClockArm+0x1914b
fffff8074cc4b610 fffff807452bcbc1 : fffff80744259180 00000019ad4c4ed2 0000000000000000 fffff8074564f840 : nt!KiRestoreClockTickRate+0x2d
fffff8074cc4b640 fffff807452bb838 : fffffffffffffffe 00002425e6c4334c ffffd586f0724050 0000000000000000 : nt!KeResumeClockTimerFromIdle+0x2b1
fffff8074cc4b6e0 fffff807452badde : 0000000000000003 0000000000000002 ffffd586f0724140 0000000000000008 : nt!PpmIdleExecuteTransition+0x8b8
fffff8074cc4ba00 fffff807453c5e84 : 0000000000000000 fffff80744259180 ffffd586fea3c080 00000000000003c6 : nt!PoIdle+0x36e
fffff8074cc4bb60 0000000000000000 : fffff8074cc4c000 fffff8074cc45000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x44


SYMBOL_NAME: nt!KiRestoreClockTickRate+2d

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 2d

FAILURE_BUCKET_ID: 0x5C_HAL_TIMER_INITIALIZATION_FAILURE_nt!KiRestoreClockTickRate

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {499a6293-2a5b-5ec1-ee06-c17ef3112bea}

Followup: MachineOwner
 

Colif

Win 10 Master
Moderator
hal = hardware abstraction layer (alas, not a computer from 2001)

what are specs of the PC?
Method 1: Setting useplatformclock to True
One of the best ways to get rid of the HAL_INITIALIZATION FAILED error on Windows 10 is by setting useplatformclock to True. With that said, here are the steps you should follow:

  1. Click the Search icon.
  2. Type “cmd” (no quotes).
  3. Right-click the Command Prompt on the results, then select Run as Administrator.
  4. If you’re prompted to give permission to the app, click Yes.
  5. In the Command Prompt, type “bcdedit /set useplatformclock true” (no quotes).
  6. The next thing you have to do is check whether useplatformclock has been set to True. You can do this by typing “bcdedit /enum” (no quotes) inside the Command Prompt. You should see ‘Yes’ beside useplatformclock.
  7. You can restart your computer and check if the problem has been resolved.
Note: If this error prevents you from accessing your operating system, we suggest performing the steps through Safe Mode.

  1. Restart your computer.
  2. While it is booting, restart it again. Do this a couple of times to initiate the Automatic Repair process.
  3. Select Troubleshoot, then go to Advanced Options.
  4. From there, click Startup Settings, then click Restart.
  5. Once your computer restarts, you will see a list of options.
  6. Press 5 or F5 on your keyboard to select Safe Mode with Networking.
  7. Once you’ve booted your computer into Safe Mode, launch Command Prompt and perform the steps above.
https://www.auslogics.com/en/articles/how-to-fix-hal-initialization-failed-in-windows-10/

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
 
Jun 1, 2020
20
0
10
0
My computer spec is this.
cpu: intel 9700K
Mainboard Z390 Extreme4
RAM 32 GB
Graphic card RTX2060
Let's try setting useplatformclock to True. Thank you.

Since the blue screen occurs intermittently,
if this problem occurs again,
I will upload the minidump log.
 
Jun 1, 2020
20
0
10
0
There's a problem.
After setting to useplatformclock to True
On the first run of chrome, loading slows down and cpu% is high.
It feels like YouTube preview loading and Chrome's image loading are slow.
 
Jun 1, 2020
20
0
10
0
hal = hardware abstraction layer (alas, not a computer from 2001)

what are specs of the PC?

https://www.auslogics.com/en/articles/how-to-fix-hal-initialization-failed-in-windows-10/

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
When I first used the bcdedit /enum command, useplatformclock was not displayed. In this case, I know that my motherboard does not support HPET, but can I set it to true?
 
Jun 1, 2020
20
0
10
0
My CPU% was stable after setting useplatformclock false.
Please tell me how to attach zip file to thread
Sorry I'm new to using threads :);;;
 
Jun 1, 2020
20
0
10
0
link
Link attached. Thank you.
Since the pc language is in Korean, the log is written in Korean even in the text file. Are you okay?
 

Colif

Win 10 Master
Moderator
that might make it difficult... and I was right.

the file includes 4 dumps so axe or someone I will senf file to will be able to convert them.

you seem to have a bad day on 22nd of May. Adobe crashed and created a cascade

Nvidia drivers are mentioned a few times, you could try running DDU in safe mode and reinstall either same drivers you have or newer ones - https://forums.tomshardware.com/faq/how-to-do-a-clean-installation-of-windows-10.3170366/

@axe0axe0 may see more in those files than I did :)
 
Jun 1, 2020
20
0
10
0
that might make it difficult... and I was right.

the file includes 4 dumps so axe or someone I will senf file to will be able to convert them.

you seem to have a bad day on 22nd of May. Adobe crashed and created a cascade

Nvidia drivers are mentioned a few times, you could try running DDU in safe mode and reinstall either same drivers you have or newer ones - https://forums.tomshardware.com/faq/how-to-do-a-clean-installation-of-windows-10.3170366/

@axe0axe0 may see more in those files than I did :)
Yes. That day I experienced a crash.

This problem It was because I installed the NVIDIA graphics card as a standard driver.

The first driver installed after PC initialization was DCH.
After deleting the standard driver with the DDU program, updating the DCH driver eliminated the driver conflict.

Although HAL_INITIALIZATION_FAILED bothers me, 😅

Thank you for your help.

I hope this blue screen won't appear anymore.
 

axe0axe0

Reputable
Jun 5, 2017
915
30
5,390
102
Microsoft has little documentation on this bugcheck and so far the only thing I know is that these crashes are because of an integer overflow as the fourth parameter is an NTSTATUS error code indicating 'integer overflow'. I'll have to look into what that means as I've never seen it before.
 
Jun 1, 2020
20
0
10
0
Microsoft has little documentation on this bugcheck and so far the only thing I know is that these crashes are because of an integer overflow as the fourth parameter is an NTSTATUS error code indicating 'integer overflow'. I'll have to look into what that means as I've never seen it before.
Is there any additional data I will provide to solve this problem?

I think this problem (Hal_BSOD) occurred after pc initialization.

I've been using pc for the past year without any problems, but recently I had a c++ runtime library error of unknown cause while using a specific game or adobe.

When the runtime error pops up, the cpu is fully loaded up to 100%, and the system time has been changed to 2374 years.

This error occurred from time to time, and I initialized the pc to fix the problem. In the process, the graphics card is installed incorrectly, I installed the adequate DCH graphics card.

Fixed c++ runtime library error and graphics card crashes as of now.
Only Hal_BSOD is bothering me.

The situation in which the Hal BSOD appears mainly to me was during surfing the web with YouTube and Twitch turned on with chrome or editing Adobe video (Pr/Ae) with YouTube turned on.

In addition, after running well for a few days without any problems, the Hal BSOD suddenly appears.

Please let me know if you have any data that can help you solve the problem, or any additional data you can provide.

The sentence may be awkward using the Google Translator. Sorry.😅

(ex)
 
Last edited:

axe0axe0

Reputable
Jun 5, 2017
915
30
5,390
102
Theoretically, this crash occurs at boot because while booting the file that acts as a layer between the physical part of your computer and Windows has problems with loading. Theoretically, because it doesn't take a few hours to boot and about half the dumps provided are crash dumps from after a few hours of Windows running.

To provide more insight on what I mentioned earlier regarding this integer overflow, say you have a limited range of numbers you can have, between 10 and 20 and it's not possible to go higher or lower. You are forced to go up to 21, but you can't do that as 20 is the limit. The number goes up to 21 anyways and that causes a problem that you have to report. That is an overflow and that analogy is basically what happens, some instruction says to go higher then there is room for and since the hardware clock is involved it's critical that something like that doesn't happen. The opposite could also happen, going below the range that's allowed, another kind of overflow.

If you could upload C:\Windows\MEMORY.dmp to google drive then I'll have a look at it when I can. The recommended way to upload the memory dump file is to copy it from command prompt to your desktop and then upload it, sometimes a copy/paste from Windows Explorer doesn't go smoothly and I would not be able to open the dump in such a case.
Code:
copy "C:\Windows\MEMORY.dmp" "%userprofile%\desktop"
 
Jun 1, 2020
20
0
10
0
Theoretically, this crash occurs at boot because while booting the file that acts as a layer between the physical part of your computer and Windows has problems with loading. Theoretically, because it doesn't take a few hours to boot and about half the dumps provided are crash dumps from after a few hours of Windows running.

To provide more insight on what I mentioned earlier regarding this integer overflow, say you have a limited range of numbers you can have, between 10 and 20 and it's not possible to go higher or lower. You are forced to go up to 21, but you can't do that as 20 is the limit. The number goes up to 21 anyways and that causes a problem that you have to report. That is an overflow and that analogy is basically what happens, some instruction says to go higher then there is room for and since the hardware clock is involved it's critical that something like that doesn't happen. The opposite could also happen, going below the range that's allowed, another kind of overflow.

If you could upload C:\Windows\MEMORY.dmp to google drive then I'll have a look at it when I can. The recommended way to upload the memory dump file is to copy it from command prompt to your desktop and then upload it, sometimes a copy/paste from Windows Explorer doesn't go smoothly and I would not be able to open the dump in such a case.
Code:
copy "C:\Windows\MEMORY.dmp" "%userprofile%\desktop"
Thank you for a detailed description.
Attached a link.
link
 
Jun 1, 2020
20
0
10
0
Just to let you know, right now my internet is down and they expect to resolve the problem by the end of the day. That means I cannot download the dump right now.
I'll wait. 😄

The CPU 100% full load problem that I thought was fixed and the system time change (5673 year) problem appeared again today.

This issue has been documented in the System/Applications tab of Event Viewer.

Can you analyze this too?

Can I show logs using SysnativeBSODCollectionApp?
 
Jun 1, 2020
20
0
10
0
I have a question.
The HAL version displayed in the system information says 10.0.18362.752.
The version that comes out when using the winver command in CMD is 18363.836. Is it abnormal or normal to look like this?
If there is a problem, can this be the cause of the Hal BSOD? Or can it cause other problems?
 
Jun 1, 2020
20
0
10
0
I'll wait. 😄

The CPU 100% full load problem that I thought was fixed and the system time change (5673 year) problem appeared again today.

This issue has been documented in the System/Applications tab of Event Viewer.

Can you analyze this too?

Can I show logs using SysnativeBSODCollectionApp?
There was a window update error at the time this issue occurred.
 

axe0axe0

Reputable
Jun 5, 2017
915
30
5,390
102
I have a question.
The HAL version displayed in the system information says 10.0.18362.752.
The version that comes out when using the winver command in CMD is 18363.836. Is it abnormal or normal to look like this?
If there is a problem, can this be the cause of the Hal BSOD? Or can it cause other problems?
I have the same thing, HAL version 10.0.18362.752 and winver 18363.836.
 
Jun 1, 2020
20
0
10
0
I finally tried a clean install with windows 1909 version.
After that, I hope that the blue screen will no longer appear.
It has helped me a lot for a few days. Thank you so much.😄
 
Jun 1, 2020
20
0
10
0
Let us know if the problem occurs again.

I'll check out the dump anyways sometime this week.
Hello how are you?

The other day, I had the same blue screen phenomenon again.

Immediately after a clean installation yesterday, I installed the chipset driver and management engine driver.

And with the xtu program, I gave underbolting as before.

As a result of the cpu stress of the xtu program, the cpu maximum temperature was 60 to 70 degrees and the test was completed for 20 minutes.

I immediately installed Adobe Premiere and imported my existing files from dDrive for rendering.

During the rendering process, the cpu temperature stayed between 60 and 75 degrees and HAL BSOD occurred 10 seconds after rendering was finished.

I was desperate.

As a second test, I removed the chipset driver and management engine driver and tried rendering.

The cpu temperature stayed between 70 and 85 degrees and forced a reboot during rendering.

The second test is presumed to be a reboot due to cpu overheating.

Can you analyze the log I posted before?
Another question is: can underbolting affect the HAL BSOD?
 

ASK THE COMMUNITY

TRENDING THREADS