BSOD not specific to loading but always within 5 min of cold start

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002aa7150, 0, ffffffffffffffff}

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

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002aa7150, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb9100
GetUlongFromAddress: unable to read from fffff80002cb91c0
 0000000000000000 Nonpaged pool

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

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

BUGCHECK_STR:  0x1E_c0000005_R

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002acc738 to fffff80002a81bc0

STACK_TEXT:  
fffff880`09f9ddd8 fffff800`02acc738 : 00000000`0000001e ffffffff`c0000005 fffff800`02aa7150 00000000`00000000 : nt!KeBugCheckEx
fffff880`09f9dde0 fffff800`02a81242 : fffff880`09f9e5b8 cffffa80`07fc0800 fffff880`09f9e660 00000000`00000008 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`09f9e480 fffff800`02a7fb4a : fffffa80`0869a5d0 fffff880`09f9e6e0 00000000`00000007 fffff800`02cbc500 : nt!KiExceptionDispatch+0xc2
fffff880`09f9e660 fffff800`02aa7150 : fffffa80`0e58c3a0 00000000`00000000 00000000`2caf0000 fffff800`02aa140c : nt!KiGeneralProtectionFault+0x10a
fffff880`09f9e7f0 fffff800`02aa590f : fffffa80`0c5d0000 00000000`00000000 fffffa80`07fce000 00000000`00000000 : nt!MiReplenishPageSlist+0xc0
fffff880`09f9e860 fffff800`02a8f044 : 00000000`00000000 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
fffff880`09f9e980 fffff800`02a7fcee : 00000000`00000001 00000000`2cbf8000 00000000`00001f01 00000000`2caf0040 : nt!MmAccessFault+0x1224
fffff880`09f9eae0 000007fe`fd9758e3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`04eff088 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd9758e3


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiReplenishPageSlist+c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

IMAGE_VERSION:  6.1.7601.18247

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!MiReplenishPageSlist+c0

BUCKET_ID:  X64_0x1E_c0000005_R_nt!MiReplenishPageSlist+c0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1e_c0000005_r_nt!mireplenishpageslist+c0

FAILURE_ID_HASH:  {99c7b38b-f313-cdbd-89d5-efeb383b1b1c}

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

As we have tken all the possible steps including a clean install, and nothing appeared as the source of the issue, I think it is the time to concentrate on the motherboard itself. Unfortunately we cannot test it, so we cannot blame on it in a remote assistance.

SAllen61 said:

I got a ASUS P8Z77-V LK how about going to a ASUS P8Z77-V LX?

Any advice?

If you can obtain a motherboard which will work with your existing CPU, then no need to swap to CPU.

Good news. Let us know how it is going.