Oh yes, it is me again. More problems..... So aside from my usual issues (cold boot problems, minor graphical issues in GTA V along with slow downs in the same game, which to be fair are not uncommon) I've had some issues with Windows 8.1. Some folders like the Steam screenshot folder have been slow to load, thumbnails not appearing quickly in general. The start button stopped working last night, but most issues have been easy to ignore or a reboot fixed them. Last night I used the "SHOW ON DISK" button within the Steam screenshot uploader/viewer to open the aforementioned slow to load Steam screenshot folder. Instead of the usual slow loading I got this error: Even now after a reboot I cannot access that folder, either through Steam or going direct to the directory. I then checked Event Log and there are a lot of these 153 errors: No idea if it is related, but there are a lot of them. So obviously I suspect the SSD as faulty or some how to blame. There is no firmware update that I could find for it, I'm running it in ACHI with the SSD Life thinks it is fine: Windows is up to date, it is running in UEFI mode. I'm using the latest drivers off the Asus website with updated Intel chipset drivers off the Intel website. The latest BIOS and so forth. I'm using the V13.1.0.1058 version of the Intel Rapid Storage Technology Driver as I've read (possibly wrongly) that this is the latest version of the driver with native AHCI support.The memory is fine as far as I can tell. I've also run sfc /scannow which showed the following error: The listed log is huge, so I'm not certain exactly what it couldn't fix. CHKDSK /R Results: Code: Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. Stage 1: Examining basic file system structure ... Read failure with status 0xc0000185 at offset 0xc52b7400 for 0x400 bytes. File record segment 84701 is unreadable. Read failure with status 0xc0000185 at offset 0x640fcf000 for 0x400 bytes. File record segment 103668 is unreadable. 323840 file records processed. File verification completed. 3071 large file records processed. Read failure with status 0xc0000185 at offset 0xc52b7400 for 0x400 bytes. 2 bad file records processed. Read failure with status 0xc0000185 at offset 0x640fcf000 for 0x400 bytes. Stage 2: Examining file name linkage ... Index entry PresentationFramework.Aero2.dll of index $I30 in file 0x383e points to unused file 0x194f4. Deleting index entry PresentationFramework.Aero2.dll in index $I30 of file 14398. Index entry PRESEN~1.DLL of index $I30 in file 0x383e points to unused file 0x194f4. Deleting index entry PRESEN~1.DLL in index $I30 of file 14398. Index entry 68 of index $I30 in file 0x1582b points to unused file 0x14add. Deleting index entry 68 in index $I30 of file 88107. 421880 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. Stage 3: Examining security descriptors ... Cleaning up 859 unused index entries from index $SII of file 0x9. Cleaning up 859 unused index entries from index $SDH of file 0x9. Cleaning up 859 unused security descriptors. Security descriptor verification completed. 49021 data files processed. CHKDSK is verifying Usn Journal... Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... 323824 files processed. File data verification completed. Stage 5: Looking for bad, free clusters ... 68198974 free clusters processed. Free space verification is complete. Adding 2 bad clusters to the Bad Clusters File. Correcting errors in the master file table's (MFT) DATA attribute. 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. No further action is required. 499566591 KB total disk space. 226179188 KB in 267610 files. 185160 KB in 49022 indexes. 8 KB in bad sectors. 406335 KB in use by the system. 65536 KB occupied by the log file. 272795900 KB available on disk. 4096 bytes in each allocation unit. 124891647 total allocation units on disk. 68198975 allocation units available on disk. Internal Info: 00 f1 04 00 47 d3 04 00 90 33 09 00 00 00 00 00 ....G....3...... 9a 01 00 00 20 00 00 00 00 00 00 00 00 00 00 00 .... ........... Windows has finished checking your disk. Please wait while your computer restarts. 2nd CHKDSK /R run: Code: Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. Stage 1: Examining basic file system structure ... 323840 file records processed. File verification completed. 3064 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 421890 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. Stage 3: Examining security descriptors ... Cleaning up 26 unused index entries from index $SII of file 0x9. Cleaning up 26 unused index entries from index $SDH of file 0x9. Cleaning up 26 unused security descriptors. Security descriptor verification completed. 49026 data files processed. CHKDSK is verifying Usn Journal... 2245568 USN bytes processed. Usn Journal verification completed. Stage 4: Looking for bad clusters in user file data ... 323824 files processed. File data verification completed. Stage 5: Looking for bad, free clusters ... 68125766 free clusters processed. Free space verification is complete. Windows has scanned the file system and found no problems. No further action is required. 499566591 KB total disk space. 226469396 KB in 267899 files. 185224 KB in 49027 indexes. 8 KB in bad sectors. 408899 KB in use by the system. 65536 KB occupied by the log file. 272503064 KB available on disk. 4096 bytes in each allocation unit. 124891647 total allocation units on disk. 68125766 allocation units available on disk. Internal Info: 00 f1 04 00 6d d4 04 00 dc 34 09 00 00 00 00 00 ....m....4...... 95 01 00 00 20 00 00 00 00 00 00 00 00 00 00 00 .... ........... Windows has finished checking your disk. Please wait while your computer restarts. Specifications Intel i7 5930K Corsair 16GB DDR4 (4x4GB) Asus X99 Deluxe GTX970 4GB x2 in SLi Samsung MZHPV512HDGL-00000 SSD Coolermaster V850 PSU (Seasonic OEM) Asus ROG Swift PG278Q Running 1440p @ 120Hz Any suggestions would be welcome, especially from those who have had issues like this or are more technically minded when it comes to storage problems. Thanks, Mark
Are you running the latest Intel AHCI/RAID Driver either the one on the ASUS site (13.1.0.1058), or the newer version direct from Intel (13.6.0.1002)
The ones on the Asus website (13.1.0.1058), simply because I read in some RST mega thread that they were the latest ones with Native X99 support for AHCI. That could be rubbish, but I was having enough issues at the time so just went with the ones that Asus would have "approved" of had I needed to contact them. Just finished running a bootime CHKDSK /R scan, results added to the OP. Seems it found a few bad sectors. I can however now access and backup the previously unreachable Steam Screenshot folder. I've done a second run, again at boot with no issues found.
That CHKDSK don't look good, if that was my system I would install the Samsung Magician software to check for obvious problems (firmware) and keep a very close eye on the Windows event log to see if Event ID 153 reoccurs, if it does then it point to a problem with the storage sub system.
Indeed, problem is the SSD doesn't support Samsung Magician. Although I will install it as you suggest and see what it does allow access to.
I believe adrock had the same issue with the self-same model of SSD. Might be worth dropping him a PM? I'm now paranoid that my 256Gb SM951 will go the same way...
Thanks jinq-sea. Shall do that. Just installed Samsung Magician software as Corky42 suggested and while next to nothing is supported it does have SMART data and there is a attribute marked Fail: Not quite sure if I can trust it though. Both Crystal and SSDLife don't report the same issue and the model isn't natively supported by the Samsung Magician software, so it could be a false reading. That being said I think it is a bit more likely for the Samsung software, supported or not, is going to be using the same IDs for error counts and thresholds. Upon doing a bit of research there is no real standard way of converting the RAW values, seems to be manufacturer specific, so maybe I should trust the Samsung software...
Yup, exactly the same issues i had. same errors in the system event log, and same issue with the unrecovered error count in the SMART data. I'm running on the X99-S with a 5820k, so pretty similar. I kept trying, eventually had disk check showing bad sectors, and it generally got worse and worse until the machine was unusable. Sent the drive back to OcUK for RMA, pointed out the error count in the smart data (mine was tenfold what yours is but it's still bad) and they sent out the replacement same day. no issues with this one so far, none of the same errors and the uncorrectable error count is a calm-inducing 0. I'd suggest you RMA.
I wonder how long mine will last? When I bought mine, I could 'only' get a 256Gb version, so it may not exhibit the same problems...?
Exactly (well sort of lol) what I wanted to hear. Many thanks for the reply and confirmation, shall get an RMA sorted soon. If you don't have any issues I wouldn't worry about it. SSDs are one of those bits of hardware that when it works, they'll almost certainly work for a long time without issue. A lot like any form of flash memory really. Issues like this generally present themselves very quickly, mine is about a month old.
This is true - I was more concerned about the controller than the flash itself I guess, but we'll see! I've had it about three months now, so I'd hope that I am safe (at least in the short term).
