Windows 10: How to identify which driver is causing BSOD

Discus and support How to identify which driver is causing BSOD in Windows 10 Software and Apps to solve the problem; 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... Discussion in 'Windows 10 Software and Apps' started by mironkrumov, Nov 8, 2021.

  1. MIRONKRUMOV
    mironkrumov Win User

    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. Please help me. These are my settings and the most recent dmp files:https://1drv.ms/u/s!Ags1BdQ1srBOnckifmUOeu-RLQRSag?e=tgtjaqThanks

    :)
     
    mironkrumov, Nov 8, 2021
    #1
  2. SILENTSTORMSP
    SilentstormSP Win User

    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, Nov 8, 2021
    #2
  3. ZBOOK
    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, Nov 8, 2021
    #3
  4. GOLDEN
    Golden Win User

    How to identify which driver is causing BSOD

    BSOD caused by driver atikmdag.sys

    Could be another driver causing the issue.

    Suggest you follow this and post in the BSOD section of the forum.

    BSOD - Posting Instructions
     
    Golden, Nov 8, 2021
    #4
Thema:

How to identify which driver is causing BSOD

Loading...

  1. How to identify which driver is causing BSOD - Similar Threads - identify driver causing

  2. Identify driver causing BSOD

    in Windows 10 Gaming
    Identify driver causing BSOD: I receive a bluescreen on reboot, it occurs twice and then when I go to the troubleshooter and select normal reboot, it starts fine. I have run windbg on the .dmp file and it appears to be a driver issue, but I cannot identify which one. Can I upload the .dmp file to be...

  3. Identify driver causing BSOD

    in Windows 10 Software and Apps
    Identify driver causing BSOD: I receive a bluescreen on reboot, it occurs twice and then when I go to the troubleshooter and select normal reboot, it starts fine. I have run windbg on the .dmp file and it appears to be a driver issue, but I cannot identify which one. Can I upload the .dmp file to be...

  4. Driver verifier confirmed a driver is causing BSOD. But which one?

    in Windows 10 Gaming
    Driver verifier confirmed a driver is causing BSOD. But which one?: My computer has been getting BSOD errors, typically with the message IRQL_NOT_LESS_OR_EQUAL. I tried several things such as scandisk and going back to old restore points, but nothing worked. Eventually I did a full re-install of Windows 10, and the errors stopped for a few...

  5. 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....

  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. how to identify which driver should be installed

    in Windows 10 Drivers and Hardware
    how to identify which driver should be installed: Previously I have taken backup of my all drivers by Code: dism /online /export-driver /destination:C:\drivers-backup They were working fine in Windows 10 Home Edition. and restored them as shown here. I now thought I should upgrade things to latest drivers.So I downloaded...

  10. Identifying driver causing BSOD

    in Windows 10 BSOD Crashes and Debugging
    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?...