I have been getting a bsod randomly over the past week and all the information it says is FAULTY_HARDWARE_CORRUPTED_PAGE. So far it has happened 3 times this week. It just started happening this week. I googled the issue and it seems to be effecting people with windows 10 on asus laptops and the threads go nowhere beyond more people stating they have the issue.
BSOD FAULTY_HARDWARE_CORRUPTED_PAGE
- Thread starter mikee
- Start date
zaka100
W͂Oͨ̍̍̒̈́͛̕
- Messages
- 762
- Location
- Birmingham, UK
Dump?
How do I get the dump? I will get it as soon as memtest86 does a few more passes.
Edit: Dump file uploaded
Last edited:
Your dump file for reference:
https://msdn.microsoft.com/en-us/li...329(v=vs.85).aspx?f=255&MSPPError=-2147217396
How long did you run Memtest for? Run it for a minimum of 4 hours (longer the better). Because according to the MSDN article, it's definitely a hardware issue.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 12B, {ffffffffc00002c4, 205, 28c93935ce0, ffffd0002548f000}
Probably caused by : ntkrnlmp.exe ( nt!ST_STORE<SM_TRAITS>::StDmPageError+ec )
Followup: MachineOwner
---------
1: 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: 0000000000000205, physical page number
Arg3: 0000028c93935ce0, zero
Arg4: ffffd0002548f000, zero
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10586.17.amd64fre.th2_release.151121-2308
SYSTEM_MANUFACTURER: System manufacturer
SYSTEM_PRODUCT_NAME: System Product Name
SYSTEM_SKU: To Be Filled By O.E.M.
SYSTEM_VERSION: System Version
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 2403
BIOS_DATE: 12/23/2010
BASEBOARD_MANUFACTURER: ASUSTeK Computer INC.
BASEBOARD_PRODUCT: M4A88T-M
BASEBOARD_VERSION: Rev X.0x
DUMP_TYPE: 2
BUGCHECK_P1: ffffffffc00002c4
BUGCHECK_P2: 205
BUGCHECK_P3: 28c93935ce0
BUGCHECK_P4: ffffd0002548f000
BUGCHECK_STR: 0x12B_c00002c4_StCtDecompressFailed
CPU_COUNT: 6
CPU_MHZ: a98
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 10
CPU_MODEL: a
CPU_STEPPING: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: MAKO
ANALYSIS_SESSION_TIME: 12-19-2015 13:49:01.0215
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
LAST_CONTROL_TRANSFER: from fffff800772909d4 to fffff800771d2760
STACK_TEXT:
ffffd000`20ffd398 fffff800`772909d4 : 00000000`0000012b ffffffff`c00002c4 00000000`00000205 0000028c`93935ce0 : nt!KeBugCheckEx
ffffd000`20ffd3a0 fffff800`772227a9 : 00000000`00000200 ffffe001`582de050 0000028c`93935ce0 00000000`c00002c4 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0xec
ffffd000`20ffd3e0 fffff800`7718efc6 : ffffe001`55a51fd0 ffff76ca`25e745ab ffffe001`5626c040 fffff800`7718dbec : nt! ?? ::FNODOBFM::`string'+0x416a9
ffffd000`20ffd4b0 fffff800`7718f441 : 00000000`00000002 ffffe001`5a0ba110 ffffe001`582de050 00000000`c0000034 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xb6
ffffd000`20ffd510 fffff800`7718f645 : ffffd000`ffffffff ffffe001`000015ce 00000000`00000969 ffffe001`55a51fd0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x1e1
ffffd000`20ffd5b0 fffff800`7718ffce : fffff800`7738c630 ffffe001`55a51fd0 00000000`00000040 ffffe001`55a51fd0 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc1
ffffd000`20ffd670 fffff800`77190199 : ffffe001`582de000 ffffd000`20ffd780 fffff800`77190178 fffff800`77190178 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x52
ffffd000`20ffd6c0 fffff800`77105b35 : ffffe001`55370840 ffffd000`20ffd780 ffffe001`5b701ea0 fffff800`770995e8 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffd000`20ffd6f0 fffff800`77189c20 : 00000000`00000003 ffffe001`55a51fd0 ffffe001`5626c000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x85
ffffd000`20ffd740 fffff800`7718bbb4 : ffffd000`20ffd840 fffff800`7718fe20 ffffe001`582de000 ffffd000`00000005 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xac
ffffd000`20ffd810 fffff800`7718b8c7 : ffffe001`582de000 ffffe001`55a51fd0 fffff800`7738f640 fffff800`7738f640 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x180
ffffd000`20ffd860 fffff800`77189ab1 : 00000000`0000000c ffffe001`5b701f50 ffffe001`55a51fd0 00000000`00000001 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbb
ffffd000`20ffd8e0 fffff800`77189945 : ffffe001`5b701f50 ffffd000`20ffd990 ffffd000`00000001 fffff680`00000000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x165
ffffd000`20ffd960 fffff800`77138681 : 00000000`00000001 00000000`00000000 ffffe001`55370940 fffff800`770e1e13 : nt!SmPageRead+0x51
ffffd000`20ffd9b0 fffff800`77137b02 : 00000000`00000002 00000000`00000000 ffffe001`5b701e50 00000000`00000000 : nt!MiIssueHardFaultIo+0x129
ffffd000`20ffda30 fffff800`770c937f : 00000000`c0033333 ffffe001`5d38b900 ffffd000`20ffdc40 ffffe001`00000000 : nt!MiIssueHardFault+0x162
ffffd000`20ffdad0 fffff800`771db9bc : ffffe001`55370840 00000000`00000000 ffffd000`20ffdc18 ffffe001`5d0b8d90 : nt!MmAccessFault+0x82f
ffffd000`20ffdc40 00000000`75d921bc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
00000000`040aec38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75d921bc
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: adbe3727bf15c95e349ee08fce74173973a6165d
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f0fffa7c9dac0aa4cc82b2617ef5564edbceccfd
THREAD_SHA1_HASH_MOD: 82d14546c43bd06881f781d6d197c4c7f7ceb9cb
FOLLOWUP_IP:
nt!ST_STORE<SM_TRAITS>::StDmPageError+ec
fffff800`772909d4 cc int 3
FAULT_INSTR_CODE: 448b44cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ST_STORE<SM_TRAITS>::StDmPageError+ec
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 565189c8
IMAGE_VERSION: 10.0.10586.17
BUCKET_ID_FUNC_OFFSET: ec
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: 2015-12-19T17:10:33.000Z
OSBUILD: 10586
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2015-11-22 03:24:24
BUILDDATESTAMP_STR: 151121-2308
BUILDLAB_STR: th2_release
BUILDOSVER_STR: 10.0.10586.17.amd64fre.th2_release.151121-2308
ANALYSIS_SESSION_ELAPSED_TIME: 8a72
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
---------https://msdn.microsoft.com/en-us/li...329(v=vs.85).aspx?f=255&MSPPError=-2147217396
How long did you run Memtest for? Run it for a minimum of 4 hours (longer the better). Because according to the MSDN article, it's definitely a hardware issue.
I'm running it again now then when I get back from the movies it should have run for about 5 hours. IT came up with one error but that error has been there for a year now. This is a new bluescreen. I am going to find out which of my sticks of ram is bad and replace it very soon.
Do you think its the ram that is causing this? I can't make heads or tails of that crash dump. What it even of any use?
Do you think its the ram that is causing this? I can't make heads or tails of that crash dump. What it even of any use?
This is what memtest86 came up with
I have gotten this result for almost a year now and the occasional MEMORY MANAGEMENT BSOD every few months but this FAULTY HARDWARE CURRUPTED PAGE one is new as of the last week
I made a thread about the ram issue back in january but now I think I am going to just replace it. I don't understand why it suddenly is causing the faulty hardware bsod though
Edit: I noticed this in the dump summary posted WIN8_DRIVER_FAULT does this mean there is a windows 8 driver contributing to this issue as well? I did just get a gtx 950 at the beginning of the month
I have gotten this result for almost a year now and the occasional MEMORY MANAGEMENT BSOD every few months but this FAULTY HARDWARE CURRUPTED PAGE one is new as of the last week
I made a thread about the ram issue back in january but now I think I am going to just replace it. I don't understand why it suddenly is causing the faulty hardware bsod though
Edit: I noticed this in the dump summary posted WIN8_DRIVER_FAULT does this mean there is a windows 8 driver contributing to this issue as well? I did just get a gtx 950 at the beginning of the month
Last edited:
This is what memtest86 came up with
I have gotten this result for almost a year now and the occasional MEMORY MANAGEMENT BSOD every few months but this FAULTY HARDWARE CURRUPTED PAGE one is new as of the last week
I made a thread about the ram issue back in january but now I think I am going to just replace it. I don't understand why it suddenly is causing the faulty hardware bsod though
Edit: I noticed this in the dump summary posted WIN8_DRIVER_FAULT does this mean there is a windows 8 driver contributing to this issue as well? I did just get a gtx 950 at the beginning of the month
Tiny pic is tiny.
Anyway...considering the BSOD, I don't think it's a driver fault. The BSOD even states it's specifically hardware related:
And your Memtest86 result backs that up - you have a memory module with an error, so it's bad (or part of it's bad). Test each module individually and see which one specifically is bad (if you have multiple modules). Could even be a bad memory slot on the board resulting in memory errors.
I'm going to do that monday while I am at work but I am thinking that since the error is at 5905mb that the error is with the second module that will be the one I take out first just based on that hunch.
On another note I will be buying new ram and I only want to spend 50 ish dollars on a 2x4gb set of DDR3. Anything I should be looking for in good quality ram? anything to avoid? Also Would it be a good idea to leave the good stick I have left here in in addition to the 8gb set? My Mobo only supports 16gb max in 4x4GB.
On another note I will be buying new ram and I only want to spend 50 ish dollars on a 2x4gb set of DDR3. Anything I should be looking for in good quality ram? anything to avoid? Also Would it be a good idea to leave the good stick I have left here in in addition to the 8gb set? My Mobo only supports 16gb max in 4x4GB.
