Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

What should I do? (Faulty_Hardware_Corrupted_Page)


  • Please log in to reply
5 replies to this topic

#1 Thunn

Thunn

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:50 AM

Posted 20 April 2017 - 10:02 PM

I am not exactly sure what to make of this.
 
===================================================================================
 
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: 0000000000000942, physical page number
Arg3: 0000000020cb7370, zero
Arg4: ffffd30009b3e000, zero
 
Debugging Details:
------------------
 
*** WARNING: Unable to verify timestamp for win32k.sys
 
DUMP_CLASS: 1
 
DUMP_QUALIFIER: 400
 
BUILD_VERSION_STRING:  10.0.14393.1066 (rs1_release_sec.170327-1835)
 
SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.
 
SYSTEM_PRODUCT_NAME:  To be filled by O.E.M.
 
SYSTEM_SKU:  To be filled by O.E.M.
 
SYSTEM_VERSION:  To be filled by O.E.M.
 
BIOS_VENDOR:  American Megatrends Inc.
 
BIOS_VERSION:  F15
 
BIOS_DATE:  10/23/2013
 
BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.
 
BASEBOARD_PRODUCT:  B75M-D3H
 
BASEBOARD_VERSION:  To be filled by O.E.M.
 
DUMP_TYPE:  2
 
BUGCHECK_P1: ffffffffc00002c4
 
BUGCHECK_P2: 942
 
BUGCHECK_P3: 20cb7370
 
BUGCHECK_P4: ffffd30009b3e000
 
SM_COMPRESSION_FORMAT: 3
 
SM_SOURCE_PFN1: 6fc0b
 
SM_SOURCE_PFN2: ffffffffffffffff
 
SM_SOURCE_OFFSET: 7370
 
SM_SOURCE_SIZE: 942
 
SM_TARGET_PFN: 85590
 
SM_BUFFER_HASH: 2dc133c
 
SM_ONEBIT_SOLUTION_COUNT: 2
 
BUGCHECK_STR:  0x12B_c00002c4_StCtDecompressFailed_POSSIBLE_ONEBIT
 
CPU_COUNT: 4
 
CPU_MHZ: c15
 
CPU_VENDOR:  GenuineIntel
 
CPU_FAMILY: 6
 
CPU_MODEL: 3a
 
CPU_STEPPING: 9
 
CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 1B'00000000 (cache) 1B'00000000 (init)
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  MemCompression
 
CURRENT_IRQL:  0
 
ANALYSIS_SESSION_HOST:  DESKTOP-0585BDD
 
ANALYSIS_SESSION_TIME:  04-20-2017 20:39:43.0422
 
ANALYSIS_VERSION: 10.0.15063.137 amd64fre
 
LAST_CONTROL_TRANSFER:  from fffff800462272b3 to fffff8004615f7c0
 
STACK_TEXT:  
ffffd300`0ad861b8 fffff800`462272b3 : 00000000`0000012b ffffffff`c00002c4 00000000`00000942 00000000`20cb7370 : nt!KeBugCheckEx
ffffd300`0ad861c0 fffff800`461aca6e : 00000000`00000200 00000000`00000003 00000000`20cb7370 ffffd300`09b3e000 : nt!ST_STORE<SM_TRAITS>::StDmPageError+0x117
ffffd300`0ad86210 fffff800`4611f823 : 00000000`00000000 ffffa407`8fe28050 00000000`00000000 00000000`00007370 : nt! ?? ::FNODOBFM::`string'+0x3ddde
ffffd300`0ad862f0 fffff800`4611fbb1 : 00000000`00000001 00000000`00001dce 00000000`00000001 ffffd300`00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0x7b
ffffd300`0ad86340 fffff800`4611fcf0 : 00000000`ffffffff ffffa407`92a0d000 ffffd300`0ad86428 ffffa407`90c308c0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x199
ffffd300`0ad863e0 fffff800`46120b12 : fffff800`4632f040 ffffa407`90c308c0 00000000`00000001 ffffa407`90c308c0 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0x98
ffffd300`0ad864a0 fffff800`46120c69 : ffffa407`8fe28000 ffffd300`0ad865b0 fffff800`46120c48 fffff800`46120c48 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x52
ffffd300`0ad864f0 fffff800`460ac2d5 : ffffa407`92ad54c0 ffffd300`0ad865b0 ffffa407`95854060 fffff800`460c7068 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffffd300`0ad86520 fffff800`46119e7d : 00000000`00000003 ffffa407`92a0d000 ffffa407`8fe28000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x85
ffffd300`0ad86570 fffff800`4611d27c : ffffd300`0ad86670 ffffd300`0ad867b0 ffffa407`8fe28000 fffff800`4611a056 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xad
ffffd300`0ad86640 fffff800`4611cf67 : ffffa407`8fe28000 ffffa407`90c308c0 fffff800`463c5a40 ffffd300`0ad867b0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1a4
ffffd300`0ad86690 fffff800`46119d13 : 00000000`0000000c ffffa407`95854110 ffffa407`90c308c0 00000000`00000001 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbf
ffffd300`0ad86710 fffff800`46120c42 : ffffa407`00000001 ffffa407`95854110 00000000`00000000 ffffa407`8fe28000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x16b
ffffd300`0ad86780 fffff800`460ef1cd : ffffd300`0ad86800 ffffa407`96771640 00000000`2c507000 fffff580`00000000 : nt!SmPageRead+0x2e
ffffd300`0ad867d0 fffff800`4605363d : 00000000`00000002 ffffd300`0ad86b00 ffffa407`95854010 00000000`00000000 : nt!MiIssueHardFaultIo+0x145
ffffd300`0ad86860 fffff800`46066778 : 00000000`c0033333 ffffa407`95854010 ffffa407`96771640 ffffd300`0ad86b00 : nt!MiIssueHardFault+0x15d
ffffd300`0ad86900 fffff800`46168dfc : ffffa407`92ad54c0 00000000`00000000 ffffd300`0ad86ad8 ffffa407`8f106b10 : nt!MmAccessFault+0x11e8
ffffd300`0ad86b00 00000000`5bdfc30f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c
00000000`008fee68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5bdfc30f
 
 
STACK_COMMAND:  kb
 
THREAD_SHA1_HASH_MOD_FUNC:  adbe3727bf15c95e349ee08fce74173973a6165d
 
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  bab2692d5b0a2ae78f6e928995da6151837e1b9d
 
THREAD_SHA1_HASH_MOD:  82d14546c43bd06881f781d6d197c4c7f7ceb9cb
 
FOLLOWUP_IP: 
nt!ST_STORE<SM_TRAITS>::StDmPageError+117
fffff800`462272b3 cc              int     3
 
