Using Driver Verifier to identify issues with Drivers

Page 5 of 7 FirstFirst ... 34567 LastLast

  1. Posts : 17
    Windows 7 Ultimate x64
       #41

    Vir Gnarus said:
    I'm not understanding why they're saying that. Driver Verifier is designed to cause BSODs by adding extra driver checks in Windows, making it more paranoid to possible bugs. The bugcheck code I see in that bluescreen snapshot you made does show a 0xC5 crash, which was made by Driver Verifier, meaning it found a driver doing something erroneous and it crashed the system in response. Often it may do this at startup when the driver loads because when the driver loads up it may already have a bug in the works, which DV will detect and respond. You'll want to go to the thread you made and post the resulting crashdumps from the crashes that DV made. Those DV-created crashdumps are more reliable than regular ones.
    Thank you for this, I showed ARC your post( he was the one saying I was doing it wrong) and he said "vir is always right" actually checked the crash dumps I had gotten from safe mode and within about 10 mins had found the problem! So thank you for your help!
      My Computer


  2. Posts : 8
    Windows 7 Ultimate x64
       #42

    6.1.7601.2.1.0.256.1 bsod


    Hi guys I got this dump files and I need help knowing what is causing my computer to randomly trow a BSOD and reboot. I just build a new computer and looks like some of my drivers are not happy I try reloading and updating some of them but not luck so far. I ran the driver verifier as suggested in this forum and I retrieve this dump files. I hope someone can help me with this issue. thanks.
    Using Driver Verifier to identify issues with Drivers Attached Files
      My Computer


  3. Posts : 1,314
    Windows 7 64-bit
       #43

    Hi there skip. Can you please start your own thread? This is more a request for help on an issue and not specifically using Driver Verifier. Plus you'll get more exposure if you make your own thread.
      My Computer


  4. Posts : 1,314
    Windows 7 64-bit
       #44

    Oops. That "intelligent" post I made earlier about IRP Logging being great but inaccessible except in live kernel debugging sessions? Scratch that. It's accessible in crashdumps, but only on kernel dumps or larger. Use !verifier 0x100 to access the logs. Remember that it only shows the 20 most recent IRPs per device. For a longer session you'll need to use DC2WMIParser tool available in Tools folder in the WDK (Windows Driver Kit) and specify length of time to run it with the /t argument.
      My Computer


  5. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
    Thread Starter
       #45

    Ok updated :)
      My Computer


  6. Posts : 3
    windows 7 64bit
       #46

    Hello there,

    I am Peter from Switzerland. I have followed the instructions on the first post and i'm getting a bluescreen on startup. I give you the file so you can look at it and tell me which driver is causing this problem and how to fix it. Thanks in advance for all the help you may give me.
    Using Driver Verifier to identify issues with Drivers Attached Files
      My Computer


  7. Posts : 2,573
    Win7 Ultimate X64
       #47

    Hi Peter, Welcome to SF

    You are posting in the wrong section, this is a `how too` area
    If you are experiencing BSOD problems then please start your own thread here, just click the orange new thread button and post your stuff
    You will get better help for your problem in the correct section
      My Computer

  8.    #48

    Pauly said:
    Hi Peter, Welcome to SF

    You are posting in the wrong section, this is a `how too` area
    If you are experiencing BSOD problems then please start your own thread here, just click the orange new thread button and post your stuff
    You will get better help for your problem in the correct section
      My Computer


  9. Posts : 30
    Windows 7 Ultimate 64
       #49

    I have been having a multitude of BSODs so ran Verifier. It BSODed before the glowing Windows logo on the black screen even got going with a Comodo Firewall driver .sys BSOD. I removed that software and it booted no problem thereafter but should I still have verifier running? Is it worth my time leaving it on given that earlier BSOD or should I just leave it for a while to ensure I have no other flaky drivers which could have been causing my BSOD problems?

    PS is there any way to 'speed it up' and/or 'increase the stress levels on the drivers' or is it just like a background monitor I have to leave to 'do its own thing'? Will it keep running happily with the PC left on idle?
      My Computer


  10. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
    Thread Starter
       #50

    DannyG13 said:
    I have been having a multitude of BSODs so ran Verifier. It BSODed before the glowing Windows logo on the black screen even got going with a Comodo Firewall driver .sys BSOD. I removed that software and it booted no problem thereafter but should I still have verifier running? Is it worth my time leaving it on given that earlier BSOD or should I just leave it for a while to ensure I have no other flaky drivers which could have been causing my BSOD problems?

    PS is there any way to 'speed it up' and/or 'increase the stress levels on the drivers' or is it just like a background monitor I have to leave to 'do its own thing'? Will it keep running happily with the PC left on idle?
    It's best to turn it off because it's a memory hog to have that running all the time.
      My Computer


 
Page 5 of 7 FirstFirst ... 34567 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:01.
Find Us