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

[Arc]

*******************************************************************************
*                                                                             *
*                        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]

I changed the bios graphic setting from auto to pcie to see if that will have anything to do with anything, it remaps memory for the iGPU otherwise I think.

 

[SAllen61]

got a different BSOD this morning before I changed the BIOS setting for the graphics.

PC Diag attached

I remark that this all seems odd that this behavior did not start until Dec 16th I believe was the begin date.

 

[SAllen61]

id be willing to swap out the motherboard I guess but how about the cpu? or both?

 

[SAllen61]

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

Any advice?

 

[Arc]

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.

 

[SAllen61]

ok, ordered another LK since the drivers and such are already set up for it.
take me a week to get it, still holding

 

[SAllen61]

new motherboard in now.......waiting to see what is going to happen

 

[Arc]

Good news. Let us know how it is going.

 

[SAllen61]

Well apparently it is not the motherboard.

Same condition BSOD. cold boot and within 5 min It happens.

Before I put in the new motherboard the BSOD was getting more vicious, it started happening sooner and sooner after a cold boot until I started getting a failure to windows restart when it was coming back up. I would select start windows normally which progressively got worse to where when it BSOD on the cold boot and I selected launch win normally it would cycle crash about 5 times (I would keep selecting start win normally) then suddenly it would seem ok I'm good now and finally start up.

now it seems I'm back to a 5 min cold start BSOD.

This is some serious condition......


Help!

 

[SAllen61]

tonight after work I gonna try the clean boot diagnostic ref: Perform a clean startup to determine whether background programs are interfering with your game or program

 

[SAllen61]

Clean boot up with no background services did not effect BSOD or it's behavior.

had another one SF diag attached:

I will try a safe mode startup next time and wait to see if it's gonna crash then.

 

[SAllen61]

Still getting the regular cold startup BSOD with a different error basically.....I just don't know what to do.
I guess I have to just start over and hang up on intel and stay with AMD......the only thing left is the chip itself and that is too expensive to replace on a thought it might fix things.

 

[Arc]

Sorry, somehow I got unsubscribed from your thread and failed to get the notifications.

In post #68, you said you changed the board.

Motherboard info from the data supplied in the first post:

BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 1301
BiosReleaseDate = 11/07/2013
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
SystemFamily = To be filled by O.E.M.
SystemVersion = System Version
SystemSKU = SKU
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = P8Z77-V LK
BaseBoardVersion = Rev X.0x

Motherboard information from the latest update:

BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 1001
BiosReleaseDate = 02/01/2013
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
SystemFamily = To be filled by O.E.M.
SystemVersion = System Version
SystemSKU = SKU
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = P8Z77-V LK
BaseBoardVersion = Rev X.0x

Same board with an older BIOS version only. Have you got a replacement from the vendor?

As a test, can you remove two RAM sticks, and run the computer with 8 GB RAM only?

 

[SAllen61]

Yes, got a direct board replacement but have not upgraded to the latest bios like the other board.
Already tried resorting back to the two memory sticks, with no change of behavior.

 

[SAllen61]

got another BSOD right after last post.

I deleated all the prior minidumps that went with the older board.

These minidumps are all new ones with the new board in.
did a chkdsk /r after the BSOD last night, apparently the BSOD's are leaving unresolved files open so I'm having to sort out the HD occasionally now as well.

Just getting really tired of all this, I'm planning on trashing the Intel chip and board and going back to AMD.

 

[Arc]

Let the computer run with 8 GB memory. If it BSODs, let us see the crash dump.

 

[SAllen61]

had two BSOD's in a row this time tonight, highly unusual considering it's usual pattern of only one per cold start for the last three months.

The SF diag attached contains 8 mini dumps, this includes the last two that just happened.

all 8 minidumps are on the new motherboard running 16 G's of ram.

I had pulled two x4 GB sticks prior to the new motherboard. The only item that we definitely found is one bad stick of memory which was replaced and verified by memtest86 back a couple of weeks or so ago. but yet again, replacing that stick did not effect the BSOD behavior wither running 8 GB or 16 GB of memory.

Given up hope I ordered this AMD bundle with an extra 8 GB memory stick and a coolermaster dual fan tower unit because folks were saying the CPU ran really hot with the stock fan unit:

AMD FX-8350 Eight-Core 4GHz AM3+ Processor and Gigabyte AMD GA-970A-DS3P AM3+ Motherboard and Patriot Viper Xtreme 8GB Desktop Memory Module Bundle

I guess I'm sticking with AMD, my only Intel unit out of about 12 systems over time fizzed out, never had and AMD fizz out on me.

 

[Arc]

It would be better if we could see a BSOD with not all the RAM slots utilized.

 

[SAllen61]

I'll get to it tonight