Latest dump on 07/20 at 11:37 is a Driver Verifier generated dump but it doesn't indicate the driver that is the problem:
Code:
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Arg2 should have the address in the driver where the exception occurred but it's zeroed out.

Stack trace shows where the exception occurred:
Code:
kb
 # RetAddr           : Args to Child                                                           : Call Site
00 fffff802`448cf02b : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
01 fffff802`4488931d : ffff8700`db822730 00000000`00000010 fffffc41`4b88bdb1 00000000`00000000 : nt!KiDispatchException+0x18c3ab
02 fffff802`44885503 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11d
03 00000000`00000000 : 00000000`00000000 fffffcbb`046363f0 00000000`00000000 fffffc87`92ba5ea0 : nt!KiPageFault+0x443
The 3rd parm should be the Trap frame address but it's not readable:
Code:
0: kd> .trap fffffc41`4b88bdb1
Unable to read trap frame at fffffc41`4b88bdb1

The previous dump on 07/20 at 11:21 is not a Driver Verifier generated dump, though it is the same failure:
Code:
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
It does show this though:
Code:
ffffb986`ca7b83e8  fffff807`81b417feUnable to load image \SystemRoot\system32\drivers\wd\WdFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WdFilter.sys
 WdFilter+0x517fe
WdFilter.sys belongs to Windows Defender.

Driver Verifier was not enabled when this dump occurred:
Code:
0: kd> !winver
No export winver found

Do you have memory you can replace the current 8GB DDR3 with?

Time to test CPU.
===================================================
Follow this tutorial to stress test your CPU:

For Intel CPUs (32 and 64 bit): Intel® Processor Diagnostic Tool

The purpose of the Intel® Processor Diagnostic Tool is to verify the functionality of an Intel® microprocessor. The diagnostic tool checks for brand identification, verifies the processor operating frequency, tests specific processor features, and performs a stress test on the processor.

Prime95 - Stress Test Your CPU - Windows 10 Forums

OCCT: OCBASE / OCCT

For both the above, read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall