Windows 10: Identifying driver causing BSOD

Discus and support Identifying driver causing BSOD in Windows 10 BSOD Crashes and Debugging to solve the problem; My laptop suddenly went into BSOD with the error IRQL_NOTLESS_OR_EQUAL. I tried using a bsod viewer to identify the driver but it just states... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by SilentstormSP, Jun 9, 2019.

  1. Identifying driver causing BSOD


    My laptop suddenly went into BSOD with the error IRQL_NOTLESS_OR_EQUAL. I tried using a bsod viewer to identify the driver but it just states ntoskrnl.exe. I have the dump files available, will it be helpful in identifying the driver that is causing this issue?

    :)
     
    SilentstormSP, Jun 9, 2019
    #1
  2. zbook Win User

    BSOD when updating W10 Insider Preview (installation)


    The BSOD minidump did not display a definitive misbehaving driver.
    All of the BSOD have been C2 Bad pool caller.
    The suggested steps for finding cause and effect are RAM testing with Memtest86+ version 5.01 and Windows driver verifier.
    If the Memtest86+ version 5.01 displays malfunctioning RAM / DIMM /MB then the troubleshooting will be completed once the hardware component is identified. If the Memtest86+ version 5.01 is negative then the next step would be windows driver verifier.
    If you prefer a clean install that is another option if hardware is ruled out.

    The memory dump will take a while to download. So it will be troubleshooted later today.
     
    zbook, Jun 9, 2019
    #2
  3. BSOD caused by driver hal.dll

    Facing frequent BSOD with error hal.dll and unable to identify the exact root cause.
     
    aibadahmed, Jun 9, 2019
    #3
  4. Rey Cam Win User

    Identifying driver causing BSOD

    Ntoskrl.exe Bsod

    Hi,

    Looking at the facts and your considerations;

    • This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    • A third party driver was identified as the probable root cause of this system error.

    Doing basic troubleshooting steps to fix the BSOD issue might work. Please check
    Troubleshoot blue screen errors. Kindly choose the appropriate radio button as to when did the error occurred
    and follow the troubleshooting steps on the dropdowns.

    Let us know if any of the solutions provided worked for you.
     
    Rey Cam, Jun 9, 2019
    #4
Thema:

Identifying driver causing BSOD

Loading...
  1. Identifying driver causing BSOD - Similar Threads - Identifying driver causing

  2. Need help identifying cause of BSOD. Information available.

    in Windows 10 BSOD Crashes and Debugging
    Need help identifying cause of BSOD. Information available.: Hello there, I've encountered a BSOD DPC_WATCHDOG_VIOLATION and would like to know the cause of it. I have the the dump information available to share if anyone could spare some time to have a look please? Kind Regards,...
  3. Experiencing reboot loop, BSOD, cannot identify the cause.

    in Windows 10 Drivers and Hardware
    Experiencing reboot loop, BSOD, cannot identify the cause.: Hello, i am having an issue with my PC and after doing many google searches my self I am at a loss, i cannot figure out the issue. I have several problems, they are: - When i boot the PC, it appears windows boots twice before going to the login screen - Once i am logged...
  4. Frequent Crashes/BSODs With No Identifiable Pattern or Cause

    in Windows 10 BSOD Crashes and Debugging
    Frequent Crashes/BSODs With No Identifiable Pattern or Cause: The computer I'm using now is the first one I ever built - I completed it about two years ago. For many months now I've had frequent crashes with no identifiable cause. There doesn't seem to be a correlation between RAM-intensive activities and crashes. Sometimes I'll only...
  5. BSOD Caused by Driver hal.dll

    in Windows 10 BSOD Crashes and Debugging
    BSOD Caused by Driver hal.dll: Hello, Last night I had a BSOD so I took a look at the minidump using BlueScreenView and this is what was highlighted. hal.dll hal.dll+47ff8 fffff806`7b4b6000fffff806`7b559000 0x000a3000 0x0f8ecc7c ntoskrnl.exe ntoskrnl.exe+463d00 fffff806`7aa00000...
  6. Help with identifying cause of BSODs - dumps included

    in Windows 10 BSOD Crashes and Debugging
    Help with identifying cause of BSODs - dumps included: These are my memory dumps just from yesterday. Can you please help me identify the cause of these? https://drive.google.com/open?id=1MURuPWp8c4ZT9Na6THI4Rccn-E7UV0hg https://drive.google.com/open?id=1PeLvOhfQh_OLTHr2DeLfloPDhNaioOi5...
  7. BSOD caused by driver atikmdag.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by driver atikmdag.sys: Got a bsod yesterday caused by driver atikmdag.sys. I recently changed graphic driver and don't know what it is that's causing this. Followed the instructions and here is the output-zip-file. bsod--(2019-12-15_14-16-37).zip 146494
  8. BSOD caused by driver atikmdag.sys

    in Windows 10 Drivers and Hardware
    BSOD caused by driver atikmdag.sys: I'm running with a new driver for my Radeon graphic card. 19.12.2 which is recommended from AMD. After install all went fine and graphic bugs in games were gone with new driver but after some days playing I got bluescreen all of the sudden....
  9. BSOD, cannot identify cause(s)

    in Windows 10 BSOD Crashes and Debugging
    BSOD, cannot identify cause(s): I’ve been struggling with multiple BSOD crashes with my HP laptop, but I cannot identify the cause. I do not know how to decipher the stop code because it looks like an actual barcode. Pls assistance would be much appreciated 134025
  10. Driver causing BSOD

    in Windows 10 BSOD Crashes and Debugging
    Driver causing BSOD: Im not sure what driver is causing it, so I was hoping someone could take a look at my dump files who knows what they are looking at. My specs are included in the folder. Thanks in advance for any help....