So I've recently had a windows error that stops my system from booting. It is the error 0xc000014c BCD missing or damages. Very strange things are happening, such as the error randomly changing to 0xc000000f BCD missing or damaged… I've tried several commands on my bootable usb such as bootrec /fixmbr followed by /fixboot and /rebuildbcd. When this last command is used, it goes "The requested system device can not be found". I've tried sec /scannow but it fails… I really don't understand, I've searched on Google about a million times unsuccessfully, went on Windows forums but their answer didn't work, Microsoft answer desk pretty much instantly kicked me out so yeah… I really need help, so thanks very much for any help I can get.
That error says that within the first sector of windows booting there is an error. The recommended fix is to do as Novasty said and use a windows repair disk.
If you don't have a windows repair/installation disk then you need to make one. Click here to get the correct win10 iso from microsoft, and then follow the instructions to create your bootable media. Since windows is moving away form using ODD, i would install the .iso to a flashdrive.
If you do not know how to do so, click here to get rufus, to install the windows .iso you just downloaded to the flash drive.
NOTE: as i typed this I saw your response. What I would recommenced is trying a different usb flash drive, if applicable (your current one may be failing), or re-burn the iso to that flash drive.
If that doesn't work then try repairing the filesystem outlined in this guide. It uses a live usb of Ubuntu.
Actually I never thought of that. I have another USB that I could use, which I will try. I've already tried re-burning the ISO to my first key several time, but it didn't change anything. I'll see what this does :)
Thing is I have no access to Windows what so ever. I only have one Windows computer which is not working so yeah…. I'll try this other bootable disk of yours though
Yeah, the ntfs rebuild should've fixed the fs if it was corrupted in any sectors.
Quick/Easy Route
Reinstall windows. You will need to have your license key handy. (see explanation below as to data recovery response)
Slightly More complicated Route
Before your computer boots into the OS press the function key that will take you into your BIOS. Change the boot order to CD, Floppy, what ever. Just put everything in-front of the HDD with windows on it. Now restart your computer. Doing the above commands will ensure that we have enough time for our keystrokes to be interpreted (bc windows like to boot so fast nowadays that the good ol' fashion method wouldn't work).
Press the F8 key. (NOTE you may have to experiment to get the right one, every manufacture likes to have the function keys different). IF windows isn't totally borked then you should be able to boot into safe mode. If you can boot into safe mode then great! That means that at its core, windows is somewhat working. Somewhere else on your HDD may be dead. If your computer can't boot into safe mode then that means that the HDD probably is on its way out. Or you have been unlucky enough to have a sector die right where windows like to sit.
You will then have to run the chkdsk command from the boot option to cmd or use the linux equivalent from the live usb. At this point you would be screwed. Bc windows 10 encrypts the HDD with your MS password as the key, which makes data recovery from a linux usb not possible. You could take your HDD to Staples or BestBuy and get the geeks there to analyze the drive to provide proof of failure so if the drive is still in warrenty you could contact the manufacture to at least get the drive replaced.
But if your data is really important to you then you would need to contact a data recovery company ($$$).
TLDR; Windows is either borked or the HDD is dying.
Try plugging your HDD into a different SATA port on your mobo, reseat all your RAM and other internal connections. But solving a potentially unknown windows issue is not worth the time or the effort IMO. The "0xc000014c" refers to a location in hexadecimal. Which means HDD or RAM. You would need to provide the windows dump files. Since theres not really any bad RAM company anymore then i'm 90% certain you have a failing HDD.
Maybe i am totally wrong i didn't read all thru the thread did you try installing windows from an another source? Maybe your installation files are corrupt?
Ok so problem is if I put my network controller before my HDD, it will boot off my controller and it'll start looking for DHCP so I'll try putting it after my HDD, my HDD being second to last so that SHOULD be enough right?