Windows 10: FAULTY_HARDWARE_CORRUPTED_PAGE BSOD, No errors in MEMTEST

I've been having periodic BSOD with a computer I built for a while now, but I thought I was in clear when I didn't get one about a month. However, a day or two ago I got one with a FAULTY_HARDWARE_CORRUPTED_PAGE, so I ran memtest over night and didn't get any errors this morning after 6 passes (picture attached). I also ran memtest about a month ago over the weekend for 29 passes without error. Hopefully this is a driver issue, but the problem has been going on for so long I may just buy new ram and see if it helps.

:)

 

PC Bluescreening

Does not appear to have verifier enabled but points to

FAULTY_HARDWARE_CORRUPTED_PAGE (12b)

This bugcheck indicates that a single bit error was found in this page.
This is a hardware memory error.

I would run memtest.

 

Getting One BSOD frequently

Hello Community,

I was having some frequent BSODs before and I got them fixed, now I am back again because I am getting BSODs' again. Faulty_Hardware_Corrupted_Page.

Here is my minidump file:

Faulty_BSOD – Google Drive

I have tried to do a memtest and It does not seem to by my ram. I may think it's an old driver but I can't pinpoint which one it is.

 

The RAM would seem to be OK. Try some of the other hardware tests:





Diagnostics Test

HDD TEST
*Arrow Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Diagnostic test

GPU TEST
*Arrow Run Prime95 - Stress Test Your CPU - Windows 10 Forums



Warning Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

 

Thanks for replying, I ran the tests and didn't seem to get any errors

Ran the GPU for an hour with no flags and ran prime95 over night. I've attached the results.

Thanks

 

MemCompression and memory_corruption going in hand with NTFS.sys all over the place are present in your dumps. I say there something wrong with SSD, Sata Cable, Sata Port or Windows filesystem.

Maybe theres a newer firmware for your SSD. You should also check Windows filesystem:
Repair Windows Filesystem:

1. Open an elevated command prompt.
2. In the elevated command prompt, type these commands below, and press Enter:

dism /Online /NoRestart /Cleanup-Image /CheckHealth
dism /Online /NoRestart /Cleanup-Image /ScanHealth
dism /Online /NoRestart /Cleanup-Image /RestoreHealth

sfc /scannow

chkdsk %systemdrive% /F /R /X
fsutil dirty set %systemdrive%

SFC:
The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
DISM:
If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
For example, you would use sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted. SFC should be able to repair the files afterwards.
CHKDSK:
Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...

 

Hello, thank you for replying.

I ran the commands

dism /Online /NoRestart /Cleanup-Image /CheckHealth
dism /Online /NoRestart /Cleanup-Image /ScanHealth
dism /Online /NoRestart /Cleanup-Image /RestoreHealth

but get the following message

The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

So I looked around online and tried to use the sources on a windows 10 iso I just downloaded today. I mounted the iso to my F drive and run

Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:F:\sources\install.esd:1

but get the same source error

The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

Any idea on how to fix this?

 

Tip
Update: The cumulative update KB4016871 fixes spurious DISM issues in Windows 10.

See: KB4016871 Fixes Spurious Win10 DISM Issue - Windows Enterprise Desktop

 

Sorry for the update delay. I tried to do a diskcheck, but the computer would blue screen every time it started the process. I couldn't figure out how to stop the computer from going into the disk check on boot, even when I de-scheduled it with the cmd prompt in the startup troubleshooter. I ended up just reinstalling windows on my SSD and haven't had any BSOD in the meantime, but I am pretty sure Ive tried reinstalling windows in the past, only for the issue to eventually start up again. Anyway, I will let you know if the computer starts BSOD again and thanks for your help in the meantime.

 

Computer started BSODing again even after the fresh install. Uploaded the dumps

 

