Windows 10: Hard Reboot - Ran Driver Verifier & Need Help Understanding Offending Driver

Discus and support Hard Reboot - Ran Driver Verifier & Need Help Understanding Offending Driver in Windows 10 Drivers and Hardware to solve the problem; Hello, I've been experiencing hard reboots when my monitor changes back and forth from HDR - SDR and between refresh rates. I followed the process... Discussion in 'Windows 10 Drivers and Hardware' started by p2im0, Apr 17, 2021.

  1. p2im0 Win User

    Hard Reboot - Ran Driver Verifier & Need Help Understanding Offending Driver


    Hello,


    I've been experiencing hard reboots when my monitor changes back and forth from HDR - SDR and between refresh rates. I followed the process for tracking down a mis-behaving drive with driver verifier and could use help reading/understanding what's causing the issues.


    First off, I noticed I was getting "BugCheck" errors in the System log after these hard reboots, an example below of one that occurred right before I setup driver verifier.


    Log Name: System

    Source: Microsoft-Windows-WER-SystemErrorReporting

    Date: 4/17/2021 1:24:01 AM

    Event ID: 1001

    Task Category: None

    Level: Error

    Keywords: Classic

    User: N/A

    Computer: DESKTOP-J7S4R81

    Description:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 0xffffe70dd235a960, 0x0000000000000005, 0x0000000000000000, 0xfffff8036d7bbbc8. A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 74b2c573-9141-4adf-9775-3b5306a6cc3a.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />

    <EventID Qualifiers="16384">1001</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2021-04-17T05:24:01.2585914Z" />

    <EventRecordID>135908</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>System</Channel>

    <Computer>DESKTOP-J7S4R81</Computer>

    <Security />

    </System>

    <EventData>

    <Data Name="param1">0x000000d1 0xffffe70dd235a960, 0x0000000000000005, 0x0000000000000000, 0xfffff8036d7bbbc8</Data>

    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>

    <Data Name="param3">74b2c573-9141-4adf-9775-3b5306a6cc3a</Data>

    </EventData>

    </Event>


    I ran the driver verifier, changed my refresh rate a bunch and back and forth to HDR SDR, etc and got the machine to crash. Here's the bugcheck error log after I triggered the crash:


    Log Name: System

    Source: Microsoft-Windows-WER-SystemErrorReporting

    Date: 4/17/2021 1:58:11 AM

    Event ID: 1001

    Task Category: None

    Level: Error

    Keywords: Classic

    User: N/A

    Computer: DESKTOP-J7S4R81

    Description:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c4 0x0000000000002000, 0xfffff80c38e42b0b, 0x0000000000000000, 0x0000000064726f4e. A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: c50f524f-ed0e-4001-a822-e1a89cb61f1f.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    <System>

    <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />

    <EventID Qualifiers="16384">1001</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2021-04-17T05:58:11.9109161Z" />

    <EventRecordID>135976</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>System</Channel>

    <Computer>DESKTOP-J7S4R81</Computer>

    <Security />

    </System>

    <EventData>

    <Data Name="param1">0x000000c4 0x0000000000002000, 0xfffff80c38e42b0b, 0x0000000000000000, 0x0000000064726f4e</Data>

    <Data Name="param2">C:\Windows\MEMORY.DMP</Data>

    <Data Name="param3">c50f524f-ed0e-4001-a822-e1a89cb61f1f</Data>

    </EventData>

    </Event>


    I then was stuck in a BSOD loop because of driver verifier. Rebooted to safe mode via Win10 USB media, did a system restore, and here I am.


    Here are the minidump and memory dump files as well as error text RAR'd up on my OneDrive total size 25MB - Dump Files issue_2020.04.17.rar


    Can someone take a look and help me understand the offending driver?


    The issue may have been fixed by the system restore, but I want to be sure as I suspect my monitor is contributing to these issues.


    Build info via Speccy

    :)
     
    p2im0, Apr 17, 2021
    #1
  2. Kebbiee Win User

    I ran Driver Verifier but I don't know which driver is casuing BSOD. Please help!

    I ran Driver Verifier to check which driver is causing my computer to malfunction. When I reboot my computer to activate Driver Verifier, it just blue screened with the stop code, DRIVER_VERIFIER_DETECTED_VIOLATION. It repeated until the system tried automatic
    repair. I booted into safe mode and shut down Driver Verifier. Still I don't know which driver is causing my computer to malfunction. Please help!
     
    Kebbiee, Apr 17, 2021
    #2
  3. NIULAND Win User
    Just ran Driver Verifier. Need help with results.

    I've been having issues with my computer freezing/crashing while playing demanding video games. I ran SFC and DISM both said nothing was wrong. So I ran the verifier, followed the instructions from here: Driver Verifier-- tracking down a mis-behaving driver.

    I have the "three important files" here: Wyman_Crash_info.rar

    It contains the minidump from the verifier, my MSinfo, and my computer specs.

    I wasn't sure what to do after that step, so I'm posting it here. Can someone make out what my computer's driver issue is?
     
    NIULAND, Apr 17, 2021
    #3
  4. Peaj Win User

    Hard Reboot - Ran Driver Verifier & Need Help Understanding Offending Driver

    Driver Verifier BSOD on Start Up DRIVER_VERIFIER_DETECTED_VIOLATION

    Update

    So the PC went down the same road, became unusable and I wiped it.

    Clean install number 6. Clean install 5 was to test if Windows 7 was as unstable as the Windows 10 installs. It was - this made me think it may be a hardware problem or just a really poorly supported motherboard.

    Clean install 6 - this time I am being methodical in my steps and testing every step of the way. PC specs are still the same other than a new stick of DDR4. What I have done so far:

    • Bought/installed a new stick of DDR4 for testing.
    • Followed Gerrys advice and installed latest BIOS, even though it is in beta it is listed as a stable release.
    • Installed Windows 10
    • Installed Chipset Drivers from Gigabyte website.
    • Installed latest Ethernet drivers (20_7) from Intel website.
    • I have made sure to not connect the PC to the internet and have left the ethernet cable unplugged.
    • Ran Verifier, rebooted with no problems, not that I was expecting there to be any.
    • Installed latest drivers from Nvidia
    • ran Verifier, rebooted, BSOD "DRIVER_VERIFIER_DETECTED_VIOLATION"
    • booted into safe mode, reset Verifier, rebooted.

    So this is where I am at. A completely clean install, and what seems to be problems with Nvidia drivers.

    Minidump link if someone could have a look. Minidump is 021216-2203-01

    https://onedrive.live.com/redir?resid=3789DDEF7B6D41D2!15823

    So I am not sure what this means. PC seems stable at the moment though there is hardly anything installed on it.

    Does Verifier reporting a problem mean that there is one? What should I do from here?
     
