Using Driver Verifier to identify issues with Drivers

[XshinysuicuneX]

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!

 

[Influxvisions]

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.

 

[Vir Gnarus]

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.

 

[Vir Gnarus]

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.

 

[Capt.Jack Sparrow]

Ok updated

 

[Calsot]

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.

 

[Pauly]

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

 

[x BlueRobot]

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

 

[DannyG13]

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?

 

[Capt.Jack Sparrow]

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.

 

[truelies]

I tried to use the driver verifier to solve BSODs, after enabled it, the computer frozen after login without BSOD. I can disable it in safe mode, but does that mean I can't use driver verifier? Anyway to enable it and use the computer normal to catch BSOD?

 

[Golden]

Anyway to enable it and use the computer normal to catch BSOD?

No, you will need to wait for a BSOD.

 

[buythiscomputer]

Hello, I upgraded from windows 7 to windows 10 and still have the same problem that I had before.

Computer is stuck in boot loop and i need to restart 10 or 20 times to access my desktop.

Because I have the same problem after upgrading to windows 10 do you think that it cannot be a driver problem ?

Did windows change all my drivers during upgrade ?

Computers always work in safe mode, but not with networking or any other option.

Thank you for your help.

 

[zapp22]

buythis: if you really mean "upgrade" in the dictionary sense, you didn't solve or escape anything.
you would want to save all your data to another device and CLEAN install 10 if you dare.

To the main intent of this thread: maybe I'm too picky but HOW does one make use of the crash data that verifier [best I can tell] produces? Where is the log? What to do with the log if there is one?
same issue with the [one of] Microsoft pages describing verifier in glorious detail except for one small omission: what is the output? where is the output? how to use to correct bad devices that were the reason for a person ever coming across the "verifier" to start with?
its the fix we're after, not how to play with verifier.exe

 

[Pauly]

Verifier is not a tool that produces an output
In terms of BSOD situations when faulting drivers cannot be identified from dump files enabling verifier (stressing drivers) will give a different dump file output that can help to narrow down/identify culprit drivers but its far from an exact science, sometimes it helps sometimes it doesnt

 

[khalidow]

Hello everyone , I'm not actually getting a BSOD the reason why I used driver verifier ( and did get a BSOD with that) is that my computer freezes either while windows is loading (booting up) and sometimes windows will load but freezes at the desktop , and when it does work i can use my computer (surfing , editing ...) but i can't play any game , it freezes after around 2min from launching a game however (while in game) sometimes it recovers with a driver error (display driver has stopped working ).
Before u ask , I have the latest nvidia driver .

 

[axe0]

Hello everyone , I'm not actually getting a BSOD the reason why I used driver verifier ( and did get a BSOD with that) is that my computer freezes either while windows is loading (booting up) and sometimes windows will load but freezes at the desktop , and when it does work i can use my computer (surfing , editing ...) but i can't play any game , it freezes after around 2min from launching a game however (while in game) sometimes it recovers with a driver error (display driver has stopped working ).
Before u ask , I have the latest nvidia driver .

That could mean a driver is causing you problems, where in this case it is your VPN. At least, that is what caused the crash, can't say it is causing the freezes..

Anyway, I suggest to create a new thread at the Performance and Maintenance section for your problem. I'm sure there are many users who will gladly help

 

[khalidow]

Thank you for the reply , I'll do that if uninstalling the VPN software doesn't solve the freezing problem which I doubt it will .

 

[VaiSupport]

Necro Driver verifier issues

Hello, and sorry for the NECRO-Awakening of all times, this just seemed to be a good place to ask.

We have been having major issues with one of our PC's here at work. I'm suspecting there could be something fishy going on, but we have 3 computers that are identical to this one, with all same driver versions but none of the other PC's are doing this.

Issue : The PC deadlocks every now and then, and doesn't respond to mouse or keyboard at all in any ways.
So far all we've done is reboot PC, and we even tried building a new PC with new hardware - but alas, the same problems continue on this new PC aswell.
Driver verifier has been running on PC for roughly 36 hours now, and it has generated 2 dump files. I have no clue how to read these, so any help would be greatly appreciated.

Driver verifier dump files attached.

 

[axe0]

Please create a new thread in the http://www.sevenforums.com/bsod-help-support/ and read Blue Screen of Death (BSOD) Posting Instructions