BSOD every 4-5 Hours while gaming, browsing or idling.

This has been a consistent problem for me and some friends as this has interrupted many of our games and caused us to start over our matches. The error is STOP: 0x7E with a iaStor.sys and a bunch of parameters. The dmp files are found below, I have heard this has to do with Intel Rapid Storage or something like that? Not too sure. Thanks in advanced.

ICIT2LOL said:

Hello and welcome NIN there seems to be something quite amiss in the machine with the bug check as shown

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffffffffffffd0, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800034d6dac, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------

Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003705100
GetUlongFromAddress: unable to read from fffff800037051c0
 ffffffffffffffd0 
FAULTING_IP: 
nt!ObfDereferenceObject+2c
fffff800`034d6dac f0480fc11f      lock xadd qword ptr [rdi],rbx
MM_INTERNAL_CODE:  0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
TRAP_FRAME:  fffff880037e18b0 -- (.trap 0xfffff880037e18b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034d6dac rsp=fffff880037e1a40 rbp=fffff800036732d8
 r8=fffff880009d3740  r9=0000000000000000 r10=0000000000000080
r11=fffffa800c756968 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ObfDereferenceObject+0x2c:
fffff800`034d6dac f0480fc11f      lock xadd qword ptr [rdi],rbx ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff8000354bbf0 to fffff800034cdbc0
STACK_TEXT:  
fffff880`037e1748 fffff800`0354bbf0 : 00000000`00000050 ffffffff`ffffffd0 00000000`00000001 fffff880`037e18b0 : nt!KeBugCheckEx
fffff880`037e1750 fffff800`034cbcee : 00000000`00000001 ffffffff`ffffffd0 00000000`00000000 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`037e18b0 fffff800`034d6dac : 00000000`00000000 00000000`00000000 fffffa80`0c756968 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`037e1a40 fffff880`0c39c0d4 : fffff800`036732d8 fffff800`038b8830 00000000`00000000 fffffa80`0d1c3100 : nt!ObfDereferenceObject+0x2c
fffff880`037e1aa0 fffff800`036732d8 : fffff800`038b8830 00000000`00000000 fffffa80`0d1c3100 fffff880`009cf180 : BEDaisy+0x1a0d4
fffff880`037e1aa8 fffff800`038b882f : 00000000`00000000 fffffa80`0d1c3100 fffff880`009cf180 00000000`00000001 : nt!ExWorkerQueue+0x58
fffff880`037e1ab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopLoadDriver+0xdaf

STACK_COMMAND:  kb
FOLLOWUP_IP: 
BEDaisy+1a0d4
fffff880`0c39c0d4 ??              ???
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  BEDaisy+1a0d4
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: BEDaisy
IMAGE_NAME:  BEDaisy.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  5499cd67
FAILURE_BUCKET_ID:  X64_0x50_BEDaisy+1a0d4
BUCKET_ID:  X64_0x50_BEDaisy+1a0d4
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x50_bedaisy+1a0d4
FAILURE_ID_HASH:  {83f2b142-6dfa-d646-ff6b-06b6113ae3bb}
Followup: MachineOwner

This may give you some idea on what that is about
Driver Reference Table - BEDaisy.sys

I installed the update for battleye and restarted my computer, and it BSODed again. Im pretty sure that isnt the error code as I get a iaStor.sys error STOP: 0x7E

Here is a picture of what the BSOD looks like.