BSOD FAULTY_HARDWARE_CORRUPTED_PAGE - Techist - Tech Forum

Go Back   Techist - Tech Forum > Computer Hardware > Hardware Repairs and Troubleshooting
Click Here to Login
Reply
 
Thread Tools Display Modes
 
Old 12-19-2015, 12:17 PM   #1 (permalink)
Master Techie
 
Join Date: Feb 2005
Posts: 2,012
Default BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

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

__________________
AMD Ryzen 5 1400 3.2Ghz
16GB CORSAIR Vengeance LPX DDR4 2400 Ram
Crucial M500 240GB SSD (boot drive)
500GB WD 5000AAKX-001CA0
1.5 TB Seagate ST1500DM003
Zotac Geforce GTX 950 2GB GDDR5
Windows 10 Pro 64 bit
mikee is offline   Reply With Quote
Old 12-19-2015, 01:01 PM   #2 (permalink)
W͂O̠̳ͨ̍̍̒̈́͛̕Ķ͎̠̱̰̓ͦĒ ̍̓ͦ
 
zaka100's Avatar
 
Join Date: Nov 2013
Location: Birmingham, UK
Posts: 747
Default Re: BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

Dump?
__________________

__________________

My Build
CPU - AMD X4 860k @ 3.7ghz
GPU - Nvidia GeForce 780
RAM - 2x HyperX Fury 4gb
MOBO - MSI A78M-E35
SSD - 120gb Kingston Hyper X
HDD - WD 320gb
Steam: zaka100123
zaka100 is offline   Reply With Quote
Old 12-19-2015, 01:25 PM   #3 (permalink)
Master Techie
 
Join Date: Feb 2005
Posts: 2,012
Default Re: BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

Quote:
Originally Posted by zaka100 View Post
Dump?
How do I get the dump? I will get it as soon as memtest86 does a few more passes.


Edit: Dump file uploaded
Attached Files
File Type: zip 121915-43062-01.zip (88.7 KB, 3 views)
__________________
AMD Ryzen 5 1400 3.2Ghz
16GB CORSAIR Vengeance LPX DDR4 2400 Ram
Crucial M500 240GB SSD (boot drive)
500GB WD 5000AAKX-001CA0
1.5 TB Seagate ST1500DM003
Zotac Geforce GTX 950 2GB GDDR5
Windows 10 Pro 64 bit
mikee is offline   Reply With Quote
Old 12-19-2015, 02:53 PM   #4 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,515
Default Re: BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

Your dump file for reference:
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/lib...or=-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.
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Old 12-19-2015, 03:19 PM   #5 (permalink)
Master Techie
 
Join Date: Feb 2005
Posts: 2,012
Default Re: BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

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?
__________________
AMD Ryzen 5 1400 3.2Ghz
16GB CORSAIR Vengeance LPX DDR4 2400 Ram
Crucial M500 240GB SSD (boot drive)
500GB WD 5000AAKX-001CA0
1.5 TB Seagate ST1500DM003
Zotac Geforce GTX 950 2GB GDDR5
Windows 10 Pro 64 bit
mikee is offline   Reply With Quote
Old 12-19-2015, 03:38 PM   #6 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,515
Default Re: BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

It points towards the problem being most likely a Hardware error caused by bad RAM.
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Old 12-19-2015, 07:46 PM   #7 (permalink)
Master Techie
 
Join Date: Feb 2005
Posts: 2,012
Default Re: BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

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
__________________
AMD Ryzen 5 1400 3.2Ghz
16GB CORSAIR Vengeance LPX DDR4 2400 Ram
Crucial M500 240GB SSD (boot drive)
500GB WD 5000AAKX-001CA0
1.5 TB Seagate ST1500DM003
Zotac Geforce GTX 950 2GB GDDR5
Windows 10 Pro 64 bit
mikee is offline   Reply With Quote
Old 12-19-2015, 08:39 PM   #8 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,515
Default Re: BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

Quote:
Originally Posted by mikee View Post
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:
Quote:
Bug Check 0x12B: FAULTY_HARDWARE_CORRUPTED_PAGE
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.
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.
__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Old 12-19-2015, 09:48 PM   #9 (permalink)
Master Techie
 
Join Date: Feb 2005
Posts: 2,012
Default Re: BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

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.
__________________
AMD Ryzen 5 1400 3.2Ghz
16GB CORSAIR Vengeance LPX DDR4 2400 Ram
Crucial M500 240GB SSD (boot drive)
500GB WD 5000AAKX-001CA0
1.5 TB Seagate ST1500DM003
Zotac Geforce GTX 950 2GB GDDR5
Windows 10 Pro 64 bit
mikee is offline   Reply With Quote
Old 12-19-2015, 11:05 PM   #10 (permalink)
Private Joker
 
carnageX's Avatar
 
Join Date: Feb 2007
Location: South Dakota
Posts: 24,515
Default Re: BSOD FAULTY_HARDWARE_CORRUPTED_PAGE

I've personally always had good luck with G.Skill..and they're relatively inexpensive.
__________________

__________________
Laptop: MSI GT70 2OC-059us | i7-4700MQ | 16GB | GTX 770m | 500GB SSD / 750GB HDD | 17.3" | Win10 Pro
Desktop: 4690k | 12GB g.Skill RipJaws | GTX 970 | 520hx | Z87X-UD4H | Corsair Vengeance C70 | Corsair H110 | Acer 25" | Acer 22" | Win10
Mobile: Samsung Galaxy Note 5


If I help you, or you just like what I said, rep me by clicking the under my post
carnageX is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
BSOD DRIVER_IRQL_NOT_EQUAL, BSOD help please? happyh1ppo Hardware Repairs and Troubleshooting 1 01-05-2012 03:52 PM
BSOD ... Help!! Slam'n Systems Microsoft Windows and Software 2 02-15-2004 11:48 PM
BSOD bad_pool_call on install; Windows XP; Linux dual boot... merlin Microsoft Windows and Software 0 01-31-2004 10:40 AM
Windows XP BSOD's annoyed llama Monitors, Printers and Peripherals 3 01-15-2004 05:14 PM
Nvidia+Via+AMD BSOD XP Advice please Moosehead Monitors, Printers and Peripherals 2 06-07-2003 07:26 PM



Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -5. The time now is 06:53 PM.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.