[SOLVED] Corrupted files on C: hard drive

tivolijake

Member
Joined
Dec 31, 2016
Posts
8
My laptop kept shutting down with no warning. I looked in event log and saw multiple NTFS errors on my hard drive.
I tried to run CHKDSK but it kept failing saying C: drive was locked. I followed instructions to get it to run
upon system restart but it did not work
I saw on a forum where it said MS update KB3022345 was causing the problem. I followed directions from Seven Forums to resolve which included uninstalling the update.

Then I found info on your forum https://www.sysnative.com/forums/windows-update/4736-windows-update-forum-posting-instructions.html

I tried to add CBS.zip to this but apparently I have not understood how it's supposed to work.
The File upload manager pop up showed an upload processing to 100% but I don't see any file to manage.
Not sure what I am missing. I don't see a file or a check mark

Upload Manager.jpg
This came out so small it of little use. I was able to get this screen capture attached.




And here we are. I'll paste the contents of SFCFix.txt here in bold:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-12-31 13:54:57.448
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.




AutoAnalysis::
CORRUPT: C:\windows\winsxs\amd64_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 1
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing
0 datablocks.
Finish time: 2016-12-31 14:22:56.447
----------------------EOF-----------------------
 

Attachments

  • Upload Manager showing attached file.jpg
    Upload Manager showing attached file.jpg
    41.2 KB · Views: 0
Hello and welcome!

Let's replace that corrupt file.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
View attachment SFCFix.zip

SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  4. This will create a file, cbs.txt on your Desktop. Please zip and attach this to your next post.
 
I hope I'm doing this right ! :-)

Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-01-04 19:53:21.666
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Jake\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\windows\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe


Successfully copied file C:\Users\Jake\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe to C:\windows\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe.


Successfully restored ownership for C:\windows\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe
Successfully restored permissions on C:\windows\WinSxS\amd64_microsoft-windows-autochk_31bf3856ad364e35_6.1.7601.17514_none_4019f2b8d860ad30\autochk.exe
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2017-01-04 19:53:25.672
Script hash: LkDPqjCCSE8W53MmQcV2YPYzH6s6PmTeMm9g8wIc33U=
----------------------EOF-----------------------


Hello and welcome!

Let's replace that corrupt file.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
View attachment 24090

SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please zip and attach this to your next post.
 

Attachments

Looks good.

Please try running chkdsk again.


I ran CHKDSK.Got error that caused CHKDSK to terminate.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\windows\system32>chkdsk c:
The type of the file system is NTFS.
Volume label is TI105957W0F.


WARNING! F parameter not specified.
Running CHKDSK in read-only mode.


