Able to load to bios, then: "Inaccessible Boot Device"

[thetylero]

After many hours of fiddling with the system to get it to show a video feed, i have finally been able to load into bios. Now, the system will not load into Windows.

 

[Colif]

This fix took a turn for the worse, didn't it. Hope PSU is all you need.

 

[thetylero]

This fix took a turn for the worse, didn't it. Hope PSU is all you need.

Yeah, things went south reaaaaally quick. After I install the new PSU, i'll give another update on the situation.

 

[thetylero]

This fix took a turn for the worse, didn't it. Hope PSU is all you need.

Alright, new PSU installed and everything hardware wise seems to be working correctly. But still having the same inaccessible boot drive issue. I already did this, as well: http://www.pcworld.com/article/245174/restore_access_to_a_write_protected_hard_drive.html


update: if i were to Advanced>Reset this PC - would this maybe fix the problem?

update 2: resetting the PC currently and keeping personal files.

update 3: SUCCESS. All files survived, system boots normally - all systems online

 

[wpgwpg]

All RIGHT!! Good to hear. Now back that system up to an external hard drive ASAP. We sure don't want a repeat of this experience! I use Easeus Todo Backup Free which is free for home use. I've seen a lot of folks say they use a Macrium product, and there are others. Whatever you use, do it NOW while things are working like you want them.

Good luck.

 

[thetylero]

All RIGHT!! Good to hear. Now back that system up to an external hard drive ASAP. We sure don't want a repeat of this experience! I use Easeus Todo Backup Free which is free for home use. I've seen a lot of folks say they use a Macrium product, and there are others. Whatever you use, do it NOW while things are working like you want them.

Good luck.

Backing up a system image to one of the other drives right now.

Also, it turns out that my ram played a part in all of this. I had it overclocked from 1333 to 2400(the kind i bought was meant for this, i bought it as 2400 but it said you had to do the OC yourself, so i did.) on day one and it has worked fine for well over a year now. But, recently it has decided that i doesn't like to be OC'd any longer so it is throwing a fit. My MB has a dual bios option, and the ram was only OC'd in one of the bios. After i got the whole system fixed and working again i started doing a ton of reinstalls of programs and such when the system froze on me. I force rebooted it and the displays were not working again, i flipped the bios switch and everything came up just fine, this time with the ram running at 1333. So, think i'll just the leave the ram at 1333.

Again, thank you so much for your help. I wouldn't have solved this without the help i received.

 

[Colif]

i like happy endings rather than inconclusive ones

 

[Luis_41]

Sure, i am helping you, i don't expect you to be here

Sorry I couldn't give you an easy answer, I wish there was one besides do a fresh install as that does fix it.. painful though.

you can try doing a reset of win 10, that is on the page next to troubleshoot.

why did you mention locking drive? or is that an error from windows as sometimes it locks the drives itself: http://www.thewindowsclub.com/the-drive-where-windows-is-installed-is-locked

I would like to avoid a reinstall.
I quoted the error that was given to me in command prompt after I entered the "chkdsk /f /r"

Sorry for the late followup, but thought some may use this info. The reason you see the drive as write protected is because you're running a small Windows instance, that resides in a different partition, and that one is write protected. In order to run chkdsk succesfully, you need to change to the proper drive first. Try typing "e:" and enter. And then throw a "dir" to see if it's the right drive. If it's not the right one, or it doesn't exist, you can always try a different letter. May sound like a chore, but you'll easily find the correct one.