SSD not being Detected in the BIOS (again)

Madmikegamerxl1

Honorable
Dec 6, 2013
52
0
10,630
Hi,
So, the other month I had an issue where my SSD isn't being detected in the BIOS (the PC would turn on, then I'd see a line flashing where it's clearly reading a device. It'd do that twice, then load into the BIOS). Looking at boot drives, only the HDD was there which doesn't have an OS. So, I tried switching off the Power supply and turning it back on using the switch on it. This worked, but come next day, it happened again. I tried different SATA ports etc., and this didn't work. In the end, I fixed it by changing the SATA power cable.
So, now that you're up to date, we come to the other day.
It happens again, but this time, I didn't need to turn off the PSU by the switch, I simply just pressed the power button to turn it off from the BIOS, then again to turn it back on. It's still very annoying to have to keep doing every day.

What I can tell you though, is that it appears to have only started after the actual power cable into the PSU came loose. I didn't realise it was loose, and tried switching the PC on. Obviously it didn't turn on, but I'm wondering if pressing the power button while the cable wasn't fully in caused some damage.
I re-connected the PSU power cable, pressed the on button, and the SSD wasn't detected. I turned the PC off and back on, and it worked. But this happens daily now. Is it another SATA cable broken? Or was the first SATA cable not broken at all, and there's a bigger issue here?

Thanks,
Mike
 
Solution
Is your SSD plugged into the correct SATA port on the motherboard? Check your motherboard manual, it will probably specify the boot drive (your SSD) be connected to SATA port 0, and there should be a diagram to indicate the SATA port numbers (locations).

In your BIOS, is the SSD designated as the first boot device?

Lutfij

Titan
Moderator
Can you please pass on your full system's specs? List them out as:
CPU:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:

Now about your problem, it's quite possible that the SSD might have ended up being damaged with the frequent power cuts since an improperly plugged in cable can require power to jump the gap so to speak. To add more injury to insult, it's possible that the cable itself isn't being connected properly. Is it possible to have it stick on with some painters tape?
 

Madmikegamerxl1

Honorable
Dec 6, 2013
52
0
10,630

Sure, sorry about that, thought completely passed my mind.
CPU: Intel Core i7-6700k 4.0GHz
Motherboard: ASUS ROG Maximus VIII Hero Motherboard
Ram: Corsair Vengeance 16GB DDR4 RAM 2400MHz
SSD/HDD: Problematic drive: Crucial MX100 512GB SSD - secondary HDD is fine (1TB Hitachi Drive)
GPU: EVGA Geforce GTX 980 Superclocked
PSU: EVGA SuperNova 850w Modular PSU
Chassis: NZXT H440 Black/Red 2015 Edition
OS: Windows 10 Home Edition 64-bit.

And I've noticed recently that it's very much an on-off thing. It won't be detected and will take me to the BIOS, then I press the power button to turn it off and back on, and it works. Then the next boot won't work, the next will, etc.

I could try either unplugging the power cable again and reconnecting, or try the old one and see if it still happens. If so, is it likely the cable (that came with the PSU) has been damaged somehow? Makes me wonder if I'd have noticed the loose cable and hadn't pressed the power button, whether it'd still have the problems.

Thanks for the reply
 
Is your SSD plugged into the correct SATA port on the motherboard? Check your motherboard manual, it will probably specify the boot drive (your SSD) be connected to SATA port 0, and there should be a diagram to indicate the SATA port numbers (locations).

In your BIOS, is the SSD designated as the first boot device?
 
Solution

Madmikegamerxl1

Honorable
Dec 6, 2013
52
0
10,630


Hey, thanks for the reply!
I set the SSD as the first boot drive in the BIOS, and since haven't replicated the issue (I've only tried about 4 boots). I'll give you another update after 24 hours. (The last time it happened, it was every 24 hours the drive just stopped being detected).

As for the port numbers, I actually never knew it mattered all that much. I did notice in the BIOS that it said "P6: Crucial MX100", and the HDD said "P3: Hitachi[something]". Whether the P3 and 6 correspond to the SATA ports I have no idea though.

Thanks for the info!
 

Madmikegamerxl1

Honorable
Dec 6, 2013
52
0
10,630


SSD Firmware is up to date, BIOS is not as of yet. I've tried mjslakeridge's suggestion and it appears it's done something. Again, I'll give you guys another update tomorrow.

I appreciate the help, it really has left me stumped. Not going to get started on any tree puns today.
 

Madmikegamerxl1

Honorable
Dec 6, 2013
52
0
10,630


Thanks for the clarification. I was thinking that too, I didn't read the manual all that much other than the important bits, but I didn't remember seeing any heads up about it being required.
I booted today and it worked first time. I wonder, how come not having the SSD as the first drive causes it to not be detected at all? When it happened, I'd look at the boot drive options and the order of them, and the SSD simply wouldn't be there at all. Strange.

Thanks!
 
When you first installed Windows to your SSD, was the HDD connected? If so, some of the Boot files may reside on the HDD, which they shouldn't. Always load the OS with only the OS drive connected. Disconnect the sata cable from the HDD and try to boot up. If it does you are fine. If not, you may want to consider re-installing the OS on the SSD with the HDD not connected.

That is the only thing I can think of for it not seeing the SSD when it is not the first boot drive.
 

Madmikegamerxl1

Honorable
Dec 6, 2013
52
0
10,630


Hm, that is interesting. I think the first time I installed it, the HDD wasn't connected, but I believe that was back on the AMD build. I since have replaced all of the hardware, except the HDD and SSD. When I reinstalled Windows after the change, I'm not sure if the HDD was disconnected. I'll give that test a go tomorrow and see how that goes, thanks for the info!
 

Madmikegamerxl1

Honorable
Dec 6, 2013
52
0
10,630


I've chosen this as the correct answer, since it's been a few days with no issues since following this message. Thanks for the help, I appreciate it!
 

Cristian_R

Commendable
Feb 7, 2017
1
0
1,510
I got the same problem in a MX100 256GB, even after updating to lastest firmware MU02. It started when I build my rig, and then stopped for about 3 months, and came back again. It doesn't seem to be a solution for this, so I think the best option is to get another SSD for the OS, and use the MX100 as storage, as it hadn't any problems after booting.
 

Madmikegamerxl1

Honorable
Dec 6, 2013
52
0
10,630


Hey,
Yeah It seems to be a common thing with this SSD specifically. My SSD has been perfectly fine since mjslakeridge's solution to make sure it's the #1 boot drive in the BIOS - I guess some files accidentally got created on the HDD when installing Windows...
I hope Crucial's newer SSD's don't suffer with this, they do seem to be one of the cheapest for what they are :)
 

Lutfij

Titan
Moderator
Glad to see this issue has been resolved. As a precautionary measure+as a thumb rule, you should always have the SSD as the only (storage)device when installing your OS and it should be connected off the first SATA port that is native to your chipset(not any third party controller). This is perhaps why you didn't face any issues the first time out with the only device to boot off of being the SSD.
 

Madmikegamerxl1

Honorable
Dec 6, 2013
52
0
10,630


Thank you for the suggestion. I believe the first time I built the PC, I did disconnect the HDD altogether, but the second time I needed to clear partitions off both drives, and must have forgotten. The bit about using the first native SATA port on the motherboard I didn't actually know, so thanks for that, too. It's definitely something I need to remember for next time.

Thanks again!
 

TRENDING THREADS