SFC scannow and SFCFix both fail, latest Windows 10 update fails

D

daneyuleb

Member
Joined
May 21, 2018
Posts
6
Hi,

I'm really hoping someone can help me get my system back in order!

I'm on Windows 10, 1709, build 16299.309
While I haven't been crashing, system behavior has been odd lately.
For one thing, I can't turn on File and Printer sharing--each time I apply it,
and close the window, it comes back set to off again. I can connect fine to the internet,
but no local network connections. This has been going on for a month or so now.

Also, all recent attempts at updating Windows 10 have failed:
Last failed install attempt on ‎5/‎22/‎2018 - 0x80240034

Trying a "repair install" using the Media Creation Tool fails as well during the installation phase at about 28%--I believe the
error is just along the lines of "process failed".

Running SFC /scannow fails too. The error looks like this:

Beginning verification phase of system scan.
Verification 61% complete.
Windows Resource Protection could not perform the requested operation.

Running SFCFix, after about a minute I get:
Something has gone horribly wrong and SFCFix has crashed!

Needless to say, I'm a bit concerned! I'm attaching my zipped cbs log file below.

Thanks!

-Daniel
 

Attachments

Code: 
2018-05-21 08:33:41, Info                  CSI    00000dd2 [SR] Beginning Verify and Repair transaction
2018-05-21 08:33:41, Info                  CSI    00000dd3 Hashes for file member [l:24]'AudioEndpointBuilder.dll' do not match.
 Expected: {l:32 b:fe254dddeb22fffbbfcc87fe035ae5c6f44f08c6ff0edfbc0c584c0c47e6ff55}.
 Actual: {l:32 b:4a42758f72c633cac50d1f2b25a21736f2ad29e53200456450a8b80d612c2d9e}.
2018-05-21 08:33:41, Info                  CSI    00000dd4 [SR] Cannot repair member file [l:24]'AudioEndpointBuilder.dll' of Microsoft-Windows-Audio-AudioCore, version 10.0.16299.248, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-05-21 08:33:41, Info                  CSI    00000dd5@2018/5/21:12:33:41.939 Primitive installers committed for repair
2018-05-21 08:33:41, Info                  CSI    00000dd6@2018/5/21:12:33:41.939 Primitive installers committed for repair
2018-05-21 08:33:41, Info                  CSI    00000dd7@2018/5/21:12:33:41.971 Primitive installers committed for repair
2018-05-21 08:33:41, Info                  CSI    00000dd8 Hashes for file member [l:24]'AudioEndpointBuilder.dll' do not match.
 Expected: {l:32 b:fe254dddeb22fffbbfcc87fe035ae5c6f44f08c6ff0edfbc0c584c0c47e6ff55}.
 Actual: {l:32 b:4a42758f72c633cac50d1f2b25a21736f2ad29e53200456450a8b80d612c2d9e}.
2018-05-21 08:33:41, Info                  CSI    00000dd9 [SR] Cannot repair member file [l:24]'AudioEndpointBuilder.dll' of Microsoft-Windows-Audio-AudioCore, version 10.0.16299.248, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-05-21 08:33:41, Info                  CSI    00000dda [SR] This component was referenced by [l:79]'Package_886_for_KB4088776~31bf3856ad364e35~amd64~~10.0.1.3.4088776-2526_neutral'
2018-05-21 08:33:42, Info                  CSI    00000ddb Hashes for file member [l:24]'AudioEndpointBuilder.dll' do not match.
 Expected: {l:32 ml:4096 b:fe254dddeb22fffbbfcc87fe035ae5c6f44f08c6ff0edfbc0c584c0c47e6ff55}.
 Actual: {l:32 b:4a42758f72c633cac50d1f2b25a21736f2ad29e53200456450a8b80d612c2d9e}.
2018-05-21 08:33:42, Info                  CSI    00000ddc Hashes for file member [l:24]'AudioEndpointBuilder.dll' do not match.
 Expected: {l:32 ml:4096 b:fe254dddeb22fffbbfcc87fe035ae5c6f44f08c6ff0edfbc0c584c0c47e6ff55}.
 Actual: {l:32 b:4a42758f72c633cac50d1f2b25a21736f2ad29e53200456450a8b80d612c2d9e}.
