TechSpot

Disk defragment I can't find C

By madara
Nov 15, 2011
Post New Reply
  1. So recently I tried to defrag my main hard drive which is C

    When I opened up disk defragmenter, the only disk that was shown was the Recovery disk, I can't find the C

    Anyone help?
  2. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    Please state what version of Windows you are using.

    Try running a disk check first. Click on Start then Run for XP.
    Type cmd into the search box and right click on the cmd in the pop up and select Run as Administrator. For XP just type cmd in the run box and hit Enter.
    At the Command Prompt type chkdsk /r (include the space before the /) and hit Enter.
    It will ask if you want to run on reboot, type y and hit enter, then reboot.
    The process will start on boot up and could take over an hour to complete, watch the results as they display on screen. If it appears to freeze this is normal, do not stop the process, be patient and leave it to complete. It will boot back into windows when it has finished.

    Now try defrag again.
  3. jobeard

    jobeard TS Ambassador Posts: 13,368   +302

    BEFORE you even think of using defrag ALWAYS run CHKDSK /F.
    (the chkdsk /r noted above is a good idea given the sequence of events)

    If you do not, you risk HD corruption from a defrag using bad clusters :(
  4. madara

    madara Newcomer, in training Topic Starter Posts: 31

    I use window 7,

    BTW i did a chkdsk before, I ran chkdsk while at boot (before the login screen)

    The chkdsk took me a day so I left it on over night and the next day I check it it was at the login screen

    When I open disk defragmenter, the main drive C was not detected. :(
  5. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    You may not know this, Window 7 is set by default to defrag the hard drive once a week, so if you have not changed the settings your hard drive is very unlikely to need a defrag.

    What parameter did you use with chkdsk, or did you just run the command without /r or /f?

    Why do you think the C: drive needs to be defraged.
  6. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    In addition to the above it may help if you could post the chkdsk log, follow this:

    • To find a detailed log of the disk check click on Start and type event into the box. You will see Event Viewer appear in a pop up list, click on it to open the Event Viewer.
    • In the left hand pane click on the > next to Windows Logs and then click on Application. In the top of the centre pane, scroll down the list to find Wininit under the Source column. Click on the first one you come to that has the date of the scan next to it. The log will be displayed in the pane below.
    • Now look in the right hand pane and click on Copy and then select Copy Details as Text.
    • Close all the windows and go back to this forum and right click on the message box and select Paste.

    The full log should then appear in the box. Add any other comments you wish to make and post the message.
  7. madara

    madara Newcomer, in training Topic Starter Posts: 31

    I run chkdsk by going to property of the disk and tool, then error checking, I checked both box and I reboot my computer and it check it automatically.

    When I try to re-schedule the disk defragmenter, I couldn't find C, probably my C got damaged.

    Log Name: Application
    Source: Microsoft-Windows-Wininit
    Date: 11/8/2011 12:59:57 AM
    Event ID: 1001
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: Kevin-PC
    Description:


    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is OS.


    One of your disks needs to be checked for consistency. You
    may cancel the disk check, but it is strongly recommended
    that you continue.
    Windows will now check the disk.

    CHKDSK is verifying files (stage 1 of 3)...
    Read failure with status 0xc0000185 at offset 0x2e2fde5000 for 0x1000 bytes.
    File record segment 23108 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fde5000 for 0x1000 bytes.
    File record segment 23109 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf0000 for 0x1000 bytes.
    File record segment 23152 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf0000 for 0x1000 bytes.
    File record segment 23153 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf0000 for 0x1000 bytes.
    File record segment 23154 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf0000 for 0x1000 bytes.
    File record segment 23155 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf1000 for 0x1000 bytes.
    File record segment 23156 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf1000 for 0x1000 bytes.
    File record segment 23157 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf1000 for 0x1000 bytes.
    File record segment 23158 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf1000 for 0x1000 bytes.
    File record segment 23159 is unreadable.
    Read failure with status 0xc00000b5 at offset 0x2e2fdf2000 for 0x1000 bytes.
    File record segment 23160 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf2000 for 0x1000 bytes.
    File record segment 23161 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf2000 for 0x1000 bytes.
    File record segment 23162 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf2000 for 0x1000 bytes.
    File record segment 23163 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdfc000 for 0x1000 bytes.
    File record segment 23200 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdfc000 for 0x1000 bytes.
    File record segment 23201 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe02000 for 0x1000 bytes.
    File record segment 23224 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe02000 for 0x1000 bytes.
    File record segment 23225 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe02000 for 0x1000 bytes.
    File record segment 23226 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe02000 for 0x1000 bytes.
    File record segment 23227 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe03000 for 0x1000 bytes.
    File record segment 23228 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe03000 for 0x1000 bytes.
    File record segment 23229 is unreadable.
    Read failure with status 0xc00000b5 at offset 0x2e2fe03000 for 0x1000 bytes.
    File record segment 23230 is unreadable.
    Read failure with status 0xc00000b5 at offset 0x2e2fe03000 for 0x1000 bytes.
    File record segment 23231 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe06000 for 0x1000 bytes.
    File record segment 23240 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe06000 for 0x1000 bytes.
    File record segment 23241 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe06000 for 0x1000 bytes.
    File record segment 23242 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe06000 for 0x1000 bytes.
    File record segment 23243 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe26000 for 0x1000 bytes.
    File record segment 23368 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe26000 for 0x1000 bytes.
    File record segment 23369 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe26000 for 0x1000 bytes.
    File record segment 23370 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe26000 for 0x1000 bytes.
    File record segment 23371 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fecd000 for 0x1000 bytes.
    File record segment 24036 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fecd000 for 0x1000 bytes.
    File record segment 24037 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fecd000 for 0x1000 bytes.
    File record segment 24038 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fecd000 for 0x1000 bytes.
    File record segment 24039 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fece000 for 0x1000 bytes.
    File record segment 24040 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fece000 for 0x1000 bytes.
    File record segment 24041 is unreadable.
    Read failure with status 0xc00000b5 at offset 0x2e2fece000 for 0x1000 bytes.
    File record segment 24042 is unreadable.
    Read failure with status 0xc00000b5 at offset 0x2e2fece000 for 0x1000 bytes.
    File record segment 24043 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fef4000 for 0x1000 bytes.
    File record segment 24192 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fef4000 for 0x1000 bytes.
    File record segment 24193 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fef4000 for 0x1000 bytes.
    File record segment 24194 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fef4000 for 0x1000 bytes.
    File record segment 24195 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fff7000 for 0x1000 bytes.
    File record segment 25228 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fff7000 for 0x1000 bytes.
    File record segment 25229 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fff7000 for 0x1000 bytes.
    File record segment 25230 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fff7000 for 0x1000 bytes.
    File record segment 25231 is unreadable.
    The attribute of type 0x80 and instance tag 0x3 in file 0x91a1
    has allocated length of 0x53000 instead of 0x52000.
    Deleting corrupt attribute record (128, "")
    from file record segment 37281.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x3b67c for possibly 0x10 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0xf8ff is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 63743.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x796e for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x10a61 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 68193.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x108f91 for possibly 0x19 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x15767 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 87911.
    The attribute of type 0x80 and instance tag 0x4 in file 0x360b4
    has allocated length of 0x1a4000 instead of 0x1a2000.
    Deleting corrupt attribute record (128, "")
    from file record segment 221364.
    294400 file records processed.

    File verification completed.
    903 large file records processed.

    Read failure with status 0xc0000185 at offset 0x2e2fde5000 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fdf0400 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fdf1000 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fdf2800 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fdfc400 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fe02800 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fe06800 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fecd800 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fef4400 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fff7000 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fff7800 for 0x400 bytes.
    48 bad file records processed.

    0 EA records processed.

    60 reparse records processed.

    CHKDSK is verifying indexes (stage 2 of 3)...
    Read failure with status 0xc0000185 at offset 0x2e2fdfd000 for 0x5000 bytes.
    Deleted invalid filename FlashConfig.xs: (23161) in directory 10041.
    The NTFS file name attribute in file 0x5a79 is incorrect.
    46 00 6c 00 61 00 73 00 68 00 43 00 6f 00 6e 00 F.l.a.s.h.C.o.n.
    66 00 69 00 67 00 2e 00 78 00 73 00 3a 00 73 00 f.i.g...x.s.:.s.
    64 00 69 00 65 00 2b 5a b3 02 aa 00 00 80 33 00 d.i.e.+Z......3.
    There is no NTFS file name attribute in file 0x5a79.
    Correcting minor file name errors in file 23161.
    Index entry ReAgent.adml of index $I30 in file 0xf01 points to unused file 0x5a44.
    Deleting index entry ReAgent.adml in index $I30 of file 3841.
    Index entry eaptlsuserpropertiesv1.xsd of index $I30 in file 0xf12 points to unused file 0x5a71.
    Deleting index entry eaptlsuserpropertiesv1.xsd in index $I30 of file 3858.
    Index entry mspeapconnectionpropertiesv1.xsd of index $I30 in file 0xf12 points to unused file 0x5a74.
    Deleting index entry mspeapconnectionpropertiesv1.xsd in index $I30 of file 3858.
    Index entry FlashConfigDevice.xsd of index $I30 in file 0xf14 points to unused file 0x5a7a.
    Deleting index entry FlashConfigDevice.xsd in index $I30 of file 3860.
    Index entry HomePremiumEdition.xml of index $I30 in file 0xf64 points to unused file 0x5aa1.
    Deleting index entry HomePremiumEdition.xml in index $I30 of file 3940.
    Unable to locate the file name attribute of index entry MI041A~1.MUM
    of index $I30 with parent 0xf67 in file 0x5ac9.
    Deleting index entry MI041A~1.MUM in index $I30 of file 3943.
    Unable to locate the file name attribute of index entry MI2DFA~1.CAT
    of index $I30 with parent 0xf67 in file 0x5abc.
    Deleting index entry MI2DFA~1.CAT in index $I30 of file 3943.
    Unable to locate the file name attribute of index entry MI351C~1.CAT
    of index $I30 with parent 0xf67 in file 0x5ac8.
    Deleting index entry MI351C~1.CAT in index $I30 of file 3943.
    Unable to locate the file name attribute of index entry MIDC32~1.MUM
    of index $I30 with parent 0xf67 in file 0x5abd.
    Deleting index entry MIDC32~1.MUM in index $I30 of file 3943.
    Unable to locate the file name attribute of index entry SE84DA~1.CAT
    of index $I30 with parent 0xf67 in file 0x5e82.
    Deleting index entry SE84DA~1.CAT in index $I30 of file 3943.
    Unable to locate the file name attribute of index entry SED493~1.MUM
    of index $I30 with parent 0xf67 in file 0x5e83.
    Deleting index entry SED493~1.MUM in index $I30 of file 3943.
    Index entry filemgmt.dll of index $I30 in file 0xf7a points to unused file 0x628e.
    Deleting index entry filemgmt.dll in index $I30 of file 3962.
    Unable to locate the file name attribute of index entry MI2DFA~1.CAT
    of index $I30 with parent 0xf83 in file 0x5abb.
    Deleting index entry MI2DFA~1.CAT in index $I30 of file 3971.
    Index entry SE84DA~1.CAT of index $I30 in file 0xf83 points to unused file 0x5e81.
    Deleting index entry SE84DA~1.CAT in index $I30 of file 3971.
    Index entry Server-Help-Package.ClientProfessional~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.cat of index $I30 in file 0xf83 points to unused file 0x5e81.
    Deleting index entry Server-Help-Package.ClientProfessional~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.cat in index $I30 of file 3971.
    Index entry eaptlsuserpropertiesv1.xsd of index $I30 in file 0x19e7 points to unused file 0x5a71.
    Deleting index entry eaptlsuserpropertiesv1.xsd in index $I30 of file 6631.
    Index entry EAPTLS~3.XSD of index $I30 in file 0x19e7 points to unused file 0x5a71.
    Deleting index entry EAPTLS~3.XSD in index $I30 of file 6631.
    Index entry mspeapconnectionpropertiesv1.xsd of index $I30 in file 0x19e7 points to unused file 0x5a74.
    Deleting index entry mspeapconnectionpropertiesv1.xsd in index $I30 of file 6631.
    Unable to locate the file name attribute of index entry mspeapuserpropertiesv1.xsd
    of index $I30 with parent 0x19e7 in file 0x5a76.
    Deleting index entry mspeapuserpropertiesv1.xsd in index $I30 of file 6631.
    Index entry MSPEAP~1.XSD of index $I30 in file 0x19e7 points to unused file 0x5a74.
    Deleting index entry MSPEAP~1.XSD in index $I30 of file 6631.
    Unable to locate the file name attribute of index entry EnterpriseEdition.xml
    of index $I30 with parent 0x19e9 in file 0x5aa0.
    Deleting index entry EnterpriseEdition.xml in index $I30 of file 6633.
    Index entry HomePremiumEdition.xml of index $I30 in file 0x19e9 points to unused file 0x5aa1.
    Deleting index entry HomePremiumEdition.xml in index $I30 of file 6633.
    Index entry HOMEPR~1.XML of index $I30 in file 0x19e9 points to unused file 0x5aa1.
    Deleting index entry HOMEPR~1.XML in index $I30 of file 6633.
    Unable to locate the file name attribute of index entry ProfessionalEdition.xml
    of index $I30 with parent 0x19e9 in file 0x5aa3.
    Deleting index entry ProfessionalEdition.xml in index $I30 of file 6633.
    Index entry filemgmt.dll of index $I30 in file 0x24a6 points to unused file 0x628e.
    Deleting index entry filemgmt.dll in index $I30 of file 9382.
    Unable to locate the file name attribute of index entry FlashConfig.xsd
    of index $I30 with parent 0x2739 in file 0x5a79.
    Deleting index entry FlashConfig.xsd in index $I30 of file 10041.
    Index entry FlashConfigDevice.xsd of index $I30 in file 0x2739 points to unused file 0x5a7a.
    Deleting index entry FlashConfigDevice.xsd in index $I30 of file 10041.
    Unable to locate the file name attribute of index entry FLASHC~1.XSD
    of index $I30 with parent 0x2739 in file 0x5a79.
    Deleting index entry FLASHC~1.XSD in index $I30 of file 10041.
    Index entry FLASHC~2.XSD of index $I30 in file 0x2739 points to unused file 0x5a7a.
    Deleting index entry FLASHC~2.XSD in index $I30 of file 10041.
    Index entry ReAgent.adml of index $I30 in file 0x2766 points to unused file 0x5a44.
    Deleting index entry ReAgent.adml in index $I30 of file 10086.
    Index entry REAGEN~1.ADM of index $I30 in file 0x2766 points to unused file 0x5a44.
    Deleting index entry REAGEN~1.ADM in index $I30 of file 10086.
    Index entry AMD2A7~1.DLL of index $I30 in file 0x2d0f points to unused file 0x628c.
    Deleting index entry AMD2A7~1.DLL in index $I30 of file 11535.
    Index entry amd64_microsoft-windows-feclient_31bf3856ad364e35_6.1.7600.16385_none_1acf02d27145db87_feclient.dll_248fccac of index $I30 in file 0x2d0f points to unused file 0x628c.
    Deleting index entry amd64_microsoft-windows-feclient_31bf3856ad364e35_6.1.7600.16385_none_1acf02d27145db87_feclient.dll_248fccac in index $I30 of file 11535.
    Index entry 74dc1f62d8a942a2c634b76396a085f8000aeee769bfb42a1bb70c484fd8185b.cat of index $I30 in file 0x2d10 points to unused file 0x5aba.
    Deleting index entry 74dc1f62d8a942a2c634b76396a085f8000aeee769bfb42a1bb70c484fd8185b.cat in index $I30 of file 11536.
    Index entry 74DC1F~1.CAT of index $I30 in file 0x2d10 points to unused file 0x5aba.
    Deleting index entry 74DC1F~1.CAT in index $I30 of file 11536.
    Index entry 7d765c31fcc7a1fec16fc8c3b048b8be020e071fcd355136439b55af4f259534.cat of index $I30 in file 0x2d10 points to unused file 0x5aca.
    Deleting index entry 7d765c31fcc7a1fec16fc8c3b048b8be020e071fcd355136439b55af4f259534.cat in index $I30 of file 11536.
    Index entry 7D765C~1.CAT of index $I30 in file 0x2d10 points to unused file 0x5aca.
    Deleting index entry 7D765C~1.CAT in index $I30 of file 11536.
    Index entry b0f523ce2768e56bd54a078cf26518d7feda4258bd36c0a33c9759c083aeefc9.cat of index $I30 in file 0x2d10 points to unused file 0x5de6.
    Deleting index entry b0f523ce2768e56bd54a078cf26518d7feda4258bd36c0a33c9759c083aeefc9.cat in index $I30 of file 11536.
    Index entry B0F523~1.CAT of index $I30 in file 0x2d10 points to unused file 0x5de6.
    Deleting index entry B0F523~1.CAT in index $I30 of file 11536.
    374904 index entries processed
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-11-08T08:59:57.000000000Z" />
    <EventRecordID>58154</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Kevin-PC</Computer>
    <Security />
    </System>
    <EventData>
    <Data>

    Checking file system on C:
    The type of the file system is NTFS.
    Volume label is OS.


    One of your disks needs to be checked for consistency. You
    may cancel the disk check, but it is strongly recommended
    that you continue.
    Windows will now check the disk.

    CHKDSK is verifying files (stage 1 of 3)...
    Read failure with status 0xc0000185 at offset 0x2e2fde5000 for 0x1000 bytes.
    File record segment 23108 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fde5000 for 0x1000 bytes.
    File record segment 23109 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf0000 for 0x1000 bytes.
    File record segment 23152 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf0000 for 0x1000 bytes.
    File record segment 23153 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf0000 for 0x1000 bytes.
    File record segment 23154 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf0000 for 0x1000 bytes.
    File record segment 23155 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf1000 for 0x1000 bytes.
    File record segment 23156 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf1000 for 0x1000 bytes.
    File record segment 23157 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf1000 for 0x1000 bytes.
    File record segment 23158 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf1000 for 0x1000 bytes.
    File record segment 23159 is unreadable.
    Read failure with status 0xc00000b5 at offset 0x2e2fdf2000 for 0x1000 bytes.
    File record segment 23160 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf2000 for 0x1000 bytes.
    File record segment 23161 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf2000 for 0x1000 bytes.
    File record segment 23162 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdf2000 for 0x1000 bytes.
    File record segment 23163 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdfc000 for 0x1000 bytes.
    File record segment 23200 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fdfc000 for 0x1000 bytes.
    File record segment 23201 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe02000 for 0x1000 bytes.
    File record segment 23224 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe02000 for 0x1000 bytes.
    File record segment 23225 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe02000 for 0x1000 bytes.
    File record segment 23226 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe02000 for 0x1000 bytes.
    File record segment 23227 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe03000 for 0x1000 bytes.
    File record segment 23228 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe03000 for 0x1000 bytes.
    File record segment 23229 is unreadable.
    Read failure with status 0xc00000b5 at offset 0x2e2fe03000 for 0x1000 bytes.
    File record segment 23230 is unreadable.
    Read failure with status 0xc00000b5 at offset 0x2e2fe03000 for 0x1000 bytes.
    File record segment 23231 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe06000 for 0x1000 bytes.
    File record segment 23240 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe06000 for 0x1000 bytes.
    File record segment 23241 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe06000 for 0x1000 bytes.
    File record segment 23242 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe06000 for 0x1000 bytes.
    File record segment 23243 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe26000 for 0x1000 bytes.
    File record segment 23368 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe26000 for 0x1000 bytes.
    File record segment 23369 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe26000 for 0x1000 bytes.
    File record segment 23370 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fe26000 for 0x1000 bytes.
    File record segment 23371 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fecd000 for 0x1000 bytes.
    File record segment 24036 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fecd000 for 0x1000 bytes.
    File record segment 24037 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fecd000 for 0x1000 bytes.
    File record segment 24038 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fecd000 for 0x1000 bytes.
    File record segment 24039 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fece000 for 0x1000 bytes.
    File record segment 24040 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fece000 for 0x1000 bytes.
    File record segment 24041 is unreadable.
    Read failure with status 0xc00000b5 at offset 0x2e2fece000 for 0x1000 bytes.
    File record segment 24042 is unreadable.
    Read failure with status 0xc00000b5 at offset 0x2e2fece000 for 0x1000 bytes.
    File record segment 24043 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fef4000 for 0x1000 bytes.
    File record segment 24192 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fef4000 for 0x1000 bytes.
    File record segment 24193 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fef4000 for 0x1000 bytes.
    File record segment 24194 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fef4000 for 0x1000 bytes.
    File record segment 24195 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fff7000 for 0x1000 bytes.
    File record segment 25228 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fff7000 for 0x1000 bytes.
    File record segment 25229 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fff7000 for 0x1000 bytes.
    File record segment 25230 is unreadable.
    Read failure with status 0xc0000185 at offset 0x2e2fff7000 for 0x1000 bytes.
    File record segment 25231 is unreadable.
    The attribute of type 0x80 and instance tag 0x3 in file 0x91a1
    has allocated length of 0x53000 instead of 0x52000.
    Deleting corrupt attribute record (128, "")
    from file record segment 37281.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x3b67c for possibly 0x10 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0xf8ff is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 63743.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x796e for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x10a61 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 68193.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x108f91 for possibly 0x19 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x15767 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 87911.
    The attribute of type 0x80 and instance tag 0x4 in file 0x360b4
    has allocated length of 0x1a4000 instead of 0x1a2000.
    Deleting corrupt attribute record (128, "")
    from file record segment 221364.
    294400 file records processed.

    File verification completed.
    903 large file records processed.

    Read failure with status 0xc0000185 at offset 0x2e2fde5000 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fdf0400 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fdf1000 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fdf2800 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fdfc400 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fe02800 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fe06800 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fecd800 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fef4400 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fff7000 for 0x400 bytes.
    Read failure with status 0xc0000185 at offset 0x2e2fff7800 for 0x400 bytes.
    48 bad file records processed.

    0 EA records processed.

    60 reparse records processed.

    CHKDSK is verifying indexes (stage 2 of 3)...
    Read failure with status 0xc0000185 at offset 0x2e2fdfd000 for 0x5000 bytes.
    Deleted invalid filename FlashConfig.xs: (23161) in directory 10041.
    The NTFS file name attribute in file 0x5a79 is incorrect.
    46 00 6c 00 61 00 73 00 68 00 43 00 6f 00 6e 00 F.l.a.s.h.C.o.n.
    66 00 69 00 67 00 2e 00 78 00 73 00 3a 00 73 00 f.i.g...x.s.:.s.
    64 00 69 00 65 00 2b 5a b3 02 aa 00 00 80 33 00 d.i.e.+Z......3.
    There is no NTFS file name attribute in file 0x5a79.
    Correcting minor file name errors in file 23161.
    Index entry ReAgent.adml of index $I30 in file 0xf01 points to unused file 0x5a44.
    Deleting index entry ReAgent.adml in index $I30 of file 3841.
    Index entry eaptlsuserpropertiesv1.xsd of index $I30 in file 0xf12 points to unused file 0x5a71.
    Deleting index entry eaptlsuserpropertiesv1.xsd in index $I30 of file 3858.
    Index entry mspeapconnectionpropertiesv1.xsd of index $I30 in file 0xf12 points to unused file 0x5a74.
    Deleting index entry mspeapconnectionpropertiesv1.xsd in index $I30 of file 3858.
    Index entry FlashConfigDevice.xsd of index $I30 in file 0xf14 points to unused file 0x5a7a.
    Deleting index entry FlashConfigDevice.xsd in index $I30 of file 3860.
    Index entry HomePremiumEdition.xml of index $I30 in file 0xf64 points to unused file 0x5aa1.
    Deleting index entry HomePremiumEdition.xml in index $I30 of file 3940.
    Unable to locate the file name attribute of index entry MI041A~1.MUM
    of index $I30 with parent 0xf67 in file 0x5ac9.
    Deleting index entry MI041A~1.MUM in index $I30 of file 3943.
    Unable to locate the file name attribute of index entry MI2DFA~1.CAT
    of index $I30 with parent 0xf67 in file 0x5abc.
    Deleting index entry MI2DFA~1.CAT in index $I30 of file 3943.
    Unable to locate the file name attribute of index entry MI351C~1.CAT
    of index $I30 with parent 0xf67 in file 0x5ac8.
    Deleting index entry MI351C~1.CAT in index $I30 of file 3943.
    Unable to locate the file name attribute of index entry MIDC32~1.MUM
    of index $I30 with parent 0xf67 in file 0x5abd.
    Deleting index entry MIDC32~1.MUM in index $I30 of file 3943.
    Unable to locate the file name attribute of index entry SE84DA~1.CAT
    of index $I30 with parent 0xf67 in file 0x5e82.
    Deleting index entry SE84DA~1.CAT in index $I30 of file 3943.
    Unable to locate the file name attribute of index entry SED493~1.MUM
    of index $I30 with parent 0xf67 in file 0x5e83.
    Deleting index entry SED493~1.MUM in index $I30 of file 3943.
    Index entry filemgmt.dll of index $I30 in file 0xf7a points to unused file 0x628e.
    Deleting index entry filemgmt.dll in index $I30 of file 3962.
    Unable to locate the file name attribute of index entry MI2DFA~1.CAT
    of index $I30 with parent 0xf83 in file 0x5abb.
    Deleting index entry MI2DFA~1.CAT in index $I30 of file 3971.
    Index entry SE84DA~1.CAT of index $I30 in file 0xf83 points to unused file 0x5e81.
    Deleting index entry SE84DA~1.CAT in index $I30 of file 3971.
    Index entry Server-Help-Package.ClientProfessional~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.cat of index $I30 in file 0xf83 points to unused file 0x5e81.
    Deleting index entry Server-Help-Package.ClientProfessional~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.cat in index $I30 of file 3971.
    Index entry eaptlsuserpropertiesv1.xsd of index $I30 in file 0x19e7 points to unused file 0x5a71.
    Deleting index entry eaptlsuserpropertiesv1.xsd in index $I30 of file 6631.
    Index entry EAPTLS~3.XSD of index $I30 in file 0x19e7 points to unused file 0x5a71.
    Deleting index entry EAPTLS~3.XSD in index $I30 of file 6631.
    Index entry mspeapconnectionpropertiesv1.xsd of index $I30 in file 0x19e7 points to unused file 0x5a74.
    Deleting index entry mspeapconnectionpropertiesv1.xsd in index $I30 of file 6631.
    Unable to locate the file name attribute of index entry mspeapuserpropertiesv1.xsd
    of index $I30 with parent 0x19e7 in file 0x5a76.
    Deleting index entry mspeapuserpropertiesv1.xsd in index $I30 of file 6631.
    Index entry MSPEAP~1.XSD of index $I30 in file 0x19e7 points to unused file 0x5a74.
    Deleting index entry MSPEAP~1.XSD in index $I30 of file 6631.
    Unable to locate the file name attribute of index entry EnterpriseEdition.xml
    of index $I30 with parent 0x19e9 in file 0x5aa0.
    Deleting index entry EnterpriseEdition.xml in index $I30 of file 6633.
    Index entry HomePremiumEdition.xml of index $I30 in file 0x19e9 points to unused file 0x5aa1.
    Deleting index entry HomePremiumEdition.xml in index $I30 of file 6633.
    Index entry HOMEPR~1.XML of index $I30 in file 0x19e9 points to unused file 0x5aa1.
    Deleting index entry HOMEPR~1.XML in index $I30 of file 6633.
    Unable to locate the file name attribute of index entry ProfessionalEdition.xml
    of index $I30 with parent 0x19e9 in file 0x5aa3.
    Deleting index entry ProfessionalEdition.xml in index $I30 of file 6633.
    Index entry filemgmt.dll of index $I30 in file 0x24a6 points to unused file 0x628e.
    Deleting index entry filemgmt.dll in index $I30 of file 9382.
    Unable to locate the file name attribute of index entry FlashConfig.xsd
    of index $I30 with parent 0x2739 in file 0x5a79.
    Deleting index entry FlashConfig.xsd in index $I30 of file 10041.
    Index entry FlashConfigDevice.xsd of index $I30 in file 0x2739 points to unused file 0x5a7a.
    Deleting index entry FlashConfigDevice.xsd in index $I30 of file 10041.
    Unable to locate the file name attribute of index entry FLASHC~1.XSD
    of index $I30 with parent 0x2739 in file 0x5a79.
    Deleting index entry FLASHC~1.XSD in index $I30 of file 10041.
    Index entry FLASHC~2.XSD of index $I30 in file 0x2739 points to unused file 0x5a7a.
    Deleting index entry FLASHC~2.XSD in index $I30 of file 10041.
    Index entry ReAgent.adml of index $I30 in file 0x2766 points to unused file 0x5a44.
    Deleting index entry ReAgent.adml in index $I30 of file 10086.
    Index entry REAGEN~1.ADM of index $I30 in file 0x2766 points to unused file 0x5a44.
    Deleting index entry REAGEN~1.ADM in index $I30 of file 10086.
    Index entry AMD2A7~1.DLL of index $I30 in file 0x2d0f points to unused file 0x628c.
    Deleting index entry AMD2A7~1.DLL in index $I30 of file 11535.
    Index entry amd64_microsoft-windows-feclient_31bf3856ad364e35_6.1.7600.16385_none_1acf02d27145db87_feclient.dll_248fccac of index $I30 in file 0x2d0f points to unused file 0x628c.
    Deleting index entry amd64_microsoft-windows-feclient_31bf3856ad364e35_6.1.7600.16385_none_1acf02d27145db87_feclient.dll_248fccac in index $I30 of file 11535.
    Index entry 74dc1f62d8a942a2c634b76396a085f8000aeee769bfb42a1bb70c484fd8185b.cat of index $I30 in file 0x2d10 points to unused file 0x5aba.
    Deleting index entry 74dc1f62d8a942a2c634b76396a085f8000aeee769bfb42a1bb70c484fd8185b.cat in index $I30 of file 11536.
    Index entry 74DC1F~1.CAT of index $I30 in file 0x2d10 points to unused file 0x5aba.
    Deleting index entry 74DC1F~1.CAT in index $I30 of file 11536.
    Index entry 7d765c31fcc7a1fec16fc8c3b048b8be020e071fcd355136439b55af4f259534.cat of index $I30 in file 0x2d10 points to unused file 0x5aca.
    Deleting index entry 7d765c31fcc7a1fec16fc8c3b048b8be020e071fcd355136439b55af4f259534.cat in index $I30 of file 11536.
    Index entry 7D765C~1.CAT of index $I30 in file 0x2d10 points to unused file 0x5aca.
    Deleting index entry 7D765C~1.CAT in index $I30 of file 11536.
    Index entry b0f523ce2768e56bd54a078cf26518d7feda4258bd36c0a33c9759c083aeefc9.cat of index $I30 in file 0x2d10 points to unused file 0x5de6.
    Deleting index entry b0f523ce2768e56bd54a078cf26518d7feda4258bd36c0a33c9759c083aeefc9.cat in index $I30 of file 11536.
    Index entry B0F523~1.CAT of index $I30 in file 0x2d10 points to unused file 0x5de6.
    Deleting index entry B0F523~1.CAT in index $I30 of file 11536.
    374904 index entries processed</Data>
    </EventData>
    </Event>
  8. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    Both of these logs are missing "stage 3 of 3" and are showing a lot of read errors. They would have run automatically when the PC was turned on and I suspect you canceled the scan. They have been carried out by the system, they are not from a Disk Check scan that you initiated. The drive has obviously been marked as dirty which is the reason it does not show in the defrag window. This is a safety feature as running a defrag on a dirty drive can make a mess of it.

    I suspect the drive is on its way out so the first thing you should do is make quite sure you have backed up all your important data to an external source before performing the next routine.

    Please run the chkdsk /r command as per the instructions in post 2. Make a note of the date and time so once it is complete you can easily find the Wininit log in Event Viewer and paste it into your next post. This scan must be allowed to complete without interruption. It will find any bad sectors on the drive and will attempt to repair them. This will confirm the physical condition of the drive.
  9. jobeard

    jobeard TS Ambassador Posts: 13,368   +302

    ouch. The first pass of CHKDSK should have corrected those bad blocks.
    The second pass confirms it was not able to do so

    Most troublesome is the note
    this is extremely rare for NTFS.

    In either case, that HD is toasted - - plan to replace the HD and reinstall -or-
    just pick up a new machine (with newer technologies).
  10. madara

    madara Newcomer, in training Topic Starter Posts: 31

    BTW my computer is running fine, it just runs slower than usual and the disk C was not shown in the defragmenter, should I replace my hard drive? Then how could I reinstall my window.
  11. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    It is very clear from the logs you posted that your hard drive has fairly serious errors.

    Please follow what I said at the end of my last post:

    That will give a much clearer picture on the health of the drive which is not likely to give an encouraging result.

    The hard drive has a Recovery partition which may be possible to rescue and transfer to a new hard drive. Complete the chkdsk routine, post the log and we will take it from there.

    Is this a laptop or desktop PC? if it is a laptop does it have a spare hard drive bay?
     
  12. madara

    madara Newcomer, in training Topic Starter Posts: 31

    how long would a chkdsk /r take for a 1tb drive and having about 300 gb files on it
  13. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    I would guess about 8 to 10 hours.

    If you start chkdsk /r from the C: drive it will check the entire disc surface for physical errors and attempt to move any data away from bad areas and produce a log that will show its condition. The time taken will depend on how big the C: partition is.

    If you then follow this routine using the same instructions but use the command sfc /scannow it will repair any file damage. That may just help to speed the PC up while you obtain a new drive and get prepared to transfer the Recovery partition.

    First and foremost though I would like to see the log from running chkdsk /r to confirm the condition of the drive.
  14. madara

    madara Newcomer, in training Topic Starter Posts: 31

    should i reset my computer into factory setting?
  15. herpaderp

    herpaderp TechSpot Enthusiast Posts: 159

    lol maybe you should try reading and following the instructions given to you, or just stop posting and solve the problem youself. You've ignored 3 requests already :\
  16. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    If you return your PC to factory settings you will loose everything on the drive, so if you want to try that you will have to back up all your data or you will loose it.

    Furthermore, it is highly likely that your drive is failing and unless you are prepared to follow the instructions given to run chkdsk /r and post the results we can't give any more advice. If you do a factory restore on a failing drive you could easily end up with a non-bootable PC.

    Please follow the instructions given to run chkdsk /r followed by sfc /scannow, after that we can advise you on what to do next. It is quite likely you will need a new hard drive but you will need guidance on transfering the Recovery partition to the new drive, without doing that you will not be able to restore your system unless you buy a copy of Windows or purchase recovery discs from the manufacturer.

    If there is anything you do not understand then please ask. There really is no other option than to perform what has already been suggested.

    It's your call :)
  17. hahahanoobs

    hahahanoobs TechSpot Booster Posts: 958   +96

    Does your C: drive show up in Disk Management? aka Create and format hard disk partitions.
  18. madara

    madara Newcomer, in training Topic Starter Posts: 31

    Yesterday, I restored my computer to the factory setting and opened the disk defragmenter, I can see the C was detected.

    So should I run chkdsk /r still? Or maybe it just an software issue that can be solve with reformatting.
  19. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    I don't understand why, after all the advice I gave you, you have done a factory restore.

    When a drive is flagged as dirty by the system it does not appear in defragmenter. Running the factory restore will have cleared the dirty flag which is why you can now see it. Running chkdsk /r would have had the same effect without a restore having to be done.

    If you now run chkdsk /r it will confirm the drives condition which is already highly suspect. Please follow the previous instructions to run chkdsk /r and the instructions to post the log.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.