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

Both chkdsk and defrag fail


  • Please log in to reply
19 replies to this topic

#1 JohnBlood

JohnBlood

  • Members
  • 26 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:59 PM

Posted 20 February 2018 - 12:09 AM

I tried to defrag my laptop with UltraDefrag and it failed. The system defrag won't work. When I try to run chkdsk on reboot, it doesn't work. I tried to clone my drive so I could get it fixed, but it failed. How can I get chkdsk and defrag repaired or replaced. Can I fixed the drive with Linux, so I can get an image?



BC AdBot (Login to Remove)

 


#2 Havachat

Havachat

  • Members
  • 1,150 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sleepy Hollow - Geelong - Go Cats.
  • Local time:08:59 AM

Posted 20 February 2018 - 01:32 AM

Cloning the Drive wont fix it....{ Bad Drive = Bad Clone }.

You need to run some diagnostics on the Hard Drive , depending on the Make ? goto the Manufacturers Website for more info.

Or you can try Seagate SeaTools or GsmartControl to test your drive , run the short tests { The long tests may take awhile depending on Drive Size }.

https://www.lifewire.com/free-hard-drive-testing-programs-2626183

 

Did you try Windows Defrag Tool ?

 

If you have an SSD then you shouldnt be Defraging it.....period !

 

If it is in fact the Hard Drive with issues a Moderator may move this to the Hardware Section.



#3 joseibarra

joseibarra

  • Members
  • 1,286 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Downstairs
  • Local time:04:59 PM

Posted 20 February 2018 - 01:57 AM

Nobody but you knows just what failed, won't work and doesn't work means and keep in mind that we can't see what you are seeing.

What's going on with your other topic here and is this somwhow related to this new issue of defrag/chkdsk?

https://www.bleepingcomputer.com/forums/t/670629/bunch-of-iexploreexe-processes-suspended/#entry4444539

 

You need to tell us more details for this defrag/chkdsk issue like:

What you are not seeing that you think you should be seeing

What you are seeing that you don't think you should be seeing ?

 

I don't know about UltraDefrag but what does "it failed" mean?

Does it mean it won't start, you get an error message, it runs but doesn't seem to produce the expected results?

 

The system defrag wont' work?

What is system defrag - is that the built in Windows defragmentation program?

If that's what system defrag means when you attempt to defrag describe exactly what happens, give the exact context of any error messages you see or include a screenshot.

 

Chkdsk on reboot doesn't work?

Do you mean you scheduled a chkdsk with error correction (chkdsk  /r) to run on the next reboot and absolutely nothing happens or something happens that you will describe?

 

You tried to clone your drive and it failed?

What software are you using to clone your drive and when it fails describe how it fails?


The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.


#4 Platypus

Platypus

  • Global Moderator
  • 15,504 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Australia
  • Local time:08:59 AM

Posted 20 February 2018 - 02:22 AM

Please note that you should not try to defragment a drive that shows signs of being faulty or cannot successfully pass a chkdsk analysis. Defragmentation involves considerable alterations to the location of data on the drive, and if the drive or file system has faults, having been defragmented or having defragmentation fail can make successfully accessing data on the drive much more difficult.

Windows Defrag will not proceed if it detects any condition on the drive that could make defrag hazardous to data.

Edited by Platypus, 20 February 2018 - 02:24 AM.

Top 5 things that never get done:

1.

#5 JohnBlood

JohnBlood
  • Topic Starter

  • Members
  • 26 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:59 PM

Posted 20 February 2018 - 07:00 AM

Cloning the Drive wont fix it....{ Bad Drive = Bad Clone }.

You need to run some diagnostics on the Hard Drive , depending on the Make ? goto the Manufacturers Website for more info.

Or you can try Seagate SeaTools or GsmartControl to test your drive , run the short tests { The long tests may take awhile depending on Drive Size }.

https://www.lifewire.com/free-hard-drive-testing-programs-2626183

 

Did you try Windows Defrag Tool ?

 

If you have an SSD then you shouldnt be Defraging it.....period !

 

If it is in fact the Hard Drive with issues a Moderator may move this to the Hardware Section.

 

Windows Defrag tool won't open. When I try to use it from the command line, nothing happens.

 

This is a regular hard drive.



#6 JohnBlood

JohnBlood
  • Topic Starter

  • Members
  • 26 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:59 PM

Posted 20 February 2018 - 07:28 AM

Nobody but you knows just what failed, won't work and doesn't work means and keep in mind that we can't see what you are seeing.

What's going on with your other topic here and is this somwhow related to this new issue of defrag/chkdsk?

https://www.bleepingcomputer.com/forums/t/670629/bunch-of-iexploreexe-processes-suspended/#entry4444539

 

You need to tell us more details for this defrag/chkdsk issue like:

What you are not seeing that you think you should be seeing

What you are seeing that you don't think you should be seeing ?

 

I don't know about UltraDefrag but what does "it failed" mean?

Does it mean it won't start, you get an error message, it runs but doesn't seem to produce the expected results?

 

The system defrag wont' work?

What is system defrag - is that the built in Windows defragmentation program?

If that's what system defrag means when you attempt to defrag describe exactly what happens, give the exact context of any error messages you see or include a screenshot.

 

