Scenario is: Dual boot - W7 and W7 (Work OS and Personal OS). "Work" partitions are hidden in the "Personal" OS and vice versa. Every time I boot into the "Personal" OS and do a clean shutdown afterwards, the next boot into the "Work" OS triggers a chkdsk of the System partition that holds the "Personal" OS (see attached image for reference). It does so by detecting the partition ID rather than a drive letter (because there is no drive letter :-). Things I've tried so far: 1. Running chkdsk /r on both System partitions in their repsective OS'. Then it occurred to me that if the "Work" OS has set a dirty bit for the other System partition, it needs to clear it itself and no amount of individual chkdsks would solve that, so: 2. I've mounted the "Personal" system partition in the "Work" OS by assigning a drive letter to it and ran a chkdsk /r, which finished successfully. An output of "fsutil dirty query X:" returned "Drive is NOT dirty". No Safe Mode troubleshooting steps have been performed so far. The problem unfortunately persists, any help would be much appreciated.

There seems to be more problems: 1. Previous shutdown has not been gracefull. 2. Too complicated structure with multiple unnecessary partitions. I have used program EasyBCD for configuring boot. Alternatively you can use native tool bcedit. http://neosmart.net/EasyBCD/ Regards Milos

1. That may very well be a contributing factor, I agree. Does not explain why the chkdsk runs every time the described scenario happens though. 2. Not complicated at all, 4 absolutely necessary partitions, 2 Operating Systems and a dual boot with Windows Boot Manager. This setup has been working flawlessly for more than 2 years on another machine. Your suggestion leads me to believe that you did not go through my question thoroughly. I do not have a problem with the boot. I have a problem with chkdsk running every time i boot my work OS. It might be worth mentioning that both Operating Systems should not be aware of each others partitions, due to unrelated factors.

Hi Boyan, Because you set a dirty bit for other System partition, so it will run chkdsk again and again. you could remove it as following steps: 1. run cmd as administrator; 2. type fsutil dirty query c: where c: is your boot driver, Enter. 3. it will show if is dirty. 4. type chkdsk /x c:, The x tells Windows to not check that particular drive on the next reboot. 5. Now manually reboot your computer, it should not do a chkdsk and should take you directly to normal Windows login. But the most thoroughly method is doing a clean install of secondary Operation System on other driver which is separated from first Operation Systems driver. Best regards, Karen Hu

Is it possibly related to the recent update from Microsoft? KB2839011 Released to Address Security Bulletin Update Issue http://blogs.technet.com/b/msrc/archive/2013/04/11/kb2839011-released-to-address-security-bulletin-update-issue.aspx You receive an Event ID 55 or a 0xc000021a Stop error in Windows 7 after you install security update 2823324 http://support.microsoft.com/kb/2839011 A lot of people were reporting constant Chkdsk runs on reboot immediately after this 2nd Tuesday patch on the 9th.

Thank you kind sir, you've just made my day. KB2823324 was present on my "Personal" OS and, of course, the System log was flooded with Event ID 55. I have removed it, rebooted, chkdsk ran once and that was the end of it. I owe you a beer. ;-)