Jsmply
asked on
Does anyone notice Event ID 55 NTFS errors that seem to have NO actual error?
Hi All,
We have noticed an odd bug on Windows 7. Some (but not all) hardware configurations at our food bank are getting odd Event ID 55 NTFS errors. However, the hardware diagnostics check out fine and it's happening on several identical donated machines (all brand new with OEM Windows 7 images) so we have to conclude it's a Windows "issue."
We have done EXHAUSTIVE research online and on Technet and we see decent amount of people reporting this issue with other brand new machines (Lenovo, HP, etc) and they reference various MS Hotfixes, etc. We are trying to narrow down a cause before just installing random hotfixes.
It seems to occur at random, once to several times a day. Chkdsk finds nothing wrong, but something keeps making Windows produce these Event 55 messages in the System Log.
Any help would be sincerely appreciated. Thanks!
We have noticed an odd bug on Windows 7. Some (but not all) hardware configurations at our food bank are getting odd Event ID 55 NTFS errors. However, the hardware diagnostics check out fine and it's happening on several identical donated machines (all brand new with OEM Windows 7 images) so we have to conclude it's a Windows "issue."
We have done EXHAUSTIVE research online and on Technet and we see decent amount of people reporting this issue with other brand new machines (Lenovo, HP, etc) and they reference various MS Hotfixes, etc. We are trying to narrow down a cause before just installing random hotfixes.
It seems to occur at random, once to several times a day. Chkdsk finds nothing wrong, but something keeps making Windows produce these Event 55 messages in the System Log.
Any help would be sincerely appreciated. Thanks!
ASKER
It can be, but if you do some Google searching or read around Technet it looks like there are cases where it is caused unnecessarily in Windows 7. In our case, we are seeing it on brand new machines (and several, all identical). So it's hard to believe it's hardware related, etc.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Dacasey. Do you recall the make/models by chance?
Like I said, we have seen it on several new machines so unless they ALL have defective SATA cables we can't see it being hardware related. Some of them were donated/delivered a few months apart also.
With the firewire device connected, was it the Windows Volume it was referencing in the event 55? Did you eventually ignore it? We are getting the following description:
"The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume WIN7."
Where Win7 is the Windows volume.
Like I said, we have seen it on several new machines so unless they ALL have defective SATA cables we can't see it being hardware related. Some of them were donated/delivered a few months apart also.
With the firewire device connected, was it the Windows Volume it was referencing in the event 55? Did you eventually ignore it? We are getting the following description:
"The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume WIN7."
Where Win7 is the Windows volume.
The issue with firwire was on an HP 6000 series machine. The error did reference the windows disk. Got the same message as you. I shutdown the machine and disconnected everything (firewire and usb disks). The system booted properly. Experimented and found that when more than one firewire device was connected I got the error. I could repeat this. This turned into the old Doctor it hurts when I put my arm up story; I told the client to work with one firewire device at a time. No complaints.
The SATA cable was on a GigaByte motherboard overclocked machine. The error has not appeared since replacing the SATA cable.
The SATA cable was on a GigaByte motherboard overclocked machine. The error has not appeared since replacing the SATA cable.
ASKER
Thx. Was the HP on windows 7?
ASKER
We have found cases of what dacasey reported above with firewire devices. Further, found a lot more links of people with the same problem with both SSD and normal hard drives. All point to a MS bug. http://superuser.com/questions/116024/spurious-alleged-file-corruption-on-windows-7
ASKER
Thx
Looks like it is way more than some benign issue!!
http://eventid.net/display.asp?eventid=55&source=
HTH,
Kent