I've seen this terrible error when system has bad RAM. It's not supposed to happen, but it does when crappy drivers die