But today when I was continuing my research into what the problem is that causes these BSODs, I had read that CrystalDiskInfo was recommended along with DLGDIAG. Yeah, I used to just rely on DLGDIAG from Western Digital since I buy only their drives. But you would assume that the brand specific tools MIGHT have more information as they likely can probe specific addresses in their own, known, controller for health information and not just rely on the industry standard SMART ID port exports. I don't have any experience with brand specific diagnostic tools since I rely on SMART info solely. 'Logic is the cement of our civilization with which we ascend from chaos using reason as our guide.' - T'Plana-hath Winders 10 OS? 'What a piece of junk!' - L. They're going to go with their own product of course. The support forum was, of course, on the Western Digital's server and they said to go with DLGDIAG. So, even after running DLGDIAG and Win7's disk checker, CrystalDiskInfo is still telling me to caution the use of this drive.Īny opinions of the utilities I used and which to actually believe to be true? I googled the difference between CDI and DLGDIAG and found that someone else ran into the same thing. I have ordered a new WD drive this morning anyway since I would rather err on the side of caution. I cannot absolutely verify the age of the drive. I would venture to estimate that the drive is actually greater than 7 years since I was using it before moving out of the old house and into our current one. The drive in question is for sure greater than 5 years old (had it when we bought this house and moved in in Oct 2012). Both tests are giving a green check mark. I have run both the quick test and extended test with DLGDIAG. attribute 'Current Pending Sector Count' is greater than 0 and that the drive is under caution.

I'm almost certain that I have narrowed my BSOD (blue screen of death) problem to a failing WD HDD.ĬrystalDiskInfo tells be that the S.M.A.R.T.

Crystaldiskinfo test