OS drive suddenly uninitialized

[Virgule]

Hello,

 

I ran a diagnostic of a boot error on a client's computer. There was an error message after the BIOS splash screen stating that no boot drive was connected.

 

Here are the specs of the PC :

 

Asrock Extreme 3 970 r2.0

FX-8350

Cooler Master Hyper T4

3x4GB DDR3

WD Blue SSD 250GB (OS)

WD Blue 1TB HDD 

...

 

Both drives showed up in the BIOS, RAM was all detected, CPU was detected fine. Computer was running for months before this problem arose.

I first tried to change the SATA mode from IDE to AHCI and to RAID in case Windows was installed with a specific SATA mode set and a crash reset some BIOS settings. I also tried different SATA ports and cables ; the drives were still detected but still no boot drive detected. I cleared CMOS, no help.

 

I ended up having to take out the SSD and connect through a USB enclosure to a separate PC. I was not being detected so I opened Drive Management and it showed up as not being initialized. I reinitialized the SSD and had to create a new partition, reinstalled Windows and apps (on a separate new SSD in case this one was problematic). 

 

I was wondering what could cause such a problem. A drive on which OS is installed and running stable for months suddenly being uninitialized. Any thoughts ?

 

Regards

[Virgule]

bump

[SSD Sean]

Simple. File system corruption or temporary drive failure.

 

The cause? Could be a lot of things. Media failure, something glitches in firmware, some improperly coded software, power issues, etc.

[Virgule]

2 hours ago, SSD Sean said:

Simple. File system corruption or temporary drive failure.

 

The cause? Could be a lot of things. Media failure, something glitches in firmware, some improperly coded software, power issues, etc.

So I guess it wasn't a bad idea to take this opportunity to change the SSD, as I did ?

[SSD Sean]

10 hours ago, Virgule said:

So I guess it wasn't a bad idea to take this opportunity to change the SSD, as I did ?

Yeah, I’d say it was a smart move. Just had the same thing happen to one of my friends the other day on a HDD due to sector issues.  And last year I had a cheap ADATA SSD do the same thing.