The other common solution to the Unmountable Boot volume is to run the automatic recovery - we have done of course and a chkdsk - we have done. Especially common with the non-clip sata cablesĮ. I also doubt this one, as it is usually of course the result of case cleaning or other component jobs when cables are disturbed. Unplug the cables and reseat them properly. ![]() Verify that hard drive/SSD SATA or IDE cables are seated properly. I DOUBT this is the cause, but if you wish we could run a Memtest from a CDĭ. If the tests fail repeatedly, replace or remove faulty module(s). If errors are detected, reseat memory modules and re-run the check. DEFECTIVE RAM so verify that memory modules are working correctly. If this one fails, try other options until Windows starts properly.Ĭ. Incorrect setting on drive controller - enter SETUP - BIOS and set your disk controller mode (aka SATA mode, RAID mode) to Standard (aka Standard IDE or SATA, Legacy) instead of AHCI or RAID (take note of the original setting first!). HOWEVER we have covered this aspect - have we notī. Plug the power cord back in and see if this helps Windows to boot properly. Then disconnect drive cables from all hard disks other than the one where Windows is installed. The remedy is to power it off and remove its power cord. Unmountable boot volume error (Blue Screen of Death) while starting Windows.Ī> Multiple hard drives (including external USB drives!), and windows is trying to load from the wrong one. Also on that post screen check if press F? usually F2 or could be delete for setup - that is BIOS, and check that the hard drive is the boot deviceĥ.UNMOUNTABLE BOOT VOLUME can also be caused by When the computer first posts do you have the press F? usually F12 for boot options if so what is the choice - if one of the options is the hard drive, as there is now only the one then click thatĤ. IN THIS REGARD PLEASE SEE ITEM 6 on that link aboveģ. ![]() Therefore if the firmware on that motherboard has now been set UEFI and I am correct in saying, that because the last set of commands worked, Windows is not installed UEFI, then that could be the reason we have. #Windows 8.1 thread stuck in device driver windows 8In view of this I was wrong in thinking that with Windows 8 and that motherboard it would have been installed UEFI, it appears that it was not. You can if you wish see this for confirmationĢ. UEFI can read NTFS but it cannot boot from NTFS it must boot from FAT If it was UEFI and GPT there would be that FAT partition on diskpart that I mentioned As those last set of commands worked to return to how you were when we started, I have come to the conclusion that Windows is not installed UEFI mode with GPT partitioning on this computer There are three remaining aspects to checkġ. #Windows 8.1 thread stuck in device driver installBefore we try the refresh or the reset or indeed the clean install
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |