The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Windows XP not loading - Stuck doing Check Disk at 87%

    Discussion in 'Windows OS and Software' started by likair, May 10, 2009.

  1. likair

    likair Notebook Consultant

    Reputations:
    0
    Messages:
    241
    Likes Received:
    0
    Trophy Points:
    30
    Hello,

    Yesterday I started my laptop as usual and instead of the normal Welcome screen a screen popped up saying that Disk D needs to be check ....

    Apparently there's a corrupted file called FOUND.000 in disk D.
    The disk scan was stuck at 87% of the process....

    To load the OS i have to skip the scan disk....
    I really don't know how all this happened....

    I tried to defrag the system but it didn't let me becasue of the mentioned corrupted file.

    Can anyone help me to solve this problem?

    Thanks for your attention.
     
  2. likair

    likair Notebook Consultant

    Reputations:
    0
    Messages:
    241
    Likes Received:
    0
    Trophy Points:
    30
    I tried to delete this file but the system is not letting me because it is corrupted.

    This might be because I stopped the Check disk while scanning and restarted by holding the power key for 5 secs. Then I skipped the scan disk to load the OS as normal.

    How can I solve this problem....?
     
  3. Shyster1

    Shyster1 Notebook Nobel Laureate

    Reputations:
    6,926
    Messages:
    8,178
    Likes Received:
    0
    Trophy Points:
    205
    Actually, I don't believe the file named "Found.000" was the (original) source of your problem. Reading through a few hits that come up when I google found.000 indicates that this file is where Chkdsk puts stuff that it's found and is trying to save, e.g., as discussed on this neowin forum thread.

    If chkdsk started automatically, that probably means that you had a pretty serious error - possibly including a hard drive that's beginning to fail and is starting to corrupt the system files, that's how I usually end up getting mandatory chkdsk visits. :D

    The Found.000 file may now be corrupted because you stopped the chkdsk operation in midstream - depending on how you stopped it, that could have left a whole bunch of files open, which might have created corruption in those files.

    I would boot up and schedule another run of chkdsk on your system partition (it won't go immediately, but has to be scheduled to run before the OS boots up next time you start the system up) - and, most importantly, have the patience to let it work through what it has to go through - I once spent several hours waiting for chkdsk to recover a good chunk of what was a thoroughly trashed file system.
     
  4. likair

    likair Notebook Consultant

    Reputations:
    0
    Messages:
    241
    Likes Received:
    0
    Trophy Points:
    30
    Thanks a lot Shyster!!!

    Your post makes sense.
    I will try to be more patience next time. Probably I will let chkdisk to run at night!! Yes it takes a lot of time to scan!!!

    Do you think I will have HD problems after running the chkdisk ??
    Bad sectors etc... and bring in the risk of losing data....?

    Thanks for your help!!!
     
  5. jackluo923

    jackluo923 Notebook Virtuoso

    Reputations:
    1,038
    Messages:
    3,071
    Likes Received:
    1
    Trophy Points:
    105
    Use HDtune to scan your hdd for "bad" sector and let chkdisk run overnight to attempt to recover the data.