Thema:

Hard Reboot - Ran Driver Verifier & Need Help Understanding Offending Driver

Loading...
  1. Hard Reboot - Ran Driver Verifier & Need Help Understanding Offending Driver - Similar Threads - Hard Reboot Ran

  2. Help with Driver Verifier

    in Windows 10 Software and Apps
    Help with Driver Verifier: Hi,I am at an advanced stage of trying to find out why I am randomly, often, getting IRQL not less or equal than BSOD. I have been through so many checks, memory, storage etc. I was told it was my bluetooth drivers. Turned them off in device manager, replaced keyboard and...
  3. Help with Driver Verifier

    in Windows 10 Gaming
    Help with Driver Verifier: Hi,I am at an advanced stage of trying to find out why I am randomly, often, getting IRQL not less or equal than BSOD. I have been through so many checks, memory, storage etc. I was told it was my bluetooth drivers. Turned them off in device manager, replaced keyboard and...
  4. Need help with driver verifier dma violation

    in Windows 10 Gaming
    Need help with driver verifier dma violation: My son has the geo book 140 and has a bsod with driver verifier dma violation stop code and keeps cycling to black screen that says preparing automatic repair. Can anyone help with this as it isn’t giving me a single option to stop the cycle?...
  5. Need help with driver verifier dma violation

    in Windows 10 Software and Apps
    Need help with driver verifier dma violation: My son has the geo book 140 and has a bsod with driver verifier dma violation stop code and keeps cycling to black screen that says preparing automatic repair. Can anyone help with this as it isn’t giving me a single option to stop the cycle?...
  6. After attempting to fix consistent BSODs, I ran driver verifier and need help with what to...

    in Windows 10 Gaming
    After attempting to fix consistent BSODs, I ran driver verifier and need help with what to...: I ran bugcheck analysis from WinDbg, but now I'm not sure where to go now. Would greatly appreciate it if someone could help. Here is the bugcheck analysis copy and pasted. 0: kd> !analyze -v******************************************************************************** **...
  7. After attempting to fix consistent BSODs, I ran driver verifier and need help with what to...

    in Windows 10 Software and Apps
    After attempting to fix consistent BSODs, I ran driver verifier and need help with what to...: I ran bugcheck analysis from WinDbg, but now I'm not sure where to go now. Would greatly appreciate it if someone could help. Here is the bugcheck analysis copy and pasted. 0: kd> !analyze -v******************************************************************************** **...
  8. After attempting to fix consistent BSODs, I ran driver verifier and need help with what to...

    in Windows 10 BSOD Crashes and Debugging
    After attempting to fix consistent BSODs, I ran driver verifier and need help with what to...: I ran bugcheck analysis from WinDbg, but now I'm not sure where to go now. Would greatly appreciate it if someone could help. Here is the bugcheck analysis copy and pasted. 0: kd> !analyze -v******************************************************************************** **...
  9. Need help on driver verifier bsod

    in Windows 10 BSOD Crashes and Debugging
    Need help on driver verifier bsod: I had a bsod 0x1000007E and did the sfc /scannow and dism steps and ran chkdsk then memtest. Everything checks out so I tried running driver verifier and after logging in i got this bsod SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 0x1000007E. Could I please request assistance in...
  10. Figure out the offending driver

    in Windows 10 Drivers and Hardware
    Figure out the offending driver: On the ASRock machine in my specs, using Acronis True Image 2018, I get the following BSOD error when trying to back to one of the M.2 SSDs. Backing up to a traditional SATA 2.5" SSD works fine. "Driver IRQL not less or equal" Someone on the Acronis site, suggested I figure...