Damaged Blocks Detected in HD Tune, Failure to Boot

Page 1 of 2 12 LastLast

  1. Posts : 11
    Windows 7 Ultimate x64
       #1

    Damaged Blocks Detected in HD Tune, Failure to Boot


    A week or so ago my PC failed to boot Windows 7 (64 bit) from my 1TB Western Digital WD10EARS. The screen would go black after the boot logo (no cursor, monitor was still displaying). after waiting several minutes, I hard shutdown my PC by holding down the power button.

    After several attempts to boot with the same results, I attempted to safe boot which would hang while loading CLASSPNP.sys. in short, I could successfully boot after running a full DSKCHK with stages 4 & 5 (which "replaced bad clusters in file 69361 of name /windows/system32/config/software" during stage 4) and running startup repair from my recovery disc.

    I thought I had resolved the issue until I booted up the next day, during which the same problem had returned. After going through the same recovery process again (DSKCHK + startup repair) I could once again successfully boot. though this time I refrained from using it to avoid causing any more damage, and installed Windows XP SP3 on my 80GB drive.

    I have since then realized that my "fix" grants me one boot before going back to it's unbootable state. I ran a full error scan in HD Tune, which detected 4 damaged blocks (0.2%) as shown in the attached picture.

    Temperature is perfectly fine and the S.M.A.R.T. info as read by HD Tune detected no issues.

    My question is, Should I:


    A. Use a program such as HDD Regenerator, DLGDIAG or Spinrite to fix this issue and continue using the drive

    B. Use a program such as HDD Regenerator, DLGDIAG or Spinrite to fix this issue then format and reinstall Windows

    C. Simply format and reinstall Windows

    D. Replace the drive

    E. Sacrifice a (stick of) RAM on the blood moon

    F. Repair install

    G. Other


    I've already backed up what I needed to, but purchasing a new drive isn't really a good option for me as I really don't have the money for it right now.
    Attached Thumbnails Attached Thumbnails Damaged Blocks Detected in HD Tune, Failure to Boot-ss9io-jpg.png  
    Last edited by nomad6770; 08 Oct 2012 at 10:32.
      My Computer


  2. Posts : 4,751
    Windows 7 Home Premium 32-Bit - Build 7600 SP1
       #2

    Try a System Restore to a date before you had a problem the first time.
      My Computer


  3. Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       #3

    bigmck said:
    Try a System Restore to a date before you had a problem the first time.
    I can go ahead and give it a try (who knows, maybe the problem lies in the registry). If I run System Restore from a Windows 7 recovery disc, will it create a Restore point prior to rolling back?

    Just in case things don't go right, because I don't know when the last Restore point was made.
      My Computer


  4. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #4

    Hi,

    Those bad sectors cannot be fixed, but what you can, and should, do is prevent data being written to them. To do that you need to run chkdsk /R. To do that, follow this:

    1. Click Start
    2. In the search box, type cmd
    3. In the list that appears, right-click on cmd.exe and choose Run as administrator
    4. In the command window that opens, type chkdsk /R and hit enter.

    You will be prompted whether you wish to schedule a check disk at next boot up. Press 'Y' and reboot your system. Now be patient whilst the chkdsk completes. Your system should run a little bit better.

    Longer term, keep an eye for more bad sectors - if more appear, consider replacing the drive.

    Regards,
    Golden
      My Computer


  5. Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Golden said:
    Hi,

    Those bad sectors cannot be fixed, but what you can, and should, do is prevent data being written to them. To do that you need to run chkdsk /R. To do that, follow this:

    1. Click Start
    2. In the search box, type cmd
    3. In the list that appears, right-click on cmd.exe and choose Run as administrator
    4. In the command window that opens, type chkdsk /R and hit enter.

    You will be prompted whether you wish to schedule a check disk at next boot up. Press 'Y' and reboot your system. Now be patient whilst the chkdsk completes. Your system should run a little bit better.

    Longer term, keep an eye for more bad sectors - if more appear, consider replacing the drive.

    Regards,
    Golden

    As I said in my first post,

    I could successfully boot after running a full DSKCHK with stages 4 & 5 (which "replaced bad clusters in file 69361 of name /windows/system32/config/software" during stage 4) and running startup repair from my recovery disc.

    I thought I had resolved the issue until I booted up the next day, during which the same problem had returned. After going through the same recovery process again (DSKCHK + startup repair) I could once again successfully boot....I have since then realized that my "fix" grants me one boot before going back to it's unbootable state.
    Also, HDD regenerator claims "HDD Regenerator is a unique program for regeneration of physically damaged hard disk drives. It does not hide bad sectors, it really restores them!"
      My Computer


  6. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #6

    Except it appeared not to have worked, since the same problem has returned............or have I missed something?

    Did you specify the /R switch when you ran chkdsk?

    Some light reading for you:
    http://en.wikipedia.org/wiki/Bad_sector

    A bad sector is a sector on a computer's disk drive or flash memory that cannot be used due to permanent damage (or an OS inability to successfully access it), such as physical damage to the disk surface (or sometimes sectors being stuck in a magnetic or digital state that cannot be reversed) or failed flash memory transistors.
      My Computer


  7. Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Are you saying DSKCHK didn't work, or HDD Regenerator? If DSKCHK, then yes it didn't work. if HDD Regenerator, then I have not used it yet.

    Also, do you think this will work?
    Last edited by nomad6770; 08 Oct 2012 at 10:38. Reason: Added Link
      My Computer


  8. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #8

    Did you specify /R switch with chkdsk?

    Your issue doesn't sound like a bootloader issue to me, so I wouldn't go down that path yet.
      My Computer


  9. Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       #9

    Golden said:
    Did you specify /R switch with chkdsk?
    I scheduled it through Explorer rather than CMD. but it is my understanding that checking both options as shown HERE is the same as using the /r switch in CMD.
      My Computer


  10. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #10

    Yes, that my understanding.

    Since your errors occur in the \windows\system32 folder you should check for system file corruptions:

    1. Click Start
    2. In the search box, type cmd
    3. In the list that appears, right-click on cmd.exe and choose Run as administrator
    4. In the command window that opens, type sfc /scannow and hit enter.

    Report the output once it finishes.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:25.
Find Us