CHKDSK is verifying files (stage 1 of 3)...
1 percent complete. (77569 of 705792 file records processed)
Attribute record (128, "") from file record segment 78574
is corrupt.
Attribute record (128, "") from file record segment 83142
is corrupt.
1 percent complete. (86529 of 705792 file records processed)
Attribute record (128, "") from file record segment 88942
is corrupt.
2 percent complete. (171265 of 705792 file records processed)
Deleted corrupt attribute list entry
with type code 128 in file 210815.
Attribute record (128, "") from file record segment 85633
is corrupt.
Attribute record (128, "") from file record segment 237559
is corrupt.
3 percent complete. (238593 of 705792 file records processed)
Attribute record (128, "") from file record segment 263774
is corrupt.
4 percent complete. (294098 of 705792 file records processed)
Attribute record (128, "") from file record segment 301584
is corrupt.
4 percent complete. (312833 of 705792 file records processed)
Attribute record (128, "") from file record segment 333100
is corrupt.
4 percent complete. (341505 of 705792 file records processed)
Attribute record (128, "") from file record segment 344454
is corrupt.
Attribute record (128, "") from file record segment 348097
is corrupt.
Attribute record (128, "") from file record segment 352030
is corrupt.
5 percent complete. (352896 of 705792 file records processed)
Attribute record (128, "") from file record segment 361348
is corrupt.
Attribute record (128, "") from file record segment 363377
is corrupt.
5 percent complete. (370177 of 705792 file records processed)
Attribute list entry with type code 48 in file 388349 is corrupt
Attribute list entry with type code 48 in file 388349 is corrupt
Attribute list entry with type code 48 in file 388349 is corrupt
Attribute list entry with type code 128 in file 388349 is corrup
Attribute list entry with type code 192 in file 388349 is corrup
Attribute list entry with type code 48 in file 388350 is corrupt
Attribute list entry with type code 48 in file 388350 is corrupt
Attribute list entry with type code 48 in file 388350 is corrupt
Attribute list entry with type code 128 in file 388350 is corrup
Attribute list entry with type code 192 in file 388350 is corrup
Attribute record (128, "") from file record segment 393110
is corrupt.
Attribute record (128, "") from file record segment 393111
is corrupt.
Attribute record (128, "") from file record segment 394399
is corrupt.
Attribute record (128, "") from file record segment 401355
is corrupt.
6 percent complete. (423476 of 705792 file records processed)
Attribute record (128, "") from file record segment 438447
is corrupt.
Attribute record (128, "") from file record segment 447867
is corrupt.
Attribute record (128, "") from file record segment 450858
is corrupt.
Attribute record (128, "") from file record segment 456831
is corrupt.
Attribute record (128, "") from file record segment 457134
is corrupt.
6 percent complete. (465716 of 705792 file records processed)
Attribute record (128, "") from file record segment 479950
is corrupt.
7 percent complete. (494055 of 705792 file records processed)
Attribute record (160, $I30) from file record segment 509784
is corrupt.
705792 file records processed.
File verification completed.
File record segment 85633 is an orphan.
File record segment 237559 is an orphan.
2603 large file records processed.


Errors found. CHKDSK cannot continue in read-only mode.

I also tried to run chkdsk /f and that resulted in the following:
C:\windows\system32>chkdsk /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) Y

This volume will be checked the next time the system restarts.

C:\windows\system32>
chkdsk does not run on restart (ever)

Thanks for your help thus far
 
Please back up any important data before continuing.

I'd like to check the disk SMART stats.

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
 
Code:
Ran gsmartcontrol.exe 

Attributes:  
[ATTACH=CONFIG]24113.vB[/ATTACH]   
Load/Unload Cycle   now  1  1  50 209085 oldage continuously 0x0032

Error log:
Complete error log:

