If your BSODs are software related, Driver Verifier can help by subjecting 3rd party drivers to a variety of stresses and tests to find improper behavior. Driver Verifier monitors selected 3rd party kernel-mode drivers to detect illegal function calls or actions that might corrupt the system.
If Driver Verifier detects a violation, it will flag (disable) the offending driver and force a BSOD. The additional info added to the memory dump file will hopefully yield clues.
1. Create a Windows System Restore Point -
Vista - START | type rstrui - create a restore point
Windows 10 & 7 - START | type create | select "Create a Restore Point"
Windows 8/ 8.1 - Swipe mouse top-right of screen to bring up Charms |click on "Search" | type create | select "Create a Restore Point"
2. Run Driver Verifier -
- Windows 10, 7 & Vista - START | type verifier
- Windows 8.1 & 8 - Press WIN +X keys | select "Command Prompt (Admin)" | type verifier
Make these selections -
1. Select 2nd option - "Create custom settings (for code developers)"
2. Select 2nd option - "Select individual settings from a full list"
3. Check these boxes -
- Special Pool
- Force IRQL checking
- Pool Tracking
- Deadlock Detection
- Security Checks (new as of Windows 7)
- Miscellaneous Checks
- Power framework delay fuzzing (new as of Windows 8)
- DDI compliance checking (new as of Windows 8)
4. Select last option - "Select driver names from a list"
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where "Microsoft" IS NOT the Provider
7. Click on Finish
If you are unable to boot into normal Windows after VERIFIER_ENABLED BSOD -
To check Driver Verifier status -
To VERIFY Driver Verifier SETTINGS -
- Driver Verifier needs to run for 24 hours minimum - even if the status screen appears clear.
If a VERIFIER_ENABLED BSOD occurs, please get the dump file from c:\windows\minidump, zip it up & attach to your next post.
Additional info from Windows Dev Center -
Regards. . .
Edited by jcgriff2, 18 May 2015 - 04:48 PM.