Windows 10: driver verifier screwed up my pc.help!

another person on here told me to use driver verifier and now me pc wont even boot properly.

can someone please help me fix what this other guy destroyed


thanks.?

:)

 

Driver Verifier BSOD on Start Up DRIVER_VERIFIER_DETECTED_VIOLATION

OK I'm going to keep this thread updated as I go through troubleshooting this issue.

As I have received no help with my minidumps, I am going through the process of learning to do it myself.

This seems
like a good guide to learn the very basics.

What has happened so far:

• New computer build, unstable windows install, slowly degrades to where the computer is unusable. Happens on multiple clean installs.

• Continuous error and critical messages in Event Viewer, some events of note are:
  • Event 219 Kernel-PnP, failed to load driver
  • Event 7031 service control manager (dozens on start up)

• First crash will happen on start up and it eventually degrades with below events.
  • Event 5 kernel general
  • Event 2 kernel-event-tracing
  • Event 3 kernel-event-tracing
  • Event 29 kernel-boot

• Tested hardware - no faults found

• Ran Driver Verifier and Windows will keep crashing with DRIVER_VERIFIER_DETECTED_VIOLATION until Driver Verifier is reset in safe mode

• Started this thread, PC became too unstable and had to do a system restore, restore had minimal changes (see above)
• Have not installed the applications and drivers removed after system restore.
• PC is heading down same road again, BSOD now appearing on startup.
• Ran Driver Verifier again - same resuslts
• Installed WinDBG to start analyzing new dumps from crashes that have been happening on startup.
  • dump 1 - pool_corruption
  • dump 2 - memory_corruption
  • dump 3 - memory_corruption
  • dump 4 - ntkrnlmp.exe

From the limited knowledge I got from the guide the only information I can get from WinDBG is shown above.

So that's where I am at the moment. My next step is to run Driver Verifier again and see what I can find.

 

 DRIVER VERIFIER

From what I gather the methodology is to run driver varifier to try and get any "bad" drivers to crash my system. Is this correct? What would be the next step after driver verifier crashes my system?

Thanks for any elaboration.

 

Driver Verifier BSOD on Start Up DRIVER_VERIFIER_DETECTED_VIOLATION

Update

So the PC went down the same road, became unusable and I wiped it.

Clean install number 6. Clean install 5 was to test if Windows 7 was as unstable as the Windows 10 installs. It was - this made me think it may be a hardware problem or just a really poorly supported motherboard.

Clean install 6 - this time I am being methodical in my steps and testing every step of the way. PC specs are still the same other than a new stick of DDR4. What I have done so far:

• Bought/installed a new stick of DDR4 for testing.
• Followed Gerrys advice and installed latest BIOS, even though it is in beta it is listed as a stable release.
  
• Installed Windows 10
• Installed Chipset Drivers from Gigabyte website.
• Installed latest Ethernet drivers (20_7) from Intel website.
• I have made sure to not connect the PC to the internet and have left the ethernet cable unplugged.
• Ran Verifier, rebooted with no problems, not that I was expecting there to be any.
• Installed latest drivers from Nvidia
• ran Verifier, rebooted, BSOD "DRIVER_VERIFIER_DETECTED_VIOLATION"
• booted into safe mode, reset Verifier, rebooted.

So this is where I am at. A completely clean install, and what seems to be problems with Nvidia drivers.

Minidump link if someone could have a look. Minidump is 021216-2203-01

https://onedrive.live.com/redir?resid=3789DDEF7B6D41D2!15823

So I am not sure what this means. PC seems stable at the moment though there is hardly anything installed on it.

Does Verifier reporting a problem mean that there is one? What should I do from here?