Possible fix for NTFS Errors

Page 1 of 3 123 LastLast

  1. Posts : 57
    Windows 7 Home Premium 64 Bit
       #1

    Possible fix for NTFS Errors


    Hi, All. As of this morning , in the Event Viewer under System, I was finding a number of NTFS errors with Event ID 55. The description was The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume OS. Note that everything seemed to be working perfectly. I ran the CHKDSK with the R parameter and the system was clean. The errors occurred mostly on reboots or on wake up from sleep mode. The night before I installed 22 Windows Updates. Thought that may have something to do with it but before attempting a System Restore prior to the updates it occurred to me that I hadn't done a boot time defrag in some time even though I do a regular defrag weekly. I ran a boot time defrag with SmartDefrag and after the reboot, no more NTFS errors! Just something to consider if anyone else encounters this issue.
    Mark
      My Computer


  2. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #2

    I personally never know Windows 7 Update to mess up NTSF.

    I would recommend using Windows 7 built in defragger instead of a 3rd party defragger.

    You could also check Windows 7 System Files by using this tutorial by Brink.

    SFC /SCANNOW Command - System File Checker
      My Computer


  3. Posts : 57
    Windows 7 Home Premium 64 Bit
    Thread Starter
       #3

    I forgot to mention that I did do the SFC /SCANNOW and it showed no problem. I was just trying to convey that a boot time defrag (regardless of which defrag tool is used) stopped the NTFS event viewer errors that I was getting. Thanks for your reply.
    Mark
      My Computer


  4. Posts : 57
    Windows 7 Home Premium 64 Bit
    Thread Starter
       #4

    Hi, again. Recently started getting ntfs error 55 again. This time when running sfc /scannow it came up with errors some which it couldn't fix. After much searching I found the solution somewhere in this forum. It was caused by a Windows Update kb3022345 which I think was installed on May 13. Uninstalling this update fixed the problem!
      My Computer


  5. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #5

    KB3022345 is unrelated to your NTFS error 55 though :) or else we all would get it
      My Computer


  6. Posts : 57
    Windows 7 Home Premium 64 Bit
    Thread Starter
       #6

    I disagree. It was directly related to the ntfs errors that I started getting after installing the May 13 2015 updates and problems found when running sfc /scannow. Maybe it didn't effect all pc's but it is a known cause of this problem. Here is a link to one of many sites that confirmes this problem:
    Windows patch KB 3022345 triggers apparent sys file corruption | InfoWorld
      My Computer


  7. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #7

    Where in the link you gave it mentions ntfs errors?

    KB3022345 causing corruption with 2 files is known, I wasn't talking about them. Ask anyone in the forums whether they have seen ntfs errors accompanying this corruption.

    However, you may have some other problem that manifested with this corruption which I would not know about.
      My Computer


  8. Posts : 57
    Windows 7 Home Premium 64 Bit
    Thread Starter
       #8

    I'm having trouble locating the link that mentioned the ntfs 55 errors that were caused by kb3022345. Maybe I misread whatever link I saw that led me ultimately to this fix. All I know is that when I uninstalled kb3022345 the ntfs 55 errors were no longer created and have not returned ever since.
      My Computer


  9. Posts : 5,656
    Windows 7 Ultimate x64 SP1
       #9

    Searched "kb3022345 ntfs error 55" at google - past month set

    Only one I found was KB3022345 Causes Blue Screen on Windows 7 - Microsoft Community, but then again I couldn't find any ntfs 55 inside, and bsod wasn't exactly caused by KB3022345.

    Also, last page of above: Version 6 of the Microsoft article on KB3022345 states "When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or corruption on a device that is running this update, and this issue will be fixed in a later service update."

    So actually there are no corruptions. (There is no spoon) :)

    Glad you fixed it though!
      My Computer


  10. Posts : 4,161
    Windows 7 Pro-x64
       #10

    NTFS 55 errors are unrelated to the SFC errors in the KB. You may have encountered them simultaneously but they reflect two different problems.

    NTFS errors are caused by a failing disk or failing power. Most often, file structure errors are caused by power faults. If your PC is not connected to an uninterruptable power supply (UPS), a mere blink of the power can cause data loss and/or a corrupt file system. Also, powering a system down without using Windows "Shutdown" can cause corruption.

    Search your event log for Kernel-Power events. You can ignore 1s and 42s as these are sleep events but others may lead to the reason you keep getting file structure errors. If it's not power, your disk drive is warning you of imminent failure.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:29.
Find Us