FAULT_INSTR_CODE:  448b44cc
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  nt!ST_STORE<SM_TRAITS>::StDmPageError+117
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  58d9f097
 
IMAGE_VERSION:  10.0.14393.1066
 
BUCKET_ID_FUNC_OFFSET:  117
 
FAILURE_BUCKET_ID:  0x12B_c00002c4_StCtDecompressFailed_POSSIBLE_ONEBIT_nt!ST_STORE_SM_TRAITS_::StDmPageError
 
BUCKET_ID:  0x12B_c00002c4_StCtDecompressFailed_POSSIBLE_ONEBIT_nt!ST_STORE_SM_TRAITS_::StDmPageError
 
PRIMARY_PROBLEM_CLASS:  0x12B_c00002c4_StCtDecompressFailed_POSSIBLE_ONEBIT_nt!ST_STORE_SM_TRAITS_::StDmPageError
 
TARGET_TIME:  2017-04-21T02:11:31.000Z
 
OSBUILD:  14393
 
OSSERVICEPACK:  1066
 
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:  2017-03-27 23:11:51
 
BUILDDATESTAMP_STR:  170327-1835
 
BUILDLAB_STR:  rs1_release_sec
 
BUILDOSVER_STR:  10.0.14393.1066
 
ANALYSIS_SESSION_ELAPSED_TIME:  1db0
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x12b_c00002c4_stctdecompressfailed_possible_onebit_nt!st_store_sm_traits_::stdmpageerror
 
FAILURE_ID_HASH:  {28669a99-bcc6-12b9-0ae8-509e180de136}
 
Followup:     MachineOwner
---------
 


BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:50 AM

Posted 20 April 2017 - 10:06 PM

Bugcheck points to faulty RAM... will you please run MemTest86 for a minimum of eight passes? Here's a good guide if you need help. Also, please run Seagate SeaTools for Windows. Be sure to test all your drives with the S.M.A.R.T. and Long Generic tests.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 Thunn

Thunn
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:50 AM

Posted 20 April 2017 - 10:14 PM

Thank you. I will try this.



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:50 AM

Posted 20 April 2017 - 10:29 PM

You're welcome. Let me know the result.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 Thunn

Thunn
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:02:50 AM

Posted 20 April 2017 - 11:08 PM

So after just 1 pass on MemTest I got this:

 

================================================

 

Intel Core i5-3350P @ 3.10GHz
 
Adrsmode: 64Bit
Pass: 1
Errors: 132
 
Error Confidence Value: 109
Lowest Error Address: 0006fc0b440 - 1788.0MB
Highest Error Address: 0006fc0b444 - 1788.0MB
Bits in Error Mask: 00080000
Bits in Error - Total: 1 Min: 1 Max: 1 Avg: 1
Max Contiguous Errors: 2
 
Test  Errors
0      0
1      2
2      2
3      8
4     16
5     16
6     3
7     64
8    16
9    2
10  3
 
================================================
 
It started a second pass, got to about 8% and over 200 errors before I hit ESC. Should I let this run all night, or is it pointless once you find errors?


#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,028 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:04:50 AM

Posted 21 April 2017 - 07:31 AM

Nope, just stop the test. Try to reseat the RAM and clean out the slots. If MemTest still reports errors, you'll need new RAM.


Edited by bwv848, 21 April 2017 - 07:45 AM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users