Windows 10: BSOD on hal.dll+18f8

Hey


I've got Windows 10 10.0.18363 Build 18363.

Every once in a while i get a BSOD, i've updated all the drivers, ran the driver verifier and this still occur.

Below are the latest minidumps:

https://1drv.ms/u/s!Aj_xrBd5HaqSiREqPQ5wNNF6SeAM?e=srOBUv


Is anyone able to understand those?


Thanks

Yahav

:)

 

Windows 10 BSOD - hal.dll+18f8 (mini dump uploaded)

I've been getting random BSOD lately. The most common BSOD pattern is on a cold start (computer turned off overnight and then booted up in the morning) as soon as I get to desktop it BSOD. After that it works fine rest of the day. Other times it BSOD is
when the computer is idle usually. I can't recall a time that is actually BSOD while I was gaming.

I researched hal.dll+18f8 and I found someone else here with same issue. His issue seemed to be resovled ever since he "changed the storage controller to standard".

I have two drivers showing up for my NVMe. They are "Microsoft Storage Spaces Controller" & "Samsung NVMe Controller". I do recall many months ago installed the Samsung as I heard it was "better". I tried to uninstall it today (created a restore point first).
When I uninstalled and windows did the restart it went into repair mode over and over. Since then I have used the restore point and here I am. The Microsoft storage driver does not have a uninstall option.

Here is mini dump on OneDrive:

51220.dmp

Any help would be appreciated.

 

BSOD caused by driver hal.dll

Facing frequent BSOD with error hal.dll and unable to identify the exact root cause.

 

[Win 10] [BSOD] hal.dll crash

Hi All,

I think I've got issues with hal.dll (specifically hal.dll+4e490) that's causing BSODs.

Had 4 BSODs with bug check code 133 within the past 3 months.

I've had a look at the minidumps in BlueScreenView - all lead to the same stack trace before crash of:

hal.dll hal.dll+4e490

ntoskrnl.exe ntoskrnl.exe+xxxxx

I'm not sure what I'm doing with WinDbg (and therefore haven't got symbols set up, etc), however WinDbg suggested that the cause was ntoskrnl.exe

Minidumps:

1) 012517-11421-01.zip

2) 020117-12390-01.zip

3) 101516-6437-01.zip

4) 112316-7875-01.zip

Any help or pointers would be really appreciated.

If there's any extra info you require, I'll provide it ASAP.

Thank you in advance!

***Post moved by the moderator to the appropriate forum category.***