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 on identifying the cause of BSOD

    in Windows 10 BSOD Crashes and Debugging
    Need help on identifying the cause of BSOD: HelloI've been having this BSOD issue for 3 weeks now and still can't figure out what's causing it.I already bought brand new RAM for this cuz I thought it was the RAM after testing some of my parts using my friend's PC.I attached the latest BSOD log, I'm not sure how to...
  3. Identifying the cause of BSOD and dmp files.

    in Windows 10 Gaming
    Identifying the cause of BSOD and dmp files.: I have been getting the BSOD on my PC every 15~20 minutes and wanted to see if the dmp files could help identify what is causing it.Here is the link to the dmp files: https://1drv.ms/u/s!AlzMBUnTtl9JjE9BM0vPB5ztnUYQ?e=NAhnA1Thank you in advance, I have a suspect feeling that...
  4. How to identify which driver is causing BSOD

    in Windows 10 Gaming
    How to identify which driver is causing BSOD: HiI have trouble almost a year now with random BSOD on my ROG Laptop. Send it back to service, they returned it with conclusion - no hardware issues.It has to be a buggy driver - that's what WhoCrashed always suggestsBut I can't identify which one.I'm constantly updating....
  5. How to identify which driver is causing BSOD

    in Windows 10 Software and Apps
    How to identify which driver is causing BSOD: HiI have trouble almost a year now with random BSOD on my ROG Laptop. Send it back to service, they returned it with conclusion - no hardware issues.It has to be a buggy driver - that's what WhoCrashed always suggestsBut I can't identify which one.I'm constantly updating....
  6. BSOD cannot identify cause

    in Windows 10 BSOD Crashes and Debugging
    BSOD cannot identify cause: Hi, for about a month I have been having frequent BSOD on my Windows 10 PC. I have updated all my drivers, ensured there are no viruses on my computer, and run windows diagnostics. I suspect it might be one of my usb devices but I can't identify what it is.These are the error...
  7. how to identify the driver causing 0xC1900101

    in Windows 10 Installation and Upgrade
    how to identify the driver causing 0xC1900101: tried twice to go from 1909 to 2004 then twice to go from 1919 to 20H2 on an HP255 G6, fails with every time most often on boot the screen goes nuts - looks like the result you get when you try to use an unsupported resolution setting - and I have to hold the power key down...
  8. BSOD caused by drivers supposedly, unable to identify which in particular.

    in Windows 10 Drivers and Hardware
    BSOD caused by drivers supposedly, unable to identify which in particular.: Hello, I followed the driver verifier wiki and my latest dump from the driver verifier is included. Any other advice is appreciated, from the tools I have used it says the issue is ntoskrnl.sys, which is the windows kernel which is most likely not the case. Any help?...
  9. bsod, cant identify whats causing it

    in Windows 10 Ask Insider
    bsod, cant identify whats causing it: mini dump files https://1drv.ms/u/s!Ai2gUp9VATsDg3u66UZYYNJXGQ85?e=PKhtIm (few of them are from when I ran driver verifier) I recently changed my pcs motherboard PSU and ram and since then these errors have been happening, from what i found out online, these errors are...
  10. bsod, cant identify whats causing it

    in Windows 10 BSOD Crashes and Debugging
    bsod, cant identify whats causing it: mini dump files https://1drv.ms/u/s!Ai2gUp9VATsDg3u66UZYYNJXGQ85?e=PKhtIm few of them are from when I ran driver verifier I recently changed my pcs motherboard PSU and ram and since then these errors have been happening, from what i found out online, these errors are...