Sign-in / Sign-up
Your question

Neither BIOS or Windows will detect Samsung 840 500GB SSD

Tags:
  • SSD
  • BIOS
  • Samsung
  • Storage
Last response: in Storage
March 16, 2013 11:52:55 AM

I have sufficient power and a SATA cable hooked up to the motherboard. At first, it picked it up, but I clicked on it in the BIOS hoping for some options, but it tried to boot from it. Now it won't pick it up at all.

More about : bios windows detect samsung 840 500gb ssd

a c 411 G Storage
a b Ô Samsung
March 17, 2013 1:11:06 PM

What is the brand and model number of your motherboard??

Which system BIOS & version do you have?
March 17, 2013 7:12:57 PM

JohnnyLucky said:
What is the brand and model number of your motherboard??

Which system BIOS & version do you have?


I have the Asus P9X79 LE motherboard and the BIOS is American Megatrends Inc. 0504. The SMBIOS version is 2.7, but I'm not sure if that is the same thing.
Related resources
a c 411 G Storage
a b Ô Samsung
March 17, 2013 7:48:49 PM

That's one of the Asus motherboards that is prone to having bent pins in the cpu socket on the motherboard. Only way to tell for sure is to disassemble the system for a close up inspection.

Is your pc a new build?
March 18, 2013 2:11:02 PM

JohnnyLucky said:
That's one of the Asus motherboards that is prone to having bent pins in the cpu socket on the motherboard. Only way to tell for sure is to disassemble the system for a close up inspection.

Is your pc a new build?


No I've had my computer for about 6 months now. I bought it online where you can customize it and they'll build it for you. Needless to say, I'm not really comfortable with doing that type of stuff. Installing an SSD wasn't too bad though. I can probably have someone look at it though.
a c 1306 G Storage
a c 92 Ô Samsung
March 18, 2013 3:01:39 PM

try installing it on a different sata3 port.
November 8, 2013 6:57:43 PM

Alright so it's been like 6 months or something since this thread and I feel like a scumbag for not posting the solution. My solution was that it just sort of... appeared in the bios one day. Not sure why or what happened to cause it.