BSOD; NTOSKRNL; and other random crashes

HI!
I'm new to the forum so I really hope I'm posting this right.
I've recently built a new machine using the MSI 890FXA-GD65 Mobo, an AMD phenom II 1100t Black Edition X6 Processor and 16GB (4 x 4GB) CORSAIR XMS 240-Pin DDR3 SDRAM DDR3 1600
I've installed windows 7 ultimate 64bit and have been getting BSOD from day one. at first i thought it was software related as i had a piece of software that had known issues but after removing it I continue to have crashes, and it's not always for the same reason, I've run Memtest on it a couple times (8 passes) no errors, and the diskcheck utility. Now I'm completely stumped so I'm hoping one of the many experts on here might have some insight. I wouldn't worry so much if i didn't need my machine for editing, so any help you can all give would be greatly appreciated. for all I know i overlooked something really simple and just can't figure it out. THANK YOU all in advance.

-Richard

Stop any overclocking and run Prime95 https://www.sevenforums.com/tutorials...t-prime95.html

Memory Corruption is alos mentioned in your dumps, use one module of RAM at a time and determine if your system is stable all the different modules

You really should uninstall whichever software you have that belongs to this ancient driver.
sentinel.sys Windows process - What is it?

Code:

Sentinel64.sys        fffff880`02a72000    fffff880`02a97000    0x00025000    0x45c1d180    01/02/2007 15:39:44

Code:

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8a21c255d, Reserved
Arg2: b3b7465ef49a03fb, Reserved
Arg3: fffff8800159eb90, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8800422872d to fffff880042286e4

STACK_TEXT:  
fffff800`00b9cc68 fffff880`0422872d : 40768000`00000000 00000000`00000000 00000000`00000000 fffff800`00b96080 : 0xfffff880`042286e4
fffff800`00b9cc70 40768000`00000000 : 00000000`00000000 00000000`00000000 fffff800`00b96080 00000000`00000001 : 0xfffff880`0422872d
fffff800`00b9cc78 00000000`00000000 : 00000000`00000000 fffff800`00b96080 00000000`00000001 fffff800`03a95509 : 0x40768000`00000000


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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

I'll try that, thanks, I think I already know what program that sentinel64.sys is from. Thanks for the advice I'll see if I can find bad ram.
-Richard