Starting on 2 September (Day 1) and continuing today 3 September (Day 2) I have been experiencing Disk errors / warnings. This afternoon there were also a Blue Screen of Death (BSOD) and a second reboot that may have been a BSOD within a 20 minute interval. The Disk errors and the BSOD may be unrelated.
On Day 2 I temporarily enabled the Excel Solver add-on and installed three new software packages:
Ubit classic menus for Excel, Word, PowerPoint
Ubit classic menus for Outlook
ASAP Utilities for Excel
I experienced one BSOD and one reboot (possibly another BSOD) shortly after those installations. On the BSOD there was a message CLOCK_WATCHDOG_TIMEOUT message. I don't know about the second event – it happened while I was away from the computer – I just saw it had rebooted. I disabled the Solver add-on in Excel, but the three software packages are still installed. The system has been operating fine for almost five hours since those two events.
The BSOD and reboot sent me to the Event Log looking for issues. I noticed that on Day 1 things started with an Event ID 129, iaStorA with the message:
Reset to device, \Device\RaidPort3, was issued.
BUT NOTE: There is no RAID configured on this system.
Then a couple minutes later a continual string of Disk errors started, all associated with Drive 3, an external Seagate Backup Plus 2TB drive that has three volumes. All are Event ID 154, Disk. A couple expanded messages below as samples:
The IO operation at logical block address 0x0 for Disk 3 (PDO name: \Device\00000058) failed due to a hardware error.
The IO operation at logical block address 0x0 for Disk 3 (PDO name: \Device\00000056) failed due to a hardware error.
Interspersed are Warnings Event ID 51, Disk; sample messages:
An error was detected on device \Device\Harddisk3\DR9 during a paging operation.
Windows 10 chkdsk /F finds no problems.
Seagate SeaTools for Windows quick test finds no problems.
MY QUESTION: It seems the Event Viewer sees disk problems yet chkdsk and seatools find nothing. Any suggestions for what to do next to determine whether the drive is truly having a problem?