BSOD hal.dll ntoskrnl.exe

Vladimir Mikhailov 21 Reputation points

today i received BSOD on windows 2019 (build 17763.1999). the cause of bsod is hal.dll. bluescreenview showed me:

is this software or hardware problems ? how can i solve it?
thank's in advanced

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,444 questions
0 comments No comments
{count} votes

Accepted answer
  1. Michael Taylor 47,716 Reputation points

    Assumption: Your a developer who understand how to debug. If you're a consumer then all I can say is it is probably a bad driver but without looking at the dump there is no way to tell.

    The HAL is for hardware interaction. So it is either a hardware issue or a driver issue. Unfortunately given just that screenshot we have no way of
    knowing. Given the bug check code it seems to be this which leads me to believe it is a bad driver. If you load this up in windbg then it should show you the module and call stack which will quickly narrow down the driver that is potentially causing the issue.

    Of course if this machine was fine for a while and you updated something and things started breaking then that is where I'd start.

2 additional answers

Sort by: Most helpful
  1. Docs 15,141 Reputation points

    Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

    If the server is not able to run the V2 log collector then run the DM log collector.

    The V2 log collector will collect more useful log files for troubleshooting.


    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post

    0 comments No comments

  2. Limitless Technology 39,341 Reputation points

    Hi there,

    These crashes are related to memory corruption and are probably caused by a driver. You can follow these below articles to find the driver and memory leak which is causing you this BSOD.

    Driver verifier is a utility built into the OS that will often find the driver/drivers that are the underlying cause of BSOD/Crashes.

    Driver Verifier-- tracking down a mis-behaving driver.

    Memtest is easy to use and is an accurate test of your computer memory. It can tell you if your memory is bad, a motherboard slot is bad, etc.

    Memory problems.

    Once you find the faulty drivers you can then update or reinstall the specific driver to rectify this issue.


    --If the reply is helpful, please Upvote and Accept it as an answer–