Windows 10: FAULTY_HARDWARE_CORRUPTED_PAGE - which memory bank it belongs to?

Hello,


I browsed through numerous questions on this topic but didn't find the answer I'm interested in.
I've had the bug, ran WinDbg, inside it the Analyze command and got the listing below. From which follows that it is a hardware error, memory error and even the physical address is given.

I wonder, is it possible without becoming a windows internals pro to deduce from the info below which memory bank should I replace? Probably some utility is able to do this?


Thanks.




Microsoft (R) Windows Debugger Version 10.0.18317.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`ba4aa000 PsLoadedModuleList = 0xfffff801`ba858150
Debug session time: Fri Mar 1 15:05:49.237 2019 (UTC + 4:00)
System Uptime: 6 days 11:42:40.290
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.
Loading User Symbols
PEB address is NULL !
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`ba6540c0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff307`c38c8590=000000000000012b
4: 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: 00000000000007ea, physical page number
Arg3: 000000000e7721d0, zero
Arg4: ffff9f00ac2ad000, zero

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

KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME: N56JK

SYSTEM_SKU: ASUS-NotebookSKU

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: N56JK.203

BIOS_DATE: 11/17/2014

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: N56JK

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: 7ea

BUGCHECK_P3: e7721d0

BUGCHECK_P4: ffff9f00ac2ad000

SM_COMPRESSION_FORMAT: 3

SM_SOURCE_PFN1: 124b26

SM_SOURCE_PFN2: ffffffffffffffff

SM_SOURCE_OFFSET: 21d0

SM_SOURCE_SIZE: 7ea

SM_TARGET_PFN: 21ee6

SM_BUFFER_HASH: a00eb0cc

BUGCHECK_STR: 0x12B_c00002c4_StCtDecompressFailed

CPU_COUNT: 8

CPU_MHZ: 9be

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 24'00000000 (cache) 24'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: MemCompression

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: OLBOLDIE

ANALYSIS_SESSION_TIME: 03-01-2019 21:59:03.0622

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

LAST_CONTROL_TRANSFER: from fffff801ba74ee1c to fffff801ba6540c0

STACK_TEXT:
fffff307`c38c8588 fffff801`ba74ee1c : 00000000`0000012b ffffffff`c00002c4 00000000`000007ea 00000000`0e7721d0 : nt!KeBugCheckEx
fffff307`c38c8590 fffff801`ba6b9496 : 00000000`00000200 00000000`00000003 ffffde86`b28da050 00000000`0e7721d0 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0xf0
fffff307`c38c85e0 fffff801`ba5fc3fd : 00000000`00000004 fffff307`c38c87f0 00000000`00000000 00000000`0000f427 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0xbd072
fffff307`c38c86c0 fffff801`ba5fc2c2 : 00000000`00000001 00000000`000021d0 00000000`000021d0 00000000`00003000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0x95
fffff307`c38c8710 fffff801`ba5fc0ed : 00000000`ffffffff ffffde86`aae06000 fffff307`c38c87f0 ffffde86`b579abe0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x****`b28db9b0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
fffff307`c38c88e0 fffff801`ba56919a : ffffde86`b53e5700 fffff307`c38c89b0 00000000`00000000 00000000`00000001 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
fffff307`c38c8910 fffff801`ba5fea8d : fffff801`ba5fbe30 fffff307`c38c89b0 00000000`00000003 ffffde86`aae06000 : nt!KeExpandKernelStackAndCalloutInternal+0x8a
fffff307`c38c8970 fffff801`ba4bfbb1 : fffff307`c38c8a70 fffff801`ba4bf755 00000000`00000000 fffff801`ba5fe03c : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xad
fffff307`c38c8a40 fffff801`ba4bf5f2 : 00000000`00000000 00000000`00000000 fffff307`c38c8af0 ffffde86`b579abe0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1b1
fffff307`c38c8a90 fffff801`ba5fdda0 : 00000000`0000000c 00000000`00000003 ffffde86`b579abe0 ffffde86`bb533390 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xce
fffff307`c38c8b10 fffff801`ba5ff446 : 00000000`00000003 ffffde86`bb533448 00000000`00000000 ffffde86`b28da000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x16****25 : nt!MiIssueHardFaultIo+0x122
fffff307`c38c8c20 fffff801`ba5043c4 : 00000000`c0033333 00000000`00000001 00000000`0372fd10 00000000`00000000 : nt!MiIssueHardFault+0x234
fffff307`c38c8cd0 fffff801`ba6617da : ffffde86`b53e5700 00000000`0399bb50 00000000`02b66210 00000000`0399bb50 : nt!MmAccessFault+0x384
fffff307`c38c8e40 00000000`049f768b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x31a
00000000`00759060 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x49f768b

