Windows 10: Computer won’t boot after “Restart to fix drive errors”

Josh_Pottinger · Oct 15, 2020

I started up my computer after plugging in a new monitor and after a couple mins of it running fine it started to slow and the notification said “Restart to fix drive errors”

The computer started to restart and it said it was fixing the errors. When it finished fixing them, it started a loading screen with 5 dots near the bottom of the screen. It sat like this for about a half hour before i tried to turn it off and on again. This did nothing and the same situation happened.

:)

n2bn2b · Oct 15, 2020

Error Message when updating from Win-7 to Won-10

Bree
I followed your suggestions (2nd Aug 19) for installing Win-10. Made the bootable flash drive successfully through the media creation tool. But when I attempted to upgrade and activate to Win-10 (64 bit) from within Win-7 (Pro-32 bit), I got the following error message:

Error # OxC1900101-Ox20017. " The installation failed in the SAFE_OS phase with an error during BOOT operation"

I read the diagnostics under this error number and carried out the proposed fixes, i.e. update Win-7, uninstall Malwarebyte antivirus, disconnect all external hardware, e.g. printer, scanner, external hard drives. I then tried to repeat the steps to do the upgrade through the Win-10 bootable flash drive as before. Got the same error message.
Appreciate any further comments and suggestions as to (a) what does a failure in the SAFE_OS during boot operation mean, (b) what can I do to solve it. Is this anything to do with the hardware in my computer? I listed these in my first posting above.
Thanks for any help

Sommer · Oct 15, 2020

Hard Drive "Read Disk Error Ctrl-Alt-Del to Restart" on Startup

I had the same problem, turned out to be a bad memory stick.

This is what I found on the net, don't remember the site now, but for what's it worth:

"A disk read error occurred Press Ctrl + Alt + Del to restart"

This is one of the most frustrating error messages you can ever deal with. Sometimes the fix is simple, sometimes it's a complete pain. Having recently dealt with this again, I thought I'd post my thoughts in the hopes that it helps someone else out there.

So you receive the dreaded "a disk read error occurred. Press Ctrl+Alt+Del to restart". Multiple restarts result in the same error message.

If you put your drive into another computer, or connecting it as a slave on your own computer, it will typically work fine, and no data is missing.

Because this error is not usually associated with data loss, DO NOT RE-PARTITION THE DRIVE. Your data is likely safe and sound.

Here's how we'll recover your data. Try each step below, in order, and see if your drive becomes accessible after each step. In my experience, you won't start seeing results until step 5 or so.

1. Run CHKDSK /R /P from the recovery console (it will typically find no error)
2. run FIXBOOT from recovery console (typically has no result)
3. run FIXMBR from recovery console (typically has no result)
4. Run the manufacturer's diagnostic utility, downloaded from their website (it will typically find no error)
5. Changing the drives from cable select to Master/Slave may fix it.
6. Replacing the data cable may fix it, but usually not.
7. Setting the BIOS to use defaults may fix it, but usually not.
8. Changing the BIOS drive settings from auto to user-specified, ensuring that LBA is selected may fix it.
9. Pulling the CMOS battery to let the BIOS lose it settings may work.

At this point, you may be feeling some frustration. *Smile

If all that fails, here's what will usually work:

Ghost your data to a new drive, and use the original one as a slave. It will work. And all of your data will still be accessible. Your computer should boot normally. If it doesn't, or it there are errors, run the Repair Installation option from your Windows boot CD.

But why does this happen? Nobody seems to know why. The problem typically evades all forms of detection.

Here's what I've learned: this error message likely has more to do with a hardware interaction between the drive and your system than any actual issues with the drive. To put it one way, your motherboard and drive are no longer on speaking terms.

I don't know why the original disk has no problems being a slave. Perhaps it got tired of running the show. Perhaps it's preparing for retirement.
Click to expand...

KBD · Oct 15, 2020

PC Won't Boot After Install and Restart

I was able to clear CMOS by taking out the battery and then putting it in after 5 min. That helped and i was able to boot, i got some kind of a checksum error and was given a choice to restore to last known good configuration or to default, i chose option number 1 and was able to boot into Windows, however after i restarted the PC i was back to square 1 where system wouldn't boot as before.

What do i do now? Clear CMOS again and attempt to boot into Windows do a system restore and uninstall that program that may have been the cause of this problem? Any suggestions?

Windows 10: Computer won’t boot after “Restart to fix drive errors”

Computer won’t boot after “Restart to fix drive errors”

Computer won’t boot after “Restart to fix drive errors”

Computer won’t boot after “Restart to fix drive errors”

Computer won’t boot after “Restart to fix drive errors” - Similar Threads - Computer won’t boot

Computer won’t restart after Windows Update

Windows computer won’t boot after enabling Secure Boot

Computer won’t restart

Computer won’t boot.

Computer won’t restart after a full reset.

Computer won’t finish restart after resetting.

My computer won’t restart after this

Computer won’t restart after updating

"The computer restarted unexpectedly..." error after boot problems