BSOD caused by hal.dll and ntoskernal.exe

cunuck32

Commendable
Aug 1, 2016
4
0
1,510
Just today I received two BSODs, both were caused by hal.dll and ntoskernal.exe, and BlueScreenViewer showed these crash logs. The first apparently happened this morning when i wasn't using it, and the second while i was in the middle of a game.

123016-18656-01.dmp
12/30/2016 1:16:47 AM
IRQL_NOT_LESS_OR_EQUAL
0x0000000a
ffffa58a`9f72c000
00000000`000000ff 00000000`000000a6
fffff803`37c50768
hal.dll
hal.dll+1aaa8 Hardware Abstraction Layer DLL
Microsoft® Windows® Operating System
Microsoft Corporation
10.0.14393.206 (rs1_release.160915-0644)
x64

hal.dll hal.dll+1aaa8 fffff803`37812000 fffff803`37887000 0x00075000 0x57dac91a 9/15/2016 11:15:22 AM Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 10.0.14393.206 (rs1_release.160915-0644) Microsoft Corporation C:\Windows\system32\hal.dll

ntoskrnl.exe ntoskrnl.exe+155829 fffff803`37887000 fffff803`380a7000 0x00820000 0x584a77f6 12/9/2016 4:23:02 AM Microsoft® Windows® Operating System NT Kernel & System 10.0.14393.576 (rs1_release_inmarket.161208-2252) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe




123016-16359-01.dmp
12/30/2016 11:39:41 AM
PFN_LIST_CORRUPT
0x0000004e
00000000`00000002
00000000`0003f063
00000000`0022efff
00000000`00000001
hal.dll
hal.dll+2277
Hardware Abstraction Layer DLL
Microsoft® Windows® Operating System
Microsoft Corporation
10.0.14393.206 (rs1_release.160915-0644)
x64
ntoskrnl.exe+14a6f0
C:\Windows\Minidump\123016-16359-01.dmp

hal.dll hal.dll+2277 fffff803`88233000 fffff803`882a8000 0x00075000 0x57dac91a 9/15/2016 11:15:22 AM Microsoft® Windows® Operating System Hardware Abstraction Layer DLL 10.0.14393.206 (rs1_release.160915-0644) Microsoft Corporation C:\Windows\system32\hal.dll

ntoskrnl.exe ntoskrnl.exe+1a6a11 fffff803`87a13000 fffff803`88233000 0x00820000 0x584a77f6 12/9/2016 4:23:02 AM Microsoft® Windows® Operating System NT Kernel & System 10.0.14393.576 (rs1_release_inmarket.161208-2252) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

My specs are:
CPU: AMD FX(tm)-6300 Six Core Processor 3.50GZ
RAM: Ares 2x4gb DDR3 RAM sticks
GPU: Radeon R9 200 Series
HDD: Seagate Barracuda ST100dM003 1TB
MOTHERBOARD: Gigabyte 78LMT-USB3 Socket AM3
BIOS: Award Modular BIOS v6.00PG
PSU: EVGA 500W Bronze
OS: Microsoft Windows 10 (build 14393), 64-bit


I think I have all the latest drivers, but could it be a hardware problem? I've had troubles in the past with my build and had to get a replacement hard drive, as well as reinstall Windows 10 many times. The most recent one was back in August, I reinstalled windows 10 form a USB drive and installed all the drivers form the disks my parts came with, I had also had computer get just an empty red screen, as well as completely freeze up while playing two separate games but they seemed to have stopped after i updated my graphics driver. Any help would be appreciated, thanks.
 
Solution
second memory dump showed 18 corruptions of the windows kernel.
It could be malware or a timing problem in the memory I can not tell.
there looks like there were 3 other corruptions in the kernel memory data
I would suspect malware but can not rule out BIOS memory timing or physical memory problems. I would run memtest on its own boot image as a first test.
if it does not find a problem then boot windows.
start cmd.exe as an admin and
run
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth
and do a Malwarebytes scan.
I would also remove the old drivers below and update the motherboard drivers from the motherboard vendor. if your BIOS is out of date you want to update it also. The drivers that windows 10 installs will...

Colif

Win 11 Master
Moderator
They both look like driver errors but its hiding the identity of them behind windows
ntoskrnl = new technology operating system kernel - brains of wndows, one of its jobs is dealing with driver requests
Hal = Hardware abstraction layer - part of windows that sits between hardware and windows

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
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
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)
 

cunuck32

Commendable
Aug 1, 2016
4
0
1,510
 
second memory dump showed 18 corruptions of the windows kernel.
It could be malware or a timing problem in the memory I can not tell.
there looks like there were 3 other corruptions in the kernel memory data
I would suspect malware but can not rule out BIOS memory timing or physical memory problems. I would run memtest on its own boot image as a first test.
if it does not find a problem then boot windows.
start cmd.exe as an admin and
run
sfc.exe /scannow
dism.exe /online /cleanup-image /restorehealth
and do a Malwarebytes scan.
I would also remove the old drivers below and update the motherboard drivers from the motherboard vendor. if your BIOS is out of date you want to update it also. The drivers that windows 10 installs will assume that your BIOS is up to date. (bios and certain drivers are a matched set)

-------
You are going to want to update your BIOS and run memtest to confirm your memory subsystem is working correctly.


debugger indicates that you windows nt kernel has a memory corruption

4 errors : !nt (fffff80387ab46eb-fffff80387b2104e)
fffff80387ab46e0 c2 48 83 cf 21 48 ba 00 00 00 40 *fa *f4 ff ff 48 .H..!H....@....H
...
fffff80387b21040 8d 34 5b 48 c1 e6 04 48 b8 00 00 00 00 *00 *84 ff .4[H...H........

I can check the second memory dump to see if it is corrupted there also.
looks like it does not like your win32k driver either.

old drivers installed:
(I would remove this old driver)
Kaspersky Lower Mouse Device Filter driver
\SystemRoot\System32\drivers\ElcMouLFlt.sys Mon Oct 4 16:30:57 2010
\SystemRoot\System32\drivers\ElcMouUFlt.sys Mon Nov 29 21:42:46 2010

(look at your motherboard vendor website for updates)
\SystemRoot\System32\drivers\Rt630x64.sys Tue Jun 17 04:56:46 2014
\SystemRoot\system32\drivers\RTKVHD64.sys Tue Jun 10 05:20:20 2014
 
Solution

Rhinofart

Distinguished
Jan 30, 2006
977
0
19,360
Did you happen to change processors at all? The amount of Cores change from the time you installed windows to when you started getting the BSODs? Usually you only get HAL errors when going from a Single Proc to Multiple Proc/Core system when windows was installed with the single core HAL.
 

Enferlain

Distinguished
Oct 30, 2014
43
2
18,545
Bit of a necro but since the thread didn't have a resolution I'll share my experience. I had the same bsod as OP, and I have a memory overclock in effect, so I'd say it's likely you encounter these if you have your timings a bit too tight.
 

Colif

Win 11 Master
Moderator
bit of a necro? post is 2 years old...
and post number 4 marked as solution so there is that as well.

irq errors can be all sorts of things, ram timings might be one as ram is often to blame for them... as are drivers.