Internal drive repeatedly repaired by Windows

Hi guys,

I have this very worrying problem with one of my internal drives. Every now and again a Windows balloon pops up and says that it fixed errors on my F: drive. When I go into the event viewer under 'system' there are tonnes of entries for the file system being repaired.

Here are a few of the errors;

1. The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x4000000004e50

1. The file system structure on volume F: cannot be corrected.
   
   
   
2. Please run the chkdsk utility on the volume F:.

1. Volume F: (\Device\HarddiskVolume9) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

Most of the error messages are the second one above. But the first ones worries me the most.

Some background on my machine;

I dual boot from two separate SSD's into Windows 8.1 and OSX 10.2 respectively. Then I have a Western Digitial 4TB hardrives partitioned into two 2TB drives - formatted NTFS.

On one of the 2TB drives is this F: drive. This is where I keep all my documents, pictures, music and such. in Windows my documents folders are mapped to the F: drive and in OSX Yosemite the users folders are linked via symbolic links.

In OSX I use Tuxera NTFS to write to the NTFS drives. I have a feeling the issues lies here somewhere! Perhaps everytime I boot into OSX and play around it corrupts the drive in windows???

Possibly the settings in Tuxera are causing problems. I think I have caching turned on. See this menu here.

Just one more note - I have Paragon Backup and Recovery 14 installed. In device manager I get an error under - UIM direct device image plugin. It says;

1. The software for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48)

I believe this allows me to open images (like .bin) directly in windows explorer. Maybe this is an issue?

Please please help! I'm really worried that the drive is just gonna not work some day!

Any ideas?

Usually means that the hard drive is failing.

I encountered a problem something like this with a member of the local computer group.
He had a dual boot system with a single drive. One partition was windows 7 the other was Windows 8.1.
When there was a disk problem, chkdsk was scheduled to run, but it would depend on which partition he booted to decide which would run.
If he had booted and restarted from Windows 8, the Windows 8 check disk routine would run, vice versa for Windows 7.

It turns out that the check disk partition structure has changed in Windows 8. So Windows 7 corrupted the Windows 8 partition running chkdsk.

Perhaps the same sort of thing is happening in your case.

Here is where I found out about the different CHKDSK structures - the location for the fsutil 'dirty' bit is different in Win 7 and 8:

https://www.raymond.cc/blog/manually-reset-or-clear-dirty-bit-in-windows-without-chkdsk/2/

1. The file system structure on volume F: cannot be corrected.
2. Please run the chkdsk utility on the volume F:.

1. Volume F: (\Device\HarddiskVolume9) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.

Most of the error messages are the second one above. But the first ones worries me the most.

Click to expand...

And did you follow the suggested advice and run chkdsk like it keeps telling you?

If not, you need to do that NOW. If you have run chkdsk as suggested, and the errors keep returning, replace the drive.

If you have not run chkdks as suggested, click on the Start Orb and start typing, powershell and when you see Windows PowerShell appear at the top of the menu, click to open. In the PowerShell windows, enter: chkdsk /r and press enter (note the space before /r). The /r switch does the same as the /f, plus a little more. Follow the prompts to let it run at next boot, then reboot. Note it can take many hours to complete and may appear to be hung up. Just let it run until done.

Hopefully, you already have a current back up of any data on this drive you don't want to lose, but if not, make one now. If the errors continue, replace the drive.

I have a similar problem with Windows 8.1 on an SSD with Windows 10 on an HDD. Windows 10 starts up with no problem but then when I re-boot to start Windows 8.1, it does a scan on the HHD that has Windows 10 on it.