Question: Hi all! A while back, I installed an update to CrystalDiskInfo after I had placed a new hard disk into my system. After the software was updated, CrystalDiskInfo quit recognizing my C drive, but would only recognize my new E drive. Piriform’s Speccy recognizes both and says that both drives are in good health, but I tried a different software that I could run in the background (HDD Health by PanteraSoft) and it, too, fails to recognize my C drive. Speccy continues to recognize it as usual, however.
I’ve tried rescanning in both CrystalDiskInfo and HDD Health but neither of them want to recognize the C drive. It’s not a huge deal for me, as I do run regular backups on an external hard drive, but it frustrates me as I do like to know the health of my drives. I’m paranoid right now, as I’m having an issue where I’m getting Event 55 errors which, I read, has to do with VSS corruption due to hardware changes… that would make sense, since I had to switch between a PS2-based keyboard and a new USB keyboard.
I like Speccy but I’ve begun to wonder if it’s reading things correctly; I suspect it’s not good that two separate HDD monitoring programs fail to recognize my C drive.
Does anyone know why this is doing this and if there’s anything I can do to fix it? I’m using Windows 7 Home Premium and can provide any system info if needed. I’d really appreciate any suggestions. Thanks!
PS: I took screenshots of the programs’ different displays for reference, here. If any further screenshots are needed, please let me know.
Answer:The SMART data look OK.
GSmartControl has an Error Log tab. That should hopefully tell you if a particular sector triggered an error.
Did you try selecting Function -> Advanced Feature -> Advanced Disk Search in CrystalDiskInfo?