Please check {windows partition}\windows\minidump and check if there are more then 1 dump files saved.
Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial
If you want proof you can search through the BSOD section, there are some who were forced to clean install Windows because of DB3 drivers. Same is for other programs that claim to update drivers.
How many passes were completed with MemTest86+?
From what I understand as this is a read error
- A driver tried to read an invalid/wrong address in the memory
- A driver tried to read corrupted data from the memory
If MemTest86+ was completed with at least 8 complete passes and its voltage and frequency in the BIOS are as they should be, then a driver is causing this.
Code:
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffa001602badb8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80034074fa4, address which referenced memory
As there is no driver flagged I'd like to first rule out the old drivers.
Code:
MBfilt64 Fri Jul 31 05:40:32 2009 MBfilt64.sys // Realtek audio driver
PDFsFilter Thu Aug 23 23:57:13 2012 PDFsFilter.sys // Not sure what driver this is, no software related to the driver
rawdsk3 Tue Feb 11 22:10:17 2014 rawdsk3.sys // Not sure what driver this is, no software related to the driver
HWiNFO64A Sun Nov 23 17:24:07 2014 HWiNFO64A.SYS // HWiNFO driver
Please check Realtek for driver updates.
Diagnostic Test
DRIVER VERIFIER
Warning
Please make a backup of your important files and get your rescue media or
create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
Note
Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.