Help with BSOD have minidump debugged

I have to also add my other crashes returned different results for what caused it, I can upload those too but I didnt want to over do it right away.

Ok so I ran a full pass off the tests and I came up with an error exactly as follows:
Does this mean bad RAM?

Tst - 6 Pass - 0 Failing Address - 00072854d1c - 1832.2 mb Good - ffbfffff Bad - ffffffff err-bits - 00400000 Count - 1 Chan - (nothing entered)

Voltage has been steady at 2.1 which is what crucial ballistix tracers are spec'd to run at. The Maximus II formula has an LCD screen to look at while the systems running which is where I'm assuming this from. I've replaced the board 2 times and I'm having a pretty hard time thinking its that again, although I guess anythings possible. Thanks much for the help I will repost results tomorrow.

If you've tried the suspect stick in both slots and it's dust free and all that jazz, it looks to be bad. Shame, but at least you found a problem. You can try to run the system without the bad stick of ram.

Turns out this still isn't fix. I have come to one blue screen since all this testing, minidump reports something different as follows.

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffffffffffffd8, 2, 0, fffff80001c63ec1}

Probably caused by : ntkrnlmp.exe ( nt!ExpScanGeneralLookasideList+51 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffffffffffffd8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80001c63ec1, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e40080
ffffffffffffffd8

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExpScanGeneralLookasideList+51
fffff800`01c63ec1 418b41d8 mov eax,dword ptr [r9-28h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffffa6001916a20 -- (.trap 0xfffffa6001916a20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffffffffff9680 rbx=0000000000000000 rcx=00000000fdfdfff3
rdx=00000000603a7218 rsi=fffffa8000c8f0f8 rdi=fffffa8000c8f040
rip=fffff80001c63ec1 rsp=fffffa6001916bb0 rbp=0000000000000000
r8=00000000603a7218 r9=0000000000000000 r10=0000000000000004
r11=fffffa80035a00c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nt!ExpScanGeneralLookasideList+0x51:
fffff800`01c63ec1 418b41d8 mov eax,dword ptr [r9-28h] ds:6ce0:ffffffff`ffffffd8=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80001c6c0ee to fffff80001c6c350

STACK_TEXT:
fffffa60`019168d8 fffff800`01c6c0ee : 00000000`0000000a ffffffff`ffffffd8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffa60`019168e0 fffff800`01c6afcb : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`01da9a50 : nt!KiBugCheckDispatch+0x6e
fffffa60`01916a20 fffff800`01c63ec1 : fffff800`00000000 00000000`00000000 fffff800`02017070 00000000`00000000 : nt!KiPageFault+0x20b
fffffa60`01916bb0 fffff800`01c5bf4a : 00000000`00000000 fffff800`01c5b9f0 fffffa80`00c8f000 00000000`00000001 : nt!ExpScanGeneralLookasideList+0x51
fffffa60`01916be0 fffff800`01c5bb0b : fffffa80`00c8f000 00000000`00000008 00000000`00000001 f4156159`00000000 : nt!ExAdjustLookasideDepth+0x2e
fffffa60`01916c10 fffff800`01e8eff3 : fffffa80`00c8f040 00000000`00000080 00000000`00000000 7604653e`00002301 : nt!KeBalanceSetManager+0x11b
fffffa60`01916d50 fffff800`01ca6546 : fffff800`01d8b680 fffffa80`00c8f040 fffff800`01d90b80 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`01916d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExpScanGeneralLookasideList+51
fffff800`01c63ec1 418b41d8 mov eax,dword ptr [r9-28h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!ExpScanGeneralLookasideList+51

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1ba35

FAILURE_BUCKET_ID: X64_0xA_nt!ExpScanGeneralLookasideList+51

BUCKET_ID: X64_0xA_nt!ExpScanGeneralLookasideList+51

Followup: MachineOwner

I updated everything possible, it was a full reinstall from a brand new HDD.

I did fix it though, and it ended up being faulty RAM (twice). Couldnt run at 1066mhz even though thats what its rated for.

Switched to some reliable G Skill and it worked great. 3 weeks not a problem yet.