If it will find the cause of a BSOD is another thing. But maybe you know after 48 hours. Then please tell us.
is driver verifier (start application in background via command "verifier") dangerous to run during 48 hours to find the cause of a bsod?
 | Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years. Thanks, CNET Support |
Question
driver verifier
Discussion is locked
3 Posts
- Collapse
- Collapse -
Answer
If it will find the cause of a BSOD is another thing. But maybe you know after 48 hours. Then please tell us.
- Collapse -
I ask it because I've heard it's needed to make a restore point before running driver verifier so I think there can go something wrong.So I doubt to run it or not.
- Collapse -
Answer
I've been at this for decades now and driver verifier has yet to find a BSOD cause for us. The methods I've used is to give the machine a quick look over to check if the machine is clean and listen to the owner's stories. We get the go ahead for the work then dive in. If it's one of the few year old desktops we warn that some require motherboards or a factory reset due to deep malware or other damage.
We check the PSU rating and age too.
Not once did driver verifier help. But it didn't hurt either.
CNET Forums
Operating Systems
Software
Electronics & Gadgets
Hardware
Tablets & Mobile Devices
General Help
Roadshow Autos
Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic