Hard Disk Monitoring

I recently purchased a new laptop with a 24GB SSD and a 500 GB Hitachi system drive. Several times, ususally shortly after coming out of sleep mode I get the following error regarding the Hitachi drive:

Failure Predicted - Attribute: 3 Spin Up Time, Time needed by spindle to spin-up to full RPM. Indicate problem with motor or bearings.
Failure Predicted - Attribute: 5 Reallocated Sectors Count, Count of sectors moved to the spare area. Indicate problem with the disk surface or the read/write heads.
Failure Predicted - Attribute: 7 Seek Error Rate, Rate of positioning errors of the read/write heads. Indicate problem with servo, head. High temperature can also cause this problem.
Failure Predicted - Attribute: 10 Spin Retry Count, Retry count of spin start attempts. Indicate problem with motor, bearings or power supply.
Replace hard disk immediately.

It is recommended to backup immediately to prevent data loss.

If I re-run the test the response is always that the drive is 100% and has no surface errors or spin-up problems detected. Likewise there is no indication of errors in the history log for the drive. How do I confirm whether this a real problem with this new drive or is HD Sentinel somehow being confused by the process Asus uses to rapidly restart Windows from the SSD after I have put the computer into sleep mode?

Thanks!

I'm almost sure the issue is related to a driver problem. After waking up from sleep mode, the disk controller (where the drives are connected) provides an incorrect status information for Hard Disk Sentinel and this may cause the confusion.

I do not know the actual chipset/disk controller/driver information and the version of Hard Disk Sentinel you have. New and new protections against such issues are constantly added, so if you have an older version, please consider upgrading to latest 4.10 or even to latest beta (4.10.5), they are both available from the Download page ( http://www.hdsentinel.com/download.php )

If the problem with these new versions still exist, the best would be if you can use Report -> Send test report to developer option two times:
- when you see this warning
- after a re-test, when the 100% status is displayed

This way it will be possible to examine the current situation, the detected (incrorrect) information (and driver version) and it will be possible to prevent the wrong details displayed. Excuse me for that.

Thanks for the response. I did notice that I was using an older version and upgraded last night. I have not seen the issue since but I will let you know.

The upgrade also fixed this type of problem on my end.