That would mean replacing most of the drives...haha. Unfortunately not feasible at the minute. I am running chkdsk on the failing ones now.
- - - Updated - - -
Okay here are results from HD Sentinel. Chkdks on disks with bad sectors still going but here is the first one.
Attachment 264722
Attachment 264721
The most important result is the Sea Tools long generic status as it's pass or fail.
It is the result that is similar to what computer manufacturers use for warranty replacement.
The SMART results are used to predict failure.
We see many drives with unremarkable SMART that have failed.
Back up data on any Sea Tools fail.
And whenever possible backup data on drives with increasing reallocation parameters.
Do you really feel it's necessary to replace drives that have any errors? Can't drives have errors and continue to function with bad blocks remapped?
What would be your threshold for drive replacement?
The terminal event is unpredictable.
Often you can continue using drives.
Decreased performance can be tolerated.
Unfortunately it typically costs a lot more to pay for data recovery and replace the drive.
Any drive can be used as long as the data is backed up.
(The exceptions are the drives that cause computer instability: unexpected shutdowns and restarts)
Oh no! I got another BSOD during another long generic scan of the drive WDC WD6002FRYZ-01WD5B0 serial K1HKDL5B. Seatools previously reported this drive with a long generic fail but HD sentinel reports it as "Perfect" and HD Tune shows no errors.
But HD tune suggests that it's communication errors could be caused by a damaged cable....
Ran another chkdsk /b /v on the C drive and no errors on it....
Once all of the drive tests have been completed plan to evaluate the computer with no attached drives.
For any BSOD run V2 > upload results into the thread
And post a share link for C:\windows\memory.dmp if the file size is < 1.5 GB
HD Tune tests SMART, Benchmark, and Surface.
It does not test long generic.
HD Sentinel and Crystal Disk do not test long generic.
So they can report any result when a drive has failed.
It had also locked up again last night. Not a BSOD. Just a blank screen and unresponsive. Latest V2 logs and memory dump link attached.
Attachment 264818
MEMORY.DMP - Google Drive
Edited for Google Drive.
Last edited by slickochet; 28 Jan 2020 at 03:36.
After the edit entry it still displayed we transfer.
Please use one drive, drop box, or google drive for share links.
Code:LastWriteTime Size (MB) FullName ------------- --------- -------- 28/01/2020 07:54:39 1028.18 C:\WINDOWS\MEMORY.DMP
Code:=============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe08620c0f0f0 Section @ ffffe08620c0f240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000003 CPU Id : fb 06 00 00 00 08 04 03 - bd e3 00 00 ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ ffffe08620c0f240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe08620c0f138 Section @ ffffe08620c0f2c0 Offset : 664 Length : 272 Flags : 0x00000000 Severity : Fatal Error : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 3 Bank 0) Status : 0xb200004000000800
Not sure how to debug these outputs....is this another CPU error?
Please don't use we transfer.
Most don't use the pay version.
Please post share links using one drive, drop box, or google drive.
The latest BSOD were WHEA 0x124.
Tests will be done after the drive testing has been completed.
Quote