Windows 7 BSOD Hardware Abstraction Layer DLL - help?

[Guest]

Hi, I'm trying to figure out why my windows 7 build is BSOD very often and unprovoked. Here's the message i get read by the program WhoCrashed...

crash dump file: C:\Windows\Minidump\030617-8860-02.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x4, 0xFFFFFA8019EDA038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


build details:
http://valid.x86.fr/6vrmy5

I did nothing of late to this PC. I did clean and reapply heatsink. No difference.

 

[Rhinofart]

Have you used the program called BluescreenView to investigate your dump file? You haven't moved from a single to multi-core system have you? Normally when the core system files in windows get corrupted, it's due to RAM corruption, or HD corruption. Make sure your thermals are OK, perform a quick backup of anything super important, and run some HD and RAM diagnostics. Get a test app from your HD manufacturer, and also get a bootable CD of MemTestx86 and test the crap out of your RAM.
Does it dump that error every single time you boot windows?

 

[Guest]

Have you used the program called BluescreenView to investigate your dump file? You haven't moved from a single to multi-core system have you? Normally when the core system files in windows get corrupted, it's due to RAM corruption, or HD corruption. Make sure your thermals are OK, perform a quick backup of anything super important, and run some HD and RAM diagnostics. Get a test app from your HD manufacturer, and also get a bootable CD of MemTestx86 and test the crap out of your RAM.
Does it dump that error every single time you boot windows?

I have a 256GB samsung 950 pro SSD. What should I run for HD diagnosis?

Here's a dump from blueescreenview...

==================================================
Dump File : 030617-9391-01.dmp
Crash Time : 3/6/2017 5:46:21 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`19b1e038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030617-9391-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 279,032
Dump File Time : 3/6/2017 5:54:28 PM
==================================================

==================================================
Dump File : 030617-9016-01.dmp
Crash Time : 3/6/2017 8:11:10 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`19b1c8d8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030617-9016-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 279,032
Dump File Time : 3/6/2017 8:12:33 PM
==================================================

==================================================
Dump File : 030617-8970-01.dmp
Crash Time : 3/6/2017 6:41:21 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`19afb8d8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030617-8970-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 279,032
Dump File Time : 3/6/2017 6:42:38 PM
==================================================

==================================================
Dump File : 030617-8938-01.dmp
Crash Time : 3/6/2017 6:06:38 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`19afc038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030617-8938-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 279,032
Dump File Time : 3/6/2017 6:07:53 PM
==================================================

==================================================
Dump File : 030617-8860-02.dmp
Crash Time : 3/6/2017 7:14:44 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`19eda038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030617-8860-02.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 279,032
Dump File Time : 3/6/2017 7:16:04 PM
==================================================

==================================================
Dump File : 030617-8860-01.dmp
Crash Time : 3/6/2017 6:15:59 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`19a1b038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030617-8860-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 279,032
Dump File Time : 3/6/2017 6:17:15 PM
==================================================

==================================================
Dump File : 030617-8580-01.dmp
Crash Time : 3/6/2017 7:20:27 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`19afc038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030617-8580-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 279,032
Dump File Time : 3/6/2017 7:21:34 AM
==================================================

==================================================
Dump File : 030517-9313-01.dmp
Crash Time : 3/5/2017 5:28:56 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`19b1b038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030517-9313-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 3/5/2017 5:31:49 PM
==================================================

==================================================
Dump File : 030517-8954-01.dmp
Crash Time : 3/5/2017 6:11:01 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000004
Parameter 2 : fffffa80`19b1a038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+70400
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\030517-8954-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 279,032
Dump File Time : 3/5/2017 6:12:22 PM
==================================================

 

[Rhinofart]

That's an aweful lot of dumps going on.
Are you able to startup in Safe Mode with command prompt, and run the following command?
sfc /scannow /offbootdir=d:\ offwindir=d:\windows
That should scan all your core windows files, and replace them with the ones locked up in secure location within the windows directory structure.
Also, make sure you run the Memtest, and HD diagnostics. There is something starting to corrupt your files on the drive.

 

[Guest]

That's an aweful lot of dumps going on.
Are you able to startup in Safe Mode with command prompt, and run the following command?
sfc /scannow /offbootdir=d:\ offwindir=d:\windows
That should scan all your core windows files, and replace them with the ones locked up in secure location within the windows directory structure.
Also, make sure you run the Memtest, and HD diagnostics. There is something starting to corrupt your files on the drive.

SFC comes out clean, says integrity verified. Running memtest86 boot cd now. Does memtest ever finish? There is no bootable Samsung ssd diagnostics. They do have a windows version.

Update: 9 hours of memtest finds no errors.

 

[Rhinofart]

You will see a "Loop Count" or something similar in Memtest. It will keep going if you let it. OK, next up, you should look into the Microsoft Sysinternals Tools. Namely Autoruns, Proccess Monitor, and Process Explorer. Setup your Symbols cache, and just let ProcMon run (as administrator) for a while, and try to re-create your error soon after it's been running. Then after the crash, you can open up ProcMon, stop the capture, and then sift through the log file and track down exactly what is causing your woes.
If you go to this site: https://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-Building-your-USB-thumbdrive and go through the process, it will help you along your troubleshooting path. There are other "versions" of this video for the different versions of windows. These videos are fantastic for helping people start out with troubleshooting, and can help you get right into the thick of it with regards to figuring out how and why something is crashing. I use these tools every day for work, and the guys in the video are actual Microsoft techs who write some of the tools, but also are Microsoft PFEs.

 

[Guest]

You will see a "Loop Count" or something similar in Memtest. It will keep going if you let it. OK, next up, you should look into the Microsoft Sysinternals Tools. Namely Autoruns, Proccess Monitor, and Process Explorer. Setup your Symbols cache, and just let ProcMon run (as administrator) for a while, and try to re-create your error soon after it's been running. Then after the crash, you can open up ProcMon, stop the capture, and then sift through the log file and track down exactly what is causing your woes.
If you go to this site: https://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-Building-your-USB-thumbdrive and go through the process, it will help you along your troubleshooting path. There are other "versions" of this video for the different versions of windows. These videos are fantastic for helping people start out with troubleshooting, and can help you get right into the thick of it with regards to figuring out how and why something is crashing. I use these tools every day for work, and the guys in the video are actual Microsoft techs who write some of the tools, but also are Microsoft PFEs.

Sorry I'm lost on this one. Attached are my dumps in case that helps. Thanks. https://dl.dropboxusercontent.com/u/2544555/MATT-PC-Tue_03_07_2017_131606_35.zip