2018-05-21 08:33:42, Info                  CSI    00000ddd [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\AudioEndpointBuilder.dll; source file in store is also corrupted
2018-05-21 08:33:59, Info                  CSI    00001274 [SR] Beginning Verify and Repair transaction
2018-05-21 08:34:00, Info                  CSI    00001275 Hashes for file member [l:12]'DismHost.exe' do not match.
 Expected: {l:32 b:c0fc152db24708d0be657d65232d6bd61a22bed4404ffe4337c82fd18bfc59dd}.
 Actual: {l:32 b:0aae7fb82773f2b1cdb0696f1af96835389db2d9996eb0165f4c1054156be459}.
2018-05-21 08:34:00, Info                  CSI    00001276 [SR] Cannot repair member file [l:12]'DismHost.exe' of Microsoft-Windows-Deployment-Image-Servicing-Management-Core, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-05-21 08:34:00, Info                  CSI    000012a0 Hashes for file member [l:12]'DismHost.exe' do not match.
 Expected: {l:32 b:c0fc152db24708d0be657d65232d6bd61a22bed4404ffe4337c82fd18bfc59dd}.
 Actual: {l:32 b:0aae7fb82773f2b1cdb0696f1af96835389db2d9996eb0165f4c1054156be459}.
2018-05-21 08:34:00, Info                  CSI    000012a1 [SR] Cannot repair member file [l:12]'DismHost.exe' of Microsoft-Windows-Deployment-Image-Servicing-Management-Core, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-05-21 08:34:00, Info                  CSI    000012a2 [SR] This component was referenced by [l:107]'Microsoft-Windows-Common-Foundation-Package~31bf3856ad364e35~amd64~~10.0.16299.15.WindowsFoundationDelivery'
2018-05-21 08:34:00, Info                  CSI    000012a3 [SR] This component was referenced by [l:144]'Microsoft-Windows-Client-Features-Package0015~31bf3856ad364e35~amd64~~10.0.16299.15.microsoft-windows-client-features-deployment00150-Deployment'
2018-05-21 08:34:00, Info                  CSI    000012a4 Hashes for file member [l:12]'DismHost.exe' do not match.
 Expected: {l:32 ml:4096 b:c0fc152db24708d0be657d65232d6bd61a22bed4404ffe4337c82fd18bfc59dd}.
 Actual: {l:32 b:0aae7fb82773f2b1cdb0696f1af96835389db2d9996eb0165f4c1054156be459}.
2018-05-21 08:34:00, Info                  CSI    000012a5 Hashes for file member [l:12]'DismHost.exe' do not match.
 Expected: {l:32 ml:4096 b:c0fc152db24708d0be657d65232d6bd61a22bed4404ffe4337c82fd18bfc59dd}.
 Actual: {l:32 b:0aae7fb82773f2b1cdb0696f1af96835389db2d9996eb0165f4c1054156be459}.
2018-05-21 08:34:00, Info                  CSI    000012a6 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\Dism\DismHost.exe; source file in store is also corrupted
2018-05-21 08:34:14, Info                  CSI    00001666 [SR] Verifying 100 components
2018-05-21 08:34:14, Info                  CSI    00001667 [SR] Beginning Verify and Repair transaction
2018-05-21 08:34:14, Info                  CSI    00001668 Hashes for file member [l:12]'cga80woa.fon' do not match.
 Expected: {l:32 b:93e7c6c123d9b53a2d933f63093b4b85302023517f56abf057f9ef8a94d83b8b}.
 Actual: {l:32 b:a70bca5feb65dc399db201dce649ed2142ebdbcdfa5149ec90ad61493187117f}.
2018-05-21 08:34:14, Info                  CSI    00001669 [SR] Cannot repair member file [l:12]'cga80woa.fon' of Microsoft-Windows-Font-Bitmap-Terminal, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-05-21 08:34:17, Info                  CSI    000016e5 Hashes for file member [l:12]'cga80woa.fon' do not match.
 Expected: {l:32 b:93e7c6c123d9b53a2d933f63093b4b85302023517f56abf057f9ef8a94d83b8b}.
 Actual: {l:32 b:a70bca5feb65dc399db201dce649ed2142ebdbcdfa5149ec90ad61493187117f}.
2018-05-21 08:34:17, Error                 CSI    000016e6 (F) Failed on regenerating file [l:12]'cga80woa.fon'[gle=0x80004005]
2018-05-21 08:34:17, Info                  CSI    000016e7 [SR] Unable to repair \SystemRoot\WinSxS\amd64_microsoft-windows-font-bitmap-terminal_31bf3856ad364e35_10.0.16299.15_none_375b84d73280ff86\\[l:12]'cga80woa.fon'
2018-05-21 08:34:17, Info                  CSI    000016e8 [SR] Repaired file \SystemRoot\WinSxS\amd64_microsoft-windows-font-bitmap-terminal_31bf3856ad364e35_10.0.16299.15_none_375b84d73280ff86\\[l:12]'cga80woa.fon' by copying from backup
2018-05-21 08:34:17, Info                  CSI    000016e9@2018/5/21:12:34:17.237 Primitive installers committed for repair
2018-05-21 08:34:17, Info                  CSI    000016ea [SR] Cannot repair member file [l:12]'cga80woa.fon' of Microsoft-Windows-Font-Bitmap-Terminal, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file is missing
2018-05-21 08:34:17, Info                  CSI    000016eb [SR] This component was referenced by [l:144]'Microsoft-Windows-Client-Features-Package0012~31bf3856ad364e35~amd64~~10.0.16299.15.microsoft-windows-client-features-deployment00120-Deployment'
2018-05-21 08:34:17, Info                  CSI    000016ec Hashes for file member [l:12]'cga80woa.fon' do not match.
 Expected: {l:32 ml:4096 b:93e7c6c123d9b53a2d933f63093b4b85302023517f56abf057f9ef8a94d83b8b}.
 Actual: {l:32 b:a70bca5feb65dc399db201dce649ed2142ebdbcdfa5149ec90ad61493187117f}.
2018-05-21 08:34:17, Info                  CSI    000016ed [SR] Could not reproject corrupted file \??\C:\WINDOWS\Fonts\cga80woa.fon; source file in store is also corrupted
2018-05-21 08:35:04, Info                  CSI    000023ec [SR] Beginning Verify and Repair transaction
2018-05-21 08:35:05, Info                  CSI    000023ed Hashes for file member [l:20]'StorageCmdlets.cdxml' do not match.
 Expected: {l:32 b:c802050213660e1f3be85799b249eb8588df04d8fdebb2bc9a83383dd19be0a6}.
 Actual: {l:32 b:260e5e1388d42622fb43cefabbebceba2f5db5b47180468d780fb8cb54e4f89f}.
2018-05-21 08:35:05, Info                  CSI    000023ee [SR] Cannot repair member file [l:20]'StorageCmdlets.cdxml' of Microsoft-Windows-StorageManagementWMI-Powershell, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-05-21 08:35:05, Info                  CSI    0000243d Hashes for file member [l:20]'StorageCmdlets.cdxml' do not match.
 Expected: {l:32 b:c802050213660e1f3be85799b249eb8588df04d8fdebb2bc9a83383dd19be0a6}.
 Actual: {l:32 b:260e5e1388d42622fb43cefabbebceba2f5db5b47180468d780fb8cb54e4f89f}.
2018-05-21 08:35:05, Info                  CSI    0000243e [SR] Cannot repair member file [l:20]'StorageCmdlets.cdxml' of Microsoft-Windows-StorageManagementWMI-Powershell, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-05-21 08:35:05, Info                  CSI    0000243f [SR] This component was referenced by [l:146]'Microsoft-Windows-Client-Features-Package00114~31bf3856ad364e35~amd64~~10.0.16299.15.microsoft-windows-client-features-deployment001140-Deployment'
2018-05-21 08:35:05, Info                  CSI    00002440 [SR] This component was referenced by [l:144]'Microsoft-Windows-Client-Features-Package0012~31bf3856ad364e35~amd64~~10.0.16299.15.microsoft-windows-client-features-deployment00120-Deployment'
2018-05-21 08:35:05, Info                  CSI    00002441 Hashes for file member [l:20]'StorageCmdlets.cdxml' do not match.
 Expected: {l:32 ml:4096 b:c802050213660e1f3be85799b249eb8588df04d8fdebb2bc9a83383dd19be0a6}.
 Actual: {l:32 b:260e5e1388d42622fb43cefabbebceba2f5db5b47180468d780fb8cb54e4f89f}.
2018-05-21 08:35:05, Info                  CSI    00002442 Hashes for file member [l:20]'StorageCmdlets.cdxml' do not match.
 Expected: {l:32 ml:4096 b:c802050213660e1f3be85799b249eb8588df04d8fdebb2bc9a83383dd19be0a6}.
 Actual: {l:32 b:260e5e1388d42622fb43cefabbebceba2f5db5b47180468d780fb8cb54e4f89f}.
2018-05-21 08:35:05, Info                  CSI    00002443 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\WindowsPowerShell\v1.0\Modules\Storage\StorageCmdlets.cdxml; source file in store is also corrupted
2018-05-21 08:35:15, Info                  CSI    000026e5 [SR] Beginning Verify and Repair transaction
2018-05-21 08:35:15, Info                  CSI    000026e6 Hashes for file member [l:12]'mrxsmb20.sys' do not match.
 Expected: {l:32 b:e07bf924c0d57eda6193d8fd149ebd8fd8cb0c9375ac7998517ad0804fbbca23}.
 Actual: {l:32 b:bfeefbde062799bba6e7620de9fce1ff51c3ff306f95c5b96e70b6cfdb59bb3e}.
2018-05-21 08:35:15, Info                  CSI    000026e7 [SR] Cannot repair member file [l:12]'mrxsmb20.sys' of Microsoft-Windows-SMB20-MiniRdr, version 10.0.16299.98, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-05-21 08:35:16, Info                  CSI    0000270e Hashes for file member [l:12]'mrxsmb20.sys' do not match.
 Expected: {l:32 b:e07bf924c0d57eda6193d8fd149ebd8fd8cb0c9375ac7998517ad0804fbbca23}.
 Actual: {l:32 b:bfeefbde062799bba6e7620de9fce1ff51c3ff306f95c5b96e70b6cfdb59bb3e}.
2018-05-21 08:35:16, Info                  CSI    0000270f [SR] Cannot repair member file [l:12]'mrxsmb20.sys' of Microsoft-Windows-SMB20-MiniRdr, version 10.0.16299.98, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-05-21 08:35:16, Info                  CSI    00002710 [SR] This component was referenced by [l:80]'Package_1076_for_KB4088776~31bf3856ad364e35~amd64~~10.0.1.3.4088776-2965_neutral'
2018-05-21 08:35:16, Info                  CSI    00002711 Hashes for file member [l:12]'mrxsmb20.sys' do not match.
 Expected: {l:32 ml:4096 b:e07bf924c0d57eda6193d8fd149ebd8fd8cb0c9375ac7998517ad0804fbbca23}.
 Actual: {l:32 b:bfeefbde062799bba6e7620de9fce1ff51c3ff306f95c5b96e70b6cfdb59bb3e}.
2018-05-21 08:35:16, Info                  CSI    00002712 Hashes for file member [l:12]'mrxsmb20.sys' do not match.
 Expected: {l:32 ml:4096 b:e07bf924c0d57eda6193d8fd149ebd8fd8cb0c9375ac7998517ad0804fbbca23}.
 Actual: {l:32 b:bfeefbde062799bba6e7620de9fce1ff51c3ff306f95c5b96e70b6cfdb59bb3e}.
2018-05-21 08:35:16, Info                  CSI    00002713 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\Drivers\mrxsmb20.sys; source file in store is also corrupted
2018-05-21 08:35:29, Info                  CSI    00002a74 [SR] Beginning Verify and Repair transaction
2018-05-21 08:35:30, Info                  CSI    00002a75 Hashes for file member [l:12]'sidubm.table' do not match.
 Expected: {l:32 b:1a640899b19bbfd210c7cea4f630a807e960f4f5561dacc2c77a1bf362b4d263}.
 Actual: {l:32 b:6556982020e551ee66e8033ea4f2f8636beea68413347a0d2084dddc0f869cfb}.
2018-05-21 08:35:30, Info                  CSI    00002a76 [SR] Cannot repair member file [l:12]'sidubm.table' of Microsoft-Windows-VoiceActivation-en-us, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-05-21 08:35:30, Info                  CSI    00002a96 Hashes for file member [l:12]'sidubm.table' do not match.
 Expected: {l:32 b:1a640899b19bbfd210c7cea4f630a807e960f4f5561dacc2c77a1bf362b4d263}.
 Actual: {l:32 b:6556982020e551ee66e8033ea4f2f8636beea68413347a0d2084dddc0f869cfb}.
2018-05-21 08:35:30, Info                  CSI    00002a97 [SR] Cannot repair member file [l:12]'sidubm.table' of Microsoft-Windows-VoiceActivation-en-us, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2018-05-21 08:35:30, Info                  CSI    00002a98 [SR] This component was referenced by [l:133]'Microsoft-Windows-LanguageFeatures-Speech-en-us-avcore-Package~31bf3856ad364e35~amd64~~10.0.16299.15.b72fc139823b9a0dd639741391c8cdd7'
2018-05-21 08:35:30, Info                  CSI    00002a99 Hashes for file member [l:12]'sidubm.table' do not match.
 Expected: {l:32 ml:4096 b:1a640899b19bbfd210c7cea4f630a807e960f4f5561dacc2c77a1bf362b4d263}.
 Actual: {l:32 b:6556982020e551ee66e8033ea4f2f8636beea68413347a0d2084dddc0f869cfb}.
2018-05-21 08:35:30, Info                  CSI    00002a9a Hashes for file member [l:12]'sidubm.table' do not match.
 Expected: {l:32 ml:4096 b:1a640899b19bbfd210c7cea4f630a807e960f4f5561dacc2c77a1bf362b4d263}.
 Actual: {l:32 b:6556982020e551ee66e8033ea4f2f8636beea68413347a0d2084dddc0f869cfb}.
2018-05-21 08:35:30, Info                  CSI    00002a9b [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\Speech_OneCore\VoiceActivation\en-US\sidubm.table; source file in store is also corrupted

Hello and Welcome!

First, since the repair install is failing as well, let's check the disk SMART stats to be sure the disk is healthy.

JcJ91sx.png
GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:

  • Download GSmartControl and save it on your Desktop;
  • Extract the content of the GSmartControl .zip archive and execute gsmartcontrol.exe; To extract you can right-click your mouse on the GSmartControl.zip file and select Extract.
  • Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
  • Go in the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, copy and paste their name in your next reply (or take a screenshot of the GSmartControl window and attach it in your next reply);
    info_failing.png
 
Thanks for responding.

The test stopped at 10%(!) Uh oh!


Here's the test screen, the error log, and the attributes screen. This looks bad, huh?


Capture.PNG


Here's the text from the error log window:

Complete error log:


SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
Device Error Count: 66 (device log contains only the most recent 4 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.


Error 66 [1] occurred at disk power-on lifetime: 10820 hours (450 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.


After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
00 -- 51 00 01 00 00 02 3b 54 6f 40 00 Error: at LBA = 0x023b546f = 37442671


Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
42 00 00 00 01 00 00 02 3b 54 6e 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 6d 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 6c 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 6b 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 6a 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT


Error 65 [0] occurred at disk power-on lifetime: 10820 hours (450 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.


After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
00 -- 51 00 01 00 00 02 3b 54 6e 40 00 Error: at LBA = 0x023b546e = 37442670


Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
42 00 00 00 01 00 00 02 3b 54 6d 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 6c 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 6b 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 6a 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 69 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT


Error 64 [3] occurred at disk power-on lifetime: 10820 hours (450 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.


After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
00 -- 51 00 01 00 00 02 3b 54 6d 40 00 Error: at LBA = 0x023b546d = 37442669


Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
42 00 00 00 01 00 00 02 3b 54 6c 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 6b 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 6a 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 69 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 68 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT


Error 63 [2] occurred at disk power-on lifetime: 10820 hours (450 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.


After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
00 -- 51 00 01 00 00 02 3b 54 6c 40 00 Error: at LBA = 0x023b546c = 37442668


Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
42 00 00 00 01 00 00 02 3b 54 6b 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 6a 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 69 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 01 00 00 02 3b 54 68 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT
42 00 00 00 02 00 00 02 3b 54 6e 40 1f 22d+02:54:18.000 READ VERIFY SECTOR(S) EXT



Capture2.PNG
 
The Magician Software shows "Good" for the health, but when I click SMART, it does show some "fails" (below).

I switched out the sata cable, thinking maybe that was the issue, but no changes. And I ran memtest86 but got no errors.

I'm thinking I may soon be in the market for a new hard drive.



Capture3.PNG
 
I agree. At this point you may wish to contact Samsung if this drive is still under the manufacturer warranty.

Do you have a spare that you can clone to?
 
Yep, I think it should be under warranty -- Samsung gives 5 years for evo 850s, and this one is just at two. Weird it's going bad!

Thanks so much for pointing me in the right direction--I really hadn't considered it to be a drive problem--is it the failed "repair install" that clued you in?
 
Glad to help! :)

Yes, the disk or filesystem is a good place to start with corruptions returning and a failed repair install.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top