Windows 7 - Using Driver Verifier to identify issues with Drivers

zigzag3143 · 01-03-2012

Quote: Originally Posted by john982

I checked the event viewer but not shure where to look for? I saw that some services not started but since I tried to boot a couple times in a row the same error should have been listed. But nothing like that....

What can I do?

Sorry

To check for freezing/crashing you need to check several things.

Event viewer.

Quote:

Type eventvwr in search and go to the windows log>application tab.
Look for errors. Errors have red in the left hand column. Then repeat the process in the system tab.

Look for errors that say app hang, or app crash, or anything related to the problem. (errors have red in the left hand column)

When you find them either take a screenshot of them and upload them to us, or note the event ID and source codes and look them up in google. If you cant find them in google tell us what they are.

john982 · 01-04-2012

Mmm no errors of hangs during the time that I was using the verifier. Some errors but long before of after I used verifier. It still hangs on logon....

Thanks for your help in advance....

jcgriff2 · 01-06-2012

See if you can boot into Recovery using your Windows 7 DVD or the HDD Recovery partition and run Windows System Restore.

Vir Gnarus · 03-09-2012

After having to mention it numerous times in threads here, I feel it best to notify others here that in addition to turning off Low Resource Simulation as instructed in the article, it's best to do the same for IRP Logging and Force Pending I/O Requests.

IRP Logging is a very beneficial debugging check for Driver Verifier that will greatly enhance finding issues in I/O on a PC. However, the logs are not retained in crashdumps; they can only be accessed during a live kernel debugging session (that means hooking your PC to the troubled PC and running Windbg through that connection). All it will cause for those here at SF is unnecessary resource consumption (I've often seen this one check slow people's PCs to a crawl).

Force Pending I/O Requests should be off for the same reason Low Resource Simulation is turned off, in that it produces an artificially induced environment for drivers that can - and often will - cause false positives. It works by randomly grabbing I/O requests from drivers and forcing them to sit and wait. This is not a common scenario in a normal PC environment, but in certain situations (especially when resources are starting to be strained) it can pop up. Because it is such an uncommon occurrence, those who code drivers often do not code their drivers to expect this result, and can actually bug the driver out if it comes across it. That's why it's best to turn this off completely. While it has the potential to find bugs in drivers, it's a very risky venture and is best used in a testing environment.

Details on Driver Verifier settings are available here.

Windows 7 - Using Driver Verifier to identify issues with Drivers

Using Driver Verifier to identify issues with Drivers problems?