Windows 10: After attempting to fix consistent BSODs, I ran driver verifier and need help with what to...

I ran bugcheck analysis from WinDbg, but now I'm not sure where to go now. Would greatly appreciate it if someone could help. Here is the bugcheck analysis copy and pasted. 0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************

:)

 

Need help on driver verifier bsod

I had a bsod 0x1000007E and did the sfc /scannow and dism steps and ran chkdsk then memtest. Everything checks out so I tried running driver verifier and after logging in i got this bsod SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 0x1000007E.
Could I please request assistance in figuring out the minidump generated by the verifier? Uploaded the minidumps on one drive

minidumps

 

Windows Driver Verifier BSOD


I took the WinTV card out of my computer and ran driver verifier again but didn't have it check dfx12x64.sys. Still got an immediate BSOD which BlueScreenView reported as being caused by wdcsam64.sys. Ran driver verifier again and didn't have it check either of those two, this time I got a BSOD that BlueScreenView reported as being caused by rtwlanu.sys (I've included that crash dump - the previous one got deleted when I had to use system restore to disable driver verifier). Ran driver verifier again and excluded all 3 of those from the list of drivers to check and finally didn't get a BSOD. So what the heck does that mean? Driver verifier's given me BSODs for 5 different drivers now. I'm about to just give up and go back to Windows 7.

 

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.