BSOD - PROCESS_NAME: MemCompression

i don't understand the technical things here :

Code:

Attachment 176394*******************************************************************************
*                                                                             *
*                        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: 000000000000098d, physical page number
Arg3: 0000000014608ee0, zero
Arg4: ffffbd816d1f8000, zero

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  PAGE_NOT_ZERO

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  MemCompression

CURRENT_IRQL:  0
STACK_COMMAND:  kb

SYMBOL_NAME:  REGION_PAGED_OUT

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_PAGE_NOT_ZERO_REGION_PAGED_OUT

BUCKET_ID:  X64_PAGE_NOT_ZERO_REGION_PAGED_OUT

Followup: MachineOwner



The 2nd time BSOD result : 

*******************************************************************************
*                                                                             *
*                        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: 0000000000000683, physical page number
Arg3: 0000000013018db0, zero
Arg4: ffffb601b659b000, zero

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR:  PAGE_NOT_ZERO

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  MemCompression

CURRENT_IRQL:  0
STACK_COMMAND:  kb

SYMBOL_NAME:  REGION_PAGED_OUT

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_PAGE_NOT_ZERO_REGION_PAGED_OUT

BUCKET_ID:  X64_PAGE_NOT_ZERO_REGION_PAGED_OUT

Followup: MachineOwner

0x12B is a hardware related error.
Someone besides the owner tried to access a page which contained unexpected data.

Code:

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: 000000000000098d, physical page number
Arg3: 0000000014608ee0, zero
Arg4: ffffbd816d1f8000, zero

1: kd> !error ffffffffc00002c4
Error code: (NTSTATUS) 0xc00002c4 (3221226180) - The system file %1 has become corrupt and has been replaced.

1: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffbd81`6a0b5348 fffff801`1b64a877 nt!KeBugCheckEx
01 ffffbd81`6a0b5350 fffff801`1b5b05b9 nt!ST_STORE<SM_TRAITS>::StDmPageError+0x117
02 ffffbd81`6a0b53a0 fffff801`1b4b87bf nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0xf7dc5
03 ffffbd81`6a0b5480 fffff801`1b4b81ab nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0x7b
04 ffffbd81`6a0b54d0 fffff801`1b4b7fce nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x183
05 ffffbd81`6a0b5570 fffff801`1b4b9bef nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xea
06 ffffbd81`6a0b5630 fffff801`1b52ba71 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x6f
07 ffffbd81`6a0b5680 fffff801`1b4a5d9b nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
08 ffffbd81`6a0b56b0 fffff801`1b4e01f5 nt!KeExpandKernelStackAndCalloutInternal+0x8b
09 ffffbd81`6a0b5700 fffff801`1b4d6892 nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xad
0a ffffbd81`6a0b57d0 fffff801`1b4d60f2 nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ae
0b ffffbd81`6a0b5820 fffff801`1b4baa6a nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xce
0c ffffbd81`6a0b58a0 fffff801`1b51c18a nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x16a
0d ffffbd81`6a0b5910 fffff801`1b485439 nt!SmPageRead+0x2e
0e ffffbd81`6a0b5960 fffff801`1b484e00 nt!MiIssueHardFaultIo+0x11d
0f ffffbd81`6a0b59b0 fffff801`1b470916 nt!MiIssueHardFault+0x190
10 ffffbd81`6a0b5a50 fffff801`1b577872 nt!MmAccessFault+0xc96
11 ffffbd81`6a0b5c40 00007ffa`e4a23b12 nt!KiPageFault+0x132
12 00000042`39ffd0c0 00000000`00000000 0x00007ffa`e4a23b12

From what it looks like, it is recommended to run SFC and chkdsk.
In an admin command, copy & paste the following

Code:

sfc /scannow&chkdsk /r

This could take some time, with chkdsk you'll need to reboot the system, press Y when asked to plan chkdsk for reboot.

'Someone else' as in a driver that didn't put the data there.

Hi eaglech,

How is it going?