[ATTACH=CONFIG]24114.vB[/ATTACH]
SMART Error Log Version: 1
ATA Error Count: 12 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
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 12 occurred at disk power-on lifetime: 19632 hours (818 days + 0 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 b2 3c d6 0c  Error: UNC at LBA = 0x0cd63cb2 = 215366834


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 80 08 3b d6 4c 00      00:03:03.724  READ FPDMA QUEUED
  60 00 80 88 3a d6 4c 00      00:03:03.713  READ FPDMA QUEUED
  60 00 60 f8 28 d6 4c 00      00:03:03.710  READ FPDMA QUEUED
  60 00 80 08 35 d6 4c 00      00:03:03.708  READ FPDMA QUEUED
  60 00 80 88 34 d6 4c 00      00:03:03.702  READ FPDMA QUEUED


Error 11 occurred at disk power-on lifetime: 19631 hours (817 days + 23 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ae 3c d6 0c  Error: UNC at LBA = 0x0cd63cae = 215366830


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 80 88 3c d6 4c 00      00:02:41.107  READ FPDMA QUEUED
  60 00 80 08 3c d6 4c 00      00:02:41.106  READ FPDMA QUEUED
  60 00 80 88 3b d6 4c 00      00:02:41.104  READ FPDMA QUEUED
  60 00 01 60 3a 0d 47 00      00:02:41.100  READ FPDMA QUEUED
  60 00 18 78 37 0d 47 00      00:02:41.088  READ FPDMA QUEUED


Error 10 occurred at disk power-on lifetime: 19118 hours (796 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 70 a2 8a 00  Error: UNC at LBA = 0x008aa270 = 9085552


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 e8 22 a2 8a 40 00  17d+22:58:32.269  READ FPDMA QUEUED
  60 00 50 ba a0 8a 40 00  17d+22:58:32.267  READ FPDMA QUEUED
  60 00 00 ba 9f 8a 40 00  17d+22:58:32.256  READ FPDMA QUEUED
  60 00 08 8a 90 8a 40 00  17d+22:58:32.249  READ FPDMA QUEUED
  60 00 08 da 7c 8a 40 00  17d+22:58:32.242  READ FPDMA QUEUED


Error 9 occurred at disk power-on lifetime: 19054 hours (793 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 78 a2 8a 00  Error: UNC at LBA = 0x008aa278 = 9085560


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ba a1 8a 40 00  15d+07:08:23.574  READ FPDMA QUEUED
  60 00 20 ba 9e 8a 40 00  15d+07:08:23.570  READ FPDMA QUEUED
  60 00 00 ba 9d 8a 40 00  15d+07:08:23.569  READ FPDMA QUEUED
  60 00 38 4a 9d 8a 40 00  15d+07:08:23.568  READ FPDMA QUEUED
  60 00 00 4a 9c 8a 40 00  15d+07:08:23.565  READ FPDMA QUEUED


Error 8 occurred at disk power-on lifetime: 10726 hours (446 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.


  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 77 a2 8a 00  Error: UNC at LBA = 0x008aa277 = 9085559


  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 20 6a a2 8a 40 00  15d+20:07:55.544  READ FPDMA QUEUED
  61 00 09 48 20 aa 46 00  15d+20:07:55.544  WRITE FPDMA QUEUED
  61 00 05 a0 52 35 43 00  15d+20:07:55.543  WRITE FPDMA QUEUED
  61 00 40 80 59 01 4a 00  15d+20:07:55.543  WRITE FPDMA QUEUED
  61 00 40 40 59 01 4a 00  15d+20:07:55.542  WRITE FPDMA QUEUED








Please back up any important data before continuing.

I'd like to check the disk SMART stats.

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
 
The load/unload cycle count can be ignored.

Does it show any reallocated sectors, reallocation events, or current pending sectors?
 
I'm sorta in uncharted territory here and may appear to be obtuse. Apologies in advance.
I'll insert a screen capture of the Attributes tab display.

GSmart output_1.jpg

GSmart output_2.jpg

I hope info you need is here. If not let me know where it it.


The load/unload cycle count can be ignored.

Does it show any reallocated sectors, reallocation events, or current pending sectors?
 
Very good, thanks.

Now that we know the disk doesn't appear to be failing, lets repair the file-system. There is a risk of data loss, so please be sure you have a current backup of any important data.

chkdsk /f

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    chkdsk /f

  4. Reboot
  5. Download ListChkdskResult.exe (by SleepyDude) from the link below:

    https://dl.dropboxusercontent.com/u/12354842/My Tools/ListChkdskResult.exe
  6. Double click on it to run it. It will take a few seconds to scan, then it will open a Notepad window with the log. Copy and paste the contents of this into your next post please!
 
Hello I haven't had any success running chkdsk on my C: drive. I'll wrap the loop I am caught in.
I also tried to run chkdsk /f and that resulted in the following:
C:\windows\system32>chkdsk /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) Y

This volume will be checked the next time the system restarts.

C:\windows\system32>
chkdsk does not run on restart (ever)



Very good, thanks.

Now that we know the disk doesn't appear to be failing, lets repair the file-system. There is a risk of data loss, so please be sure you have a current backup of any important data.

chkdsk /f

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    chkdsk /f

  4. Reboot
  5. Download ListChkdskResult.exe (by SleepyDude) from the link below:

    https://dl.dropboxusercontent.com/u/12354842/My Tools/ListChkdskResult.exe
  6. Double click on it to run it. It will take a few seconds to scan, then it will open a Notepad window with the log. Copy and paste the contents of this into your next post please!
 
Hello again. I finally got chkdsk /f to run. I ran command window as admin.
I keyed in command *chkdsk C: /f /r /x*
I have me a msg that C: driver was locked and did I want to run on re-boot. (Y/N)
I replied *Y* and when I re-booted lo and behold , the chkdsk command ran successfully.
I should have grabbed a screen capture but famous last words.
I ran Event Viewer and the Custom Views-> Administrative events and did not see any
NTFS errors since 9 43 A.M. this morning Friday Jan 6.

I'll post if my system still shuts down unexpectedly. Thanks for all your help.


Looks good.

Please try running chkdsk again.


I ran CHKDSK.Got error that caused CHKDSK to terminate.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\windows\system32>chkdsk c:
The type of the file system is NTFS.
Volume label is TI105957W0F.


WARNING! F parameter not specified.
Running CHKDSK in read-only mode.


CHKDSK is verifying files (stage 1 of 3)...
1 percent complete. (77569 of 705792 file records processed)
Attribute record (128, "") from file record segment 78574
is corrupt.
Attribute record (128, "") from file record segment 83142
is corrupt.
1 percent complete. (86529 of 705792 file records processed)
Attribute record (128, "") from file record segment 88942
is corrupt.
2 percent complete. (171265 of 705792 file records processed)
Deleted corrupt attribute list entry
with type code 128 in file 210815.
Attribute record (128, "") from file record segment 85633
is corrupt.
Attribute record (128, "") from file record segment 237559
is corrupt.
3 percent complete. (238593 of 705792 file records processed)
Attribute record (128, "") from file record segment 263774
is corrupt.
4 percent complete. (294098 of 705792 file records processed)
Attribute record (128, "") from file record segment 301584
is corrupt.
4 percent complete. (312833 of 705792 file records processed)
Attribute record (128, "") from file record segment 333100
is corrupt.
4 percent complete. (341505 of 705792 file records processed)
Attribute record (128, "") from file record segment 344454
is corrupt.
Attribute record (128, "") from file record segment 348097
is corrupt.
Attribute record (128, "") from file record segment 352030
is corrupt.
5 percent complete. (352896 of 705792 file records processed)
Attribute record (128, "") from file record segment 361348
is corrupt.
Attribute record (128, "") from file record segment 363377
is corrupt.
5 percent complete. (370177 of 705792 file records processed)
Attribute list entry with type code 48 in file 388349 is corrupt
Attribute list entry with type code 48 in file 388349 is corrupt
Attribute list entry with type code 48 in file 388349 is corrupt
Attribute list entry with type code 128 in file 388349 is corrup
Attribute list entry with type code 192 in file 388349 is corrup
Attribute list entry with type code 48 in file 388350 is corrupt
Attribute list entry with type code 48 in file 388350 is corrupt
Attribute list entry with type code 48 in file 388350 is corrupt
Attribute list entry with type code 128 in file 388350 is corrup
Attribute list entry with type code 192 in file 388350 is corrup
Attribute record (128, "") from file record segment 393110
is corrupt.
Attribute record (128, "") from file record segment 393111
is corrupt.
Attribute record (128, "") from file record segment 394399
is corrupt.
Attribute record (128, "") from file record segment 401355
is corrupt.
6 percent complete. (423476 of 705792 file records processed)
Attribute record (128, "") from file record segment 438447
is corrupt.
Attribute record (128, "") from file record segment 447867
is corrupt.
Attribute record (128, "") from file record segment 450858
is corrupt.
Attribute record (128, "") from file record segment 456831
is corrupt.
Attribute record (128, "") from file record segment 457134
is corrupt.
6 percent complete. (465716 of 705792 file records processed)
Attribute record (128, "") from file record segment 479950
is corrupt.
7 percent complete. (494055 of 705792 file records processed)
Attribute record (160, $I30) from file record segment 509784
is corrupt.
705792 file records processed.
File verification completed.
File record segment 85633 is an orphan.
File record segment 237559 is an orphan.
2603 large file records processed.


Errors found. CHKDSK cannot continue in read-only mode.

I also tried to run chkdsk /f and that resulted in the following:
C:\windows\system32>chkdsk /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) Y

This volume will be checked the next time the system restarts.

C:\windows\system32>
chkdsk does not run on restart (ever)

Thanks for your help thus far
 
Hello again. My status now is hard drive looks good but system still crashes for as yet unknown reasons.
This thread can be closed out and I'll start new thread for system crash problems. Thanks again for your
assistance and patience.
Jake



Hello again. I finally got chkdsk /f to run. I ran command window as admin.
I keyed in command *chkdsk C: /f /r /x*
I have me a msg that C: driver was locked and did I want to run on re-boot. (Y/N)
I replied *Y* and when I re-booted lo and behold , the chkdsk command ran successfully.
I should have grabbed a screen capture but famous last words.
I ran Event Viewer and the Custom Views-> Administrative events and did not see any
NTFS errors since 9 43 A.M. this morning Friday Jan 6.

I'll post if my system still shuts down unexpectedly. Thanks for all your help.


Looks good.

Please try running chkdsk again.


I ran CHKDSK.Got error that caused CHKDSK to terminate.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\windows\system32>chkdsk c:
The type of the file system is NTFS.
Volume label is TI105957W0F.


WARNING! F parameter not specified.
Running CHKDSK in read-only mode.


CHKDSK is verifying files (stage 1 of 3)...
1 percent complete. (77569 of 705792 file records processed)
Attribute record (128, "") from file record segment 78574
is corrupt.
Attribute record (128, "") from file record segment 83142
is corrupt.
1 percent complete. (86529 of 705792 file records processed)
Attribute record (128, "") from file record segment 88942
is corrupt.
2 percent complete. (171265 of 705792 file records processed)
Deleted corrupt attribute list entry
with type code 128 in file 210815.
Attribute record (128, "") from file record segment 85633
is corrupt.
Attribute record (128, "") from file record segment 237559
is corrupt.
3 percent complete. (238593 of 705792 file records processed)
Attribute record (128, "") from file record segment 263774
is corrupt.
4 percent complete. (294098 of 705792 file records processed)
Attribute record (128, "") from file record segment 301584
is corrupt.
4 percent complete. (312833 of 705792 file records processed)
Attribute record (128, "") from file record segment 333100
is corrupt.
4 percent complete. (341505 of 705792 file records processed)
Attribute record (128, "") from file record segment 344454
is corrupt.
Attribute record (128, "") from file record segment 348097
is corrupt.
Attribute record (128, "") from file record segment 352030
is corrupt.
5 percent complete. (352896 of 705792 file records processed)
Attribute record (128, "") from file record segment 361348
is corrupt.
Attribute record (128, "") from file record segment 363377
is corrupt.
5 percent complete. (370177 of 705792 file records processed)
Attribute list entry with type code 48 in file 388349 is corrupt
Attribute list entry with type code 48 in file 388349 is corrupt
Attribute list entry with type code 48 in file 388349 is corrupt
Attribute list entry with type code 128 in file 388349 is corrup
Attribute list entry with type code 192 in file 388349 is corrup
Attribute list entry with type code 48 in file 388350 is corrupt
Attribute list entry with type code 48 in file 388350 is corrupt
Attribute list entry with type code 48 in file 388350 is corrupt
Attribute list entry with type code 128 in file 388350 is corrup
Attribute list entry with type code 192 in file 388350 is corrup
Attribute record (128, "") from file record segment 393110
is corrupt.
Attribute record (128, "") from file record segment 393111
is corrupt.
Attribute record (128, "") from file record segment 394399
is corrupt.
Attribute record (128, "") from file record segment 401355
is corrupt.
6 percent complete. (423476 of 705792 file records processed)
Attribute record (128, "") from file record segment 438447
is corrupt.
Attribute record (128, "") from file record segment 447867
is corrupt.
Attribute record (128, "") from file record segment 450858
is corrupt.
Attribute record (128, "") from file record segment 456831
is corrupt.
Attribute record (128, "") from file record segment 457134
is corrupt.
6 percent complete. (465716 of 705792 file records processed)
Attribute record (128, "") from file record segment 479950
is corrupt.
7 percent complete. (494055 of 705792 file records processed)
Attribute record (160, $I30) from file record segment 509784
is corrupt.
705792 file records processed.
File verification completed.
File record segment 85633 is an orphan.
File record segment 237559 is an orphan.
2603 large file records processed.


Errors found. CHKDSK cannot continue in read-only mode.

I also tried to run chkdsk /f and that resulted in the following:
C:\windows\system32>chkdsk /f
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) Y

This volume will be checked the next time the system restarts.

C:\windows\system32>
chkdsk does not run on restart (ever)

Thanks for your help thus far
 

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

Back
Top