Comment 40 for bug 120834

scorched3d doesn't crash X on my machine (though when I close it it logs a segfault in the game itself), suggesting that how to trigger this bug depends on one's hardware and/or software configuration, which could also account for the developers not being able to reproduce it. Is there anything OpenGL on the liveCD (screensavers?) that we could use to try and reproduce this in a clean environment?

I have also found that the keyboard LEDs go out and do not respond to the Caps Lock key, and that after each restart the mouse pointer works, though it freezes again before the screen goes off. The attached is a kernel log containing Alt+SysRq+t traces, but while those taken during the restarts list a process named Xorg, they don't appear to have a trace for it (one taken after it had all stopped didn't list an Xorg or x-session* process at all).

Bug 154343 appears to be a duplicate of this. Bug 68150 and (if we are counting the same symptoms on the i945gm as the same bug) bug 177518 might also be, but since there seems to be more than one X crash bug on the 965, I wouldn't label them as such without the logs.