[SOLVED] Recurring BSOD even after clean OS install

Dec 11, 2019
4
0
10
0
I am using Win 10 on my ASUS N56JN laptop.
I have been having this occasional BSOD with FAULTY HARDWARE CORRUPTED PAGE for a long time now, even after a system reinstallation.
As the name implies, this should be a hardware issue, but i need to know which device/driver to investigate.

Here is windbg report of the latest memory dump:

Code:
************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols

Microsoft (R) Windows Debugger Version 10.0.18362.1 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.


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff804`07200000 PsLoadedModuleList = 0xfffff804`076480b0
Debug session time: Fri Nov  8 10:14:57.141 2019 (UTC + 3:00)
System Uptime: 0 days 14:09:01.898
Loading Kernel Symbols
...............................................................
................................................................
................................................................

Loading User Symbols
PEB address is NULL !
Loading unloaded module list
...........................
For analysis of this file, run !analyze -v
2: kd> !analyze -v
Page fb9e8 not present in the dump file. Type ".hh dbgerr004" for details
Page fb9e8 not present in the dump file. Type ".hh dbgerr004" for details
*******************************************************************************
*                                                                             *
*                        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: 00000000000006c3, physical page number
Arg3: 000001be32df6fc0, zero
Arg4: ffffda81852eb000, zero

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

Page fb9e8 not present in the dump file. Type ".hh dbgerr004" for 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:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME:  N56JN

SYSTEM_SKU:  ASUS-NotebookSKU

SYSTEM_VERSION:  1.0       

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  N56JN.205

BIOS_DATE:  06/11/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  N56JN

BASEBOARD_VERSION:  1.0       

DUMP_TYPE:  1

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: 6c3

BUGCHECK_P3: 1be32df6fc0

BUGCHECK_P4: ffffda81852eb000

SM_COMPRESSION_FORMAT: 3

SM_SOURCE_PFN1: 185fd3

SM_SOURCE_PFN2: 943d2

SM_SOURCE_OFFSET: 6fc0

SM_SOURCE_SIZE: 6c3

SM_TARGET_PFN: 5be68

SM_BUFFER_HASH: 9099eab2

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: 25'00000000 (cache) 25'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  MemCompression

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  MOS-LAPTOP

ANALYSIS_SESSION_TIME:  12-11-2019 08:53:32.0245

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80407523c3b to fffff804073c1410

STACK_TEXT: 
ffff9c88`4d580618 fffff804`07523c3b : 00000000`0000012b ffffffff`c00002c4 00000000`000006c3 000001be`32df6fc0 : nt!KeBugCheckEx
ffff9c88`4d580620 fffff804`074630be : 00000000`00000200 00000000`c00002c4 ffffda81`852eb000 00000000`00000002 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0xfb
ffff9c88`4d580670 fffff804`0735fef4 : 00000000`00000004 ffff9c88`4d580880 00000000`00000000 00000000`00000041 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x1031aa
ffff9c88`4d580750 fffff804`0735fd72 : 00000000`00000001 00000000`00006fc0 00000000`00006fc0 ffffc90b`000fe000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0
ffff9c88`4d5807a0 fffff804`0735fb9b : 00000000`ffffffff ffffc90b`4153f000 ffff9c88`4d580880 ffffc90b`3f764640 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186
ffff9c88`4d580840 fffff804`0735f9e1 : ffffc90b`4153f000 00000000`00000000 00000000`00000000 ffffc90b`40b85788 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xcb
ffff9c88`4d5808f0 fffff804`0735f8f1 : ffffc90b`40b84000 ffffc90b`3f764640 ffffc90b`4153f000 ffffc90b`40b859b0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
ffff9c88`4d580970 fffff804`07269e28 : ffffc90b`3e996040 ffffc90b`40b84000 ffffda81`ffffffff 00000000`00000001 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffff9c88`4d5809a0 fffff804`07362e51 : fffff804`0735f8d0 ffff9c88`4d580a50 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffff9c88`4d580a10 fffff804`0734b9c1 : ffffc90b`3e996040 00000000`00000000 00000076`9bdc8e61 fffff804`07cb7848 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xcd
ffff9c88`4d580ae0 fffff804`07363949 : ffffc90b`3e996000 00000076`9bdc8e61 fffff804`0778de90 fffff804`0778dc68 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1a5
ffff9c88`4d580b30 fffff804`072bd4b5 : 00000000`00989680 ffffc90b`3e996040 fffff804`073638a0 ffffc90b`3ed78b60 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmAsyncReadQueueWorker+0xa9
ffff9c88`4d580b70 fffff804`0732a7a5 : ffffc90b`3e996040 00000000`00000080 ffffc90b`34ca4380 69766965`00000001 : nt!ExpWorkerThread+0x105
ffff9c88`4d580c10 fffff804`073c8a5a : ffffda81`81b20180 ffffc90b`3e996040 fffff804`0732a750 62617473`6520746f : nt!PspSystemThreadStartup+0x55
ffff9c88`4d580c60 00000000`00000000 : ffff9c88`4d581000 ffff9c88`4d57b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  ff9fa57c7680abd1dcc0965b29595a2867689951

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  e1e7ac8889d547e98605cc54ebb97199f1ee8158

