Add'l BSODs (1909)

Thanks Phil.

I'm not sure if the description of the args match, arg1 looks to be an NTSTATUS error code, arg2 I doubt is the physical page and args 3 and 4 clearly are not zero. Double-checking the documentation on the 0x12B it looks more like the descriptions of the args are mixed up.

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: 0000000000000d03, physical page number
Arg3: 0000016d9f866a60, zero
Arg4: ffff86816ff74000, zero

Clearly the store manager is involved which suggests that arg1 is the error code/type of failure, arg2 is the compressed size of the page being read, arg3 is the source buffer and arg4 is the target buffer.

Code:

PROCESS_NAME:  MemCompression

3: kd> k
 # Child-SP          RetAddr           Call Site
00 fffffb88`509150f8 fffff804`3492402b nt!KeBugCheckEx
01 fffffb88`50915100 fffff804`3486545a nt!ST_STORE<SM_TRAITS>::StDmPageError+0xfb
02 fffffb88`50915150 fffff804`3475ff74 nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x1054c6
03 fffffb88`50915230 fffff804`3475fdf2 nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0
04 fffffb88`50915280 fffff804`3475fc1b nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186
05 fffffb88`50915320 fffff804`3475fa61 nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xcb
06 fffffb88`509153d0 fffff804`3475f971 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
07 fffffb88`50915450 fffff804`3464f678 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
08 fffffb88`50915480 fffff804`34763301 nt!KeExpandKernelStackAndCalloutInternal+0x78
09 fffffb88`509154f0 fffff804`3474c721 nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xcd
0a fffffb88`509155c0 fffff804`3474c307 nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1a5
0b fffffb88`50915610 fffff804`347621e3 nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbf
0c fffffb88`509156a0 fffff804`34763cef nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
0d fffffb88`50915710 fffff804`34693eaf nt!SmPageRead+0x33
0e fffffb88`50915760 fffff804`346949d9 nt!MiIssueHardFaultIo+0x117
0f fffffb88`509157b0 fffff804`346587fb nt!MiIssueHardFault+0x489
10 fffffb88`50915860 fffff804`347d041e nt!MmAccessFault+0x40b
11 fffffb88`50915a00 00007ff8`1fc7c474 nt!KiPageFault+0x35e
12 00000054`f7fff060 00000000`00000000 0x00007ff8`1fc7c474

System file corruption appears to be the type of failure.

Code:

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

Although system file corruption is involved here, this crash only occurs when memory corruption on physical memory is the case. Therefore I suggest that you run a memory test first before anything else.
Please run memtest86.
How to boot MemTest86: PassMark MemTest86 - Memory Diagnostic Tool - Technical Information.
Note, memtest86 has a limit of 4 passes total. We need at least 8 passes to get anything indicative and therefore memtest86 needs to be run at least twice.

It's best to run the tests one after another immediately because after the first test some heat may be present and the RAM should still function fine even with some heat.

Great.

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc /scannow" (without quotes) and press enter
• It may take a while for SFC to finish, let it run until it finishes.

Let me know what SFC reports, i.e. found corruption and fixed them, unable to resolve corruption or no corruption detected.

Good to hear, use your pc as you normally would and see how things go for the next couple days.