Bad sectors in SSD after fresh install

grit

Limp Gawd
Joined
Jul 29, 2002
Messages
136
I just reinstalled Windows 7 (no other OS's) on my Crucial C300 256GB SSD. Its the only SSD/HDD storage in the system. After getting intermittent pauses, I ran a chkdsk and found
116KB in bad sectors. If this was a HDD, I'd replace it, since that's usually a precursor to the drive failing. I have NO idea what, if anything, that means for SSDs. Also, I ran the chkdsk with "fix errors"... so what happened to the data in the bad sectors? Do I need to reinstall?

Here's the chkdsk log, in case that helps.
----------------------------------------


Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows 7 Pro.

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

CHKDSK is verifying files (stage 1 of 5)...
554752 file records processed. File verification completed.
373 large file records processed. 0 bad file records processed. 2 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
612764 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
554752 file SDs/SIDs processed. Cleaning up 454 unused index entries from index $SII of file 0x9.
Cleaning up 454 unused index entries from index $SDH of file 0x9.
Cleaning up 454 unused security descriptors.
Security descriptor verification completed.
29007 data files processed. CHKDSK is verifying Usn Journal...
33568792 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc00000b5 at offset 0x5bfb54000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x5bfb56000 for 0x1000 bytes.
Windows replaced bad clusters in file 41
of name \Windows\Prefetch\AgRobust.db.
Read failure with status 0xc00000b5 at offset 0xd111000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0xd11c000 for 0x1000 bytes.
Windows replaced bad clusters in file 17531
of name \Windows\winsxs\amd64_microsoft-windows-f..crosoftjhengheibold_31bf3856ad364e35_6.1.7600.1 6385_none_baa58b03c657ca8d\msjhbd.ttf.
Read failure with status 0xc00000b5 at offset 0x34f1e000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x34f2c000 for 0x1000 bytes.
Windows replaced bad clusters in file 44542
of name \MSOCache\ALLUSE~1\{90140~2\PptLR.cab.
Read failure with status 0xc00000b5 at offset 0x20557f2000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x20557fd000 for 0x1000 bytes.
Windows replaced bad clusters in file 60629
of name \PROGRA~1\MICROS~1\Office14\OART.DLL.
Read failure with status 0xc00000b5 at offset 0x1f556e6000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1f556e6000 for 0x1000 bytes.
Windows replaced bad clusters in file 65493
of name \PROGRA~2\ORIGIN~1\BATTLE~1\Data\cas_03.cas.
Read failure with status 0xc00000b5 at offset 0x20a8753000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x20a8762000 for 0x1000 bytes.
Windows replaced bad clusters in file 75265
of name \PROGRA~2\Steam\STEAMA~1\common\ORCSMU~1\data\scen es\Stream\LIGHTM~2.PAK.
Read failure with status 0xc00000b5 at offset 0x1f816a5000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1f816a9000 for 0x1000 bytes.
Windows replaced bad clusters in file 89898
of name \MSOCache\ALLUSE~1\{90140~4\OutlkLR.cab.
Read failure with status 0xc00000b5 at offset 0x1f8402a000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1f84039000 for 0x1000 bytes.
Read failure with status 0xc00000b5 at offset 0x1f8446a000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1f84470000 for 0x1000 bytes.
Read failure with status 0xc00000b5 at offset 0x1f847a1000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1f847ae000 for 0x1000 bytes.
Windows replaced bad clusters in file 90753
of name \MSOCache\ALLUSE~1\{92787~1\Proof.en\Proof.cab.
Read failure with status 0xc00000b5 at offset 0x1e49050000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1e4905b000 for 0x1000 bytes.
Windows replaced bad clusters in file 91593
of name \MSOCache\ALLUSE~1\{92787~1\Proof.fr\Proof.cab.
Read failure with status 0xc00000b5 at offset 0x534e5000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x534e9000 for 0x1000 bytes.
Windows replaced bad clusters in file 91900
of name \MSOCache\ALLUSE~1\{92572~1\OnoteLR.cab.
Read failure with status 0xc00000b5 at offset 0x1f386a4000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1f386aa000 for 0x1000 bytes.
Windows replaced bad clusters in file 91921
of name \PROGRA~1\COMMON~1\MICROS~1\TRANSLAT\ENES\MSB1ENES .ITS.
Read failure with status 0xc00000b5 at offset 0x1dd9ba3000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1dd9bb2000 for 0x1000 bytes.
Windows replaced bad clusters in file 91990
of name \PROGRA~1\MICROS~1\Office14\PROOF\MSGR3EN.LEX.
Read failure with status 0xc00000b5 at offset 0x1fd0270000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1fd0276000 for 0x1000 bytes.
Read failure with status 0xc00000b5 at offset 0x1fd0407000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1fd0413000 for 0x1000 bytes.
Windows replaced bad clusters in file 92022
of name \MSOCache\ALLUSE~1\{9AFC7~1\Access.en-us\AccLR.cab.
Read failure with status 0xc00000b5 at offset 0x1e626b8000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1e626ba000 for 0x1000 bytes.
Windows replaced bad clusters in file 92036
of name \PROGRA~1\MICROS~1\TEMPLA~1\1033\ONENOTE\14\STATIO ~1\BLANK.ONE.
Read failure with status 0xc00000b5 at offset 0x1fe4588000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1fe4589000 for 0x1000 bytes.
Windows replaced bad clusters in file 92070
of name \MSOCache\ALLUSE~1\{9877A~1\PubLR.cab.
Read failure with status 0xc00000b5 at offset 0x1fe5147000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1fe514e000 for 0x1000 bytes.
Windows replaced bad clusters in file 92104
of name \PROGRA~1\MICROS~1\TEMPLA~1\1033\Access\NORTHW~1.A CC.
Read failure with status 0xc00000b5 at offset 0x1fe5f17000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1fe5f23000 for 0x1000 bytes.
Read failure with status 0xc00000b5 at offset 0x1fe6094000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1fe60a0000 for 0x1000 bytes.
Windows replaced bad clusters in file 92142
of name \PROGRA~1\MICROS~1\Office14\1033\MSACCE~1.HXS.
Read failure with status 0xc00000b5 at offset 0x1fe63a7000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1fe63ac000 for 0x1000 bytes.
Windows replaced bad clusters in file 92147
of name \PROGRA~1\MICROS~1\Office14\1033\MSACCESS.HXS.
Read failure with status 0xc00000b5 at offset 0x1fe7188000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x1fe7195000 for 0x1000 bytes.
Windows replaced bad clusters in file 92166
of name \PROGRA~2\COMMON~1\MICROS~1\OFFICE14\1033\MSOINT~2 .IDX.
Read failure with status 0xc00000b5 at offset 0x75026f000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x750271000 for 0x1000 bytes.
Windows replaced bad clusters in file 92211
of name \MSOCache\ALLUSE~1\{94297~1\SIWW.cab.
Read failure with status 0xc00000b5 at offset 0x74b11f000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x74b121000 for 0x1000 bytes.
Windows replaced bad clusters in file 92663
of name \PROGRA~1\MICROS~1\TEMPLA~1\1033\BLACKT~2.DOT.
Read failure with status 0xc00000b5 at offset 0x65a21000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x65a26000 for 0x1000 bytes.
Windows replaced bad clusters in file 95082
of name \Windows\winsxs\X86_MI~2.405\msvcr80.dll.
Read failure with status 0xc00000b5 at offset 0x20279cd000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0x20279d4000 for 0x1000 bytes.
Windows replaced bad clusters in file 95376
of name \PROGRA~2\MICROS~2\AS OLEDB\10\MSMDLO~1.DLL.
554736 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
31238847 free clusters processed. Free space verification is complete.
Adding 29 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

249954303 KB total disk space.
124243364 KB in 173381 files.
93096 KB in 29008 indexes.
116 KB in bad sectors.
662343 KB in use by the system.
65536 KB occupied by the log file.
124955384 KB available on disk.

4096 bytes in each allocation unit.
62488575 total allocation units on disk.
31238846 allocation units available on disk.

Internal Info:
00 77 08 00 a0 16 03 00 2e d1 05 00 00 00 00 00 .w..............
8f 01 00 00 2c 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 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
 
Run CrystalDiskInfo and post us a screenshot of the SMART screen. Bad clusters in Windows and bad NAND cells are two completely different things. Everything from BSODs to viruses can cause windows errors. Even if it were a hardware error SSDs have reserve capacity to remap bad cells. If it continues to happen, you should replace the drive.
 
Get yourself a free imgur.com or flicker account, and then post a link to there.
 
Based on what I can see your SSD looks fine. How old is that drive, it is showing power on counts over 2200.
 
About a year to 18 months... I don't reboot that much. is coming out of sleep mode counting?
 
It varies drive to drive, but yes it is most likely sleep/wake cycles counted in there. Another issue, you are at formware 0002, which is 3 firmware updates ago. You should download and install the latest SSD firmware update from http://www.crucial.com/support/firmware.aspx which fixes a number or stability problems and performance issues known with the version you are running.
 
Thanks for that. I haven't updated since the 002 firmware because there were several problems with firmware updates when Crucial first came out with this drive. I'll look into that.

Also, how can you tell from the SMART screen if the drive is "ok" or not?
 
Well, you don't have any items which are beyond their stated thresholds, and some error states which don't have a single tick, even if that would be ok.
 
Back
Top