Vista - BSOD driving me nuts

hello everyone. i'm new to the forum. i hope someone can help me out here. i've been searching for a solution to my BSOD everywhere but haven't really found anything that works. here is my system:

Asus P5E vanilla x38
q6600 @ 3.3 ghz
2 x 2gb G.skill DDR2 1066 @ 978
sapphire hd 2900 pro 512mb 256-bit
2 x seagate 250gb sata 1.5gb (RAID0)
1 x seagate 750gb sata 3.0gb
1 x seagate 1.5tb sata 3.0gb
520 watt corsair PSU.
vista ultimate x64 sp1

ok. first of all i'd like to say for my overclocking i of course ran prime95. i let it go for over 2 weeks and it never crashed. i also run seti@home full time which can go for weeks at a time without a crash. but completely randomly, almost always int he middle of the night when im sleeping, i get 0x000000a BSOD. it does not list a driver or anything it simply says IRQ not less or equal. it always happens when i'm not at the computer. occasionally it'll BSOD nightly for a week and then it'll be gone for a month. i originally had my cpu at 3.5 ghz but i lowered it twice at 100mhz intervals to see if it would clear it up. no help. i have never overclocked my ram. it has always been run under its rated speed. i have also memtest'd it for a multiple days at a time and no errors come up. my CPU temps aren't amazing but they're safe. under full load it'll be mid-to-high 60's (celcius).
i'm assuming its a driver problem. everything is fully updated except my raid drivers. the p5e's seem to only work in raid or ahci mode with a certain driver without cuasing instant bluescreens when the HDD is under load. i have tried older drivers for various things like my video card and my audio. i even tried a newer raid driver but the computer is unusuble with any other driver than the one i'm using. i'm not the only one with that either its a fairly common problem i've read.
if anyone needs any more information i'll try to answer as best as i can.
i have attached my last minidump, hopefully someone can tell me what it says??

thanks!

commonly it is the CPU overheating. A close second would be bad RAM.

Minifile dump-
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.

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: explorer.exe

Try running Memory Diagnostic
start>control Panel (classic View) Admin tools> memory test

and run sfc/scannow:
System Files - SFC Command




---------
1: 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: 00000000000000c0, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000001, 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: fffff80001ec0b32, address which referenced memory
Debugging Details:
------------------

WRITE_ADDRESS: 00000000000000c0
CURRENT_IRQL: c
FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`01ec0b32 48890a mov qword ptr [rdx],rcx
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: explorer.exe
TRAP_FRAME: fffffa6005293970 -- (.trap 0xfffffa6005293970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800020898c0 rbx=0000000000000000 rcx=fffffa60005ec970
rdx=00000000000000c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80001ec0b32 rsp=fffffa6005293b00 rbp=0000000000000147
r8=fffffa6005293c30 r9=0000000000000000 r10=fffff8000212eea0
r11=00000000002781a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KxWaitForLockOwnerShip+0x12:
fffff800`01ec0b32 48890a mov qword ptr [rdx],rcx ds:00000000`000000c0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80001eb312e to fffff80001eb3390
STACK_TEXT:
fffffa60`05293828 fffff800`01eb312e : 00000000`0000000a 00000000`000000c0 00000000`0000000c 00000000`00000001 : nt!KeBugCheckEx
fffffa60`05293830 fffff800`01eb200b : 00000000`00000001 fffff960`001acd27 0000000c`a3801f00 00000008`d3a7905a : nt!KiBugCheckDispatch+0x6e
fffffa60`05293970 fffff800`01ec0b32 : fffff880`025de390 00000000`00010140 00000000`00000020 fffff800`020e6f4f : nt!KiPageFault+0x20b
fffffa60`05293b00 fffff800`01f027be : 00000008`d3a7905a 00000000`00000000 fffffa60`005ec970 00000000`00000147 : nt!KxWaitForLockOwnerShip+0x12
fffffa60`05293b30 fffff800`01ec0869 : 00000008`d3a7694a 00000000`00000000 00000000`00000147 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x3995
fffffa60`05293b60 fffff800`0212eefd : 00000000`00000001 00000000`00240000 00000000`00000147 fffffa60`05293c30 : nt!KeDelayExecutionThread+0x4ed
fffffa60`05293bf0 fffff800`01eb2e33 : fffffa80`0673b060 00000000`00000000 ffffffff`ffffd8f0 00000000`00000000 : nt!NtDelayExecution+0x5c
fffffa60`05293c20 00000000`77335dba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0945f6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77335dba

STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`01ec0b32 48890a mov qword ptr [rdx],rcx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KxWaitForLockOwnerShip+12
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 479192b7
FAILURE_BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12
BUCKET_ID: X64_0xA_nt!KxWaitForLockOwnerShip+12
Followup: MachineOwner
---------

ah thank you! i just ran sfc/scannow but it did not find any integrity violations. i am not at the computer, i had to vnc that, so i will not be able to run the memory diagnostic until i get home later today becauase of the restart needed.
i suppse maybe its possible the cpu is overheating. to be honest i haven't gotten in the case and cleaned out the heatsink for a while and i never liked the slow rpm fan my cooler has. maybe i need an upgrade. at what temperature would it be likely for a bluescreen to happen? 70s? 80s?
any way i got a good place to start. thanks for the quick help! i'll post back if i come up with anything useful

I would make sure your RAM voltage and FSB are set correctly to match your CPU. Download memtest86 and test each stick of RAM separate. If they all pass, test together for 24 hours.