Windows 10 Cannot find boot drive after being forced to update Windows

  • Thread starter Thread starter ComputerDucky
  • Start date Start date
C

ComputerDucky

I got a message that an update was required as support for my version of Windows 10 was not support as it was a version before April of 2018. However, after the update completed and the PC attempted a restart, I get an error that a boot drive is required and it will not load Windows at all. I had a very similar issue when it forced me to update a few months ago which not was a pain to fix but my computer has not been the same since, so this is very frustrating for me.

In my BIOS, it just lists my only drive which is a Crucial P1 1TB. It does not list any other boot options and it is set for that drive, but I get the error mentioned above. Last time this happened it listed my drive twice, one as MBR drive. I have since tried another drive in the system with a previously working version of Windows 10 (that was my old drive for that PC) which is also encountering the same issue (It is a Crucial 250GB MX500 2.5 inch SSD).


My PC has the following hardware:

Gigabyte X470 Auroras motherboard

Ryzen 7 2700X

32GB of Ballistic Tactical DDR4 RAM rated at 3000MT/s (4 modules with 8GB each, same exact model)

1TB Crucial P1 NVMe SSD

XFX 8GB RX580


When this first happened, it took a lot of time and effort to get it working again, but at first it would only run the memory at 2400MT/s which previously it worked at the rated 3000MT/s without any issue. It would also often restart before even getting to the BIOS several times without any noticeable pattern; sometimes it did within a few seconds, sometimes within a few minutes, but always would not get to the BIOS the first few (or more) times.


I replaced the PSU with a better one at that time, but the issue persisted. I also used Memtest 86 which did not find any problems with the memory (I though that the system only running the memory at 2400MT/s despite the profile having it at 3000MT/s may show signs that the issue stemmed from the RAM, but I was wrong).

After clocking my memory down to 2933 I was able to boot into Windows, but it would often BSOD and ran the memory at 2400 instead of 2933. So I reverted Windows back to a previous version and it partially fixed the issue. It would still restart a few times before getting to the BIOS, but would be able to boot to Windows 10 and run the memory at 2933 without BSOD.

I did not turn off or had any loss in power during the update; I allowed the update to be uninterrupted and it took about an hour for this last one.

I really need help with this one as this has become a very frustrating issue for me.

Continue reading...
 
Back
Top