I've found a similar issue. http://communities.vmware.com/thread/259842?start=0&tstart=0
it seems that this issue is already there for a long time without a solution.
According to this KB ( http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004233 ) the solution is to replace a file with a working one. This is stupid because if I would have a working one, I would not be looking for a solution...
Anyway, is anyone has some tips I would love to hear them.
This is kinda annoying and I have no idea how to monitor hardware failures on esx hosts.