If data was corrupted, could it still open and copy okay?
Posted on 2010-11-21
Here is the situation. We have three identical computers (same specs, bought together) that our volunteers use in our food banks. They are all brand new, same hardware, and Windows 7 on all of them. They all are yielding Event ID 55 NTFS errors in the event viewer on a somewhat regular basis.
We exchanged one under warranty just to be safe (we were given another exact replacement) and after a few days of use it started giving the ntfs error also.
All three machines run identical hardware and software. The only real thing imported to them was the data that all machines use. It's the same data set on all three, about 5 GB of data that includes various contact information, resource material for our clients, and pictures of each family we serve.
We are failing to understand how three machines (one which was replaced under warranty) can have the exact same error. It pretty much rules out a hardware problem. That leaves either actual data corruption or the fact the error is a false positive.
We spoke to Microsoft and they said they have encountered an issue of false positives on Windows 7 machines before and the development team is working on a fix. However, there are of course legitimate event 55's also.
The question is, the 5 Gb or so of data that we moved onto all three of these new machines . . . could the data (the common link on them) be corrupted and causing the issue? We wouldn't think so as the data resided on the old computers without a problem and we are able to access the data, use it, etc. It also copied to the machines okay and backs up okay. We also don't encounter any issues when working with the data (Docs open okay, PSTs open okay, access database opens okay, etc).
It's not really plausible to run the machines without the data to test as we are a volunteer food bank and have very limited resources and need our machines during the day. The machines run fine, no errors during use or any GUI errors. These errors are only observed in the event viewer. We have tried updating drivers, etc.