HAL_INITIALIZATION_FAILED Windows 10

[andres_florio]

Hello, I've been stuck with this trouble for a while.
Since I formated my pc and installed Windows 10 pro from scratch, every time I start my pc after been powered down for at least 15 minutes, it restarts after reaching the blue Windows logo.
Checking BlueScreenView shows that I get a BSOD every time that happens (I never get to even see it). The error is called HAL_INITIALIZATION_FAILED involving hal.dll and ntoskrnl.exe.
I've reinstalled Win10, done a chkdsk /r but none of them worked. In the cmd of the repair tools (the one you access via holding down shift and clicking restart) I entered the commands:
bootrec /RebuildBcd
bootrec /FixMbr
bootrec /FixBoot
and it fixed the problem! But 4 days later I was having the same issue again.
I got the .dmp file but did not know how to share it.

 

[axe0axe0]

Upload the dumps to onedrive, google drive or dropbox and post a share link.

 

[andres_florio]

Upload the dumps to onedrive, google drive or dropbox and post a share link.

Here it is: https://drive.google.com/open?id=0B4giEdrwyltjTFZZR2tscHgyVDA

 

[axe0axe0]

What is the text file for?

Remove either of the memory brand sticks and reseat the other sticks in a way that your motherboard supports.
See http://asrock.nl/downloadsite/Manual/980DE3U3S3.pdf, page 16.

 

[andres_florio]

What is the text file for?

Remove either of the memory brand sticks and reseat the other sticks in a way that your motherboard supports.
See http://asrock.nl/downloadsite/Manual/980DE3U3S3.pdf, page 16.

Why? I have this mobo and RAM since January. Why would it be failing now the way they are set?

 

[axe0axe0]

It's merely a suggestion, I can't pinpoint the exact cause with a single minidump and the memory was something I noticed.

Hardware can fail in a short period, medium and long period, it's something inevitable.
The current issue is that you're running memory with 2 different brands that aren't seated in a way the motherboard supports. Different brands have different spec designs which could contribute to the problem.

 

[andres_florio]

It's merely a suggestion, I can't pinpoint the exact cause with a single minidump and the memory was something I noticed.

Hardware can fail in a short period, medium and long period, it's something inevitable.
The current issue is that you're running memory with 2 different brands that aren't seated in a way the motherboard supports. Different brands have different spec designs which could contribute to the problem.

Ok. I'll remove the two Hyper Blue and leave two Corsair I got.

 

[andres_florio]

No trouble starting the pc so far. But I'd like to keep this thread open for a few more tests (if am allowed).

 

[andres_florio]

I'd like to close this thread as Solved.
Thanks.

 

[andres_florio]

It happened again.

 

[axe0axe0]

Follow https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.html, upload the zip to google drive and post a share link.

 

[andres_florio]

Follow https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/68-blue-screen-of-death-bsod-posting-instructions-windows-10-8-1-8-7-vista.html, upload the zip to google drive and post a share link.

It's been an hour SysnativeBSODCollection is stuck on "Waiting for SystemInfo".

"The "waiting for systeminfo" never-ending messages apparently has to do with the WERCON section of msinfo32 and affects <1% of users.

In the future, you can just kill the app and zip up the output folder per the BSOD Posting instructions."

 

[axe0axe0]

Kill the msinfo process and upload everything else.