Multiple BSODs at random use

I'm seeing a lot of memory corruption here.

Code:

BugCheck 3B, {c0000005, fffff800030b8ea5, fffff88006f51f80, 0}

Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+49d )

Code:

BugCheck BE, {fffff8a00a18dff8, 8000000088435121, fffff88006c4f5b0, b}

Attempted write of read only memory can easily be caused by bad RAM.

Code:

0: kd> [COLOR="rgb(46, 139, 87)"]!pte 8000000088435121[/COLOR]
                                           VA 8000000088435121
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00010    PDE at FFFFF6FB40002210    PTE at FFFFF680004421A8
Unable to get PXE FFFFF6FB7DBED000
WARNING: noncanonical VA, accesses will fault !

Code:

BugCheck 1E, {ffffffffc0000005, fffff8000309b878, 0, ffffffffffffffff}

Here we see and access violation, with an attempt to read from an invalid address.

Code:

0: kd> .trap fffff880`034fb820
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000003921 rbx=0000000000000000 rcx=0000000000000001
rdx=0000058000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000309b878 rsp=fffff880034fb9b0 rbp=fffff6800004f280
 r8=0000000000000008  r9=fffff800032b6680 r10=0000000fffffffff
r11=fffff68000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiDispatchFault+0x548:
fffff800`0309b878 410fb6561a      movzx   edx,byte ptr [r14+1Ah] ds:00000000`0000001a=??

The register is zeroed, this may be true or the minidump hasn't recorded the information.

With all this said, I suggest running Memtest86+

   Information

Download it here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which one should I download?

You have two options to choose from, you can either download the ISO version then burn it do a CD and boot it from there.
The other option is downloading the auto installer for USB sticks, you then boot from that USB stick.
Be warned though, it will format your USB then install the files needed to make it bootable so any files left over will be wiped off.

So how does it work?

It works by writing a series of test patterns to most memory addresses over 9 tests, it then reads the data back to compare it for errors.

The default pass does 9 different tests varying in access patterns and test data. A tenth pass is optional from the menu which writes all the memory in zeroes then sleeps for 90 minutes and compares it to see if any address have changed, this takes 3 hours per pass each time.

My memtest86 isn't booting! What should I do?

This can be caused by a number of different reasons, common ones include your BIOS not setting using the correct settings, you might want to change your boot priority order.
Other causes include your motherboard not supporting bootable USB sticks in which case you'll need to use a CD (or floppy drive).

Any other issues you might want to look here:

FAQ : please read before posting

@Thedoctor44

I ran memtest86+ all night and discovered no errors.

Enable Driver Verifier again, if it crashes and you can't get into Windows boot into Safe Mode.
Make sure you create a restore point before hand to allow you to restore back if you can't boot into safe mode.

@Thedoctor44

Enabled verifier - crashes on windows welcome screen with reference to srvnet.sys and ntfs.sys.
I am on safe mode now. attached the dumps.

I'm struggling to find anything despite Driver Verifier being enabled, it looks like a driver is hiding from it so I thought it'd be best to dump the raw stack.
System service exceptions can be caused by Anti Virus programs which we can see here. It's not surprising with the amount of filter drivers and other kernel mode drivers that issues are bound to happen with some of them.

Code:

fffff880`0294c5a0  fffff880`03cb0394Unable to load image \SystemRoot\system32\DRIVERS\eamonm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for eamonm.sys
*** ERROR: Module load completed but symbols could not be loaded for eamonm.sys
 eamonm+0x29394

The ESET Amon driver is causing problems, more specifically it's causing working set corruption.

For testing purposes I suggest you replace it with MSE and Malwarebytes.

Microsoft Security Essentials - Microsoft Windows

Malwarebytes | Free Anti-Malware & Internet Security Software

   Tip

Make sure you don't enable the free trial of malwarebytes pro, deselect the option when prompted.

It may have been a memory issue after all.
I have G.skill PI Black DDR2 memory rated at 900mhz CL4 at 2.1V
I underclocked it to 800mhz at 1.8V and so far no BSOD.
Could be wishful thinking but i hope that solves this issue.