BSOD around every 30 hours on custom computer, may be Outlook issue

You have had many BSODs. I did not check the cause of everyone, but checked at least 6. They were all consistent, so I am pretty sure of the cause. It seems to be a memory problem. We need to test your ram.
Using Memtest
Run for at least 8 passes, for each stick.
Then run for at least 8 passes, using a good stick and testing each slot.

Code:

 Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_ROB-PC-Sun_01_18_2015_155236_52.zip\110314-11169-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0305c000 PsLoadedModuleList = 0xfffff800`0329f890
Debug session time: Mon Nov  3 00:31:24.603 2014 (UTC - 5:00)
System Uptime: 5 days 7:55:10.743
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80003372c0f, fffff8800a4edf20, 0}
Probably caused by : memory_corruption ( nt!MiUnsecureVirtualMemory+15f )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003372c0f, Address of the instruction which caused the bugcheck
Arg3: fffff8800a4edf20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt!MiUnsecureVirtualMemory+15f
fffff800`03372c0f 488b0f          mov     rcx,qword ptr [rdi]
CONTEXT:  fffff8800a4edf20 -- (.cxr 0xfffff8800a4edf20)
rax=4000000000000000 rbx=fffffa800ab13060 rcx=4000000000000000
rdx=0000000000000000 rsi=fffffa8007984550 rdi=4000000000000000
rip=fffff80003372c0f rsp=fffff8800a4ee900 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000000 r10=00000000000007d1
r11=fffff8800a4ee910 r12=fffffa8007984768 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!MiUnsecureVirtualMemory+0x15f:
fffff800`03372c0f 488b0f          mov     rcx,qword ptr [rdi] ds:002b:40000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  winlogon.exe
CURRENT_IRQL:  0
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003372c0f
STACK_TEXT:  
fffff880`0a4ee900 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUnsecureVirtualMemory+0x15f
 
FOLLOWUP_IP: 
nt!MiUnsecureVirtualMemory+15f
fffff800`03372c0f 488b0f          mov     rcx,qword ptr [rdi]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!MiUnsecureVirtualMemory+15f
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb
STACK_COMMAND:  .cxr 0xfffff8800a4edf20 ; kb
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0x3B_nt!MiUnsecureVirtualMemory+15f
BUCKET_ID:  X64_0x3B_nt!MiUnsecureVirtualMemory+15f
Followup: MachineOwner
---------

RAM - Test with Memtest86+
I have bolded the cause of your problem

If you are showing errors with the sticks, best to buy new ram. It is cheap.
If the problem is with the MB, then you will have a big expense
My guess is that you have a problem when using Outlook is because too much memory is required.

You are very welcome. It was only fair to give the thread some closure. By doing so you will be helping other members with similar problems to find the cause.