Share via

What is hardware memory error?

Anonymous
2023-06-25T03:34:51+00:00

So i got a bluescreen with a stop code "FAULTY_HARDWARE_CORRUPTED_PAGE" then i went to check on the dmp files to see whats happen, it appears that it says something like:

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: 0000000000000f53, physical page number Arg3: 000001908525a6e0, zero Arg4: ffff8e01168fb000, zero

I'm not sure about which one is goes wrong is it my ssd, hdd or my RAM because i have both of them on my laptop so i hope someone here might able to tell

Here's the rest of the debugging dmp files in case it needed

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 5390

Key  : Analysis.Elapsed.mSec
Value: 11842

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key  : BlackBox.SmDecompressionFailure.CompressedSize
Value: 0xf53

Key  : BlackBox.SmDecompressionFailure.CompressionFormat
Value: 0x3

Key  : BlackBox.SmDecompressionFailure.SourceDataHash
Value: 0x3e5d0708

Key  : BlackBox.SmDecompressionFailure.SourceDataOffset
Value: 0x1a6e0

Key  : BlackBox.SmDecompressionFailure.SourcePFN1
Value: 0x26e5d

Key  : BlackBox.SmDecompressionFailure.SourcePFN2
Value: 0x8df5c

Key  : BlackBox.SmDecompressionFailure.TargetPFN
Value: 0x35f86

Key  : Bugcheck.Code.LegacyAPI
Value: 0x12b

Key  : Dump.Attributes.AsUlong
Value: 8

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key  : Failure.Bucket
Value: 0x12B\_c00002c4\_StCtDecompressFailed\_nt!ST\_STORE\_SM\_TRAITS\_::StDmPageError

Key  : Failure.Hash
Value: {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}

BUGCHECK_CODE: 12b

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: f53

BUGCHECK_P3: 1908525a6e0

BUGCHECK_P4: ffff8e01168fb000

FILE_IN_CAB: 062523-15234-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MemCompression

STACK_TEXT:
ffff8a0f1cfdf518 fffff8035079a542 : 000000000000012b ffffffffc00002c4 0000000000000f53 000001908525a6e0 : nt!KeBugCheckEx ffff8a0f1cfdf520 fffff80350639de3 : 0000000000000000 00000000c00002c4 ffff8e01168fb000 000000000011672e : nt!ST_STORE<SM_TRAITS>::StDmPageError+0x10a ffff8a0f1cfdf580 fffff8035045b9a1 : 0000000000000004 fffff8035055758a 0000000000000000 0000000000000001 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x1de41f ffff8a0f1cfdf640 fffff803505572f0 : 0000000000000001 000000000001a6e0 0000000000000000 ffffca8e00079000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa5 ffff8a0f1cfdf690 fffff80350557c04 : fffff803ffffffff ffffca8e024ed000 ffff8a0f1cfdf770 ffffca8dfeb2f0a0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x180 ffff8a0f1cfdf730 fffff80350557ded : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc8 ffff8a0f1cfdf7e0 fffff8035045c071 : ffffca8df6864000 ffffca8dfeb2f0a0 ffffca8e024ed000 ffffca8df68659c0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85 ffff8a0f1cfdf860 fffff803504ad488 : ffffca8df68e2040 ffffca8df6864000 ffffca8d00000000 0000000000000064 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21 ffff8a0f1cfdf890 fffff8035045cb57 : fffff8035045c050 ffff8a0f1cfdf930 0000000000000003 0000000000000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78 ffff8a0f1cfdf900 fffff8035045713c : 0000000000000000 0000000000000000 0000006b477ceb47 fffff80350f23c68 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7 ffff8a0f1cfdf9d0 fffff80350587970 : ffffca8dfeb2f0c8 0000006b477ceb47 ffffffffffffffff fffff80350f23c68 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac ffff8a0f1cfdfa20 fffff8035048e5c5 : 0000000000989680 ffffca8df68e2040 fffff803505878d0 ffffca8d00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmAsyncReadQueueWorker+0xa0 ffff8a0f1cfdfa70 fffff803505268f5 : ffffca8df68e2040 0000000000000080 ffffca8df2ac5080 0000000000000000 : nt!ExpWorkerThread+0x105 ffff8a0f1cfdfb10 fffff80350604c68 : ffff8e00edd5c180 ffffca8df68e2040 fffff803505268a0 0000000000000000 : nt!PspSystemThreadStartup+0x55 ffff8a0f1cfdfb60 0000000000000000 : ffff8a0f1cfe0000 ffff8a0f1cfd9000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME: nt!ST_STORE<SM_TRAITS>::StDmPageError+10a

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.3086

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 10a

FAILURE_BUCKET_ID: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-06-25T04:56:12+00:00

    You're welcome!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-06-25T04:51:25+00:00

    Thank you i will try this

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-06-25T04:07:18+00:00

    Hello! My name is Mostafa; I will assist you today.

    I'm sorry that you are experiencing this issue. The minidump analysis points to a BSOD caused by ntkrnlmp.exe, although it doesn't specify any particular driver as the culprit. ntkrnlmp.exe usually happens by memory corruption.

    Please Update BIOS and chipset driver by visiting your computer support page website.

    Disable any overclocking and XMP on your computer and reset BIOS setting to its default.

    Check your memory

    1. Click the Start button, type memory and click Run as administrator to start Windows Memory Diagnostic with full privileges.
    2. Now, click on the first option. Restart now and check for problems.
    3. After the restart, the system will run a diagnostic on your RAM modules and find any possible problems. Unfortunately, you must replace the damaged module(s) if it does.

    Please let me know the result. Thank you.

    Was this answer helpful?

    0 comments