Code: 0x0000003B: SYSTEM_SERVICE_EXCEPTION (31.05.2017 19:29:15) [Windows 10] CAUSED BY: memory_corruption NTFS.sys [6.07.1994] * NT File System Driver (Windows System File) PROCESS: MsMpEng.exe ffffa101`f0f10060 fffff803`c07f0c35 NTFS!NtfsFlushVolume+0x1055 ffffa101`f0f10120 fffff803`c07f0c35 NTFS!NtfsFlushVolume+0x1055 ffffa101`f0f104c8 fffff803`c073f510 NTFS!NtfsMultipleAsync+0xe0 ffffa101`f0f107d0 fffff803`c07f1382 NTFS!NtfsFlushVolume+0x17a2 ffffa101`f0f107d8 fffff803`c0730000 NTFS!LfsSetDefragLsn <PERF> (NTFS+0x0) ffffa101`f0f107e0 fffff803`c07ba218 NTFS!g_RpcBindingHandleBound <PERF> (NTFS+0x8a218) ffffa101`f0f107e8 fffff803`c0730000 NTFS!LfsSetDefragLsn <PERF> (NTFS+0x0) ffffa101`f0f107f0 fffff803`c07b6ce4 NTFS!g_RpcBindingHandleBound <PERF> (NTFS+0x86ce4) ffffa101`f0f107f8 fffff803`c0730000 NTFS!LfsSetDefragLsn <PERF> (NTFS+0x0) ffffa101`f0f10800 fffff803`c07b6798 NTFS!g_RpcBindingHandleBound <PERF> (NTFS+0x86798) ffffa101`f0f10808 fffff803`c0730000 NTFS!LfsSetDefragLsn <PERF> (NTFS+0x0) ffffa101`f0f10810 fffff803`c07b678c NTFS!g_RpcBindingHandleBound <PERF> (NTFS+0x8678c) ffffa101`f0f10868 fffff803`c0747d8a NTFS!NtfsCommonWrite+0x354a ffffa101`f0f10870 fffff803`c07f0c35 NTFS!NtfsFlushVolume+0x1055 ffffa101`f0f10878 fffff803`c07f0c45 NTFS!NtfsFlushVolume+0x1065 ffffa101`f0f10880 fffff803`c07f0c36 NTFS!NtfsFlushVolume+0x1056 ffffa101`f0f10898 fffff803`c07f0c35 NTFS!NtfsFlushVolume+0x1055 ffffa101`f0f10a18 fffff803`c07f0c35 NTFS!NtfsFlushVolume+0x1055 ffffa101`f0f10dc8 fffff803`c07ec8e8 NTFS!NtfsCheckAttributeRecord+0x498 ffffa101`f0f10e48 fffff803`c07ec3f1 NTFS!NtfsCheckFileRecord+0x161 ffffa101`f0f10ed8 fffff803`c07ec273 NTFS!NtfsReadMftRecord+0x3c3 ffffa101`f0f110f8 fffff803`c07f0c35 NTFS!NtfsFlushVolume+0x1055 ffffa101`f0f112a8 fffff803`c0739818 NTFS!NtfsAcquireExclusiveFcb+0x78 ffffa101`f0f112d8 fffff803`c073af0b NTFS!NtfsReleaseFcb+0x4b ffffa101`f0f112f8 fffff803`c07f0c35 NTFS!NtfsFlushVolume+0x1055 ffffa101`f0f11458 fffff803`c083b8f4 NTFS!NtfsAcquireExclusiveVcb+0x30 ffffa101`f0f11498 fffff803`c074a70c NTFS!NtfsVolumeDasdIo+0x208 ffffa101`f0f11558 fffff803`c073deba NTFS!NtfsCommonRead+0x23aa ffffa101`f0f11748 fffff803`c073b93e NTFS!NtfsFsdRead+0x1ee ffff8981`9cf8c4a8 fffff808`56533c08 NTFS!NtfsCreateFcb+0x9e8 ffff8981`9cf8c4f8 fffff808`5652d6ef NTFS!NtfsBuildRelativeName+0x1af ffff8981`9cf8c578 fffff808`56479818 NTFS!NtfsAcquireExclusiveFcb+0x78 ffff8981`9cf8c5a8 fffff808`5647af0b NTFS!NtfsReleaseFcb+0x4b ffff8981`9cf8c5e8 fffff808`5652d50f NTFS!NtfsWalkUpTree+0xb5f ffff8981`9cf8c8a8 fffff808`5647a103 NTFS!NtfsCleanupIrpContext+0x173 ffff8981`9cf8c978 fffff808`5653ca34 NTFS!NtfsCommonQueryInformation+0xd84 ffff8981`9cf8cc18 fffff808`56489b5d NTFS!DirtyPageRoutine+0x8d ffff8981`9cf8cd58 fffff808`5654285b NTFS!NtfsCheckpointVolume+0xc47 ffff8981`9cf8cd68 fffff808`56489ad0 NTFS!DirtyPageRoutine ffff8981`9cf8ce78 fffff808`5652bde4 NTFS!NtfsReadFileRecord+0xe4 ffff8981`9cf8cfe8 fffff808`565414dc NTFS!NtfsCleanupAttributeContext+0x18 ffff8981`9cf8d118 fffff808`56548e5a NTFS!NtfsAddRecentlyDeallocated+0xa6 ffff8981`9cf8d228 fffff808`5652133c NTFS!NtfsAcquireSharedVcb+0x34 ffff8981`9cf8d268 fffff808`5650b8e4 NTFS!NtfsDefragFileInternal+0x690 ffff8981`9cf8d518 fffff808`5650b1e5 NTFS!NtfsDefragFile+0x1dd ffff8981`9cf8d5b8 fffff808`565238a8 NTFS!NtfsUserFsRequest+0x2d4 ffff8981`9cf8d5f8 fffff808`5647adef NTFS!NtfsInitializeTopLevelIrp+0x3f ffff8981`9cf8d638 fffff808`56523546 NTFS!NtfsFsdFileSystemControl+0x356 ffff8981`9cf8da18 fffff802`8ff39ab6 nt!NtFsControlFile+0x56[/quote]
Again theres a problem with filesystem or disk.

 

Ran the chkdsk commands again and there weren't any errors. Didn't get a BSOD for about a week, but got one over the weekend while I was away.

 

hmm theres the memory_corruption error again:

Code: 0x00000154: UNEXPECTED_STORE_EXCEPTION (11.06.2017 07:14:15) [Windows 10] CAUSED BY: memory_corruption PROCESS: MemCompression[/quote]
Is there a special thing u do at the time as the bsod occurs?

 

This may be completely wrong, but could this be caused by google drive trying to sync when the computer is locked. Since its my work computer I really don't have many extra programs running other than google drive.

 

can u provide us with the an full memory dump? Its located in C:\Windows\MEMORY.DMP. U could upload it via Dropbox or one drive