Chkdsk on reboot doesn't work?

Do you mean you scheduled a chkdsk with error correction (chkdsk  /r) to run on the next reboot and absolutely nothing happens or something happens that you will describe?

 

You tried to clone your drive and it failed?

What software are you using to clone your drive and when it fails describe how it fails?

I apologize for the lack of information in my original post. I was dead tired and wanted to get this posted before I went to bed.

 

1. I'm not sure, but I would not be surprised.

 

2. I should be seeing chkdsk working to repair the bad sectors on the drive. I try to run it and it says that it will run on reboot. On reboot, it starts but exits quickly..

 

3. When I try to defrag with UltraDefrag, the program crashes. According to their site, this is caused when there is a problem with the disk.

 

4. The built-in Windows Defrag will not open. When I try if from the cmd nothing happens.

 

5. See answer #2.

 

6. I tried to clone the drive with EaseUS Todo Backup Home. It seemed to detect that there was a problem with the drive and told me to select sector by sector clone. I did that and it failed 5 times. The error message told me that there were too many fragments and to defrag or free up more space.



#7 JohnBlood

JohnBlood
  • Topic Starter

  • Members
  • 26 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:59 PM

Posted 20 February 2018 - 07:35 AM

The ultimate goal of cloning this drive is to get a new drive from the manufacturer. (it is still under warranty, thankfully). 

 

I forgot that I have tried in the past to replace the corrupted system files from a Windows install disk. However, the disk I had was a rescue disk from the laptop maker, so I used another Windows 7 install disk to do it. Now, the files are mismatched. 

 

Here is the information for a src scan I ran last night. Might help.

 

