Windows 10: chkdsk running at every boot, can't stop it

Hello! I recently set my Windows 10 computer to run chkdsk at the next reboot. Well, I just rebooted, and chkdsk is failing. It pops up the standard "Checking drive C:" message for a split second then I get a BSOD with the error "CRITICAL_SERVICE_FAILED".

I figured it's just a bug with Windows 10, no big deal, but now I can't prevent chkdsk from running at startup and, therefore, I can't boot into Windows.

I tried the methods I found elsewhere (from recovery): open regedit, edit the BootExecute key (key doesn't exist to be edited); run chkdsk manually (completed on all drives with no errors); check if drives are flagged as dirty (none are); use chkntfs to disable the check on next startup (had no effect).

I have no idea what else to try. Any advice would be greatly appreciated!

:)

 

After latest updates (early Dec.) on reboot comp starts "scanning and repairing drive (G" hard drive

Wow just ran some win10 updates and now everything is bork.. every reboot it runs chdsk on my G: drive (there is nothing wrong with it..) and when it finishes, the computer runs super slow.

tried multiple reboots, cold boot and what not.. haven't yet tried safe mode or reverting to previous configuration (mostly cause can't get a stable desktop)

How do we fix this?

How do we stop this chkdsk action in the first place? (no, not the press any key to skip thing, but stop it from even starting)

 

Automatic Check Disk on Win 10 startup.

These two options being disabled is normal!

Click HERE for a Technet article on how to disable this chkdsk at boot, this will probably be the answer you need . . .

 

How did you schedule chkdsk to run?
Which commands/options did you use with chkdsk?

I used chkdsk /f from an elevated Command Prompt
Then I rebooted the system and it booted to Windows without any problems.

Could there be a problem with the drive that Windows is installed on?
Why did you run chkdsk in the first place (were there indications that there might be a problem of some sort?)?

autochk.exe runs at boot normally, and it launches chkdsk if it's needed. If this is what is happening with your system, then it's Windows saying that there is a problem that needs to be fixed. Have you tried running Startup Repair/Automatic Repair?

 

usasma asks some very good questions, please address those first.

You say that all drives are ok when you check them manually ... but you also say that you cannot boot into Windows, so you must be using a live disc of some kind. Please identify what you're using to boot and run the utilities (chkdsk, regedit, chkNTFS, etc).

I also wonder if the System Reserve partition might be the culprit - it normally doesn't have a drive letter. There's also the EFI partition - but only if you have an EFI capable system.

When you get the chance, could you create a Minitool Partiton Wizard boot CD
Minitool Partition Wizard: downloads
scroll down to the bottom of the page and pick:
Bootable CD


MiniTool Partition Wizard Bootable CD allows user to boot computer directly into MiniTool Partition Wizard to manage partitions without any limitations.
Then boot from the PW disc and post a screen shot (a camera or phone will have to do). You can also check the drives for errors with PW, but you've already indicated that they are clean - at least the ones you tested.

I'll be off until next year.

Have a great last night of 2014!

Bill
.

 

I scheduled chkdsk using "chkdsk c: /f /r" and accepted when it prompted me to run it at startup (since the volume was in use). I also scheduled my data drive to run at the same time, same command, just with g: instead of c:.

I'm fairly certain that there isn't a problem with either drive; I just run chkdsk every now and then in case any errors exist that can be cleaned. I've never had a problem before this one, even on Windows 10. I actually did a refresh install about five days ago too, so it should be relatively stable.

Startup Repair was unable to diagnose/fix any problems.

I ran chkdsk off of the recovery partition and it reported no errors. I'm currently making a Windows 10 flash drive (using the build 9879 iso) and I'll try running repair from that in case it makes a difference. After that finishes I'll run Minitool and post the screenshot.

EDIT: Ran "chkdsk <drive> /f /r", it reported no errors on any drive. I do have a GPT/EFI setup, and I've attached the requested Minitool screenshot. I can't see an option anywhere to repair the drive, so I'm not sure what that's referring to. I therefore did not make any changes with Minitool. (In case it matters/helps, I was able to successfully use the "Explore Partition" option and see all of the files on each drive, so there doesn't appear to be any partition table corruption.)

 

Thanks for the update.

The chkdsk equivalent in PW is called Surface test. That was my reference - so we're both confused about repair *Smile

Are those other drives external or internal? Either way, it would be great if you could disconnect them to remove them from the equation. What I'd like you to test is: boot with only Disk 1 connected. It's easier to troubleshoot when there are fewer variables involved.