Page 1 of 12 12311 ... LastLast
Results 1 to 10 of 116
  1. #1
    Member
    Join Date
    Dec 2014
    Location
    Fort Worth, Texas
    Posts
    165
    Points
    0

    Default Laptop froze-up during backup!

    I am currently bacing up my Dell Inspiron N5040 for the first time. Yes, shame on me! I was having minor problems, including slow-to-unresponsive windows. So I went to the Dell support site to do a diagnostic. The check showed that my hard drive failed the slow self test. And I decided to back it up so I could replace the HD. It froze up for an hour and a half. Did that freeze up effect my back up? No progress occurred during the freeze, so I'm guessing this shows that the system locked up instead of the graphics locking up.

    Windows7 running on a Dell N5040, mid 2011. First time backing up any computer, to a Maxtor 500gig converted to external. Sorry if I don't have enough info here, this is just one of many problems I have had in the past two days.

  2. #2
    Member Spyware Fighter DonnaB's Avatar
    Join Date
    Apr 2009
    Location
    Illiana, Ill. USA
    Posts
    3,521
    Points
    563

    Default

    Hi mrick36,

    Let me get you started here. First of all, only way to tell if the freeze up effected the back up is to access the files that you backed up onto the Maxtor. There is no need to back up anything except your personal files such as pictures, music etc. Installed programs can be replaced.

    For now, see if you can go to your user profile, right click then copy/paste your personal file folders (pictures, music, documents, etc.) to the external for safe keeping.

    Since the hard drive failed the the slow self test, let's focus on that for now and see if there are any bad sectors found. If either of the following tests show the hard drive is ok then we will have you run a couple other scans for diagnostic purposes:

    Please do the following:

    • Click on Start then click on Computer
    • Right click on the C: drive, scroll down and click on Properties
    • Click on the Tools tab
    • Click on the Check Now... button
    • In the dialog box that opens, place a checkmark in the 2 boxes and click on Start
    • The next dialog box will now show a similar message as below:
      • Windows can't check the disk while it's in use.
        Do you want to check for hard disk errors the next time you
        start your computer ? <Schedule disk check/Cancel>
      • Click on Schedule disk check and reboot the computer if it does not reboot on it's own.
    • Checkdisk will start once the computer reboots. It can take up to an hour or more to complete as it goes through the stages. Allow it to run uninterrupted till complete.


    To find the log that is produced please do the following:

    Please download ListChkdskResult by SleepyDude to the desktop.

    1. Double click on the icon and click Run
    2. The log will appear on your desktop as a .txt file and the notepad will open.

    Please copy and paste the results in your next reply.

    For a 2nd opinion, you could also download Seagate SeaTools which is a free program that is used to test all computer hard drives. Just click on the download tab at the top of the page and under Downloads > Utilities > SeaTools for Windows and select your OS.

    Thank you,

    Donna
    If you think you might be infected with malware or have recently cleansed your computer of malware without the help of an expert, please read and follow the instructions in How to Start Removing Viruses and Spyware from your Computer. This can alleviate time consumed in trouble shooting your current computer problems.

    If your problem is solved, here's how to say thanks!

    Very proud parent of a U.S. Navy "CB"



    "People may forget what you say,
    People may forget what you did,
    but People will never forget how you made them feel!"

  3. The Following User Says Thank You to DonnaB For This Useful Post:


  4. #3
    Member
    Join Date
    Dec 2014
    Location
    Fort Worth, Texas
    Posts
    165
    Points
    0

    Default

    Right now it is backing up with the Windows Backup utility. I am really hesitant to touch it before it finishes. It is 42% complete now. So, it will not be finished before midnight. We should all get a good night's sleep before tackling this beast! I will begin the tests in the a.m. Thanks!

  5. #4
    Member Spyware Fighter DonnaB's Avatar
    Join Date
    Apr 2009
    Location
    Illiana, Ill. USA
    Posts
    3,521
    Points
    563

    Default

    Good morning mrick36,

    From my understanding, a typical back up should not take hours, but minutes.

    Some links for your viewing/reading pleasure:

    How To Use Backup and Restore in Windows 7

    Backup and Restore - Microsoft Windows

    Windows 7 backup solution? - AnandTech Forums

    Off to work. Have a nice day!
    If you think you might be infected with malware or have recently cleansed your computer of malware without the help of an expert, please read and follow the instructions in How to Start Removing Viruses and Spyware from your Computer. This can alleviate time consumed in trouble shooting your current computer problems.

    If your problem is solved, here's how to say thanks!

    Very proud parent of a U.S. Navy "CB"



    "People may forget what you say,
    People may forget what you did,
    but People will never forget how you made them feel!"

  6. #5
    Member
    Join Date
    Dec 2014
    Location
    Fort Worth, Texas
    Posts
    165
    Points
    0

    Default

    I'm sorry Donna, but some urgent business came up and I have to go out of town to take care of it. I will deal with this when I return.

    Have a nice day!

    Darryl

  7. #6
    Member Spyware Fighter DonnaB's Avatar
    Join Date
    Apr 2009
    Location
    Illiana, Ill. USA
    Posts
    3,521
    Points
    563

    Default

    Not a problem Darryl. Be safe. See you when you return.
    If you think you might be infected with malware or have recently cleansed your computer of malware without the help of an expert, please read and follow the instructions in How to Start Removing Viruses and Spyware from your Computer. This can alleviate time consumed in trouble shooting your current computer problems.

    If your problem is solved, here's how to say thanks!

    Very proud parent of a U.S. Navy "CB"



    "People may forget what you say,
    People may forget what you did,
    but People will never forget how you made them feel!"

  8. #7
    Member
    Join Date
    Dec 2014
    Location
    Fort Worth, Texas
    Posts
    165
    Points
    0

    Default

    Back in town and decided to see what my computer thought of the HD before I read your last instructions. I ran the disk check with only the first box checked and then went to check your instructions. Now I'm repeating the procedure with only the second option, and it is bearly moving! BTW, I am on my tablet again, waiting to see if the laptop will complete the test. It has been running for about 2 hours now. I'm only guessing, but from what I've read on the Windows instructions for these tests, it seems like it might be fixing errors? Will send the test results when or if this ever finishes. Another thing that I failed to mention is that I had to replace the battery about a month ago because it would not hold a charge for more the 20 minutes. I am hoping that the fluctuate of power caused errors that the system is fixing. I will patiently wait for it to finish and focus my energy toward the healing powers of this wonderful machine! ����

  9. #8
    Member
    Join Date
    Dec 2014
    Location
    Fort Worth, Texas
    Posts
    165
    Points
    0

    Default

    I will post each disk check in separate replies. The message it gave me said that my device was ready to use.

    ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013

    ------< Log generate on 5/29/2015 4:44:22 PM >------
    Category: 0
    Computer Name: Owner-PC
    Event Code: 1001
    Record Number: 79699
    Source Name: Microsoft-Windows-Wininit
    Time Written: 05-29-2015 @ 21:42:22
    Event Type: Information
    User:
    Message:

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


    A disk check has been scheduled.
    Windows will now check the disk.

    CHKDSK is verifying files (stage 1 of 3)...
    Cleaning up instance tags for file 0x21402.
    179200 file records processed. File verification completed.
    1746 large file records processed. 0 bad file records processed. 0 EA records processed. 47 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
    237996 index entries processed. Index verification completed.
    0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
    179200 file SDs/SIDs processed. Cleaning up 2411 unused index entries from index $SII of file 0x9.
    Cleaning up 2411 unused index entries from index $SDH of file 0x9.
    Cleaning up 2411 unused security descriptors.
    Security descriptor verification completed.
    29399 data files processed. CHKDSK is verifying Usn Journal...
    35216440 USN bytes processed. Usn Journal verification completed.
    CHKDSK discovered free space marked as allocated in the
    master file table (MFT) bitmap.
    CHKDSK discovered free space marked as allocated in the volume bitmap.
    Windows has made corrections to the file system.

    472922135 KB total disk space.
    128383616 KB in 144646 files.
    96164 KB in 29400 indexes.
    0 KB in bad sectors.
    296775 KB in use by the system.
    65536 KB occupied by the log file.
    344145580 KB available on disk.

    4096 bytes in each allocation unit.
    118230533 total allocation units on disk.
    86036395 allocation units available on disk.

    Internal Info:
    00 bc 02 00 ea a7 02 00 1b f5 04 00 00 00 00 00 ................
    32 09 00 00 2f 00 00 00 00 00 00 00 00 00 00 00 2.../...........
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

    Windows has finished checking your disk.
    Please wait while your computer restarts.

    -----------------------------------------------------------------------
    Category: 0
    Computer Name: Owner-PC
    Event Code: 26214
    Record Number: 54630
    Source Name: Chkdsk
    Time Written: 10-13-2014 @ 18:23:10
    Event Type: Information
    User:
    Message: Chkdsk was executed in read/write mode.

    Checking file system on E:

    CHKDSK is verifying files (stage 1 of 5)...
    256 file records processed. File verification completed.
    0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
    282 index entries processed. Index verification completed.


    CHKDSK is verifying security descriptors (stage 3 of 5)...
    256 file SDs/SIDs processed. Cleaning up 2 unused index entries from index $SII of file 0x9.
    Cleaning up 2 unused index entries from index $SDH of file 0x9.
    Cleaning up 2 unused security descriptors.
    Security descriptor verification completed.
    14 data files processed. CHKDSK is verifying Usn Journal...
    1120 USN bytes processed. Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
    Read failure with status 0xc0000185 at offset 0xcc961000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xcc962000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 32 of name \$Extend\$RmMetadata\$TxfLog\$TxfLog.blf.
    Read failure with status 0xc000000e at offset 0xcc971000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xcc971000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 33 of name \$Extend\$RmMetadata\$TxfLog\$TXFLO~1.
    Read failure with status 0xc000000e at offset 0xcd371000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xcd371000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 34 of name \$Extend\$RmMetadata\$TxfLog\$TXFLO~2.
    Read failure with status 0xc000000e at offset 0xcdd72000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xcdd72000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 35 of name \697.flv.
    Read failure with status 0xc000000e at offset 0xd1e5f000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd1e5f000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 36 of name \15545.flv.
    Read failure with status 0xc000000e at offset 0xd28c6000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd28c6000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 37 of name \254444~1.FLV.
    Read failure with status 0xc000000e at offset 0xd2cf5000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd2cf5000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 38 of name \278282~1.FLV.
    Read failure with status 0xc000000e at offset 0xd3924000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd3924000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 39 of name \283720~1.FLV.
    Read failure with status 0xc000000e at offset 0xd44d8000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd44d8000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 40 of name \292119~1.FLV.
    Read failure with status 0xc000000e at offset 0xd59d2000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd59d2000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 41 of name \$RECYCLE.BIN\S-1-5-~1\$R3TBHKI.flv.
    Read failure with status 0xc000000e at offset 0xd63da000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd63da000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 47 of name \9334.flv.
    Read failure with status 0xc000000e at offset 0xd9d22000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd9d22000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 48 of name \10701.flv.
    Read failure with status 0xc000000e at offset 0xdac8e000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xdac8e000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 49 of name \10702.flv.
    Read failure with status 0xc000000e at offset 0xdbbdd000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xdbbdd000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 50 of name \10703.flv.
    Read failure with status 0xc000000e at offset 0xdcaac000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xdcaac000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 51 of name \10704.flv.
    Read failure with status 0xc000000e at offset 0x130004000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x130004000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 52 of name \11969.flv.
    Read failure with status 0xc000000e at offset 0x1305fd000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x1305fd000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 53 of name \290204~1.FLV.
    Read failure with status 0xc000000e at offset 0x180000000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x180000000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 54 of name \303403~1.FLV.
    Read failure with status 0xc000000e at offset 0x180eed000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x180eed000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 55 of name \310449~1.FLV.
    Read failure with status 0xc000000e at offset 0x181e69000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x181e69000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 56 of name \334569~1.FLV.
    Read failure with status 0xc000000e at offset 0x18334f000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x18334f000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 57 of name \336106~1.FLV.
    Read failure with status 0xc000000e at offset 0x183ce0000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x183ce0000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 58 of name \349017~1.FLV.
    Read failure with status 0xc000000e at offset 0x18466e000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x18466e000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 59 of name \361296~2.FLV.
    240 files processed. File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    0 free clusters processed. 0 free clusters processed. Free space verification is complete.
    Read failure with status 0xc000000e at offset 0xbfffe000 for 0x1000 bytes.
    The attribute definition table cannot be read.
    Correcting errors in the Attribute Definition Table.
    Read failure with status 0xc000000e at offset 0xbfffe000 for 0x1000 bytes.
    Read failure with status 0xc000000e at offset 0xbfffe000 for 0x1000 bytes.
    Read failure with status 0xc000000e at offset 0xbfffe000 for 0x1000 bytes.
    Insufficient disk space to fix the attribute definition table.
    CHKDSK aborted.

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

  10. #9
    Member
    Join Date
    Dec 2014
    Location
    Fort Worth, Texas
    Posts
    165
    Points
    0

    Default

    And the second disk check.


    ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013

    ------< Log generate on 5/29/2015 9:55:34 PM >------
    Category: 0
    Computer Name: Owner-PC
    Event Code: 26212
    Record Number: 79745
    Source Name: Chkdsk
    Time Written: 05-30-2015 @ 02:54:24
    Event Type: Information
    User:
    Message: Chkdsk was executed in read-only mode on a volume snapshot.

    Checking file system on C:
    Volume label is OS.

    CHKDSK is verifying files (stage 1 of 5)...
    179200 file records processed. File verification completed.
    1746 large file records processed. 0 bad file records processed. 0 EA records processed. 47 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
    238006 index entries processed. Index verification completed.


    CHKDSK is verifying security descriptors (stage 3 of 5)...
    179200 file SDs/SIDs processed. Cleaning up 6 unused index entries from index $SII of file 0x9.
    Cleaning up 6 unused index entries from index $SDH of file 0x9.
    Cleaning up 6 unused security descriptors.
    Security descriptor verification completed.
    29404 data files processed. CHKDSK is verifying Usn Journal...
    35459216 USN bytes processed. Usn Journal verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    85834271 free clusters processed. Free space verification is complete.
    Found 1060 bad clusters.
    The Volume Bitmap is incorrect.
    Windows found problems with the file system.
    Run CHKDSK with the /F (fix) option to correct these.

    472922135 KB total disk space.
    129192100 KB in 144700 files.
    96172 KB in 29405 indexes.
    296779 KB in use by the system.
    65536 KB occupied by the log file.
    343332844 KB available on disk.

    4096 bytes in each allocation unit.
    118230533 total allocation units on disk.
    85833211 allocation units available on disk.

    -----------------------------------------------------------------------
    Category: 0
    Computer Name: Owner-PC
    Event Code: 1001
    Record Number: 79699
    Source Name: Microsoft-Windows-Wininit
    Time Written: 05-29-2015 @ 21:42:22
    Event Type: Information
    User:
    Message:

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


    A disk check has been scheduled.
    Windows will now check the disk.

    CHKDSK is verifying files (stage 1 of 3)...
    Cleaning up instance tags for file 0x21402.
    179200 file records processed. File verification completed.
    1746 large file records processed. 0 bad file records processed. 0 EA records processed. 47 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
    237996 index entries processed. Index verification completed.
    0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
    179200 file SDs/SIDs processed. Cleaning up 2411 unused index entries from index $SII of file 0x9.
    Cleaning up 2411 unused index entries from index $SDH of file 0x9.
    Cleaning up 2411 unused security descriptors.
    Security descriptor verification completed.
    29399 data files processed. CHKDSK is verifying Usn Journal...
    35216440 USN bytes processed. Usn Journal verification completed.
    CHKDSK discovered free space marked as allocated in the
    master file table (MFT) bitmap.
    CHKDSK discovered free space marked as allocated in the volume bitmap.
    Windows has made corrections to the file system.

    472922135 KB total disk space.
    128383616 KB in 144646 files.
    96164 KB in 29400 indexes.
    0 KB in bad sectors.
    296775 KB in use by the system.
    65536 KB occupied by the log file.
    344145580 KB available on disk.

    4096 bytes in each allocation unit.
    118230533 total allocation units on disk.
    86036395 allocation units available on disk.

    Internal Info:
    00 bc 02 00 ea a7 02 00 1b f5 04 00 00 00 00 00 ................
    32 09 00 00 2f 00 00 00 00 00 00 00 00 00 00 00 2.../...........
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

    Windows has finished checking your disk.
    Please wait while your computer restarts.

    -----------------------------------------------------------------------
    Category: 0
    Computer Name: Owner-PC
    Event Code: 26214
    Record Number: 54630
    Source Name: Chkdsk
    Time Written: 10-13-2014 @ 18:23:10
    Event Type: Information
    User:
    Message: Chkdsk was executed in read/write mode.

    Checking file system on E:

    CHKDSK is verifying files (stage 1 of 5)...
    256 file records processed. File verification completed.
    0 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
    282 index entries processed. Index verification completed.


    CHKDSK is verifying security descriptors (stage 3 of 5)...
    256 file SDs/SIDs processed. Cleaning up 2 unused index entries from index $SII of file 0x9.
    Cleaning up 2 unused index entries from index $SDH of file 0x9.
    Cleaning up 2 unused security descriptors.
    Security descriptor verification completed.
    14 data files processed. CHKDSK is verifying Usn Journal...
    1120 USN bytes processed. Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
    Read failure with status 0xc0000185 at offset 0xcc961000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xcc962000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 32 of name \$Extend\$RmMetadata\$TxfLog\$TxfLog.blf.
    Read failure with status 0xc000000e at offset 0xcc971000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xcc971000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 33 of name \$Extend\$RmMetadata\$TxfLog\$TXFLO~1.
    Read failure with status 0xc000000e at offset 0xcd371000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xcd371000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 34 of name \$Extend\$RmMetadata\$TxfLog\$TXFLO~2.
    Read failure with status 0xc000000e at offset 0xcdd72000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xcdd72000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 35 of name \697.flv.
    Read failure with status 0xc000000e at offset 0xd1e5f000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd1e5f000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 36 of name \15545.flv.
    Read failure with status 0xc000000e at offset 0xd28c6000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd28c6000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 37 of name \254444~1.FLV.
    Read failure with status 0xc000000e at offset 0xd2cf5000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd2cf5000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 38 of name \278282~1.FLV.
    Read failure with status 0xc000000e at offset 0xd3924000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd3924000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 39 of name \283720~1.FLV.
    Read failure with status 0xc000000e at offset 0xd44d8000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd44d8000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 40 of name \292119~1.FLV.
    Read failure with status 0xc000000e at offset 0xd59d2000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd59d2000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 41 of name \$RECYCLE.BIN\S-1-5-~1\$R3TBHKI.flv.
    Read failure with status 0xc000000e at offset 0xd63da000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd63da000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 47 of name \9334.flv.
    Read failure with status 0xc000000e at offset 0xd9d22000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xd9d22000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 48 of name \10701.flv.
    Read failure with status 0xc000000e at offset 0xdac8e000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xdac8e000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 49 of name \10702.flv.
    Read failure with status 0xc000000e at offset 0xdbbdd000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xdbbdd000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 50 of name \10703.flv.
    Read failure with status 0xc000000e at offset 0xdcaac000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0xdcaac000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 51 of name \10704.flv.
    Read failure with status 0xc000000e at offset 0x130004000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x130004000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 52 of name \11969.flv.
    Read failure with status 0xc000000e at offset 0x1305fd000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x1305fd000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 53 of name \290204~1.FLV.
    Read failure with status 0xc000000e at offset 0x180000000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x180000000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 54 of name \303403~1.FLV.
    Read failure with status 0xc000000e at offset 0x180eed000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x180eed000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 55 of name \310449~1.FLV.
    Read failure with status 0xc000000e at offset 0x181e69000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x181e69000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 56 of name \334569~1.FLV.
    Read failure with status 0xc000000e at offset 0x18334f000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x18334f000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 57 of name \336106~1.FLV.
    Read failure with status 0xc000000e at offset 0x183ce0000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x183ce0000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 58 of name \349017~1.FLV.
    Read failure with status 0xc000000e at offset 0x18466e000 for 0x10000 bytes.
    Read failure with status 0xc000000e at offset 0x18466e000 for 0x1000 bytes.
    The disk does not have enough space to replace bad clusters
    detected in file 59 of name \361296~2.FLV.
    240 files processed. File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
    0 free clusters processed. 0 free clusters processed. Free space verification is complete.
    Read failure with status 0xc000000e at offset 0xbfffe000 for 0x1000 bytes.
    The attribute definition table cannot be read.
    Correcting errors in the Attribute Definition Table.
    Read failure with status 0xc000000e at offset 0xbfffe000 for 0x1000 bytes.
    Read failure with status 0xc000000e at offset 0xbfffe000 for 0x1000 bytes.
    Read failure with status 0xc000000e at offset 0xbfffe000 for 0x1000 bytes.
    Insufficient disk space to fix the attribute definition table.
    CHKDSK aborted.

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

  11. #10
    Member
    Join Date
    Dec 2014
    Location
    Fort Worth, Texas
    Posts
    165
    Points
    0

    Default

    Uh, new question: What and where is drive E ?

    Update: Answered my own question! The E drive is my SD card slot! Why on earth is my computer checking that drive when I chose C:, the HD?
    Last edited by mrick36; 05-30-2015 at 12:00 AM.

Page 1 of 12 12311 ... LastLast