BSOD at random intervals, no specific pattern even after clean install

You are welcome. Let us know what happened there.

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

Disable Verifier.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff980160faee0, fffff980160fa087, 650118, 32}

Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff980160faee0, address trying to free
Arg2: fffff980160fa087, address where one bit is corrupted
Arg3: 0000000000650118, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error

Debugging Details:
------------------


BUGCHECK_STR:  0xC1_32

SPECIAL_POOL_CORRUPTION_TYPE:  32

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

IRP_ADDRESS:  fffffa8007c16548

LAST_CONTROL_TRANSFER:  from fffff80002b5b353 to fffff80002ad4fc0

STACK_TEXT:  
fffff880`0a3a8678 fffff800`02b5b353 : 00000000`000000c1 fffff980`160faee0 fffff980`160fa087 00000000`00650118 : nt!KeBugCheckEx
fffff880`0a3a8680 fffff800`02bd3fb3 : fffffa80`05eb2010 00000000`00000001 00000000`00000003 fffffa80`07c16060 : nt!MiCheckSpecialPoolSlop+0x83
fffff880`0a3a86c0 fffff800`02bff93b : fffff800`02a56000 00000000`2b707249 00000000`001b75a8 00000000`00000001 : nt!MmFreeSpecialPool+0x1d3
fffff880`0a3a8800 fffff800`02f76026 : fffffa80`08450f02 fffffa80`08450f10 00000000`00000000 fffff980`160faee0 : nt!ExDeferredFreePool+0xf33
fffff880`0a3a88b0 fffff800`02f765ec : fffff800`02ae9712 fffff980`160faee0 fffff880`0a3a8ca0 00000000`00000000 : nt!VfIoFreeIrp+0xe6
fffff880`0a3a88e0 fffff800`02ae9712 : fffff880`0a3a8ca0 fffff980`160faee0 00000000`00000000 00000000`00000000 : nt!IovFreeIrpPrivate+0x5c
fffff880`0a3a8920 fffff800`02aa407d : fffffa80`07c165c0 fffff800`02f76026 fffffa80`07d19c00 fffffa80`07d19c10 : nt!IopCompleteRequest+0x402
fffff880`0a3a89f0 fffff800`02db9237 : 00000000`00000000 fffffa80`0530d001 fffffa80`083e8500 00000000`00000000 : nt!IopPostProcessIrp+0x4d
fffff880`0a3a8a70 fffff800`02d8b5c5 : fffff880`00000000 fffff880`0a3a8b68 fffff880`0a3a8b60 00000000`00000001 : nt!IoRemoveIoCompletion+0xe7
fffff880`0a3a8b00 fffff800`02ad4253 : fffffa80`07c16060 00000000`01a3efd8 fffff880`0a3a8bc8 00000000`00cc8644 : nt!NtRemoveIoCompletion+0x145
fffff880`0a3a8bb0 00000000`746b2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01a3efb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x746b2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiCheckSpecialPoolSlop+83
fffff800`02b5b353 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiCheckSpecialPoolSlop+83

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83

BUCKET_ID:  X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83

Followup: MachineOwner
---------

► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

► Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.

CliveK said:

Should I try running memtest on a CD if I can get my hands on it?

Try it.

Hopefully it will provide a result.

If you cannot see the results on the screen, it is not normal.

IMO you should try it again. Follow the directions carefully .... How to Test and Diagnose RAM Issues with Memtest86+. (Part 2)