Windows 10: FAULTY_HARDWARE_CORRUPT_PAGE

Discus and support FAULTY_HARDWARE_CORRUPT_PAGE in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello All, I have had four system crashes in the past 3~4 months, two have said KERNEL_SECURITY_CHECK_FAIL, but the first one was from my mouse... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by win7betterthanwin8, Nov 30, 2020.

  1. FAULTY_HARDWARE_CORRUPT_PAGE


    Hello All, I have had four system crashes in the past 3~4 months, two have said KERNEL_SECURITY_CHECK_FAIL, but the first one was from my mouse sliding off my desk, off my leg, and hitting the side of the case. The second one was when I was playing a game, I do not know why that one happened, so I run Memory Diagnostic and SFC, no BSOD for 2 months. Yay! Until this Saturday 11/28/20.FAULTY_HARDWARE_CORRUPT_PAGE when shutting down my PC. I used an app to read the .dmp file, and apparently the kernel had some error or crash or something. I update all drivers and run SFC, behold, corrupt files found. Successfully repaired according to my PC. Today 11/30/20 I was playing a game and I hear BRRRRRRRRRRR [ : ] [ ]


    FAULTY_HARDWARE_CORRUPT_PAGE. I'll run SFC again tomorrow, and Memory Diagnostic. Let me know if I should try DSIM, CHKDSK or do a re-install if the Memory Diagnostic doesn't find anything. If this helps, my hardware may be obsolete in some respects besides RAM, 16GB set from Crucial I have an Intel core i5 processor, Nvidia GeForce GTX 660 GPU. Should be well more than what I would need to run the games I was playing, so it couldn't be that. Please comment any suggestions you may have. Thanks!

    :)
     
    win7betterthanwin8, Nov 30, 2020
    #1

  2. Windows 10 upgrade - "FAULTY_HARDWARE_CORRUPT_PAGE" crash BSOD

    Hello,

    I have an Asus TP300L (6GB memory, Intel Core i5-4210U, HDD 500GB) that continually has the BSOD after my upgrade to Windows 10. When it crashes it has the following error: "FAULTY_HARDWARE_CORRUPT_PAGE". I have looked through all the message boards, and
    it appears to be a common problem. My brother tried every test he knew of and he said that it appears my computer is running fine. I have tried everything online and it just seems to keep crashing.

    I have read that the crashes do not damage the computer, so normally I would not care about the inconvenience. However, I am starting online classes and the exams are done on my laptop and I am worried that it will crash in the middle of my exam. The computer
    is only 1 1/2 years old, so it would be a shame to replace it.

    My brother suggested that I post the memory dump on here and maybe someone can help me read it! I would appreciate any help to try to resolve this problem!

    Thank you very much in advance! FAULTY_HARDWARE_CORRUPT_PAGE :)

    -------------------------------------------------------------------

    Memory Dump:

    Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Bitmap Dump File: Only kernel address space is available

    ************* Symbol Path validation summary **************

    Response Time (ms) Location

    Deferred SRV*C:\Windows\symbol_cache*Symbol information

    Symbol search path is: SRV*C:\Windows\symbol_cache*Symbol information

    Executable search path is:

    Windows 8 Kernel Version 10586 MP (4 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Built by: 10586.545.amd64fre.th2_release.160802-1857

    Machine Name:

    Kernel base = 0xfffff801`e848b000 PsLoadedModuleList = 0xfffff801`e8768cf0

    Debug session time: Fri Aug 12 20:22:39.338 2016 (UTC - 7:00)

    System Uptime: 1 days 5:49:46.082

    Loading Kernel Symbols

    .............................................................Page bad76 not present in the dump file. Type ".hh dbgerr004" for details

    ..

    ................................................................

    ........................................................

    Loading User Symbols

    Loading unloaded module list

    .................

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 12B, {ffffffffc00002c4, 15e, 28e847bbd80, ffffd000211a1000}

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Probably caused by : hardware ( REGION_PAGED_OUT )

    Followup: MachineOwner

    ---------

    0: 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: 000000000000015e, physical page number

    Arg3: 0000028e847bbd80, zero

    Arg4: ffffd000211a1000, zero

    Debugging Details:

    ------------------

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    Page 1c0 not present in the dump file. Type ".hh dbgerr004" for details

    BUGCHECK_STR: PAGE_NOT_ZERO

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

    STACK_TEXT:

    ffffd000`931b8268 fffff801`e868b424 : 00000000`0000012b ffffffff`c00002c4 00000000`0000015e 0000028e`847bbd80 : nt!KeBugCheckEx

    ffffd000`931b8270 fffff801`e85f597b : 00000000`00000200 ffffe001`d0c95050 0000028e`847bbd80 00000000`c00002c4 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0xec

    ffffd000`931b82b0 fffff801`e858a18e : ffffe001`cf7c9490 fffffcb4`bd43c6bc ffffe001`d5fee040 fffff801`e8588db4 : nt! ?? ::FNODOBFM::`string'+0x1967b

    ffffd000`931b8380 fffff801`e858a609 : 00000000`00000002 ffffe001`d4cf5610 ffffe001`d0c95050 00000000`00000000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xb6

    ffffd000`931b83e0 fffff801`e858a864 : ffffe001`ffffffff 00000000`00001bd8 fffff680`00000071 ffffe001`cf7c9490 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x1e1

    ffffd000`931b8480 fffff801`e858b2b6 : fffff801`e87866f0 ffffe001`cf7c9490 00000000`00000040 ffffe001`cf7c9490 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0x118

    ffffd000`931b8540 fffff801`e858b361 : ffffe001`d0c95000 ffffd000`931b8650 fffff801`e858b340 fffff801`e858b340 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x52

    ffffd000`931b8590 fffff801`e84f1115 : ffffe001`cc274080 ffffd000`931b8650 ffffe001`d2d52740 fffff801`e84d1d20 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21

    ffffd000`931b85c0 fffff801`e8584de8 : 00000000`00000003 ffffe001`cf7c9490 ffffe001`d5fee000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x85

    ffffd000`931b8610 fffff801`e8586d7c : ffffd000`931b8710 fffff801`e858afe8 ffffe001`d0c95000 ffffd000`00000002 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xac

    ffffd000`931b86e0 fffff801`e8586a8f : ffffe001`d0c95000 ffffe001`cf7c9490 fffff801`e8789700 fffff801`e8789700 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x180

    ffffd000`931b8730 fffff801`e8584c79 : 00000000`0000000c ffffe001`d2d527f0 ffffe001`cf7c9490 00000000`00000008 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbb

    ffffd000`931b87b0 fffff801`e8584b0d : ffffe001`d2d527f0 ffffd000`931b8860 ffffd000`00000008 fffff680`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x165

    ffffd000`931b8830 fffff801`e850e079 : 00000000`00000001 ffffe001`cb6b3be0 ffffe001`cc298140 ffffe001`cb6b3be0 : nt!SmPageRead+0x51

    ffffd000`931b8880 fffff801`e850d3d2 : 00000000`00000002 00000000`00000000 ffffe001`d2d526f0 00000000`00000000 : nt!MiIssueHardFaultIo+0x129

    ffffd000`931b8900 fffff801`e8528823 : 00000000`c0033333 00000181`b0dca7a0 ffffd000`931b8b00 fffff801`00000000 : nt!MiIssueHardFault+0x162

    ffffd000`931b89a0 fffff801`e85d6bbc : ffffe001`cc274080 00000000`0000001a 00000000`00000000 ffffe001`d50cdda0 : nt!MmAccessFault+0x7f3

    ffffd000`931b8b00 00007ff9`b41c6085 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c

    00000041`1b4faa80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`b41c6085

    STACK_COMMAND: kb

    SYMBOL_NAME: REGION_PAGED_OUT

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    IMAGE_VERSION:

    FAILURE_BUCKET_ID: PAGE_NOT_ZERO_REGION_PAGED_OUT

    BUCKET_ID: PAGE_NOT_ZERO_REGION_PAGED_OUT

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: kmFAULTY_HARDWARE_CORRUPT_PAGE :page_not_zero_region_paged_out

    FAILURE_ID_HASH: {2116c973-78f0-ac8c-fd80-e8f7849726ae}

    Followup: MachineOwner

    ---------
     
    SamanthaPotts, Nov 30, 2020
    #2
Thema:

FAULTY_HARDWARE_CORRUPT_PAGE

Loading...
  1. FAULTY_HARDWARE_CORRUPT_PAGE - Similar Threads - FAULTY_HARDWARE_CORRUPT_PAGE

  2. SB3 BSOD Faulty_Hardware_Corrupt_Page

    in Windows 10 Gaming
    SB3 BSOD Faulty_Hardware_Corrupt_Page: Hi TeamMy Surface Book 3 randomly crashes whist using Chrome and Google Meet esp when sharing presentations.C:\Windows\Minidump has no files in this folder to share.I have run mdsched.exe and that checks out fine.sfc /scannow and that check out fine.The unit is fully updated...
  3. SB3 BSOD Faulty_Hardware_Corrupt_Page

    in Windows 10 Software and Apps
    SB3 BSOD Faulty_Hardware_Corrupt_Page: Hi TeamMy Surface Book 3 randomly crashes whist using Chrome and Google Meet esp when sharing presentations.C:\Windows\Minidump has no files in this folder to share.I have run mdsched.exe and that checks out fine.sfc /scannow and that check out fine.The unit is fully updated...