Boot process jumps into consistency checking mode often

[sono]

I have a Probook which has an eSata port. I have Win 7 on the drive that is in the default hard drive caddy. I installed Win 10 through the eSata port on an external drive. When I run Win 10 from that drive, and then I shut it down and boot again from the in-laptop drive to run Win 7, very often the boot process stops and Chkdsk is started to check the drive consistency. What causes this? I fear running Win 10 will mess up the drive with Win 7 after a while. The boot settings are in Hybrid mode anyway, not sure if it matters or not.

 

[Bree]

I have a Probook which has an eSata port. I have Win 7 on the drive that is in the default hard drive caddy. I installed Win 10 through the eSata port on an external drive. When I run Win 10 from that drive, and then I shut it down and boot again from the in-laptop drive to run Win 7, very often the boot process stops and Chkdsk is started to check the drive consistency. What causes this?

Windows 10 has a setting called 'Fast Startup' which is turned on by default. This is a form of hibernation that saves just the kernel state to the hard drive and reloads it at start up. If you are dual booting you should turn Fast Startup off, else the other operating system will see the disk as being marked as 'dirty' at start up and trigger a Chkdsk as a precaution.

Turn On or Off Fast Startup in Windows 10

How to Turn On or Off Fast Startup in Windows 10

www.tenforums.com

I fear running Win 10 will mess up the drive with Win 7 after a while.

No, there should be no corruption. The 'dirty' flag is the only thing that gets set, to indicate that the disk has not been fully shut down, it's in hibernation.