Cannot boot into Windows 10 (BSOD), possibly due to hard drive failure

B

brokenpcguy

Hello, a few things to note before i start:

The computer in question is a custom built computer running Windows 10 in a triple boot configuration with 2 versions of Linux

The boot drive in question is an Intel SSD (all 3 operating systems are on this SSD)

Now, the issue that i am faced with is as follows:

A few days ago when i woke my desktop from sleep, Windows got stuck on the lock screen (the one with the clock) and so i had to forcefully shut down my desktop. Afterwards when i rebooted my computer and selected Windows 10 from the GRUB Bootloader which i have on my desktop as i have multiple operating systems, there was an error which was: failure writing sector 0x0 to 'hd0', press any key to continue. The GRUB Bootloader screen then changed to the normal Windows booting screen but then was followed by a BSOD with the stop code: Unmountable Boot Volume, and Windows restarted but to no avail. I got my windows installation disc and followed the steps to boot from the cd, and then went on to select 'repair your computer' which lead me to the recovery options. It is worth noting that this process takes an extremely long amount of time for some unknown reason (close to 20min just to wait for the screens to load). I selected 'troubleshoot' from the two options, the other being turn off your computer, and it brought me to the list of choices in "Advanced options" i could choose from to repair the computer. It is worth noting that "Startup Options" is missing. The first thing i did was to select "Startup Repair" but all it did was to "diagnose my computer" and "attempt to fix my drive" for another 20min before suddenly causing the computer to restart and to be back to square one. "System Restore" and "System Image Recovery" could not do anything as well. "System Restore" said that i had to "select an operating system before restoring" or something along those lines and basically i did not get anywhere with it. Lastly i tried to use the command prompt option to see if there was anything i could do to fix the issue.


Here's where it gets really frustrating. I take like 5 minutes to load into the command prompt. The directory(??) ( the starting text at every line before you type commands in) is x\sources>. So i ran a list of commands targeted at the boot drive suggested by many forums. Firstly i tried to run "chkdsk" but that command (along with all the other different parameters) will always return 2 unspecified errors, followed by a final line of "failed to transfer logged messages to the event log with status 50". I also tried bootrec /fixboot and that returned an "i/o device error". sfc /scannow and many other commands didn't work, and when i tried to change the directory from x\sources to the boot drive, the i/o error happens again. I unplugged and plugged the SATA cable to and from the hard drive as a last resort, but it did not work (i predicted this anyway as i doubted that it would be because of a faulty cable) At this point thanks to all the forum reading i suspected that my boot drive had a "physical bad sector" or something like that, or the master boot record or partitions were corrupted, and so i tried to at least boot windows into safe mode to see if i could run some 3rd party partitioning/repairing software to fix this. However, as i cannot boot up windows and f8 no longer works i had to go back to the cmd and run the "bcdedit" command to allow windows to enter safe mode. As previously mentioned "startup options" is not present in the "advanced options" and hence i could not restart windows from that recovery mode to enter safe mode. "bcdedit" related commands all returned an error saying "the boot configuration data store could not be opened, the system could not find the file specified." Long story short i could not even find a way to boot into safe mode to try and fix the suspected faulty boot drive. Lastly as mentioned before i have multiple operating systems residing in the same boot drive i did not install them recently they were all working for a long time before) and so i tried to boot linux in a last ditch attempt but as guessed all systems could not boot. Side note i ran a "fsck" command in linux recovery mode but that didn't help.

I would be inclined to conclude that the forced shut down at the beginning caused physical damage to the boot drive hence resulting in physical bad sectors or like a corrupted mbr/partitions, so what i need advice on is that is there anyway to access the drive to repair it, when all repair commands are not able to get through seemingly due to the drive being corrupted? If not, can someone help me to access windows in safe mode so i can try running 3rd party software to fix the drive? Any help would be appreciated as i am urgent to get my computer up and running for work purposes... Also, if any more details are needed (such as commands and errors, or hardware models etc) just ask me and i will rerun the commands/check the hardware specifics (i am currently remembering all these from memory so i apologize for the vagueness). Thank you!!

Continue reading...
 
Back
Top Bottom