Software-initiated NTFS 55 Errors

Win 7 64-bit Ultimate on Dell XPS8300 I have noted a number of adhoc NTFS 55 errors (System disk corrupt etc.-run Chkdsk) in my logs. The first lot seemed to be caused by a scheduled job DEFRAG running against my long-time defragmenter Diskeeper. I therefore disabled the scheduled job and also the Defrag service, since when it has not recurred. However, I have had another crop of 55 errors. A close examination of the Scheduled Tasks log against the System Error log shows that the timing of the errors is simultaneous with another Scheduled Task LPREMOVE (MUI) running. This is some routine to remove unused Language Packs, as I understand it. The curious thing is that LPREMOVE's trigger is "run on start-up", yet it has kicked off hours after a startup, apparently at a random time. I have therefore disabled the Scheduled Task, and wait to see results. I have also:- - run CHKDSK several times, which reveals no errors - run Seatools disk tests - no errors - run Dell disk tests - again, no errors - run Malwarebytes and Avast scans - nothing reported - examined every log I can think of that may show something - checked that KB2823324 isn't installed My questions therefore are these:- 1) does anyone else have any experience of this problem, and by implication, information or suggestions? 2) is the random running of scheduled tasks something which others have experienced?

Thanks for reply. Diskeeper is a substitute for DEFRAG and runs all the time as a service. If I right click drive properties\Tools\Defragment then I am presented with the Diskeeper program rather than standard Win 7 defrag. In theory, if the Defrag service is set to manual, it shouldn't have run if the Scheduler also has it disabled. However, it did, and that's why it's now disabled both as a service and in Scheduler. I have been looking at the other Scheduled tasks and their timing as against the NTFS errors. I find that, as well as the LPREMOVE task, I have a System restore point creation task scheduled for startup and again at 1100 hrs. Looking at the dates and times of the System restore points, it's clear that it hasn't run at startup or at the time scheduled. It does however coincide with my NTFS errors, so perhaps that has something to do with it. Although it says it ran at that time, it failed to create a restore Point. It has also produced a crop of Warnings in the Scheduler history (see screenshot). I have also examined the Scheduler entries carefully, and the explanation of the seemingly random starts is that the Conditions for run include a 10 minute elapsed period of machine idle time. This applies to both LPREMOVE and the SR task, and is why they kicked off at the same time - which coincides with the 55 errors. So one or the other is somehow responsible. I think I may well examine all the active Windows tasks in the Scheduler and see what their history and settings are.

The NTFS 55 errors are apparently caused by the scheduled SR (System restore) run.

When it ran automatically, it caused one 55 error at the exact time.

I then ran the scheduled SR interactively. It reported itself as successfully completed. HOWEVER, it produced another 55 error and DID NOT create a System Restore entry (verified with CCleaner and System Restore Explorer).

HOWEVER, when I installed System Restore Explorer, it created its own installation Restore Point. A further System Restore created by me before the errors using Computer\Properties\System Protection produced a bona fide Restore Point. I have then created yet another Restore Point using the same process AFTER the 55 errors and this has again produced a bona fide Restore Point (and no errors).

It thus seems clear that the Scheduled System Restore (SR) job runs, causes 55 errors but doesn't create a good Restore Point.

It is also notable, when examining the Restore Points, that although the scheduled SR job is supposed to run daily at startup and 1100 hrs, the Restore Points labelled "System: Scheduled Checkpoint" are many days apart, on 18th April and 1st May. Therefore the whole concept of producing regular daily Restore Points is wholly flawed.

I suppose the only way around this is to disable the scheduled SR job, and create Restore Points "manually".

I'd be grateful if anyone can throw any light upon this!