Hard drive not detected in BIOS but detected in Windows 10

Excalv

Commendable
May 23, 2016
12
0
1,510
My SATA HDD is not detected in my BIOS but I can boot via windows boot manager that brought me to Windows 10, which is detected and functioning there. Even sometimes my windows boot manager is not detected in my bios (which position's at SATA 6G slot). The problem is after several hours or even minutes, my pc would freeze/hang completely. I guess it has something to do with booting via windows boot manager. I don't understand why this is happening, it all started when my attempt to boot from HDD failed (bootmgr is missing), and then afterwards it's 'gone' and my only choice to boot is via Windows boot manager. Is there anyway I can fix this so I can boot via HDD normally?
(Also at this point, is it safe to do a clean reinstall?)

What I have tried :
-Switching sata ports
-Running chkdsk (no bad sectors)
-Resetting my bios to default

PS : unfortunately I don't have a 2nd PC or mobo or even SATA cables.
 
Solution
Yep, as I suspected you drive is not in good shape.

The counts for the two counters below show that you drive has what used to be called Bad Sectors which most likely is causing all those Read Errors.

Current Pending Sector Count
Uncorrectable Sector Count

I would recommend to back up your data and replace the drive.

Excalv

Commendable
May 23, 2016
12
0
1,510

sorry, how do i do it?

 
Excalv...
What Emerald is getting at is to determine whether the problem you're experiencing is due to a failing HDD. I understand chkdsk apparently reports no problems with the drive while it's operational but be that as it may there still could be problems with the disk itself.

You didn't indicate the make of the HDD. Presumably it's a model from one of the major manufacturers - WD, Seagate, Toshiba, etc. Most of these manufacturers have diagnostic programs available to test their drives, so if you haven't done so already, access the appropriate website and download the HDD diagnostic testing program to see if the problem is basically a failing HDD.
 

Excalv

Commendable
May 23, 2016
12
0
1,510


I am currently running seatool for windows (seagate) but I'm not sure to start testing it or not. Apparently, I've found that my disk would crash if put under much stress that it shouldn't before, so probably it's a failing HDD. I will update if the test is successful.

 
Yep, as I suspected you drive is not in good shape.

The counts for the two counters below show that you drive has what used to be called Bad Sectors which most likely is causing all those Read Errors.

Current Pending Sector Count
Uncorrectable Sector Count

I would recommend to back up your data and replace the drive.
 
Solution

Excalv

Commendable
May 23, 2016
12
0
1,510

alright, thanks for the help :)