optimize drives The parameter is incorrect. (0x80070057)

Well, my USN isn't showing any corruption at all.  So I don't think deleting and recreating it would have any effect to the positive.  It seems that there could be multiple causes for this error and the USN and MFT may just be a small handful.  I've attempted to resize the partition to see if it would rewrite anything useful to no avail.  Even though it resized alright, the problems still persist.

I would recommend scanning with a demo of Zero Assumption Recovery to see if there are a large number of corrupt files on the drive.  It seems that something has randomly corrupted several files on this drive all over the place and there are no bad sectors what-so-ever.  I'm not sure what's happened, but I've scanned this drive with all sorts of anti-viruses, disk scanners, etc. and I can't find the cause of the corruption.  It's entirely random and this system is an always on system with a battery backup.  Whatever happened, it wasn't caused by a power outage or anything else of that nature.  The problem existed within Windows itself.

So I allthough had this Problem for a while and some People mentioned , a clean 8.1 install should do it. I don't know if this works for all other users, but for me it helped. For me it seems, that the Problem is in the MFT record, as ErickCouts II mentioned and that some Updates from 8 to 8.1 corrupt this.

So i installed Windows once again from a Windows 8.1 CD, where i delete all Partitions in the Setup and created them again, and the Problem is gone. I will have an eye on it, if it will occur again.

Greeting

Sascha

Well, first off, deleting and recreating the partitions would affect the MFT and USN journal at the same time, so that doesn't give definitive proof of it being either.  I'm also not entirely sure that it's the updates that corrupted it since mine happened just randomly as though it were something in the disk controller drivers or something odd like that.  I almost suspect that they're trying to force people to adopt the ReFS filesystem that's due to come out soon with this little stunt, but I'm not 100% sure and there's not a lot of proof outside of Microsoft's blatant disregard for anyone who's having obvious problems with their filesystem.

So, yeah, for some of us who don't have time to go through everything and try to reinstall everything on their 2-3 TB drives, we need to find the cause or it will be repeated even after we've found a solution.  Otherwise, we can't even be sure that we've found a permanent solution as much as a temporary fix.

If it is something inside of the Windows OS itself causing the problems, that specific file, patch, driver, etc. needs to be identified.  If it's something else entirely, then it needs to be identified as well.  But I've had a computer come factory direct with a corrupt Windows OS on it that couldn't be fixed with a repair install of Windows and couldn't even shut-down properly when faced with being plugged into a USB3.0 touch-based monitor with displayport and HDMI.  And it would refuse to close a program with the Task Manager if the said program had been corrupted by a faulty download.  So I know that it's not beyond the OS to be the possible cause of this data corruption.

Now watch as a Microsoft agent comes along, apologizes for the OS problems and gives me some copy-paste BS fix before trying to close the unresolved case.  >_>