Intermittent BSODs with no obvious commonality

OK. Let us know how you get on. Sorry it couldn't be a simpler solution for you

If most of them are ntfs, directx, and system service exceptions (which is what I see here the most), and memory tests out OK, then the likelihood is this is driver related, a kernel-mode driver specifically. I'd put good money on either the disk controller driver or the antivirus driver, so we'll have to see how things go from here.

I guess I'll upload another dump from the fresh install and minidumps included to see if anyone has an idea

It's another crash in Chrome - can you please configure your system for a complete memory dump, and zip \Windows\Memory.dmp then upload to a file sharing site the next time the crash occurs? Minidumps are, for the most part, useless for things like this.

This looks an awful lot like a driver issue:

Code:

// Thread involved in the crash:
0: kd> !thread
THREAD fffffa800d352b50  Cid 0944.07e0  Teb: 00000000fff80000 Win32Thread: 0000000000000000 RUNNING on processor 0
Not impersonating
DeviceMap                 fffff8a0023575d0
Owning Process            fffffa800ccf5060       Image:         chrome.exe
Attached Process          N/A            Image:         N/A
Wait Start TickCount      2832752        Ticks: 0
Context Switch Count      75596          IdealProcessor: 3             
UserTime                  00:01:04.802
KernelTime                00:00:01.638
Win32 Start Address 0x000000005d33958b
Stack Init fffff8800772fdb0 Current fffff8800772faa0
Base fffff88007730000 Limit fffff8800772a000 Call 0
Priority 9 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0772e8a8 fffff800`02cd0169 : 00000000`0000003b 00000000`c0000005 fffff800`02cd5325 fffff880`0772f170 : nt!KeBugCheckEx
fffff880`0772e8b0 fffff800`02ccfabc : fffff880`0772f918 fffff880`0772f170 00000000`00000000 fffff800`02cfbc50 : nt!KiBugCheckDispatch+0x69
fffff880`0772e9f0 fffff800`02cfb75d : fffff800`02ef2d48 00000000`00000000 fffff800`02c5b000 fffff880`0772f918 : nt!KiSystemServiceHandler+0x7c
fffff880`0772ea30 fffff800`02cfa535 : fffff800`02e206c4 fffff880`0772eaa8 fffff880`0772f918 fffff800`02c5b000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0772ea60 fffff800`02d0b4c1 : fffff880`0772f918 fffff880`0772f170 fffff880`00000000 fffff800`02e4be80 : nt!RtlDispatchException+0x415
fffff880`0772f140 fffff800`02cd0242 : fffff880`0772f918 fffffa80`56b34cc0 fffff880`0772f9c0 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`0772f7e0 fffff800`02cceb4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0772f9c0 fffff800`02cd5325 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`74d12450 : nt!KiGeneralProtectionFault+0x10a (TrapFrame @ fffff880`0772f9c0)
fffff880`0772fb50 fffff800`02fb9d44 : 00000000`00000000 00000000`00000001 fffffa80`09754800 fffff880`0772fc01 : nt!KeSetEvent+0x1e3
fffff880`0772fbc0 fffff800`02ccfe53 : fffffa80`0d352b50 00000000`00000514 00000000`00000000 fffffa80`56b34cc0 : nt!NtSetEvent+0x90
fffff880`0772fc20 00000000`74d12e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0772fc20)
00000000`07ccf028 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74d12e09

// Exception chain showing KiSystemServiceHandler as an exception handler for KiSystemServiceCopyEnd - exception handler is spanning a protection boundary
0: kd> !exchain
12 stack frames, scanning for handlers...
Frame 0x03: nt!RtlpExecuteHandlerForException+0xd (fffff800`02cfb75d)
  ehandler nt!RtlpExceptionHandler (fffff800`02cfb720)
Frame 0x05: nt!KiDispatchException+0x135 (fffff800`02d0b4c1)
  ehandler nt!_GSHandlerCheck_SEH (fffff800`02ca7be8)
Frame 0x09: nt!NtSetEvent+0x90 (fffff800`02fb9d44)
  ehandler nt!_C_specific_handler (fffff800`02cfbc50)
Frame 0x0a: nt!KiSystemServiceCopyEnd+0x13 (fffff800`02ccfe53)
  ehandler nt!KiSystemServiceHandler (fffff800`02ccfa40)
Frame 0x0b: error getting module for 0000000074d12e09


// Disassembling this, we can see the 3B bugcheck:
0: kd> uf nt!KiSystemServiceHandler

...
nt!KiSystemServiceHandler+0x54:
fffff800`02ccfa94 65488b042588010000 mov   rax,qword ptr gs:[188h]
fffff800`02ccfa9d 80b8f601000000  cmp     byte ptr [rax+1F6h],0      // <- will call KiBugCheckDispatch with 3B
fffff800`02ccfaa4 7416            je      nt!KiSystemServiceHandler+0x7c (fffff800`02ccfabc)

nt!KiSystemServiceHandler+0x66:
fffff800`02ccfaa6 4d33d2          xor     r10,r10
fffff800`02ccfaa9 4d8bc8          mov     r9,r8
fffff800`02ccfaac 4c8b4110        mov     r8,qword ptr [rcx+10h]
fffff800`02ccfab0 8b11            mov     edx,dword ptr [rcx]
fffff800`02ccfab2 b93b000000      mov     ecx,3Bh
fffff800`02ccfab7 e844060000      call    nt!KiBugCheckDispatch (fffff800`02cd0100)      // <- this is on the stack
...

The system checks an exception in kernel mode, and if it would result in a user-mode unwind, the system bugchecks with this code (0x3B, SYSTEM_SERVICE_EXCEPTION). What this means is that you (very) likely have a driver that's causing issues, assuming your system RAM has passed MemTestx86+ testing. If that's the case, Driver Verifier is going to be required (enable, reboot, wait for another crash) to catch the culprit that's actually causing the exception from user-mode. The settings discussed here are appropriate.