The ST3000DM001-1CH166 drive tests displayed:
long generic test: fail
surface test: 5 bad blocks
Check the warranty status.
Long generic / long DST failures are used by HP and others as a threshold for warranty replacement.
Please backup any important data.
Drives with failed long generic should be replaced.
However once data is backed up failed drives can be used until the terminal event (there may be slow read / write, hangs / freezes, unexpected shutdowns and restarts, BSOD, etc.)
Current settings are:
AutoReboot=TRUE
DebugInfoType=3
It can be easy to miss BSOD with automatic reboot is checked.
It's best to uncheck autoreboot when troubleshooting / monitoring
Change debug type to 7
These can run using administrative command prompt:
1) wmic recoveros set autoreboot = false
2) wmic recoveros set DebugInfoType = 7
3) wmic recoveros get autoreboot
4) wmic recoveros get DebugInfoType
5) wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
6) wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
The logs displayed BSOD on:
1/16
4/18 > 4/24
5/18 > 5/23
5/31
There were no BSOD for approximately 7 days 5/23 > 5/31 and 24 days 4/4 > 5/18.
Was the problematic drive always or intermittently connected?
If possible, leave the drive unattached for at least 10 days while monitoring for BSOD.
Also if there is another PC you can connect the problematic drive and monitor for BSOD.
Monitor using: reliability monitor:
Reliability Monitor is the Best Windows Troubleshooting Tool You Aren’t Using
