Driver+Verifier

Since no dumps available, you can try and create some by running the driver verifier, which will stress-test your non-MS drivers. If the verifier flags a driver, it will BSOD the system. To re-start, it may be necessary to run Windows   or Vista System Repair. If this were my system and I had the chance to have it looked over - I would do it. No guarantees of course. But one never knows what another set of eyes can see.

To run the driver verifier - bring up an elevated administrative cmd/DOS prompt: ** START | type cmd.exe | right-click on cmd.exe uptop under programs | Run as | type verifier **  **& hit enter - the Verifier screen will appear | do the following:** code format="prettyprint lang-auto linenums:0 prettyprinted" 1. Select 2nd option - Create custom settings ( for code developers ) 2. Select 2nd option - Select individual settings from a full list. 3. Check the boxes • SpecialPool • PoolTracking • Force IRQL checking 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] isnot the Provider 7. Click on Finish 8. Re - boot

Again... if the Driver Verifier (DV) finds a violation (flags a driver), it will result in a BSOD. To see the status of the D/Verifier, bring up an elevated cmd/DOS prompt and type **verifier ** - select the last option on the first screen - "Display information about the currently verified drivers..". If your system becomes too unstable (the d/v utilizes CPU & RAM), turn d/v off - type **verifier /reset ** then re-boot.

If you get a verifier-enabled BSOD, get the mini dump - go to \windows\minidump - copy it out, zip it up and attach. code