Recurring FAULTY_HARDWARE_CORRUPTED_PAGE BSOD


  1. Posts : 3
    Windows 10
       #1

    Recurring FAULTY_HARDWARE_CORRUPTED_PAGE BSOD


    Hi guys, I've been getting at least a BSOD daily, for the past 2-3 months, ever since I've purchases my current laptop. For few months, I had ThrottleStop installed, and up until a few weeks ago, I was undervolting the CPU (started with -150mV, ended at about -30mV, was still getting BSODs (not always FAULTY_HARDWARE_CORRUPTED_PAGE))

    Most if not all of my daily BSODs are FAULTY_HARDWARE_CORRUPTED_PAGE

    CPU: Core i7 9750h
    GPU: GeForce 1660 TI
    RAM: 2 x 16 GB (Kingston, 2666 MHz)


    All my drivers are up to date.
    I've also ran:
    "sfc /scannow" - found issues and were fixed,
    DISM /Online /Cleanup-Image /scanhealth & DISM /Online /Cleanup-Image /restorehealth - found no issues
    chkdisk /x /f /r - but it found nothing
    MemTestX86 - for about 4h (4 successful passes)
    HciDesign MemTest - for about 2h - no BSODs
    Prime95 - blend - for about 5h - no BSODs

    Code:
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff800`38fc2380 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc583`f7c27520=000000000000012b
    11: 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: 00000000000008c2, physical page number
    Arg3: 000001909b019c00, zero
    Arg4: ffffc70191a29000, zero
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.Sec
        Value: 2
    
        Key  : Analysis.DebugAnalysisProvider.CPP
        Value: Create: 8007007e on DESKTOP-2SF5UBJ
    
        Key  : Analysis.DebugData
        Value: CreateObject
    
        Key  : Analysis.DebugModel
        Value: CreateObject
    
        Key  : Analysis.Elapsed.Sec
        Value: 2
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 60
    
        Key  : Analysis.System
        Value: CreateObject
    
        Key  : Dump.Attributes.FilterDumpFile
        Value: 1
    
    
    ADDITIONAL_XML: 1
    
    DUMP_FILE_ATTRIBUTES: 0x40
      Filter Dump
    
    BUGCHECK_CODE:  12b
    
    BUGCHECK_P1: ffffffffc00002c4
    
    BUGCHECK_P2: 8c2
    
    BUGCHECK_P3: 1909b019c00
    
    BUGCHECK_P4: ffffc70191a29000
    
    SM_COMPRESSION_FORMAT: 3
    
    SM_SOURCE_PFN1: 14cf3e
    
    SM_SOURCE_PFN2: 3653d
    
    SM_SOURCE_OFFSET: 19c00
    
    SM_SOURCE_SIZE: 8c2
    
    SM_TARGET_PFN: 347265
    
    SM_BUFFER_HASH: 88308cb
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    BLACKBOXWINLOGON: 1
    
    PROCESS_NAME:  MemCompression
    
    STACK_TEXT:  
    ffffc583`f7c27518 fffff800`3912400b : 00000000`0000012b ffffffff`c00002c4 00000000`000008c2 00000190`9b019c00 : nt!KeBugCheckEx
    ffffc583`f7c27520 fffff800`39017a28 : 00000000`00000200 00000000`c00002c4 ffffc701`91a29000 00000000`00000002 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0xfb
    ffffc583`f7c27570 fffff800`38f5ff04 : 00000000`00000004 ffffc583`f7c27780 00000000`00000000 00000000`0000011b : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0xb7b04
    ffffc583`f7c27650 fffff800`38f5fd82 : 00000000`00000001 00000000`00019c00 00000000`00019c00 ffffb282`000fe000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0
    ffffc583`f7c276a0 fffff800`38f5fbab : 00000000`ffffffff ffffb282`6e8ee000 ffffc583`f7c27780 ffffb282`501fa810 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186
    ffffc583`f7c27740 fffff800`38f5f9f1 : ffffb282`6e8ee000 00000000`00000000 ffffb282`00000000 ffffb282`6ac11788 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xcb
    ffffc583`f7c277f0 fffff800`38f5f901 : ffffb282`6ac10000 ffffb282`501fa810 ffffb282`6e8ee000 ffffb282`6ac119b0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
    ffffc583`f7c27870 fffff800`38ec00f8 : ffffb282`725cb080 ffffb282`6ac10000 ffffb282`725cb080 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
    ffffc583`f7c278a0 fffff800`38f63291 : fffff800`38f5f8e0 ffffc583`f7c27950 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
    ffffc583`f7c27910 fffff800`38f4c6e1 : ffffb282`725cb080 00000000`00000000 000000a9`cbeec102 fffff800`398b8848 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xcd
    ffffc583`f7c279e0 fffff800`38f63d89 : 00000000`00000000 000000a9`cbeec102 fffff800`3938de90 fffff800`3938dc68 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1a5
    ffffc583`f7c27a30 fffff800`38ef43c5 : 00000000`00989680 ffffb282`725cb080 fffff800`38f63ce0 ffffb282`6ab61b20 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmAsyncReadQueueWorker+0xa9
    ffffc583`f7c27a70 fffff800`38e6bce5 : ffffb282`725cb080 00000000`00000080 ffffb282`4cad1080 00000000`00000001 : nt!ExpWorkerThread+0x105
    ffffc583`f7c27b10 fffff800`38fc99ca : fffff800`340f2180 ffffb282`725cb080 fffff800`38e6bc90 00000000`00000246 : nt!PspSystemThreadStartup+0x55
    ffffc583`f7c27b60 00000000`00000000 : ffffc583`f7c28000 ffffc583`f7c21000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
    
    
    SYMBOL_NAME:  nt!ST_STORE<SM_TRAITS>::StDmPageError+fb
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  fb
    
    FAILURE_BUCKET_ID:  0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError
    
    OS_VERSION:  10.0.18362.1
    
    BUILDLAB_STR:  19h1_release
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {c6a6bb4d-3b77-dff6-2d9b-75f5d0f61a50}
    
    Followup:     MachineOwner
    ---------
      My Computer


  2. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #2

    Hello and welcome to the BSOD section of TenForums

    Please follow the posting instructions at the top. This will provide us with more info for troubleshooting.
      My Computers


  3. Posts : 3
    Windows 10
    Thread Starter
       #3

    Hi. Thanks for your reply. There's just too much sensitive info in the generated logs. Is there anything in particular that would help you?
      My Computer


  4. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #4

    There is no sensitive data that I am aware of. Please PM me with examples of things you are seeing in your logs and I will investigate.
      My Computers


  5. Posts : 3
    Windows 10
    Thread Starter
       #5

    COmputer name, mac addresses, usernames, installed apps, etc. :)
      My Computer


  6. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #6

    Why do you consider any of that sensitive? Thousands of others have posted it here without a problem.
    I don't know about the other BSOD guys but I'm not going to get into another back and forth on this. Either you provide the data we ask for or you don't get the help you need, from me at least.

    Sorry if that sounds harsh or unreasonable but there are just too many BSOD systems here to take the time to work offline with you.

    Best of luck in whatever path you choose, and I mean that sincerely.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:24.
Find Us




Windows 10 Forums