Multiple Different BSODs Custom PC

No those dump files aren't much use because they're old.

Can you just upload dump files that are created from driver verifier.
Just run it as usual.

Got a brand new BSOD that I've never seen before. Got it while I was watching a series, full-screened, in Google Chrome. Verifier was running at the time it BSOD, I will continue to keep it running.

The bugcheck you have indicates special pool corruption which has been caused by the special pool option from Driver Verifier.

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff98052b02ee0, address trying to free
Arg2: fffff98052b0227e, address where one bit is corrupted
Arg3: 0000000000330118, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error

Parameter 1 is the one we're most interested in as this indicates the address was trying to be freed.

Code:

Pool page fffff98052b02ee0 region is Unknown
GetUlongFromAddress: unable to read from fffff80003873a38
fffff98052b02000 is not a valid small pool allocation, checking large pool...
unable to get pool big page table - either wrong symbols or pool tagging is disabled
fffff98052b02000 is freed (or corrupt) pool
Bad previous allocation size @fffff98052b02000, last size was 0

***
*** An error (or corruption) in the pool was detected;
*** Pool Region unknown (0xFFFFF98052B02000)
***
*** Use !poolval fffff98052b02000 for more details.
***

We can see this pool page is corrupted so we should take it a bit further.

Code:

Pool page fffff98052b02000 region is Unknown

Validating Pool headers for pool page: fffff98052b02000

Pool page [ fffff98052b02000 ] is __inVALID.

Analyzing linked list...


Scanning for single bit errors...

None found

There's not much information here so we'll need to continue.

Code:

   +0x000 PreviousSize     : 0y00011000 (0x18)
   +0x000 PoolIndex        : 0y00000001 (0x1)
   +0x000 BlockSize        : 0y00110011 (0x33)
   +0x000 PoolType         : 0y00000000 (0)
   +0x000 Ulong1           : 0x330118
   +0x004 PoolTag          : 0x2b707249
   +0x008 ProcessBilled    : (null) 
   +0x008 AllocatorBackTraceIndex : 0
   +0x00a PoolTagHash      : 0

The Previous Page is wrong as it should be 0 because 0 is non paged pool and 1 is paged pool.
non paged pool is space within memory that contains information for kernel objects such as device drivers.

Code:

rax=0000000000000000 rbx=0000000000000000 rcx=0000000009175000
rdx=0000000066e38f70 rsi=0000000000000000 rdi=0000000000000000
rip=0000000072f02e09 rsp=0000000004b2eb68 rbp=00000000063ef8d4
 r8=000000000000002b  r9=00000000778cf959 r10=0000000000000000
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
0033:00000000`72f02e09 ??              ???

Now the registers are corrupt or are unavailable so I can't go any further.

Can you try disabling the special pool option in Driver Verifier?

How do I disable that part?

Just disable it and follow these instructions

Driver Verifier - Enable and Disable

You must have selected individual settings from a list.

Yet another Memory Corruption BSOD while gaming.

Driver Verifier will have to be enabled again because if your RAM isn't faulty memory corruption will be caused by drivers most of the time.

This is getting really tough, if driver verifier doesn't pick up the culprit soon I'm afraid I'll soon be all out of ideas.

That BSOD was caused when Driver Verifier was running. I still have it running, it's been running for the past 3 days straight.

Edit: Is it possible that it's being caused by GPU memory?

If it is memory corruption then yes, it can be caused by video RAM.

The reason I asked is that most of the time Driver Verifier will create "driver verifier" bugchecks, mainly 0xC4 or 0xC5 bugchecks I believe.