New
#20
You might consider to add any driver with 'dump' as a prefix to Option one #5, for example; dump_dumpfve.sys and dump_iastor.sys. these should be unchecked also.
They are drivers created to provide disk access during crash dump file generation.
i've followed all the steps given but i think i ticked dump_dumpfve.sys and dump_iastor.sys.Is it matter?Now i running it for 5 hours already.So should i restart the process?
No, I would leave it running.
If Driver Verifier generates a BSOD and blames dump_dumpfve.sys and/or dump_iastor.sys, then disable them and let it run again.
These two drivers aren't blamed very often, but there isn't any necessity to stress them so they don't need to be included in the testing.
This didn't work for me. I applied all settings as described, it said I needed to restart so I told it "OK" and nothing happened. I manually restarted, and it just booted up normally without any special screen or status report for the verification. i tried it again but nothing happened.
What should I do to try and force this to work?
i did this and my computer would lock up everytime i started it up windows would briefly start then log off and lock....why is this?
I tried to use this and that was impossible because my pc crashed with brief flash of bscreen before Windows even started to load. Had to do recovery in there start screen to get normally in Windows. So this verifier-program seem to be quite hazardous to use.