• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Need help! Current Pending Sector

Scrubls

n00b
Joined
Mar 16, 2013
Messages
35
30% of the time I start my PC it says "One of your disk needs to be checked for consistency" I did let it finish the first time and no errors wore found. Since then the windows on my problematic HDD (WD Caviar Black 1TB) (2months old) has been screwed. The trouble started when my PC froze and I had to shut it down incorrectly.

CMD "diskdrive get status" and "WD Lifeguard" report all is ok. While "HD Tune Pro" and "CrystalDiskInfo" report Current Pending Sector!!

How to fix??

5247b7ac_HDDWDBLACK.jpeg
 
A single pending sector is nothing to write home about, as long as it does not increase and your reallocated sector count is zero. This can happen for example if the drive loses power while writing. The pending sector is invalid and will be cleared when it is written the next time. The data contained in that sector is lost however. I would check the SMART data regularly and if it increases exchange the drive.
 
Yes, this only happened after my PC froze (I could still actually hear the hdd working), maybe it was writing something when it froze due to unstable OC.

Should I right 0's to it? or whatever its called...:p
 
How are you going to do that? It is not required - just ignore it.

Well...WD Lifeguard offers that option, the windows on that drive is screwed now, and I would like to use that drive as my bootable drive. I have to do something...

EDIT: BTW I'm currently running "chkdsk /x /v /r /b" on the drive to see if the bad sector goes away :D
 
No the drive caused the system to freeze.

I don't think so, when my PC froze I was in the process of getting a stable OC (getting the right voltage), you know the deal... blue screens...freezes... all that good stuff. Also I was running PS2 emulator (cpu heavy) when PC froze.
 
My point is a pending sector is internal to the drive (representing a sector that the drive wrote in the past but can no longer read) and should not be caused by anything the OS or CPU does.
 
My point is a pending sector is internal to the drive (representing a sector that the drive wrote in the past but can no longer read) and should not be caused by anything the OS or CPU does.

Well if the PC froze, causing me to shut the PC down inappropriately while the HDD was reading/writing a sector, I'm guessing there is a high chance that sector will became a bad sector.

It was only right after that little incident that windows informed me that "One of your disks need to be checked for consistency" and the windows on that drive stopped working properly.
 
It is indeed possible... the good OC mainboards switch the whole PC off and on when in some cases a simple reset won't help. Some timing/clock settings require that (especially RAM settings).

Well...WD Lifeguard offers that option, the windows on that drive is screwed now, and I would like to use that drive as my bootable drive. I have to do something...

EDIT: BTW I'm currently running "chkdsk /x /v /r /b" on the drive to see if the bad sector goes away :D
If the Windows does not boot because of that sector, there is still the chance that it won't be able to boot after chkdsk. Consider to just reinstall Windows if it is a new system or run a repair if you don't want to reinstall. Whether the sector reports an error or if it is zeroed makes no difference... the data is lost either way. If it is a metadata sector (unlikely with a journaling FS like NTFS) chkdsk may be able to repair it or you may lose a directory tree.
 
Last edited:
It is indeed possible... the good OC mainboards switch the whole PC off and on when in some cases a simple reset won't help. Some timing/clock settings require that (especially RAM settings).


If the Windows does not boot because of that sector, there is still the chance that it won't be able to boot after chkdsk. Consider to just reinstall Windows if it is a new system or run a repair if you don't want to reinstall. Whether the sector reports an error or if it is zeroed makes no difference... the data is lost either way. If it is a metadata sector (unlikely with a journaling FS like NTFS) chkdsk may be able to repair it or you may lose a directory tree.

The windows does boot, but explorer.exe stops responding every 3 seconds, I tried starting it via task manager but it just stops responding every time, probably because some of the files windows needs are on the bad sector.

EDIT: Just finished the chkdsk, still have the pending sector...

dd17de9c_pendingsectorr.jpeg
 
Last edited:
only way your gonna get rid of that is via something that is going to check every sector of the drive and repair for badblocks. a chkdisk with a full sector scan might do it (that will take 5+ hours) or using a tool like Spinrite.
 
only way your gonna get rid of that is via something that is going to check every sector of the drive and repair for badblocks. a chkdisk with a full sector scan might do it (that will take 5+ hours) or using a tool like Spinrite.

I just did a "chkdsk /x /v /r /b" look at the pic... bad sector is still there. I think writing zeros would solve the problem but I would have to format...
 
if you want to play with the fire of overclocking, then be prepared for the possibility of your hardware getting irreversibly tweaked.

forget chkdsk, that's amateur hour. put partedmagic on a flashdisk and run badblocks against the drive.
 
I just did a "chkdsk /x /v /r /b" look at the pic... bad sector is still there. I think writing zeros would solve the problem but I would have to format...

And this is your boot drive? as I am pretty sure you can't do a bad block scan while the machine is running the OS i thought. I know spinright would probably fix it.
 
There probably is a way to determine the corrupt file and replace it by a good copy from install media - google is your friend here. The question is, wouldn't it be easier to just run a recovery from install media or even better, just reinstall Windows.
 
Back
Top