BSOD/Random Shut Downs - New Build

Right off the bat the errors look kind of random, there is only one consistent thing though, pretty much every other crash is the direct result of a memory problem.

The only thing I can suggest to test this is running memtest86 overnight (5 to 7 passes) to check your ram.
It's not a 100% test method but it works better than the windows memtest util.
RAM - Test with Memtest86+

I guess it goes without saying that if you have any custom timings or overclocks going on, to remove them at this time as well.

Code:

Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+c6 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000008884, The subtype of the bugcheck.
Arg2: fffffa800371bc80
Arg3: fffffa8003625cb0
Arg4: 0000000000000504

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


BUGCHECK_STR:  0x1a_8884

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f72d46 to fffff80002ec4700

STACK_TEXT:  
fffff880`045fa8b8 fffff800`02f72d46 : 00000000`0000001a 00000000`00008884 fffffa80`0371bc80 fffffa80`03625cb0 : nt!KeBugCheckEx
fffff880`045fa8c0 fffff800`02fd1575 : fffffa80`03d5a408 fffffa80`03d57000 00000000`00000000 00000000`00000000 : nt!MiRelinkStandbyPage+0xc6
fffff880`045fa930 fffff800`032d6b44 : fffffa80`03d59000 fffff880`045faca0 fffff880`045faa08 00000000`00140001 : nt!MmSetPfnListPriorities+0x175
fffff880`045fa980 fffff800`0333786a : 00000000`00000020 00000000`00000000 fffffa80`03d59000 00000000`00000001 : nt!PfpPfnPrioRequest+0x84
fffff880`045fa9d0 fffff800`0333bfae : 00000000`00000000 00000000`0160b830 00000000`0000004f 00000000`07ab4f01 : nt!PfSetSuperfetchInformation+0x199
fffff880`045faab0 fffff800`02ec3953 : fffffa80`061f3b60 00000000`02d67800 00000000`02cbb5d0 00000000`002ca0b6 : nt!NtSetSystemInformation+0xb91
fffff880`045fac20 00000000`77af0daa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0160b7b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77af0daa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiRelinkStandbyPage+c6
fffff800`02f72d46 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiRelinkStandbyPage+c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd34

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6

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

Okay meanwhile you can clear out the minidump folder so that any new ones will be easier for you to find and upload in the meantime.
(just the files inside, not the actual folder)

If a memory stick is bad, pretty much anything can fail because of it resulting in a bsod. If the computer checks the ram for something and receives corrupt data ... you crash basically.
The actual driver/cause may vary too.
Anyhow, it's the best first step I have.
If you are just dying to do something right now it never hurts to run a secure file check on your windows installation, I would still work on getting a memtest disc made though.
SFC /SCANNOW Command - System File Checker

Okay the memtest has been running for 1 hour and so far there are 4million errors, what does it mean?

Edit - "Unexpected Interrupt - Halting CPU0" - Just got that with 5.7million errors

Edit2 - Running with 1 stick of RAM now and in the Test #7 [Block move] there are lots of errors.

I don't think I have ever seen a failure rate that bad.
Let's try running memtest on each stick individually (pull one stick test/replace with other)
hopefully you'll only need to rma one.

You can also try testing both memory slots on the motherboard. It's possible one of them is the problem as well.

Do you have another computer you can test that ram in around?
It's about 50/50 whether it's the ram or the motherboard at this point.