AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() My keyboard was rescheduled for Tuesday as well, but lo and behold, it got here today, Saturday. Ryzen users ran into this problem trying to install Windows 7. Windows 7 doesn't have any drivers for USB 3.0 in any installation media unless you add the driver to the install files before installing. Mine was ordered early this week for delivery on Thursday, but won't be delivered until Tuesday after Christmas. I wonder if lots of people ordered new keyboards for Christmas. :(Įveryone have a very Merry Christmas and a Happy New Year! :) It's delivery has been rescheduled for the day after Christmas. It was supposed to get here yesterday (Friday 12/22) but didn't. Now, if only I could get my new replacement keyboard. Oh, and CrystalDiskInfo (for topic purposes) is reporting both drives as good and that my new drive is running cooler than my data drive. I now have all the updates from Micro$oft installed except for a few stragglers that showed up yesterday afternoon. A few posters had mentioned that when they hit the problem they unplugged their external optical drive from USB 3.0 and plugged it into USB 2.0. I was on a help forum where others were having the same problem. I found my external USB floppy drive and a disk I thought the drivers were on, but no such luck. I searched and searched and could not find the drivers. I remember having to put drivers on a floppy disk a long time ago. The installation wanted me to "install a driver". ![]() Good thing I have a laptop to get to the Internet. When it went looking for the HDD, that's when things went hay wacky. The file load went ok read from installation DVD. I only had 1 little hiccup when trying to install Win 7 Pro 64bit. I just wanted to find out what others think of or experienced these utilities. The past week or so now they're more frequent, every 2 or 3 days.Īnyway, thanks for the reply. They weren't real frequent, about once every 10 to 15 days. :( June 2016 I quit running SETI on this PC because of the BSODs. Re-installing is now in my immediate future. So I have ordered a new drive from Newegg and it will be here on Wednesday. I ran them both and CDI still reports the pending count as greater than 0. I also had read that DLGDIAG and Window's own Error Checking utility should fix it. That was when I discovered the caution and the cause was the pending sector count. 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.
0 Comments
Read More
Leave a Reply. |