locked
I have a Toshiba Satellite C665D running on windows 7. It has been a year old and nowadays I see a lot of the apps not responding or the laptop freezes.. Why? RRS feed

  • Question

  • My Toshiba Satellite C665D  is about a year old and nowadays I am experiencing the windows explorer, Firefox, etc not
    responding, the start-up's take like ages, the laptop gets really slow (Freezes) and have to force shut down with the power
    switch.

    --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Toshiba Satellite C665D

    . Runs on Windows 7 Home Premium (32-bit)

    . RAM 2 GB

    . HDD 500 GB

    . Processor AMD E-450 APU with Radeon HD Graphics 1.65 GHz

    -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Processor calulation rate per second: 3.8 (sub score)

    Memory RAM: 5.5

    Graphics: 4.4

    Gaming Graphics: 5.8

    Primary Hard Disk: 5.6

    The above data is given to ask u'll if I should change my motherboard or increase my RAM. Please help me on this issue.

    ....Thank You Guys!!
    Saturday, December 29, 2012 1:59 PM

Answers

  • Jonahtan

    Over time the things you have installed, and removed create clutter that sometimes results in instability, and crashes.  The cure (though painful) is to rest or re-install windows.

    If you cant or dont want to do that the problems can be diagnosed one at a time but it is usually a long process.  If you want to do this please upload your event viewer logs as a start

    Please provide us with your Event Viewer administrative logs by following these steps:


    Click Start Menu
    Type eventvwr into Search programs and files (do not hit enter)
    Right click eventvwr.exe and click Run as administrator
    Expand Custom Views
    Click Administrative Events
    Right click Administrative Events
    Save all Events in Custom View As...
    Save them in a folder where you will remember which folder and save as Errors.evtx
    Go to where you saved Errors.evtx
    Right click Errors.evtx -> send to -> compressed (zipped) folder
    Upload the .zip file here (if you can) to skydrive or a file sharing service


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Sunday, December 30, 2012 1:23 AM

