Windows 10: BSOD hall.dll

Hi! Could you help me find the cause of this BSOD? It is completely random, not in a specific situation. I already checked the SSD, did a RAM test no error and reinstalled drivers from the video card. I also ran the "Driver Verifier" utility, but it seems to me it was not effective. I haven't done a Windows format yet, but I would like to leave it for the latter. A few days ago before the BSODs occurred I noticed that I had an update to the May version of Windows, and yet it was not downloaded because it apparently failed. I don't know if it will have something to do with it, but it is a fact. I don't know where to load the minidumps!

:)

 

randomly BSOD occurs, HALL.dll error

Goodday all,

One of our Windows 10 users is getting a BSOD regularly (like once a week), I checked it out with Bluescreenview and it shows that the HALL.DLL is giving the bluescreen error.

After today's BSOD, I tried to do sfc.exe /scannow and when it reached 100% validating it got another bluescreen.

Is there anyone who can read out the .dmp file? I added two of them as attachment.

The user only using Outlook and Internet Explorer for some webapplications.

Thanks in advance

 

BSOD - HALL.DLL & NTOSKRNL.exe Windows 10 64 bit

Thanks for this list. I'll update/remove the drivers and check all the other things you've listed. Will update when I've done this and tested the system for BSOD. Thanks

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.