BSOD followed by dump of physical memory

SystemId · 22 Nov 2012

Hi, sorry I can't give more info as the blue screen flashes up for less than a second before restarting.

It doesn't seem to happen when I'm doing any one particular thing, I could be watching netflix, listening to spotify etc. The .zip file attached came from a crash when I was running the SF diagnostic tool!

Thanks in advance for any help you can give me.

Arc · 23 Nov 2012

Hello SystemId.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 137dfc, 3, 15dc60}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 0000000000137dfc, page frame number
Arg3: 0000000000000003, current page state
Arg4: 000000000015dc60, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800035100ec to fffff80003489fc0

STACK_TEXT:  
fffff880`05472d18 fffff800`035100ec : 00000000`0000004e 00000000`00000099 00000000`00137dfc 00000000`00000003 : nt!KeBugCheckEx
fffff880`05472d20 fffff800`0343b4a1 : 00000000`00137dfc 00000000`00127c2c fffffa80`03774840 fffffa80`06f54f58 : nt!MiBadShareCount+0x4c
fffff880`05472d60 fffff800`03457c52 : 00000000`00000000 fffffa80`06c59a00 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2c8b5
fffff880`05472e50 fffff880`012cf53f : fffffa80`0a34edb8 00000000`00000000 fffff8a0`00000000 00000000`00000000 : nt!CcPurgeCacheSection+0x172
fffff880`05472ec0 fffff880`012f00c3 : fffff880`05473730 fffff8a0`08a79b40 fffff8a0`013658f0 fffff880`054731c8 : Ntfs!NtfsDeleteFile+0x57b
fffff880`05473140 fffff880`0125ec99 : fffffa80`072374e0 00000000`000007ff fffff880`05473690 00000000`00006000 : Ntfs!NtfsCommonCleanup+0x1653
fffff880`05473550 fffff800`03495c48 : fffff880`05473690 fffff880`054738c8 fffffa80`07ba3650 fffffa80`06c98c80 : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`05473580 fffff880`0125ed12 : fffff880`0125ec80 fffffa80`07f72a30 fffff880`05473900 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`05473660 fffff880`012fda94 : fffff880`05473730 fffff880`05473730 fffff880`05473730 fffff880`01070cdf : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`054736d0 fffff880`01006bcd : fffff880`05473730 fffffa80`07268c10 fffffa80`07268fb0 fffffa80`06e07c30 : Ntfs!NtfsFsdCleanup+0x144
fffff880`05473940 fffff880`010056df : fffffa80`07ba3650 00000000`00000000 fffffa80`06c98900 fffffa80`07268c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24d
fffff880`054739d0 fffff800`0378d5ef : fffffa80`07268c10 fffffa80`07217060 00000000`00000000 fffffa80`06e2fd00 : fltmgr!FltpDispatch+0xcf
fffff880`05473a30 fffff800`0377cd14 : 00000000`00000000 fffffa80`07217060 fffffa80`071d0100 fffffa80`06e2fd00 : nt!IopCloseFile+0x11f
fffff880`05473ac0 fffff800`0377cad1 : fffffa80`07217060 fffffa80`00000001 fffff8a0`0c4664e0 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`05473b40 fffff800`0377d094 : 00000000`0000015c fffffa80`07217060 fffff8a0`0c4664e0 00000000`0000015c : nt!ObpCloseHandleTableEntry+0xb1
fffff880`05473bd0 fffff800`03489253 : fffffa80`07226060 fffff880`05473ca0 00000000`00981300 00000000`00008000 : nt!ObpCloseHandle+0x94
fffff880`05473c20 00000000`770f140a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0028cb48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770f140a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
2 errors : !nt (fffff80003489010-fffff80003489570)
fffff80003489010 *c4  45  ab  02  65  48  8b  1c  25  88  01  00  00  0f  0d  8b .E..eH..%.......
...
fffff80003489570 *64  0f  1f  84  00  00  00  00  00  0f  1f  80  00  00  00  00 d...............

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

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, per RAM module per slot.

Let us know the results.