I have attached both Health reports from SSD drives.
However, when I hit Health tab on HDDs, I get nothing at all.
Edit: Downloaded the Trial version and that seems to work better - so will use this going forward.
I've noticed that SSD 2 (D:) and HDD 2 (I:) both have issues - but HDD 2 shouldn't be causing my crashes as nothing on it that the OS would load or even look at - it's all media files.
I tried SeaTools under Windows again on a whim - seems it came through this time.
Screenshot Attached.
Will do benchmarks shortly.
Do you have any early thoughts or good/bad news for me?
So far, it looks like my only saving grace is that SSD 2 isn't anywhere near full but it concerns me that it's having issues - it's only 3 years old, same as the rest of my PC hardware, except GPU (which is 2 years old).
Have finished benchmarks as well.
That is unfortunately incorrect, all partitions from a HDD are optimized by Windows for example with a defragmentation in the background. If no defragmentation, then still the HDD is being optimized by Windows.but HDD 2 shouldn't be causing my crashes as nothing on it that the OS would load or even look at
I'll wait for the error scan in HDtune before saying anything about the results :)
What I've done is disable background defrag, disk scans etc. In the case of HDD 2, I also disabled shadow copies.
It's all a mystery though - it only crashes after I login but sometimes it does it, sometimes not. I'd almost think it was an errant driver, but not a core system driver, but a user level driver or an app that loads, loads a driver and that causes it - but I just don't know.
But how would a ropey HDD and/or SSD cause another SSD on a different channel to just 'disappear'?
What I mean is that sometimes Windows would act as if SSD 1 had been unplugged. Windows would either stop working entirely, forcing a hard reboot or would BSOD. Upon hard reboot, SSD 1 wouldn't show in the BIOS, it took another cold reboot to make it reappear. It hasn't done it for a very long time though, so I assume the problem has gone away or I fixed it somehow or has turned into something else. In any case, I still need to know why it is crashing now :)
Finally - we have error scans :)
Hi Axe0,
I updated the SSD firmware when I first started having issues.
Whilst I couldn't find the release notes on the firmware, I updated it anyway.
I believe it was v5.05 to v5.24 (I hadn't updated firmware on SSDs since purchase).
In addition, which may or may not shed any light on what is going on, you may notice that my Intel drivers are out of date - this is deliberate.
If I update them to latest, I lose my DVD-ROM. The BIOS can see it, but Windows cannot, no matter what I do. Rolling the drivers back, fixes this issue - although I don't use the DVD-ROM much, I still have software on DVD.
Just had a lock-up. Nothing in EventViewer except below.
It was like Drive-C disappeared again. It happened at 15:15 local-time.
The only thing I can spot in EventViewer is this:
Date/Time: 26/08/2016 14:25:31
Source: iaStorA
Event: 129
Message: Reset to device, \Device\RaidPort0, was issued.
It may not be related to the BSODs or it may be related, not sure.
Quote