Hard Disk Monitoring

I consistently get 2-4 CRC errors on every boot. They show up in the HD log and also in that windows 10 Event Log. changed sata cables twice, also got a lock in cable and also tried several different ports.

Ran win10 surface scan: chkdsk c: /r /scan

no errors showed up during or after the scan. To make sure, I closed HD, then brought it back up: no crc errors in loG. Checked Event Log: no errors. Issued a win10 reboot and sure enough saw 2 errors. Time of the errors was during the boot process.

This is a small cube size desk top system, core 2 quad but has a small laptop drive that is practically unused. It came from a netbook when I replaced the drive with an SSD shortly after got it. HD shows it to be in excellent condition, just CRC errors, up to 302 of them now.

I recently moved the system into the garage, it does get cool at night, like 40f, and there are 3 other systems next to it. I dont recall having these problems before I moved it. I also replaced the video board from a gtx 650 to a gtx 670. The CPU is a low power (65 Watt) Q9550S

any ideas?

Thanks for looking!

Without knowing the actual situation, hard to say anything for sure, but a very common cause of such problems (if we are sure that cables, connections are really perfect) is an incompatibility between the drive and the current disk controller (motherboard), more precisely its driver.

This happens very often with some SSDs if the onboard controller (usually Intel chipset controller) does not have proper drivers installed and it works as Standard AHCI Controller driver (you may verify on the Information page in Hard Disk Sentinel).
Then on every reboot (or complete power cycle) yes, the error counter increases.

I suggest to please check and install the proper driver from the Support -> Driver Zone ( www.hdsentinel.com/driverzone.php ) or from the website of the manufacturer, usually it fixes the problem: the error counter does not increase further.
Then existing errors remain (as the device counts all problems in the lifetime) but the counter can be easily cleared by Hard Disk Sentinel to ignore these and be notified about possible new problems (if there will be).
The procedure described at https://www.hdsentinel.com/hard_disk_ca ... _error.php

If you use Report menu -> Send test report to developer option, I can check the actual situation, verify the driver used and assist about the best possible driver version (which is not always the latest).


> Ran win10 surface scan: chkdsk c: /r /scan

The idea to perform test is good to confirm the situation: to reveal possible further issues - or confirm if the status is stable.
However, using chkdsk is a very bad solution for this purpose.

Even if this may sounds surprising, chkdsk does not check/verify/repair the hard disk itself, but verifies (and repairs) the logical drive, the partition itself. The problems found and "fixed" by chkdsk are in most cases different than the actual hard disk problems:
Windows may find, report and "fix" problems on a perfect hard disk - and may not find anything on an almost failed hard disk.
(For example see https://www.hdsentinel.com/hard_disk_ca ... ectors.php page, which shows a such situation, illustrates how chkdsk can't really "fix" bad sectors).

Chkdsk only scans the current partition, but does not care (for example) the current operation temperature, the possible slowness of sectors, the retry count - which can be all signs of possible problems, degradations.
This is why it is recommended to use the tests in Hard Disk Sentinel instead as described at:

https://www.hdsentinel.com/faq.php#tests

which shows the most important tests in such suspicious situation. These tests designed exactly to verify if the disk is really working correctly - or reveal / fix any possible problems.

Pretty sure I found the problem: System is under powered for the type of video board. GTX670 requires 550 watt supply as it takes 170watts at full load. BOINC runs 24/7 and the board is usually at full load the entire time. I put in a GTX 650 TI (110 watts) with 1GB ram and the problem went away. I tried a 650 TI with 2GB memory (130 watts) and the problem returned but not as bad as the GTX670. Probably need to use a more recent video board the like 750 TI that is only 60 watts. I suspect the large current draw when powered up and possibly a delay in starting the hard drive might mitigate that.

Thanks for your message and the information, yes, power issues can frequently cause such troubles....
Your experiences may help other users having same / similar issue.