THREAD_SHA1_HASH_MOD:  38bc5fec3f0409c265cf5c87da6f8f8859d0711c

FOLLOWUP_IP:
nt!ST_STORE<SM_TRAITS>::StDmPageError+fb
fffff804`07523c3b cc              int     3

FAULT_INSTR_CODE:  48c033cc

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d2db2db

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  fb

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-11-08T07:14:57.000Z

OSBUILD:  18362

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:  2011-01-12 16:55:39

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  7faf

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
---------

2: kd> !blackboxpnp
Page fb9e8 not present in the dump file. Type ".hh dbgerr004" for details
Page fb9e8 not present in the dump file. Type ".hh dbgerr004" for details
    PnpActivityId      : {00000000-0000-0000-0000-000000000000}
    PnpActivityTime    : 132176313496648964
    PnpEventInformation: 3
    PnpEventInProgress : 0
    PnpProblemCode     : 24
    PnpVetoType        : 0
    DeviceId           : SWD\RADIO\{BBB1A5BB-39E5-495E-BC87-B07CA8019E4E}
    VetoString         :
 

Colif

Win 10 Master
Moderator
see if this helps

right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

error occurred in compressed memory, seems a driver tried to access ram it didn't own.

If I was going to look at any driver as cause, I think ASMMAP64.sys from 2008 is a good place to start. Its the ASUS Memory Mapping driver which probably doesn't play well with WIn 10 memory modes. Try running autoruns and use it to disable the driver and see if it helps = https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
 

Colif

Win 10 Master
Moderator
FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

if it finds no errors, do you have an ssd or hdd?
If ssd, try running chkdsk c: /f in command prompt (with admin rights)
If hdd, try running chkdsk C: /f /r in command prompt (with admin rights)
Main difference is ssd don't have physical sectors so /repair won't work on them.

2 paragraphs will appear, agree to running the CHkdsk at startup and restart PC to let it run.

Corrupted Page could be Memory or storage, so we check both.
 
Last edited:
Dec 11, 2019
4
0
10
0
FAULTY_HARDWARE_CORRUPTED_PAGE (12b)
This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

if it finds no errors, do you have an ssd or hdd?
If ssd, try running chkdsk c: /f in command prompt (with admin rights)
If hdd, try running chkdsk C: /f /r in command prompt (with admin rights)
Main difference is ssd don't have physical sectors so /repair won't work on them.

2 paragraphs will appear, agree to running the CHkdsk at startup and restart PC to let it run.

Corrupted Page could be Memory or storage, so we check both.
Thanks for the advice, I have followed your instructions.

CHKDSK went fine. Anyway, I do not think it is my drive, because I have recently changed to a brand new SSD, but the problem still persists after that.
4 passes of Memtest (all tests) came back with 0 errors, so RAM seems to be ok. I enclose the report
EFI Specifications2.31
System
ManufacturerASUSTeK COMPUTER INC.
Product NameN56JN
Version1.0
Serial NumberE8N0BC054517338
BIOS
VendorAmerican Megatrends Inc.
VersionN56JN.205
Release Date06/11/2019
Baseboard
ManufacturerASUSTeK COMPUTER INC.
Product NameN56JN
Version1.0
Serial NumberBSN12345678901234567
CPU TypeIntel Core i7-4710HQ @ 2.50GHz
CPU Clock2494 MHz [Turbo: 3292.4 MHz]
# Logical Processors8 (4 enabled for testing)
L1 Cache4 x 64K (182542 MB/s)
L2 Cache4 x 256K (52347 MB/s)
L3 Cache6144K (38603 MB/s)
Memory6034M (16711 MB/s)
DIMM Slot #04GB DDR3 PC3-12800
Kingston / ASU16D3LS1KFG/4G / BF0D2D6C
11-11-11-28 / 1600 MHz / 1.5V, 1.35V
DIMM Slot #12GB DDR3 PC3-12800
SK Hynix / HMT425S6AFR6A-PB / 031AC138
11-11-11-28 / 1600 MHz / 1.5V, 1.35V
Result summary
Test Start Time2019-12-18 19:19:55
Elapsed Time1:54:58
Memory Range Tested0x0 - 1AF200000 (6898MB)
CPU Selection ModeParallel (All CPUs)
ECC PollingEnabled
# Tests Passed48/48 (100%)
Test# Tests PassedErrors
Test 0 [Address test, walking ones, 1 CPU]4/4 (100%)0
Test 1 [Address test, own address, 1 CPU]4/4 (100%)0
Test 2 [Address test, own address]4/4 (100%)0
Test 3 [Moving inversions, ones & zeroes]4/4 (100%)0
Test 4 [Moving inversions, 8-bit pattern]4/4 (100%)0
Test 5 [Moving inversions, random pattern]4/4 (100%)0
Test 6 [Block move, 64-byte blocks]4/4 (100%)0
Test 7 [Moving inversions, 32-bit pattern]4/4 (100%)0
Test 8 [Random number sequence]4/4 (100%)0
Test 9 [Modulo 20, ones & zeros]4/4 (100%)0
Test 10 [Bit fade test, 2 patterns, 1 CPU]4/4 (100%)0
Test 13 [Hammer test]4/4 (100%)0
 

Colif

Win 10 Master
Moderator
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
 
Dec 11, 2019
4
0
10
0
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents

upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem
Thank you for your responce. It happens to be, I have already taken the minidump before, for my own research. Since the BSOD is not very frequent, let me enclose the one that I have, rather then wait for another occaion: 110819-7062-01.dmp
 

Colif

Win 10 Master
Moderator
I have sent link to a friend, he will reply later (although I cannot guarantee I will be around to answer as its going to be around 40C here tomorrow and using PC just makes room too hot - but i will answer when I can).
 

gardenman

Admirable
Moderator
Hi, I ran the dump file through the debugger and got the following information: https://malcontentcaiman.htmlpasta.com/ (The htmlpasta.com is a new site for me, I hope it works out.)

File information:110819-7062-01.dmp (Nov 8 2019 - 02:14:57)
Bugcheck:FAULTY_HARDWARE_CORRUPTED_PAGE (12B)
Probably caused by:memory_corruption (Process: MemCompression)
Uptime:0 Day(s), 14 Hour(s), 09 Min(s), and 01 Sec(s)

Comment: 2 or more types of RAM are installed.

Possible Motherboard page: https://www.asus.com/Laptops/N56JN/
It appears you have the latest BIOS already installed.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Dec 11, 2019
4
0
10
0
see if this helps

right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

error occurred in compressed memory, seems a driver tried to access ram it didn't own.

If I was going to look at any driver as cause, I think ASMMAP64.sys from 2008 is a good place to start. Its the ASUS Memory Mapping driver which probably doesn't play well with WIn 10 memory modes. Try running autoruns and use it to disable the driver and see if it helps = https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
Two things speak against broken system files hypothesis:
  1. Two months ago I have wiped my system partition and installed clean Win 10 from a bootable USB that I have made with a most recent Media Creation Tool from Microsoft. All updates have been installed as well.
  2. I have had the same BSOD even before that, my system being Win 10 that has been updated from 8.1 during early days of Win 10 release
However, I have run sfc /verifyonly to make sure, and it had found no integrity errors whatsoever.

I tend to agree with your outdated ASUS drivers hypothesis. When BSODs started even after OS reinstall, I have tried manually installing more recent or manufacturer-provided drivers for some of the hardware (network adapters, intel chipset, etc.), but to no avail. As of now, I have tried disabling my Bluetooth adapter that has never been too reliable on this machine, and I haven't had a BSOD since. If I do get a BSOD in the future, I will try ASMMAP64.sys driver as well.
 
Last edited:

ASK THE COMMUNITY

TRENDING THREADS