F5F Stay Refreshed Power Users Overclocking BIOS fails to identify SSD as a bootable device following the "Overclock Failure" notification.

BIOS fails to identify SSD as a bootable device following the "Overclock Failure" notification.

BIOS fails to identify SSD as a bootable device following the "Overclock Failure" notification.

S
supercube49
Member
172
02-09-2016, 01:48 PM
#1
Earlier today I tried to increase the clock speed of my Asus Geforce GTX 970 STRIX.
I stayed within the normal safe limits for successful overclocking, and there were no white errors, and the temperature remained around 65 degrees Celsius without any issues—everything proceeded smoothly.
Then suddenly everything stopped working, and I couldn't restore it even after a few minutes, so I decided to power off the machine by pressing the standby button.
After restarting, I got the message "Overclocking Failed."
I told myself it would reset to factory settings and I’d have to redo the clocking for a smoother result, but then I ended up in BIOS because the BIOS didn’t recognize my SSD as a bootable device.
This SSD contains Windows 10 and all installed programs, along with an SSHD for storage. In the boot priority list and EZmode boot devices, only my SSD and DVD drive appear—no SSD, no OS.
After some time of troubleshooting, I located my SSD in the Advanced section of BIOS under the Override list.
Double-clicking it brought me back to Windows, allowing me to use the computer again.
However, now every time I boot or restart, I have to go through BIOS and use the Override function—this is definitely not ideal, isn’t it?
At this point, the BIOS refuses to recognize my SSD as a standard bootable device, yet still keeps it in the Override list, which causes strange behavior.
The SSD itself is only about two weeks old and in good condition, having worked perfectly before the overclocking test.
Everything in Windows 10 seems normal now, but I can’t access it like before.
How can I fix this?
S
supercube49
02-09-2016, 01:48 PM #1

Earlier today I tried to increase the clock speed of my Asus Geforce GTX 970 STRIX.
I stayed within the normal safe limits for successful overclocking, and there were no white errors, and the temperature remained around 65 degrees Celsius without any issues—everything proceeded smoothly.
Then suddenly everything stopped working, and I couldn't restore it even after a few minutes, so I decided to power off the machine by pressing the standby button.
After restarting, I got the message "Overclocking Failed."
I told myself it would reset to factory settings and I’d have to redo the clocking for a smoother result, but then I ended up in BIOS because the BIOS didn’t recognize my SSD as a bootable device.
This SSD contains Windows 10 and all installed programs, along with an SSHD for storage. In the boot priority list and EZmode boot devices, only my SSD and DVD drive appear—no SSD, no OS.
After some time of troubleshooting, I located my SSD in the Advanced section of BIOS under the Override list.
Double-clicking it brought me back to Windows, allowing me to use the computer again.
However, now every time I boot or restart, I have to go through BIOS and use the Override function—this is definitely not ideal, isn’t it?
At this point, the BIOS refuses to recognize my SSD as a standard bootable device, yet still keeps it in the Override list, which causes strange behavior.
The SSD itself is only about two weeks old and in good condition, having worked perfectly before the overclocking test.
Everything in Windows 10 seems normal now, but I can’t access it like before.
How can I fix this?

A
Amegahoney
Posting Freak
789
02-09-2016, 09:43 PM
#2
The "Harddrive BBS Priorities" were set to swap the BIOS boot order, making my SSHD the top priority instead of my SSD. Reverting to the SSD resolved the issue.
A
Amegahoney
02-09-2016, 09:43 PM #2

The "Harddrive BBS Priorities" were set to swap the BIOS boot order, making my SSHD the top priority instead of my SSD. Reverting to the SSD resolved the issue.

P
Pharenir
Member
61
02-10-2016, 02:02 AM
#3
The "Harddrive BBS Priorities" were set to swap the BIOS boot order, making my SSHD the top priority instead of my SSD. Reverting to the SSD resolved the issue.
P
Pharenir
02-10-2016, 02:02 AM #3

The "Harddrive BBS Priorities" were set to swap the BIOS boot order, making my SSHD the top priority instead of my SSD. Reverting to the SSD resolved the issue.