About two weeks ago, I installed Win8 and have had almost daily blue screens, system freezes or other errors. The CPU, motherboard, power supply and case are less than six months old.
Twice now, three days apart, my system froze and when rebooting could not see the Intel 520 SSD (the boot drive.) The first time, I immediately removed the drive from the system and attached it to my notebook via a SATA/USB adapter. It was immediately recognized, and I copied everything from it as an additional backup. I replaced the drive in my desktop system and it booted right up like nothing had happened.
Today when it occurred, I simply pulled the power plug, had dinner before reapplying power and it booted right up. Not even a data gathering error message from Windows.
I have done several secure erases of the drive -- before changing from MBR to GPT to MBR back to GPT and now again on MBR. (Long story involving a retiree with waaay too much time on his hands.)
Does anything in the SMART data seem amiss?
When I had the SSD out, I traded power connectors with the HDD to see if the cable/connector were the culprit. I meant to trade out the SATA cable, but forgot. It is a new cable, one that came with the motherboard.
How can I be sure my Intel 520 SSD is not the cause? It could be symptom of some other problem, too, no? If so, how does one definitively track it down?
I don't have a spare processor, motherboard or power supply to swap.
It seems suspicious that all of this started when I installed Win8, but could an OS cause a drive to (fleetingly) not be recognized by the motherboard? I could see Win8 causing all the blue screens, freezes and other weirdness, but the disappearing SSD?
I had blue screens and freezes before I flashed a beta, Win8-aware UEFI(BIOS) and after I reverted to the stable (non-beta) non-Win8-aware UEFI(BIOS). (Confusing because Gigabyte calls it BIOS, but it's actually UEFI.)
Twice now, three days apart, my system froze and when rebooting could not see the Intel 520 SSD (the boot drive.) The first time, I immediately removed the drive from the system and attached it to my notebook via a SATA/USB adapter. It was immediately recognized, and I copied everything from it as an additional backup. I replaced the drive in my desktop system and it booted right up like nothing had happened.
Today when it occurred, I simply pulled the power plug, had dinner before reapplying power and it booted right up. Not even a data gathering error message from Windows.
I have done several secure erases of the drive -- before changing from MBR to GPT to MBR back to GPT and now again on MBR. (Long story involving a retiree with waaay too much time on his hands.)
Does anything in the SMART data seem amiss?
When I had the SSD out, I traded power connectors with the HDD to see if the cable/connector were the culprit. I meant to trade out the SATA cable, but forgot. It is a new cable, one that came with the motherboard.
How can I be sure my Intel 520 SSD is not the cause? It could be symptom of some other problem, too, no? If so, how does one definitively track it down?
I don't have a spare processor, motherboard or power supply to swap.
It seems suspicious that all of this started when I installed Win8, but could an OS cause a drive to (fleetingly) not be recognized by the motherboard? I could see Win8 causing all the blue screens, freezes and other weirdness, but the disappearing SSD?
I had blue screens and freezes before I flashed a beta, Win8-aware UEFI(BIOS) and after I reverted to the stable (non-beta) non-Win8-aware UEFI(BIOS). (Confusing because Gigabyte calls it BIOS, but it's actually UEFI.)
