CHKDSK keeps restarting on Stage 4. Can anyone help?

Megahertz · 14 Jul 2023

ken1943 said:

Your reply made me check and found out chkdsk does not harm an ssd

Thanks at 80 yrs old still learning !!

Not only you. We all learn something new here.

FreeBooter · 15 Jul 2023

Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below command into Command Prompt and press Enter key.

Following command will fixes errors on the disk and locates bad sectors and recovers readable information.

Code:

Chkdsk C: /r

Please replace partition letter C: with Windows installed partition letter. When the computer boots into Windows Recovery Environment (WinRE) environment, the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assigned any other drive letter, usually D: drive letter is assign to Windows installed partition. The Bcdedit | find "osdevice" command can be used to find out the drive letter of the Windows installed partition, the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

mdb1983 · 20 Jul 2023

thank you everyone for your help. i found out it indeed was the hard drive failing and i replaced it with an ssd and it runs so much faster. it didn't tell me on crystaldisk or seatools that the drive had any failing sectors but i formatted the drive in a last ditch attempt to see if that fix anything but that didn't fix it. however when i used a hard drive recovery tool to see if i can get some files back it told me they found errors in the drive so i realized it was definitely failing. just happy it didn't end up being the motherboard

dalchina · 20 Jul 2023

To note: if you use disk imaging regularly, as I've posted a number of times- the act of creating an image (at least with Macrium Reflect) performs a CRC check on the data read.

I found that when creating the next image for one disk failed with a CRC error, that disk was beginning to fail (bad sectors).

Yet another benefit of using imaging.