2015-05-29 18:47:51, Info                  CSI    00000009 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:47:51, Info                  CSI    0000000a [SR] Beginning Verify and Repair transaction
2015-05-29 18:47:54, Info                  CSI    0000000c [SR] Verify complete
2015-05-29 18:47:55, Info                  CSI    0000000d [SR] Verifying 100 (0x00000064) components
2015-05-29 18:47:55, Info                  CSI    0000000e [SR] Beginning Verify and Repair transaction
2015-05-29 18:47:58, Info                  CSI    00000010 [SR] Verify complete
2015-05-29 18:47:59, Info                  CSI    00000011 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:47:59, Info                  CSI    00000012 [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:03, Info                  CSI    00000014 [SR] Verify complete
2015-05-29 18:48:04, Info                  CSI    00000015 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:04, Info                  CSI    00000016 [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:08, Info                  CSI    00000018 [SR] Verify complete
2015-05-29 18:48:09, Info                  CSI    00000019 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:09, Info                  CSI    0000001a [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:11, Info                  CSI    0000001c [SR] Verify complete
2015-05-29 18:48:12, Info                  CSI    0000001d [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:12, Info                  CSI    0000001e [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:13, Info                  CSI    00000020 [SR] Verify complete
2015-05-29 18:48:14, Info                  CSI    00000021 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:14, Info                  CSI    00000022 [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:15, Info                  CSI    00000024 [SR] Verify complete
2015-05-29 18:48:16, Info                  CSI    00000025 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:16, Info                  CSI    00000026 [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:18, Info                  CSI    00000028 [SR] Verify complete
2015-05-29 18:48:19, Info                  CSI    00000029 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:19, Info                  CSI    0000002a [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:20, Info                  CSI    0000002c [SR] Verify complete
2015-05-29 18:48:21, Info                  CSI    0000002d [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:21, Info                  CSI    0000002e [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:23, Info                  CSI    00000030 [SR] Verify complete
2015-05-29 18:48:23, Info                  CSI    00000031 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:23, Info                  CSI    00000032 [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:26, Info                  CSI    00000034 [SR] Verify complete
2015-05-29 18:48:27, Info                  CSI    00000035 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:27, Info                  CSI    00000036 [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:29, Info                  CSI    00000038 [SR] Verify complete
2015-05-29 18:48:30, Info                  CSI    00000039 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:30, Info                  CSI    0000003a [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:32, Info                  CSI    0000003c [SR] Verify complete
2015-05-29 18:48:33, Info                  CSI    0000003d [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:33, Info                  CSI    0000003e [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:35, Info                  CSI    00000040 [SR] Verify complete
2015-05-29 18:48:35, Info                  CSI    00000041 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:35, Info                  CSI    00000042 [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:37, Info                  CSI    00000044 [SR] Verify complete
2015-05-29 18:48:37, Info                  CSI    00000045 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:37, Info                  CSI    00000046 [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:41, Info                  CSI    00000048 [SR] Verify complete
2015-05-29 18:48:41, Info                  CSI    00000049 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:41, Info                  CSI    0000004a [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:44, Info                  CSI    0000004c [SR] Verify complete
2015-05-29 18:48:44, Info                  CSI    0000004d [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:44, Info                  CSI    0000004e [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:47, Info                  CSI    00000050 [SR] Verify complete
2015-05-29 18:48:47, Info                  CSI    00000051 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:47, Info                  CSI    00000052 [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:52, Info                  CSI    00000054 [SR] Verify complete
2015-05-29 18:48:52, Info                  CSI    00000055 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:52, Info                  CSI    00000056 [SR] Beginning Verify and Repair transaction
2015-05-29 18:48:58, Info                  CSI    00000058 [SR] Verify complete
2015-05-29 18:48:58, Info                  CSI    00000059 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:48:58, Info                  CSI    0000005a [SR] Beginning Verify and Repair transaction
2015-05-29 18:49:00, Info                  CSI    0000005c [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:49:03, Info                  CSI    0000005f [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:49:03, Info                  CSI    00000060 [SR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7601.17514.WindowsFoundationDelivery"
2015-05-29 18:49:03, Info                  CSI    00000063 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"autochk.exe"; source file in store is also corrupted
2015-05-29 18:49:04, Info                  CSI    00000066 [SR] Verify complete
2015-05-29 18:49:04, Info                  CSI    00000067 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:49:04, Info                  CSI    00000068 [SR] Beginning Verify and Repair transaction
2015-05-29 18:49:08, Info                  CSI    0000006c [SR] Verify complete
2015-05-29 18:49:08, Info                  CSI    0000006d [SR] Verifying 100 (0x00000064) components
2015-05-29 18:49:08, Info                  CSI    0000006e [SR] Beginning Verify and Repair transaction
2015-05-29 18:49:12, Info                  CSI    00000070 [SR] Verify complete
2015-05-29 18:49:12, Info                  CSI    00000071 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:49:12, Info                  CSI    00000072 [SR] Beginning Verify and Repair transaction
2015-05-29 18:49:17, Info                  CSI    00000076 [SR] Verify complete
2015-05-29 18:49:17, Info                  CSI    00000077 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:49:17, Info                  CSI    00000078 [SR] Beginning Verify and Repair transaction
2015-05-29 18:49:25, Info                  CSI    00000082 [SR] Verify complete
2015-05-29 18:49:25, Info                  CSI    00000083 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:49:25, Info                  CSI    00000084 [SR] Beginning Verify and Repair transaction
2015-05-29 18:49:31, Info                  CSI    00000086 [SR] Verify complete
2015-05-29 18:49:31, Info                  CSI    00000087 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:49:31, Info                  CSI    00000088 [SR] Beginning Verify and Repair transaction
2015-05-29 18:49:36, Info                  CSI    0000008a [SR] Verify complete
2015-05-29 18:49:36, Info                  CSI    0000008b [SR] Verifying 100 (0x00000064) components
2015-05-29 18:49:36, Info                  CSI    0000008c [SR] Beginning Verify and Repair transaction
2015-05-29 18:49:40, Info                  CSI    0000008e [SR] Verify complete
2015-05-29 18:49:41, Info                  CSI    0000008f [SR] Verifying 100 (0x00000064) components
2015-05-29 18:49:41, Info                  CSI    00000090 [SR] Beginning Verify and Repair transaction
2015-05-29 18:49:45, Info                  CSI    00000092 [SR] Verify complete
2015-05-29 18:49:46, Info                  CSI    00000093 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:49:46, Info                  CSI    00000094 [SR] Beginning Verify and Repair transaction
2015-05-29 18:49:50, Info                  CSI    00000096 [SR] Verify complete
2015-05-29 18:49:50, Info                  CSI    00000097 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:49:50, Info                  CSI    00000098 [SR] Beginning Verify and Repair transaction
2015-05-29 18:49:56, Info                  CSI    0000009a [SR] Verify complete
2015-05-29 18:49:56, Info                  CSI    0000009b [SR] Verifying 100 (0x00000064) components
2015-05-29 18:49:56, Info                  CSI    0000009c [SR] Beginning Verify and Repair transaction
2015-05-29 18:50:06, Info                  CSI    000000a0 [SR] Verify complete
2015-05-29 18:50:06, Info                  CSI    000000a1 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:50:06, Info                  CSI    000000a2 [SR] Beginning Verify and Repair transaction
2015-05-29 18:50:13, Info                  CSI    000000a4 [SR] Verify complete
2015-05-29 18:50:13, Info                  CSI    000000a5 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:50:13, Info                  CSI    000000a6 [SR] Beginning Verify and Repair transaction
2015-05-29 18:50:26, Info                  CSI    000000a8 [SR] Verify complete
2015-05-29 18:50:26, Info                  CSI    000000a9 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:50:26, Info                  CSI    000000aa [SR] Beginning Verify and Repair transaction
2015-05-29 18:50:34, Info                  CSI    000000ac [SR] Verify complete
2015-05-29 18:50:35, Info                  CSI    000000ad [SR] Verifying 100 (0x00000064) components
2015-05-29 18:50:35, Info                  CSI    000000ae [SR] Beginning Verify and Repair transaction
2015-05-29 18:50:37, Info                  CSI    000000b0 [SR] Verify complete
2015-05-29 18:50:38, Info                  CSI    000000b1 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:50:38, Info                  CSI    000000b2 [SR] Beginning Verify and Repair transaction
2015-05-29 18:50:39, Info                  CSI    000000b4 [SR] Verify complete
2015-05-29 18:50:39, Info                  CSI    000000b5 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:50:39, Info                  CSI    000000b6 [SR] Beginning Verify and Repair transaction
2015-05-29 18:50:42, Info                  CSI    000000b8 [SR] Verify complete
2015-05-29 18:50:42, Info                  CSI    000000b9 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:50:42, Info                  CSI    000000ba [SR] Beginning Verify and Repair transaction
2015-05-29 18:50:51, Info                  CSI    000000d8 [SR] Verify complete
2015-05-29 18:50:52, Info                  CSI    000000d9 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:50:52, Info                  CSI    000000da [SR] Beginning Verify and Repair transaction
2015-05-29 18:50:54, Info                  CSI    000000dc [SR] Verify complete
2015-05-29 18:50:55, Info                  CSI    000000dd [SR] Verifying 100 (0x00000064) components
2015-05-29 18:50:55, Info                  CSI    000000de [SR] Beginning Verify and Repair transaction
2015-05-29 18:50:56, Info                  CSI    000000e0 [SR] Verify complete
2015-05-29 18:50:57, Info                  CSI    000000e1 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:50:57, Info                  CSI    000000e2 [SR] Beginning Verify and Repair transaction
2015-05-29 18:51:00, Info                  CSI    000000e4 [SR] Verify complete
2015-05-29 18:51:01, Info                  CSI    000000e5 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:51:01, Info                  CSI    000000e6 [SR] Beginning Verify and Repair transaction
2015-05-29 18:51:05, Info                  CSI    000000e8 [SR] Verify complete
2015-05-29 18:51:06, Info                  CSI    000000e9 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:51:06, Info                  CSI    000000ea [SR] Beginning Verify and Repair transaction
2015-05-29 18:51:15, Info                  CSI    000000ed [SR] Verify complete
2015-05-29 18:51:16, Info                  CSI    000000ee [SR] Verifying 100 (0x00000064) components
2015-05-29 18:51:16, Info                  CSI    000000ef [SR] Beginning Verify and Repair transaction
2015-05-29 18:51:21, Info                  CSI    000000f1 [SR] Verify complete
2015-05-29 18:51:21, Info                  CSI    000000f2 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:51:21, Info                  CSI    000000f3 [SR] Beginning Verify and Repair transaction
2015-05-29 18:51:22, Info                  CSI    000000f5 [SR] Verify complete
2015-05-29 18:51:23, Info                  CSI    000000f6 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:51:23, Info                  CSI    000000f7 [SR] Beginning Verify and Repair transaction
2015-05-29 18:51:26, Info                  CSI    000000f9 [SR] Verify complete
2015-05-29 18:51:26, Info                  CSI    000000fa [SR] Verifying 100 (0x00000064) components
2015-05-29 18:51:26, Info                  CSI    000000fb [SR] Beginning Verify and Repair transaction
2015-05-29 18:51:31, Info                  CSI    000000fd [SR] Verify complete
2015-05-29 18:51:31, Info                  CSI    000000fe [SR] Verifying 100 (0x00000064) components
2015-05-29 18:51:31, Info                  CSI    000000ff [SR] Beginning Verify and Repair transaction
2015-05-29 18:51:36, Info                  CSI    00000101 [SR] Verify complete
2015-05-29 18:51:37, Info                  CSI    00000102 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:51:37, Info                  CSI    00000103 [SR] Beginning Verify and Repair transaction
2015-05-29 18:51:42, Info                  CSI    00000105 [SR] Verify complete
2015-05-29 18:51:42, Info                  CSI    00000106 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:51:42, Info                  CSI    00000107 [SR] Beginning Verify and Repair transaction
2015-05-29 18:51:53, Info                  CSI    0000012d [SR] Verify complete
2015-05-29 18:51:53, Info                  CSI    0000012e [SR] Verifying 100 (0x00000064) components
2015-05-29 18:51:53, Info                  CSI    0000012f [SR] Beginning Verify and Repair transaction
2015-05-29 18:52:01, Info                  CSI    00000131 [SR] Verify complete
2015-05-29 18:52:01, Info                  CSI    00000132 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:52:01, Info                  CSI    00000133 [SR] Beginning Verify and Repair transaction
2015-05-29 18:52:19, Info                  CSI    00000135 [SR] Verify complete
2015-05-29 18:52:19, Info                  CSI    00000136 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:52:19, Info                  CSI    00000137 [SR] Beginning Verify and Repair transaction
2015-05-29 18:52:26, Info                  CSI    00000139 [SR] Verify complete
2015-05-29 18:52:27, Info                  CSI    0000013a [SR] Verifying 100 (0x00000064) components
2015-05-29 18:52:27, Info                  CSI    0000013b [SR] Beginning Verify and Repair transaction
2015-05-29 18:52:36, Info                  CSI    0000013e [SR] Verify complete
2015-05-29 18:52:37, Info                  CSI    0000013f [SR] Verifying 100 (0x00000064) components
2015-05-29 18:52:37, Info                  CSI    00000140 [SR] Beginning Verify and Repair transaction
2015-05-29 18:52:42, Info                  CSI    00000142 [SR] Verify complete
2015-05-29 18:52:43, Info                  CSI    00000143 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:52:43, Info                  CSI    00000144 [SR] Beginning Verify and Repair transaction
2015-05-29 18:52:47, Info                  CSI    00000146 [SR] Verify complete
2015-05-29 18:52:47, Info                  CSI    00000147 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:52:47, Info                  CSI    00000148 [SR] Beginning Verify and Repair transaction
2015-05-29 18:52:52, Info                  CSI    0000014a [SR] Verify complete
2015-05-29 18:52:53, Info                  CSI    0000014b [SR] Verifying 100 (0x00000064) components
2015-05-29 18:52:53, Info                  CSI    0000014c [SR] Beginning Verify and Repair transaction
2015-05-29 18:52:57, Info                  CSI    0000014e [SR] Verify complete
2015-05-29 18:52:57, Info                  CSI    0000014f [SR] Verifying 100 (0x00000064) components
2015-05-29 18:52:57, Info                  CSI    00000150 [SR] Beginning Verify and Repair transaction
2015-05-29 18:53:01, Info                  CSI    00000153 [SR] Verify complete
2015-05-29 18:53:01, Info                  CSI    00000154 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:53:01, Info                  CSI    00000155 [SR] Beginning Verify and Repair transaction
2015-05-29 18:53:09, Info                  CSI    00000157 [SR] Verify complete
2015-05-29 18:53:09, Info                  CSI    00000158 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:53:09, Info                  CSI    00000159 [SR] Beginning Verify and Repair transaction
2015-05-29 18:53:22, Info                  CSI    0000015b [SR] Verify complete
2015-05-29 18:53:22, Info                  CSI    0000015c [SR] Verifying 100 (0x00000064) components
2015-05-29 18:53:22, Info                  CSI    0000015d [SR] Beginning Verify and Repair transaction
2015-05-29 18:53:29, Info                  CSI    00000160 [SR] Verify complete
2015-05-29 18:53:29, Info                  CSI    00000161 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:53:29, Info                  CSI    00000162 [SR] Beginning Verify and Repair transaction
2015-05-29 18:53:34, Info                  CSI    00000164 [SR] Verify complete
2015-05-29 18:53:34, Info                  CSI    00000165 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:53:34, Info                  CSI    00000166 [SR] Beginning Verify and Repair transaction
2015-05-29 18:53:40, Info                  CSI    00000168 [SR] Verify complete
2015-05-29 18:53:40, Info                  CSI    00000169 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:53:40, Info                  CSI    0000016a [SR] Beginning Verify and Repair transaction
2015-05-29 18:53:49, Info                  CSI    0000016d [SR] Verify complete
2015-05-29 18:53:49, Info                  CSI    0000016e [SR] Verifying 100 (0x00000064) components
2015-05-29 18:53:49, Info                  CSI    0000016f [SR] Beginning Verify and Repair transaction
2015-05-29 18:53:54, Info                  CSI    00000171 [SR] Verify complete
2015-05-29 18:53:54, Info                  CSI    00000172 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:53:54, Info                  CSI    00000173 [SR] Beginning Verify and Repair transaction
2015-05-29 18:53:59, Info                  CSI    00000175 [SR] Verify complete
2015-05-29 18:53:59, Info                  CSI    00000176 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:53:59, Info                  CSI    00000177 [SR] Beginning Verify and Repair transaction
2015-05-29 18:54:04, Info                  CSI    00000179 [SR] Verify complete
2015-05-29 18:54:04, Info                  CSI    0000017a [SR] Verifying 100 (0x00000064) components
2015-05-29 18:54:04, Info                  CSI    0000017b [SR] Beginning Verify and Repair transaction
2015-05-29 18:54:09, Info                  CSI    0000017e [SR] Verify complete
2015-05-29 18:54:09, Info                  CSI    0000017f [SR] Verifying 100 (0x00000064) components
2015-05-29 18:54:09, Info                  CSI    00000180 [SR] Beginning Verify and Repair transaction
2015-05-29 18:54:15, Info                  CSI    00000182 [SR] Verify complete
2015-05-29 18:54:16, Info                  CSI    00000183 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:54:16, Info                  CSI    00000184 [SR] Beginning Verify and Repair transaction
2015-05-29 18:54:16, Info                  CSI    00000186 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:54:16, Info                  CSI    00000188 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:54:19, Info                  CSI    0000018a [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:54:19, Info                  CSI    0000018b [SR] This component was referenced by [l:158{79}]"Package_168_for_KB3022345~31bf3856ad364e35~x86~~6.1.1.2.3022345-604_neutral_GDR"
2015-05-29 18:54:19, Info                  CSI    0000018d [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:54:19, Info                  CSI    0000018e [SR] This component was referenced by [l:158{79}]"Package_168_for_KB3022345~31bf3856ad364e35~x86~~6.1.1.2.3022345-604_neutral_GDR"
2015-05-29 18:54:19, Info                  CSI    00000191 [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:24{12}]"utc.app.json"; source file in store is also corrupted
2015-05-29 18:54:19, Info                  CSI    00000194 [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:66{33}]"telemetry.ASM-WindowsDefault.json"; source file in store is also corrupted
2015-05-29 18:54:19, Info                  CSI    00000197 [SR] Verify complete
2015-05-29 18:54:19, Info                  CSI    00000198 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:54:19, Info                  CSI    00000199 [SR] Beginning Verify and Repair transaction
2015-05-29 18:54:25, Info                  CSI    0000019b [SR] Verify complete
2015-05-29 18:54:26, Info                  CSI    0000019c [SR] Verifying 100 (0x00000064) components
2015-05-29 18:54:26, Info                  CSI    0000019d [SR] Beginning Verify and Repair transaction
2015-05-29 18:54:32, Info                  CSI    000001a0 [SR] Verify complete
2015-05-29 18:54:32, Info                  CSI    000001a1 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:54:32, Info                  CSI    000001a2 [SR] Beginning Verify and Repair transaction
2015-05-29 18:54:37, Info                  CSI    000001a4 [SR] Verify complete
2015-05-29 18:54:38, Info                  CSI    000001a5 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:54:38, Info                  CSI    000001a6 [SR] Beginning Verify and Repair transaction
2015-05-29 18:54:44, Info                  CSI    000001a8 [SR] Verify complete
2015-05-29 18:54:44, Info                  CSI    000001a9 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:54:44, Info                  CSI    000001aa [SR] Beginning Verify and Repair transaction
2015-05-29 18:54:50, Info                  CSI    000001ac [SR] Verify complete
2015-05-29 18:54:50, Info                  CSI    000001ad [SR] Verifying 100 (0x00000064) components
2015-05-29 18:54:50, Info                  CSI    000001ae [SR] Beginning Verify and Repair transaction
2015-05-29 18:54:55, Info                  CSI    000001b0 [SR] Verify complete
2015-05-29 18:54:55, Info                  CSI    000001b1 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:54:55, Info                  CSI    000001b2 [SR] Beginning Verify and Repair transaction
2015-05-29 18:54:56, Info                  CSI    000001b4 [SR] Verify complete
2015-05-29 18:54:57, Info                  CSI    000001b5 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:54:57, Info                  CSI    000001b6 [SR] Beginning Verify and Repair transaction
2015-05-29 18:55:01, Info                  CSI    000001b8 [SR] Verify complete
2015-05-29 18:55:01, Info                  CSI    000001b9 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:55:01, Info                  CSI    000001ba [SR] Beginning Verify and Repair transaction
2015-05-29 18:55:06, Info                  CSI    000001bc [SR] Verify complete
2015-05-29 18:55:06, Info                  CSI    000001bd [SR] Verifying 100 (0x00000064) components
2015-05-29 18:55:06, Info                  CSI    000001be [SR] Beginning Verify and Repair transaction
2015-05-29 18:55:11, Info                  CSI    000001c0 [SR] Verify complete
2015-05-29 18:55:11, Info                  CSI    000001c1 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:55:11, Info                  CSI    000001c2 [SR] Beginning Verify and Repair transaction
2015-05-29 18:55:14, Info                  CSI    000001c4 [SR] Verify complete
2015-05-29 18:55:15, Info                  CSI    000001c5 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:55:15, Info                  CSI    000001c6 [SR] Beginning Verify and Repair transaction
2015-05-29 18:55:19, Info                  CSI    000001c8 [SR] Verify complete
2015-05-29 18:55:19, Info                  CSI    000001c9 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:55:19, Info                  CSI    000001ca [SR] Beginning Verify and Repair transaction
2015-05-29 18:55:32, Info                  CSI    000001cc [SR] Verify complete
2015-05-29 18:55:32, Info                  CSI    000001cd [SR] Verifying 100 (0x00000064) components
2015-05-29 18:55:32, Info                  CSI    000001ce [SR] Beginning Verify and Repair transaction
2015-05-29 18:55:47, Info                  CSI    000001d0 [SR] Verify complete
2015-05-29 18:55:48, Info                  CSI    000001d1 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:55:48, Info                  CSI    000001d2 [SR] Beginning Verify and Repair transaction
2015-05-29 18:55:52, Info                  CSI    000001d4 [SR] Verify complete
2015-05-29 18:55:53, Info                  CSI    000001d5 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:55:53, Info                  CSI    000001d6 [SR] Beginning Verify and Repair transaction
2015-05-29 18:55:56, Info                  CSI    000001d8 [SR] Verify complete
2015-05-29 18:55:56, Info                  CSI    000001d9 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:55:56, Info                  CSI    000001da [SR] Beginning Verify and Repair transaction
2015-05-29 18:55:58, Info                  CSI    000001dc [SR] Verify complete
2015-05-29 18:55:58, Info                  CSI    000001dd [SR] Verifying 100 (0x00000064) components
2015-05-29 18:55:58, Info                  CSI    000001de [SR] Beginning Verify and Repair transaction
2015-05-29 18:56:02, Info                  CSI    000001e0 [SR] Verify complete
2015-05-29 18:56:02, Info                  CSI    000001e1 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:56:02, Info                  CSI    000001e2 [SR] Beginning Verify and Repair transaction
2015-05-29 18:56:07, Info                  CSI    000001e4 [SR] Verify complete
2015-05-29 18:56:07, Info                  CSI    000001e5 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:56:07, Info                  CSI    000001e6 [SR] Beginning Verify and Repair transaction
2015-05-29 18:56:09, Info                  CSI    000001e8 [SR] Verify complete
2015-05-29 18:56:09, Info                  CSI    000001e9 [SR] Verifying 100 (0x00000064) components
2015-05-29 18:56:09, Info                  CSI    000001ea [SR] Beginning Verify and Repair transaction
2015-05-29 18:56:10, Info                  CSI    000001ec [SR] Verify complete
2015-05-29 18:56:10, Info                  CSI    000001ed [SR] Verifying 100 (0x00000064) components
2015-05-29 18:56:10, Info                  CSI    000001ee [SR] Beginning Verify and Repair transaction
2015-05-29 18:56:15, Info                  CSI    000001f0 [SR] Verify complete
2015-05-29 18:56:15, Info                  CSI    000001f1 [SR] Verifying 53 (0x00000035) components
2015-05-29 18:56:15, Info                  CSI    000001f2 [SR] Beginning Verify and Repair transaction
2015-05-29 18:56:17, Info                  CSI    000001f4 [SR] Verify complete
2015-05-29 18:56:17, Info                  CSI    000001f5 [SR] Repairing 2 components
2015-05-29 18:56:17, Info                  CSI    000001f6 [SR] Beginning Verify and Repair transaction
2015-05-29 18:56:17, Info                  CSI    000001f8 [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:56:17, Info                  CSI    000001fa [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:56:17, Info                  CSI    000001fc [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:56:17, Info                  CSI    000001fe [SR] Cannot repair member file [l:22{11}]"autochk.exe" of Microsoft-Windows-Autochk, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:56:17, Info                  CSI    000001ff [SR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7601.17514.WindowsFoundationDelivery"
2015-05-29 18:56:17, Info                  CSI    00000202 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:22{11}]"autochk.exe"; source file in store is also corrupted
2015-05-29 18:56:17, Info                  CSI    00000204 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:56:17, Info                  CSI    00000205 [SR] This component was referenced by [l:158{79}]"Package_168_for_KB3022345~31bf3856ad364e35~x86~~6.1.1.2.3022345-604_neutral_GDR"
2015-05-29 18:56:17, Info                  CSI    00000207 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-29 18:56:17, Info                  CSI    00000208 [SR] This component was referenced by [l:158{79}]"Package_168_for_KB3022345~31bf3856ad364e35~x86~~6.1.1.2.3022345-604_neutral_GDR"
2015-05-29 18:56:17, Info                  CSI    0000020b [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:24{12}]"utc.app.json"; source file in store is also corrupted
2015-05-29 18:56:17, Info                  CSI    0000020e [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:66{33}]"telemetry.ASM-WindowsDefault.json"; source file in store is also corrupted
2015-05-29 18:56:18, Info                  CSI    00000211 [SR] Repair complete
2015-05-29 18:56:18, Info                  CSI    00000212 [SR] Committing transaction
2015-05-29 18:56:18, Info                  CSI    00000216 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired


#8 Torchwood

Torchwood

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Hampshire UK
  • Local time:10:59 PM

Posted 20 February 2018 - 09:37 AM

very interresting dates on that scan

2015

Take it you have not been able to update since then

 

 

kb3022345 WAS a known problematic update released by MS  and caused the json errors part of the GWX readiness suite

(and since been superceeded)

the Autochk problem is why the inbuilt defrag is failing 

 

please uninstall KB3022345

 

as for autochk

please download/run this tool to your desktop copy/paste the output

 

http://www.sysnative.com/niemiro/apps/SFCFix.exe

 

 

your quote

so I used another Windows 7 install disk to do it. Now, the files are mismatched. 

suspect this was corrupt

Dell provides a download service, all you need is your service tag

http://www.dell.com/support/home/uk/en/ukbsdt1/drivers/osiso/recoverytool/

 

also see your thread @W7 my comments

 

Roy


Edited by Torchwood, 20 February 2018 - 10:09 AM.


#9 Allan

Allan

  • BC Advisor
  • 8,646 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:59 PM

Posted 20 February 2018 - 09:39 AM

Download SeaTools for DOS, burn it to a CD, boot to it and let it run: https://www.seagate.com/support/downloads/seatools/seatools-dos-master/



#10 joseibarra

joseibarra

  • Members
  • 1,286 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Downstairs
  • Local time:04:59 PM

Posted 20 February 2018 - 11:28 AM

If your autochk.exe is afflicted like your old log file indicates that could be why your scheduled chkdsk isn't running on restart.

 

When you schedule a chkdsk to run on restart it modifies an entry in the registry and when the system starts and if the value is present autochk.exe will run the chkdsk - so if your autochk.exe is afflicted that could be why the scheduled chkdsk is not running on restart.

 

Pursuing SFCFix is a good start with SFC problems and if there are problems it can't fix and nobody here can fix them  pursue the problem in the Sysnative community where they know how to fix SFC problems by doing things instead of trying things.  Try not.  Do or do not.  There is no try.

 

As was pointed out it looks like you have some KBs installed that are knows to cause SFC to report errors so you need to get rid of (uninstall then hide) those too - do that first.

 

Another thing autochk.exe does on every restart is it checks the "dirty" bit on all volumes and if a volume is dirty, autochk wll automatically run a chkdsk with error correction (chkdsk  /r) to try to fix the dirty volume.

 

This is why sometimes after power failures a chkdsk with error correction seems to run unscheduled...  the volume was marked dirty because of the power failure or maybe some other things like reset button, plug pulling, ungraceful shutdown or aborted restart, etc.

 

Go ahead and check the dirty bit on your system volumes (hard drives).

 

Here's how:

 

You can query the dirty bit on a volume from the command prompt window with Administrator privileges.

 

Click the Start orb/button and in the box enter the following:

cmd.exe

Right click cmd.exe and choose to Run as Administrator:

 

[attachment=202389:1.jpg]

 

To query the dirty bit on drive C, in the Command Prompt window enter the following command:

fsutil  dirty  query  C:

 

[attachment=202390:2.jpg]

 

Sample output should be one or the other of:

 

Volume C: is dirty
Volume C is NOT dirty

You should check each of your volumes or each of your hard drives (C, D, E, etc.).

 

Enter 'exit' to close the Command Prompt window.

 

If a volume is dirty the only thing that can clear it is a chkdsk with error correction and you might need to run it more than one time.  If the drive is failing, you might not ever be able to clear the dirty bit so chkdsk will always run on a restart. 

 

If the dirty bit will never clear you should consider replacing the drive but in the meantime you can tell Windows to NOT check the dirty bit on a volume by issuing a command like this example for the C drive:

 

chkntfs   /x   c:

 

That would tell Windows to never check the dirty bit on volume C but that is risky behavior because if the dirty bit will not clear, something is wrong with that drive.

 

You can undo that command and reset the automatic error checking back to the default value with this command:

 

chkntfs   /d


Edited by joseibarra, 20 February 2018 - 11:29 AM.

The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.


#11 Allan

Allan

  • BC Advisor
  • 8,646 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:59 PM

Posted 20 February 2018 - 11:47 AM

autocheck will run checkdisk with the /f switch but not the /r switch. To make it simple for the OP, he should either run chkdsk /r "manually" (from the command prompt and then "yes" to run at the next boot) or, even better, Sea Tools for DOS as suggested above.



#12 Torchwood

Torchwood

  • Members
  • 48 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Hampshire UK
  • Local time:10:59 PM

Posted 20 February 2018 - 03:33 PM

Running the Sea tools is the priority

NO point in trying anything else if its Bad.

 

if the Sfc report comes back as i expect - i have the fix for it (Autochk.)

I also have a fix if that KB will not uninstall using the normal - uninstall update option

 

The bigger problem is that if the bad blocks are within the OS "operational run files"  it wont make a blind bit of difference what we do it will either recorrupt the same files or others

 

Roy


Edited by Torchwood, 20 February 2018 - 03:36 PM.


#13 JohnBlood

JohnBlood
  • Topic Starter

  • Members
  • 26 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:59 PM

Posted 20 February 2018 - 11:57 PM

I was unable to run the SeaTools because I forgot that I'm out of CDs. I tried to put it on a thumbdrive using instructions that I found on SevenForums. However, when I rebooted, it just said "FreeDOS" in the corner. I'll try that again tomorrow.

 

I installed Data Lifeguard Diagnostics from Western Digital the makers of the drive and ran those scans. Below are the results: 

 

e4Sfiks.jpg

 

 

 

 

I also ran SFCFix tool. Here are the results:

 

SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-02-20 23:07:14.140
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
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-defrag-core_31bf3856ad364e35_6.1.7600.16385_none_74535a2cd1bda1d0\defragproxy.dll
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-icm-profiles_31bf3856ad364e35_6.1.7600.16385_none_f5547dd01f628131\D65.camp
 
 
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     3
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          102
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.
 
 
 
 
Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2018-02-20 23:08:25.994
----------------------EOF-----------------------
 
P.S. I spent half an hour trying to figure out how to add an image to this post and getting progressively more pissed off. I wish the dialog boxes had a little more help text. Going to bed now.
 
P.P.S. I finally figured out the image thing and updated the post.

Edited by JohnBlood, 21 February 2018 - 10:45 PM.


#14 Allan

Allan

  • BC Advisor
  • 8,646 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:04:59 PM

Posted 21 February 2018 - 07:14 AM

Buy cd's and run Sea Tools.



#15 joseibarra

joseibarra

  • Members
  • 1,286 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Downstairs
  • Local time:04:59 PM

Posted 21 February 2018 - 07:18 PM

Your SFCFix report indicates some of the files you need to run the things you want to run seem afflicted.

 

If Torchwood doesn't have the fix the you should do this (I chopped out all the stuff you've already done):

 

 

 

If SFCFix.exe can't fix the problem you then register a new account at Sysnative, follow the directions and they will send you back a ZIP file with the fixes for you to apply.  Often you get the fix in one message cycle because they know what they are doing.  It might take a little more depending on what is wrong.

 

Be sure to read, understand and follow their directions exactly:

 

https://www.sysnative.com/forums/windows-update/4736-windows-update-forum-posting-instructions.html

 

Following the directions will get you the fastest and best reply in the fewest message cycles.

 

For simple cases what usually happens is they will analyze the report (may ask for more details) and eventually send you some instructions and a ZIP file that has in it the files you need to correct the problem and you are done.

 

Sometimes the problems are more complicated but eventually they should help get things squared away.

 

Be a mench and come back and tell us how it goes!


The mediocre teacher tells. The good teacher explains. The superior teacher demonstrates.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users