Windows 10: Random BSODs with various bug checks, possibly a driver is at fault.

I'm back.
After quite a while the computer just did not blue screen as soon as Driver Verifier was on. Only recently has it started blue screening again.
It's strange that it was only stable with it on, but once it was off the crashes resumed.

The crash reports still only give me IRQL errors, except for once.
Driver Verifier found the Intel Smart Connect driver causing an issue. I updated it but its still happening and I can't get rid of the Intel thing.

Here are the recent and past crash dumps.
Any ideas or suggestions?

 

Following Intel drivers could use some updating, please try to update as much as possible.
This list includes the Intel Smart Connect Driver, because it is dating 2014.
Driver Reference Table - HECIx64.sys
Driver Reference Table - imsevent.sys
Driver Reference Table - ikbevent.sys
Driver Reference Table - isctd.sys
Driver Reference Table - INETMON.sys

 

Thanks, I'll get each one I can. I already did the Intel Smart Connect driver and I think 2014 is as new as it gets.
Download Intel Smart Connect Technology
Unless I can get a newer one elsewhere.

 

Majority of those drivers are in the Intel Smart Connect which I've installed already.
One of them tells me the computer doesn't meet the minimum requirements.
Not sure what to do now.

Here's what the new errors were

system_service_exception 0x3b
irql_not_less_or_equal 0x0a
system_thread_exception_not_handled 0x7e

Pointed towards ntfs.sys causing it

 

A new zip file comes in handy.

 

FYI, if you haven't done a clean install yet then this could well be a bug that appeared due to the upgrade.
There are quite some dumps that are pointing to memory corruption, this usually refers to the memory.
Memory corruption could also be caused by power problems, frequency issues, hard drive problems, page file problems or simply drivers.






Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.