THREAD_SHA1_HASH_MOD_FUNC: 0e25f7e1a5e1caae3d28e6a7023983c4503045c5

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6db4be163088908f6c9d6ba621218c7bc7c9aa08

THREAD_SHA1_HASH_MOD: 82d14546c43bd06881f781d6d197c4c7f7ceb9cb

FOLLOWUP_IP:
nt!ST_STORE<SM_TRAITS>::StDmPageError+f0
fffff801`ba74ee1c cc int 3

FAULT_INSTR_CODE: 48c033cc

SYMBOL_STACK_INDEX: 1

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

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5c5a45ab

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: f0

FAILURE_BUCKET_ID: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

BUCKET_ID: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

PRIMARY_PROBLEM_CLASS: 0x12B_c00002c4_StCtDecompressFailed_nt!ST_STORE_SM_TRAITS_::StDmPageError

TARGET_TIME: 2019-03-01T11:05:49.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2019-02-06 06:25:47

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 46ea

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x12b_c00002c4_stctdecompressfailed_nt!st_store_sm_traits_::stdmpageerror

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

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

:)

 

LiveKernelEvent 141 and 117, BSOD with FAULTY_HARDWARE_CORRUPTED_PAGE

Hello Lim,

Thank you for bringing up your query on Microsoft Community.

We sincerely regret for the inconvenience caused.

• 
  Are you able to boot to the desktop?
  

The FAULTY_HARDWARE_CORRUPTED_PAGE bug check has a value of 0x00000128. This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.

Let us try the following steps, and check if it helps.

Step 1:

Let us follow the steps suggested in the following article and check if ti helps in resolving the issue.

Troubleshoot blue screen errors

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Step 2:

If you are unable to boot to the desktop, I suggest you to run Startup repair from Advance boot option.

It may ask you to insert the Installation DVD/USB while doing startup repair.

You have to create an installation media for that.

You may download an ISO from the below link:

https://www.microsoft.com/en-us/software-download/windows10

Once your media is ready follow the steps.

• 
  After you boot your computer using Windows 10 CD/ DVD or System Repair Disc, a black screen appears with gray text "Press any key to boot from CD or DVD". Press any key.
  
• 
  Select the correct time and Keyboard type.
  
• 
  Click on Repair your computer in the lower left corner.
  
• 
  Select Troubleshoot from Choose an option screen.
  
• 
  Click on Advanced options in Troubleshoot screen.
  
• 
  Click on Automatic Repair from Advanced Options screen.
  
• 
  Next, choose the operating system by clicking on its button.
  
• 
  Windows 10 will look for problems on hard drive(s) and verify that all required files are intact.
  

Hope it helps.

Let us know the status, we are glad to assist you further.

 

Blue Screen of Death--FAULTY_HARDWARE_CORRUPTED_PAGE--DRIVER_VERIFIER_DETECTED_VIOLATION

Hi,

i am encountering with these problems on my system.

• FAULTY_HARDWARE_CORRUPTED_PAGE
• DRIVER_VERIFIER_DETECTED_VIOLATION

Please attached the share "OneDrive"link for your kind consideration.

I have reset system several time but after few day similar errors pop up. I tried using driver verifier command and capture dump memory.

Link: https://onedrive.live.com/redir?res...24&authkey=!AIO5Mn8NQIS0BqQ&ithint=folder,DMP

Please help to solve these problems.

Many thanks

Regards

MC

 

Overclocking / Undervolting guide for Vega 56 or 64?

Here's a quick laundry list:

List of software to use for overclocking and testing
Examples:
Wattman (and how to find and use it, like an overview, including profiles)
Unigine Valley or Heaven (use this for quick testing while changing settings in Wattman and checking for stability / artifacts) ...just suggesting this
How to monitor cores / mem speeds and temps during testing (I've seen screen overlays, and others using GPUz)

Step-by step overclocking in Wattman
Fan speeds
Power limit
Temp limit
Voltages
Core speeds
Memory speeds