Possible fix for NTFS Errors

Thanks for everyone's input. I recently started getting ntfs 55 errors again. sfc /scannow found no integrity violations and chkntfs said volume is not dirty. This time it appears that an outdated SMbus driver was the cause. Updated the driver (was available as an optional Windows Update) and the ntfs errors were gone and have stayed gone immediately after the updateted driver was installed. They have not returned for a few weeks so far including after reboots. I don't believe my drive is failing or anything like that. The pc runs perfectly. Never had a BSOD. Through a lot of searching it appears that several things can cause false positive ntfs 55 errors. I'll see if they stay away after a couple of months and report back to this thread. Pain in the neck kind of problem.
Thanks.

Hi, carwiz. Thanks for your input. The business with some of the drivers goes a little beyond my area of knowledge but so far this SMBus driver "seems" to have stopped the problem from the moment I updated it. I also went through the list of device drivers via Device Manager and it appears that everything including the bios driver is most current. I'll surely report back at some point and state weather the problem stays fixed or not. At this point I'm somewhat apprehensive. Time will tell. I thought I had it resolved previously and it had recurred maybe for a different reason, maybe not.
Mark

Hi, again. As of 6/12/2015 I started getting ntfs 55 errors again but very rarely and still false positives. They will occur 2 at a time at the same exact time. It is not happening after a reboot. Does not happen after a wake up from sleep mode. I can't seem to isolate the cause so at this time I'll just live with it as no integrity violations are found and the volume is not dirty. If I manage to find the "real" cause of these errors I'll post back. The pc is clean and runs perfectly and is very fast. I'm starting to feel a little foolish since every time I think I had it resolved it comes back to bite me in the butt. I believe I did everything I found suggested on the web plus my own ideas. I definitely feel that the drive is not going flakey on me. Apologies for any misleads I may have given in this thread for possible fixes for the ntfs 55 error problem.
Mark

Hi,again. I kept troubleshooting for the cause of the false ntfs 55 errors. I checked for the Kernel-Power events as suggested by carwiz and all were related to sleep mode. I found that the time of the errors correlated to the time of the scheduled task System Restore checks. I also found that the Distributed Link Tracking Client service was set to Manual for some reason rather than Automatic (started). I took care of that. Then I disabled the System Restore scheduled task and installed a program called Restore Point Creator and set it to create a scheduled restore point once a week which it did without any ntfs errors. Next I re-enabled the Windows SR scheduled task (and disabled Restore Point Creator scheduled task). So far there have been no more ntfs 55 errors. Hopefully the problem is once again resolved. I hope so!
Mark

This post details my experience with "NTFS 55 errors". There was nothing wrong with the hard drive. The root kit was the cause of the "NTFS 55 errors".

All ntfs(false) errors have been eradicated. The errors seemed to be caused by different issues and resolved as per my posts on this thread. This post refers to my last post when I was getting 2 ntfs errors at the same time that Scheduled Tasks SR point operations occurred and Distributed Link Tracking Client Service somehow got set to Manual rather than Automatic. Disabling the SR scheduled task for a week , reset Distributed Link Tracking Client Service to Automatic (started) and then enabled the SR scheduled task again definitely fixed the last ntfs errors.
Mark

Thanks carwiz for your input. I really didn't go through the process of trying to check if the Distributed Link Tracking Client Service had anything to do with my issue. All I know is that it was originally set to Automatic and it somehow got changed to Manual so I set it back to Automatic as recommended. I agree that the SR startup task really is not needed but I just left it alone and changed the idle time required to 5 minutes (was set to 10 minutes as default.) In any case I'm glad that this annoying problem is gone and has stayed gone! Take care everyone.
Mark