All replies

  • Jonahtan

    Over time the things you have installed, and removed create clutter that sometimes results in instability, and crashes.  The cure (though painful) is to rest or re-install windows.

    If you cant or dont want to do that the problems can be diagnosed one at a time but it is usually a long process.  If you want to do this please upload your event viewer logs as a start

    Please provide us with your Event Viewer administrative logs by following these steps:


    Click Start Menu
    Type eventvwr into Search programs and files (do not hit enter)
    Right click eventvwr.exe and click Run as administrator
    Expand Custom Views
    Click Administrative Events
    Right click Administrative Events
    Save all Events in Custom View As...
    Save them in a folder where you will remember which folder and save as Errors.evtx
    Go to where you saved Errors.evtx
    Right click Errors.evtx -> send to -> compressed (zipped) folder
    Upload the .zip file here (if you can) to skydrive or a file sharing service


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Sunday, December 30, 2012 1:23 AM
  • https://skydrive.live.com/redir?resid=3C555F6704E05E9!170&authkey=!AO6Ffpzsj_908MQ
    Sunday, December 30, 2012 5:28 PM
  • If I want to reinstall windows can I get the windows7 Home Premium OS from the net because I have no recovery disk with my laptop. Pls Help (But my OS key should work wit it)???
    Sunday, December 30, 2012 5:44 PM
  • JS

    If win 7 came pre-installed it is called OEM (original equipment mfr) and the OS key you have is for that.  You can find win 7 on the net but your key and version have to match so you would need an win 7 Home Prem OEM, not retail.  Then, if you havent changed any hardware, it should work.

    I suspect this answers your questions

    https://gtipjg.bay.livefilestore.com/y1p80u9zEesbP9Ea6_-aeU4psVqh7fBRKxIWE4Fm62KbG9P0kO-PeBf8M6Lk_AYp7lZZ0RmeKJicPvmkKp3M1gHaEA0b7bYQ3rC/ntfs.jpg?psid=1

    A- CHKDSK /R /F:

    Chkdsk disclaimer: While performing chkdsk on the hard drive if any bad sectors are found  when chkdsk tries to repair that sector  any data available on that sector might be lost.


    Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.
    Do this for each hard drive on your system.
    When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

    Then reboot and let the test run.
    It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.
    http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/


     See "CHKDSK LogFile" below in order to check the results of the test.


    B- Elevated Command Prompt:
    Go to Start and type in "cmd.exe" (without the quotes)
    At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"


    C-CHKDSK LogFile:

    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
    Copy/paste the results into your next post. 


    MS-MVP 2010, 2011, 2012 Team ZigZag



    • Edited by ZigZag3143x Sunday, December 30, 2012 8:10 PM
    Sunday, December 30, 2012 8:04 PM
  • Can I get a download link from U'll. As I fear to get an OS from somewhere where I can't trust??. My RAM goes upto 80% with out any reason. Should I Upgrade my RAM?? and Nowadays I am experiencing a blue screen which is texted as "There is a new hardware installed and this is blue screen is shown so that there is not harm caused to windows and this screen shows up when the windows start's up and win start's up again and again, till I force shut it down using the power switch and switching it back on after few mins resolve's it. (I don't understand this as I have not installed any new hardware from the time I bought it??).
    Wednesday, January 2, 2013 11:08 AM
  • Log Name:      Application
    Source:        Microsoft-Windows-Wininit
    Date:          2/01/2013 3:51:30 PM
    Event ID:      1001
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      Jonathan
    Description:


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


    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)...
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0xc317 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x8ba8 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 35752.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x22a75 for possibly 0x16 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xc061 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 49249.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x1d56d0 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xc2ef is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 49903.
    Attribute record of type 0x80 and instance tag 0x0 is cross linked
    starting at 0x177ddf for possibly 0x9 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x0
    in file 0xcc6c is already in use.
    Deleted corrupt attribute list entry
    with type code 128 in file 52332.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x2bd00000000dcc1.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 56513.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x2835b8 for possibly 0x8 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xdcca is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 56522.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x166eb3 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xe58c is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 58764.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x15bc40 for possibly 0x6 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xec00 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 60416.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x1eb06e for possibly 0x22 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xf681 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 63105.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x2769ca for possibly 0x8 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xfc0e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 64526.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x150213 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x10106 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 65798.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x219f0b for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x10156 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 65878.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x21291b for possibly 0x9 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x10c84 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 68740.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x954b for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x10cc8 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 68808.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x1cfce6 for possibly 0x8 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x10d4e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 68942.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x18034f for possibly 0xc clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x13e61 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 81505.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x37d98 for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x13fda is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 81882.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x15e5e2 for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1401a is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 81946.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x15eaf0 for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1401d is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 81949.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x151a62 for possibly 0x7d clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x14091 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 82065.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x25bdd1 for possibly 0xb clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x14229 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 82473.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x151480 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x14369 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 82793.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x16bbfc for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x145e6 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 83430.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3bdadef for possibly 0xeb clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x14658 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 83544.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x1d5ce3 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x15cdf is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 89311.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x203458 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x15d5e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 89438.
    Attribute record of type 0xa0 and instance tag 0x3 is cross linked
    starting at 0x2ec73a for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
    in file 0x15dd5 is already in use.
    Deleting corrupt attribute record (160, $I30)
    from file record segment 89557.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x1d2a54 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x15ff3 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90099.
    Attribute record of type 0xa0 and instance tag 0x3 is cross linked
    starting at 0x1d56d2 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
    in file 0x15ff4 is already in use.
    Deleting corrupt attribute record (160, $I30)
    from file record segment 90100.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x1d2a55 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x15ff5 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90101.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x1d56d1 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x15ff7 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90103.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x1d56d3 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x15ffb is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90107.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x2027be for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x16077 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90231.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x219a24 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x16083 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90243.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x219fd2 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x16084 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90244.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x2ef6c3 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x16091 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90257.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x30c6b5 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x16095 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90261.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x15170b for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x160ad is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90285.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x1513f3 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x160fc is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90364.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x16bbf9 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1657c is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 91516.
    Attribute record of type 0x80 and instance tag 0x5 is cross linked
    starting at 0x15003b for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x5
    in file 0x2223c is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 139836.
      142336 file records processed.                                         

    File verification completed.
      295 large file records processed.                                   

      0 bad file records processed.                                     

      0 EA records processed.                                           

      65 reparse records processed.                                      

    CHKDSK is verifying indexes (stage 2 of 3)...
    The multi-sector header signature for VCN 0x0 of index $I30
    in file 0xc9 is incorrect.
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    Correcting error in index $I30 for file 201.
    The index bitmap $I30 in file 0xc9 is incorrect.
    Correcting error in index $I30 for file 201.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
    ff ff ff ff ff ff ff ff 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    Sorting index $I30 in file 201.
    The file reference 0xac00000000e590 of index entry bookmarks-2012-12-30.json of index $I30
    with parent 0x103 is not the same as 0xa900000000e590.
    Deleting index entry bookmarks-2012-12-30.json in index $I30 of file 259.
    Correcting error in index $I30 for file 10283.
    Correcting error in index $I30 for file 10283.
    The index bitmap $I30 in file 0x282b is incorrect.
    Correcting error in index $I30 for file 10283.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
    ff ff ff ff ff ff ff ff 00 00 77 00 73 00 5c 00  ..........w.s.\.
    30 00 00 00 20 00 00 1a 00 00 00 00 00 00 00 00  0... ...........
    Sorting index $I30 in file 10283.
    The file reference 0xb100000000fd88 of index entry 61 of index $I30
    with parent 0x3894 is not the same as 0xb200000000fd88.
    Deleting index entry 61 in index $I30 of file 14484.
    The file reference 0x7b00000000fd81 of index entry 27 of index $I30
    with parent 0x3992 is not the same as 0x8400000000fd81.
    Deleting index entry 27 in index $I30 of file 14738.
    The file reference 0x5b000000010563 of index entry EE of index $I30
    with parent 0x3992 is not the same as 0x5c000000010563.
    Deleting index entry EE in index $I30 of file 14738.
    The file reference 0x4d000000010123 of index entry A3 of index $I30
    with parent 0x3a05 is not the same as 0x4e000000010123.
    Deleting index entry A3 in index $I30 of file 14853.
    The file reference 0x7a00000000fd53 of index entry C7 of index $I30
    with parent 0x3a05 is not the same as 0x8200000000fd53.
    Deleting index entry C7 in index $I30 of file 14853.
    The file reference 0x44000000010142 of index entry C5 of index $I30
    with parent 0x53fc is not the same as 0x46000000010142.
    Deleting index entry C5 in index $I30 of file 21500.
    The file reference 0x10f00000001014a of index entry 66 of index $I30
    with parent 0x89b6 is not the same as 0x11000000001014a.
    Deleting index entry 66 in index $I30 of file 35254.
    The index bitmap for index $I30 in file 0x15dd5 is invalid or missing.
    Correcting error in index $I30 for file 89557.
    The index bitmap $I30 is present but there is no corresponding
    index allocation attribute in file 0x15dd5.
    Correcting error in index $I30 for file 89557.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
    ff ff ff ff ff ff ff ff 64 44 3a 5e ba e6 cd 01  ........dD:^....
    de 88 b4 3a ba e6 cd 01 96 b9 3a 5e ba e6 cd 01  ...:......:^....
    Sorting index $I30 in file 89557.
    The index bitmap for index $I30 in file 0x15ff4 is invalid or missing.
    Correc
    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="2013-01-02T10:21:30.000000000Z" />
        <EventRecordID>121946</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>Jonathan</Computer>
        <Security />
      </System>
      <EventData>
        <Data>

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


    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)...
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0xc317 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x8ba8 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 35752.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x22a75 for possibly 0x16 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xc061 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 49249.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x1d56d0 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xc2ef is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 49903.
    Attribute record of type 0x80 and instance tag 0x0 is cross linked
    starting at 0x177ddf for possibly 0x9 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x0
    in file 0xcc6c is already in use.
    Deleted corrupt attribute list entry
    with type code 128 in file 52332.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0x2bd00000000dcc1.  The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 56513.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x2835b8 for possibly 0x8 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xdcca is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 56522.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x166eb3 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xe58c is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 58764.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x15bc40 for possibly 0x6 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xec00 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 60416.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x1eb06e for possibly 0x22 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xf681 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 63105.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x2769ca for possibly 0x8 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xfc0e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 64526.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x150213 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x10106 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 65798.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x219f0b for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x10156 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 65878.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x21291b for possibly 0x9 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x10c84 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 68740.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x954b for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x10cc8 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 68808.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x1cfce6 for possibly 0x8 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x10d4e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 68942.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x18034f for possibly 0xc clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x13e61 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 81505.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x37d98 for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x13fda is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 81882.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x15e5e2 for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1401a is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 81946.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x15eaf0 for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1401d is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 81949.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x151a62 for possibly 0x7d clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x14091 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 82065.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x25bdd1 for possibly 0xb clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x14229 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 82473.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x151480 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x14369 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 82793.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x16bbfc for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x145e6 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 83430.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3bdadef for possibly 0xeb clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x14658 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 83544.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x1d5ce3 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x15cdf is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 89311.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x203458 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x15d5e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 89438.
    Attribute record of type 0xa0 and instance tag 0x3 is cross linked
    starting at 0x2ec73a for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
    in file 0x15dd5 is already in use.
    Deleting corrupt attribute record (160, $I30)
    from file record segment 89557.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x1d2a54 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x15ff3 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90099.
    Attribute record of type 0xa0 and instance tag 0x3 is cross linked
    starting at 0x1d56d2 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0xa0 and instance tag 0x3
    in file 0x15ff4 is already in use.
    Deleting corrupt attribute record (160, $I30)
    from file record segment 90100.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x1d2a55 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x15ff5 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90101.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x1d56d1 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x15ff7 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90103.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x1d56d3 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x15ffb is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90107.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x2027be for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x16077 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90231.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x219a24 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x16083 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90243.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x219fd2 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x16084 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90244.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x2ef6c3 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x16091 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90257.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x30c6b5 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x16095 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90261.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x15170b for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x160ad is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90285.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x1513f3 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x160fc is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90364.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x16bbf9 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1657c is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 91516.
    Attribute record of type 0x80 and instance tag 0x5 is cross linked
    starting at 0x15003b for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x5
    in file 0x2223c is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 139836.
      142336 file records processed.                                         

    File verification completed.
      295 large file records processed.                                   

      0 bad file records processed.                                     

      0 EA records processed.                                           

      65 reparse records processed.                                      

    CHKDSK is verifying indexes (stage 2 of 3)...
    The multi-sector header signature for VCN 0x0 of index $I30
    in file 0xc9 is incorrect.
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    Correcting error in index $I30 for file 201.
    The index bitmap $I30 in file 0xc9 is incorrect.
    Correcting error in index $I30 for file 201.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
    ff ff ff ff ff ff ff ff 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    Sorting index $I30 in file 201.
    The file reference 0xac00000000e590 of index entry bookmarks-2012-12-30.json of index $I30
    with parent 0x103 is not the same as 0xa900000000e590.
    Deleting index entry bookmarks-2012-12-30.json in index $I30 of file 259.
    Correcting error in index $I30 for file 10283.
    Correcting error in index $I30 for file 10283.
    The index bitmap $I30 in file 0x282b is incorrect.
    Correcting error in index $I30 for file 10283.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
    ff ff ff ff ff ff ff ff 00 00 77 00 73 00 5c 00  ..........w.s.\.
    30 00 00 00 20 00 00 1a 00 00 00 00 00 00 00 00  0... ...........
    Sorting index $I30 in file 10283.
    The file reference 0xb100000000fd88 of index entry 61 of index $I30
    with parent 0x3894 is not the same as 0xb200000000fd88.
    Deleting index entry 61 in index $I30 of file 14484.
    The file reference 0x7b00000000fd81 of index entry 27 of index $I30
    with parent 0x3992 is not the same as 0x8400000000fd81.
    Deleting index entry 27 in index $I30 of file 14738.
    The file reference 0x5b000000010563 of index entry EE of index $I30
    with parent 0x3992 is not the same as 0x5c000000010563.
    Deleting index entry EE in index $I30 of file 14738.
    The file reference 0x4d000000010123 of index entry A3 of index $I30
    with parent 0x3a05 is not the same as 0x4e000000010123.
    Deleting index entry A3 in index $I30 of file 14853.
    The file reference 0x7a00000000fd53 of index entry C7 of index $I30
    with parent 0x3a05 is not the same as 0x8200000000fd53.
    Deleting index entry C7 in index $I30 of file 14853.
    The file reference 0x44000000010142 of index entry C5 of index $I30
    with parent 0x53fc is not the same as 0x46000000010142.
    Deleting index entry C5 in index $I30 of file 21500.
    The file reference 0x10f00000001014a of index entry 66 of index $I30
    with parent 0x89b6 is not the same as 0x11000000001014a.
    Deleting index entry 66 in index $I30 of file 35254.
    The index bitmap for index $I30 in file 0x15dd5 is invalid or missing.
    Correcting error in index $I30 for file 89557.
    The index bitmap $I30 is present but there is no corresponding
    index allocation attribute in file 0x15dd5.
    Correcting error in index $I30 for file 89557.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
    ff ff ff ff ff ff ff ff 64 44 3a 5e ba e6 cd 01  ........dD:^....
    de 88 b4 3a ba e6 cd 01 96 b9 3a 5e ba e6 cd 01  ...:......:^....
    Sorting index $I30 in file 89557.
    The index bitmap for index $I30 in file 0x15ff4 is invalid or missing.
    Correc</Data>
      </EventData>
    </Event>

    Wednesday, January 2, 2013 2:33 PM
  • J

    I would run it again (but no need to post the entire output).  Yours was in bad shape this run.


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Wednesday, January 2, 2013 6:37 PM
  • I run It again and what should I do next? Can I also get the download link I requested to.
    Wednesday, January 2, 2013 7:19 PM
  • JS

    You should expect a clean bill of health (no errors), if not the HD may be failing.  Unfortunately I cant help you with that link. 


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Thursday, January 3, 2013 7:45 AM