Solved!
Go to SolutionD
dnsroberts
4 Posts
0
8047
December 20th, 2018 11:00
Diagnostics says hard drive failed, suspect something else
I have an Inspiron 5676 Gaming desktop with Win10, just out of warranty. Immediately after purchase I replaced the boot drive with an SSD and added memory and a large data drive, as I use it for photography/editing. I am not worried about data loss, as it is all backed up to the cloud. Yesterday it began having trouble when opening programs, things were very slow and failed to open. There were no unusual processes running on task manager. I was unable to open file explorer or any diagnostics apps. I rebooted several times, and it was VERY slow to reboot and when the desktop came up, it wasn't fully functional. I booted into diagnostics using F12, and the diagnostics returned error 2000-0145 against my SSD. I still had the original boot drive (it has just been sitting disconnected in the case), so I moved the cable from the SSD to it and rebooted. Same behavior - the windows desktop comes up, but I can't run anything, and it is all extremely slow. I ran diagnostics again and got the same error on this hard drive. I replaced the cable, in case it was a bad cable. Same error returned. Because two different hard drives return the same error, I don't think this is actually the problem. But I am not sure what to investigate next. The diagnostics stops when it finds this error. Any advice on what to look at next?
7528
0
Posted December 20th, 2018 11:00
I would accept that the SSD failed if the original hard drive was not also returning the same error and having the same boot up behavior.
7539
0
Posted December 20th, 2018 11:00
Improperly installed and optimized SSD's can be written to death in as little as a few hours. This is also why cloning a hdd to ssd instead of clean install is a BAD IDEA.
SSD has failed because it was written to death.
The items below are not comprehensive or inclusive
Disabling background disk defragmentationKey Name:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction\ Name: Enable Type: REG_SZ Value: N
Disable Background auto-layout:
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OptimalLayout Value Name: EnableAutoLayout Type: REG_DWORD Value: 0Disable update of filesystem’s “last access timestamps”
“Key Name: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem Name: NtfsDisableLastAccessUpdate Type: REG_DWORD Value: 1Disable Prefetch and Superfetch
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters
Name: EnablePrefetcher Type: REG_DWORD Value: 0Disable Hibernation
Go to the system settings and disable the swap file (pagefile)
and disable the system restore service
move the temporary and log files directories to non-SSD media7523
0
Posted December 20th, 2018 12:00
One thing i would try if it was possible for you to do so...
Unetbootin (or choice of flashing software) a live usb stick of Ubuntu and run badblocks
So once booted open a terminal
type lsblk and hit enter = lists all block devices (disks for the most part)
you will see /dev/sdb or sdc (/dev/sda may be the usb stick)
then run badblocks -svn /dev/sdb (this will check every single block on the hdd or ssd for read/write errors)
IF you dont care about any data on the drives at all then run badblocks -svw "device" (comprehensive test that also wipes drive)
Keep in mind depending on speed/size of a drive this may take a looooong time
7520
0
Posted December 20th, 2018 12:00
Try the following page and the link it points to. Especially look at speedstep's great post about errors.
I am not a Dell employee...I am forum volunteer
Serious work on an E5430 and constantly building and working on an i5-6500 Desktop
7502
0
Posted December 20th, 2018 13:00
Post back and let us know what happens...
7504
0
Posted December 20th, 2018 13:00
Ok, that sounds like a good next step. It might explain why it gave me the same error for the other drive. I will try that tonight when I get home from work. Thanks!
7484
0
Posted December 20th, 2018 18:00
Thank you, that did the trick. Now it has evaluated the original HD to have no issues, and Windows is booting up relatively quickly and functional again. Now I can get on with recovery.
Also, thanks to the poster above with tips for correct setup for the SSD boot drive, if I decide to replace the SSD I will take those into consideration.
7446
0
Posted December 21st, 2018 10:00
:Yes: :Yes:
Now image your hard drive on external media with something like Macrium (free). And then make sure all Windows updates are successfully installed. You probably have a bunch of them since the drive hasn't been used for a while.
You might even be offered the fall update, build 1809, of Win 10 via Windows Update, but you need to make sure you have the latest Intel Graphics and Intel Audio drivers for your system installed before allowing that update.
RoHe
12 Elder
•
45230 Posts
•
172625 Points
7511
1
Posted December 20th, 2018 13:00
Do we assume the old HDD was still connected to the power supply?
Since you moved the SATA data cable from the SSD back to the old HDD, you might have to clear BIOS because it might still be looking for the SSD on that SATA port, but not finding it.
What happens now..?