I have seen this error as well - happened on al older MacBook Pro late 2008.
I thinking it is this one:...