win 7 - bsod - ntoskrnl.exe (nt+0x74540)

Hello everyone,

Last week i am expiericing bsod i analysed the dump but i cannot find out why it is crashing, maybe you people can help me out?
bellow you find the dump

here are the files download here

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 19-7-2014 10:35:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071914-20342-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74540)
Bugcheck code: 0xA (0xFFFFFA8068E16F50, 0x2, 0x1, 0xFFFFF80002EA7DA0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 19-7-2014 10:35:03 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA8068E16F50, 0x2, 0x1, 0xFFFFF80002EA7DA0)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

Attention: merkelbeek

Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

If you need to add new information like the dump files, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa8068e16f50, 2, 1, fffff80002ea7da0}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )

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

2: 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: fffffa8068e16f50, memory referenced
Arg2: 0000000000000002, 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: fffff80002ea7da0, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bc100
GetUlongFromAddress: unable to read from fffff800030bc1c0
 fffffa8068e16f50 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+c0
fffff800`02ea7da0 f00fba6b1000    lock bts dword ptr [rbx+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

TRAP_FRAME:  fffff8800b6e03d0 -- (.trap 0xfffff8800b6e03d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000022f5cfc rbx=0000000000000000 rcx=0000058000000000
rdx=0000000000000050 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ea7da0 rsp=fffff8800b6e0560 rbp=fffffa8008e18740
 r8=fffff800030bf500  r9=fffffa800c5d0000 r10=fffffa800c5d1380
r11=fffff88002f65180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiReplenishPageSlist+0xc0:
fffff800`02ea7da0 f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e81ae9 to fffff80002e82540

STACK_TEXT:  
fffff880`0b6e0288 fffff800`02e81ae9 : 00000000`0000000a fffffa80`68e16f50 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0b6e0290 fffff800`02e80760 : 00000000`00000111 fffff8a0`0feb3000 fffffa80`0d51b060 fffffa80`68e16f40 : nt!KiBugCheckDispatch+0x69
fffff880`0b6e03d0 fffff800`02ea7da0 : fffff880`0b6e05f0 fffff800`02e8077d 00000000`00000001 fffff8a0`0feb3000 : nt!KiPageFault+0x260
fffff880`0b6e0560 fffff800`02ea655f : fffffa80`0c5d1360 00000000`0000007c fffffa80`08e1b740 00000000`0000007c : nt!MiReplenishPageSlist+0xc0
fffff880`0b6e05d0 fffff800`02e92982 : 00000000`00000080 80000002`00000002 fffffa80`0e536ec8 00000000`00000003 : nt!MiRemoveAnyPage+0x24f
fffff880`0b6e06f0 fffff800`02ea0975 : 00000000`00000001 00000000`39cd3ff8 fffff880`0b6e0ae0 fffff8a0`0feb49e0 : nt!MiResolveDemandZeroFault+0x9f2
fffff880`0b6e07e0 fffff800`02e9f163 : 00000000`002fee6a 00000000`39cd3ff8 fffff680`001ce698 fffffa80`0e536ec8 : nt!MiResolveProtoPteFault+0x4f5
fffff880`0b6e0870 fffff800`02e8eb79 : 00000000`00000000 00000000`39cd3ff8 fffffa80`0d51b060 fffff880`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0b6e0980 fffff800`02e8066e : 00000000`00000001 00000000`39cd3ff8 00000000`04eeee01 00000000`04eee4d0 : nt!MmAccessFault+0x359
fffff880`0b6e0ae0 00000000`7706dc8b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`04eee288 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7706dc8b


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiReplenishPageSlist+c0
fffff800`02ea7da0 f00fba6b1000    lock bts dword ptr [rbx+10h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiReplenishPageSlist+c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5315a462

IMAGE_VERSION:  6.1.7601.22616

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0

BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!mireplenishpageslist+c0

FAILURE_ID_HASH:  {bfd4b47d-f7c1-0239-94a3-b05674fed1ca}

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

2: kd> .bugcheck
Bugcheck code 0000000A
Arguments fffffa80`68e16f50 00000000`00000002 00000000`00000001 fffff800`02ea7da0

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

Thats our problem, :)

Read the tutorial at the bottom of the link i sent before.