Win10 crash - minidumps included

[C0RR0SIVE]

Can someone poke at these minidumps and let me know what they think? Lately my little sister has been having a few random crashes, shrugged it off till it crashed twice in this last week. I looked at the minidumps but not exactly a pro in reading them.

While waiting for a response I will go ahead and do a memory test on this laptop (it's an OLD Dell Vostro 1500) and see if that turns anything up.

https://mega.nz/#!g4wVXZIL!KzMPkALwsKOUhvdEvGYrPeX5TVRHvxjyZ031M7hQYio

 

[carnageX]

The crash log from 11/13 as well as the one from 10/12 shows:

Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 12B, {ffffffffc00002c4, 3f5, d91082a450, ffffd0007c22e000}

Probably caused by : hardware ( REGION_PAGED_OUT )

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

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

FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page.  This is a hardware memory error.
Arguments:
Arg1: ffffffffc00002c4, virtual address mapping the corrupted page
Arg2: 00000000000003f5, physical page number
Arg3: 000000d91082a450, zero
Arg4: ffffd0007c22e000, zero

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


BUGCHECK_STR:  PAGE_NOT_ZERO

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

STACK_TEXT:  
ffffd000`7dab6348 fffff803`eb24ebb9 : 00000000`0000012b ffffffff`c00002c4 00000000`000003f5 000000d9`1082a450 : nt!KeBugCheckEx
ffffd000`7dab6350 fffff803`eb1cd25f : 00000000`00000003 ffffe000`12e1c050 ffffe000`12e1c050 00000000`00000003 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0xe5
ffffd000`7dab63c0 fffff803`eb12017e : ffffe000`13768220 ffffdf1b`51c715f2 ffffe000`15067040 fffff803`eb12194c : nt! ?? ::FNODOBFM::`string'+0x6215f
ffffd000`7dab64a0 fffff803`eb11ff85 : 00000000`00000002 ffffe000`155c6540 ffffe000`12e1c050 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xb6
ffffd000`7dab6500 fffff803`eb11fcbd : ffffe000`ffffffff ffffe000`00001a45 00000000`000007b7 ffffe000`13768220 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x1e1
ffffd000`7dab65a0 fffff803`eb11f37d : ffffd000`7dab6790 ffffe000`13768220 00000000`00000040 ffffe000`147dd4c0 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc1
ffffd000`7dab6660 fffff803`eb11f2b1 : ffffe000`12e1c000 ffffe000`13768220 ffffe000`12e1c000 fffff803`eb11f298 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x91
ffffd000`7dab66d0 fffff803`eb08a925 : ffffe000`13768220 ffffd000`7dab6790 ffffe000`12e1d1d4 fffff803`eb0f4ac0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x19
ffffd000`7dab6700 fffff803`eb11f1c3 : 00000000`00000003 fffff803`eb350300 ffffe000`15067000 ffffe000`12e1c000 : nt!KeExpandKernelStackAndCalloutInternal+0x85
ffffd000`7dab6750 fffff803`eb11dc88 : ffffe000`13768220 00000000`00000801 ffffe000`12e1c000 00000000`00000002 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xb7
ffffd000`7dab6820 fffff803`eb11d92f : ffffe000`13768220 ffffe000`13768220 ffffe000`12e1c000 fffff803`eb350300 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1c8
ffffd000`7dab6880 fffff803`eb11bad1 : 00000000`0000000c ffffe000`1034eb60 00000000`00000001 ffffe000`1034eab0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc7
ffffd000`7dab6910 fffff803`eb11b965 : ffffe000`1034ea60 ffffd000`7dab69d0 ffffd000`00000001 fffff680`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x165
ffffd000`7dab6990 fffff803`eb03ff81 : ffffd000`200473e6 00000000`00000000 00000000`0000047b fffff803`eb02c1f2 : nt!SmPageRead+0x75
ffffd000`7dab69d0 fffff803`eb03e1e8 : 00000000`00000002 ffffe000`127ae778 ffffe000`1034ea60 00000000`00000000 : nt!MiIssueHardFaultIo+0x129
ffffd000`7dab6a50 fffff803`eb02d93d : 00000000`c0033333 ffffe000`127ae778 000000e1`82a07f50 ffffd000`00000000 : nt!MiIssueHardFault+0x168
ffffd000`7dab6af0 fffff803`eb1655bd : ffffe000`147dd080 000000e1`82a28190 000000e1`82a77160 ffffc000`0ebea8e0 : nt!MmAccessFault+0x39d
ffffd000`7dab6c40 00007ffa`dbf79e20 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13d
000000e1`83eddcb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`dbf79e20


STACK_COMMAND:  kb

SYMBOL_NAME:  REGION_PAGED_OUT

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  PAGE_NOT_ZERO_REGION_PAGED_OUT

BUCKET_ID:  PAGE_NOT_ZERO_REGION_PAGED_OUT

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:page_not_zero_region_paged_out

FAILURE_ID_HASH:  {2116c973-78f0-ac8c-fd80-e8f7849726ae}

Followup: MachineOwner

Specifically this bit:

FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page.  This is a hardware memory error.

Definitely sounds like a memory error going off of just those ones.

 

[C0RR0SIVE]

Thanks for the info Carnage, I will post back with the memory test results shortlyish. 4GB takes awhile on this old thing.

 

[carnageX]

Good luck, let us know how it turns out.

 

[C0RR0SIVE]

Well, Memtest came back clean on one pass, going to let it go through a few more...

This computer has an SSD - but it reports health as good, so I am now at a loss...

 

[carnageX]

Possibly a corrupt page file? Have you tried removing it and re-adding it, or not having one at all?

 

[C0RR0SIVE]

Possibly a corrupt page file? Have you tried removing it and re-adding it, or not having one at all?

That I have not attempted - will try that tonight once she gives her laptop up again.