Issue with BSOD "faulty hardware corrupted"

Question

Having issue with BSOD intermittently not too sure what’s happening running on win 11 left it to sleep mode every time try to resume this happens Blue screen “faulty hardware corrupted” hope someone out there can advise on what this minidump means

further analysis to the hardware minidump shows the following

Loading Dump File [C:\Windows\Minidump\122621-19375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22000 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff806`57800000 PsLoadedModuleList = 0xfffff806`58429750
Debug session time: Sun Dec 26 12:21:12.082 2021 (UTC + 8:00)
System Uptime: 1 days 11:03:49.059
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
.........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`57c159c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffac03`345cee00=000000000000012b
7: 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: 00000000000004fd, physical page number
Arg3: 000002b2282c3d40, zero
Arg4: ffff87814ce5b000, zero

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 5640

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 56545

    Key  : Analysis.Init.CPU.mSec
    Value: 1765

    Key  : Analysis.Init.Elapsed.mSec
    Value: 72240

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 96

    Key  : BlackBox.SmDecompressionFailure.CompressedSize
    Value: 0x4fd

    Key  : BlackBox.SmDecompressionFailure.CompressionFormat
    Value: 0x3

    Key  : BlackBox.SmDecompressionFailure.SourceDataHash
    Value: 0xfe8d1a9e

    Key  : BlackBox.SmDecompressionFailure.SourceDataOffset
    Value: 0x13d40

    Key  : BlackBox.SmDecompressionFailure.SourcePFN1
    Value: 0x25f2c6

    Key  : BlackBox.SmDecompressionFailure.SourcePFN2
    Value: 0x2171aa

    Key  : BlackBox.SmDecompressionFailure.TargetPFN
    Value: 0x21a963

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1

FILE_IN_CAB:  122621-19375-01.dmp

BUGCHECK_CODE:  12b

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: 4fd

BUGCHECK_P3: 2b2282c3d40

BUGCHECK_P4: ffff87814ce5b000

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MemCompression

STACK_TEXT:  
ffffac03`345cedf8 fffff806`57df57d3     : 00000000`0000012b ffffffff`c00002c4 00000000`000004fd 000002b2`282c3d40 : nt!KeBugCheckEx
ffffac03`345cee00 fffff806`57c4a128     : 00000000`00000200 00000000`00000003 ffff8781`4ce5b000 00143de2`0009d9ba : nt!ST_STORE<SM_TRAITS>::StDmPageError+0xfb
ffffac03`345cee50 fffff806`57b8d544     : ffffe603`9f18ccc0 00000000`00000001 ffffe603`00013d40 ffffe603`a7915050 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0xbcbb8
ffffac03`345cef20 fffff806`57b8d3b6     : 00000000`00000001 00000000`00000006 ffffe603`9ea61050 ffffe603`00088000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0x8c
ffffac03`345cef60 fffff806`57b8d1cb     : ffffe603`ffffffff ffffe603`a7915000 ffffac03`345cf040 ffffe603`9f18ccc0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x172
ffffac03`345cf000 fffff806`57b8d01e     : ffffac03`345cf239 00000000`00000000 ffffe603`9eb775f0 00000000`20150626 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0x9f
ffffac03`345cf0b0 fffff806`57b8cf21     : ffffe603`9ea61000 ffffe603`9f18ccc0 ffffe603`a7915000 ffffe603`9ea629c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x92
ffffac03`345cf130 fffff806`57b5f928     : ffffe603`a5cee040 ffffe603`9ea61000 ffffe603`00000000 ffffe603`a7915000 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffac03`345cf160 fffff806`57b8f52e     : fffff806`57b8cf00 ffffac03`345cf200 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffac03`345cf1d0 fffff806`57b78823     : ffffe603`00000000 fffff806`57ad6848 00000125`e8d301f0 fffff806`58531d08 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xbe
ffffac03`345cf2a0 fffff806`57b900c0     : fffff806`58531d08 00000125`e8d301f0 ffffffff`ffffffff fffff806`58531d08 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1a7
ffffac03`345cf2f0 fffff806`57b1d10f     : 00000000`00989680 ffffe603`a5cee040 ffffe603`8d9f6e18 ffffe603`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmAsyncReadQueueWorker+0xa0
ffffac03`345cf340 fffff806`57a478f5     : ffffe603`a5cee040 ffff8781`43c4f000 ffffe603`a5cee040 00000000`00000000 : nt!ExpWorkerThread+0x14f
ffffac03`345cf530 fffff806`57c19a74     : ffff8781`43c40180 ffffe603`a5cee040 fffff806`57a478a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffac03`345cf580 00000000`00000000     : ffffac03`345d0000 ffffac03`345c9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME:  nt!ST_STORE<SM_TRAITS>::StDmPageError+fb

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.376

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  fb

FAILURE_BUCKET_ID:  0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}

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

Answer 1

Just turn it off and on again. If that doesn't work just throwing it away and getting a new one always works.

Answer 2

BSOD will automatically turn restart by itself. my new one wont be a surface device anymore after experiencing sending in for a replacement twice this year

Answer 3

To diagnose whether this is hardware or software, you should do a wipe and reimage from the official downloadable recovery image. Back up any files and data stored locally first. Go to https://support.microsoft.com/en-us/surfacerecoveryimage  

(with a different Windows computer if yours is not working properly) 

and download a recovery image for your Surface. You will need a 16GB or 32GB USB stick (also called a flash drive) formatted FAT32 (use a Windows computer).  You can't use an actual external USB hard drive for this and don't use anything larger than a 32 GB USB stick. Best to purchase and use a new, previously unused USB stick for this. Use FULL format and not quick format and give the volume a name like surfboot. Unzip/extract the recovery zip to the root of the formatted USB stick.

There are full instructions and a video at https://support.microsoft.com/en-us/help/4023512/surface-creating-and-using-a-usb-recovery-drive#download

After you do this, do not install any apps or programs, or connect to a dock or external monitors, etc., but go to Settings, Windows Update, and check for updates and keep installing until none are available. Do you still have this issue or not?