Seriously though, we got the issue pretty much figured out. It occurs roughly when you pass the 70 hour gaming mark (console-on/game time, including paused mode time), and only in certain scenes. That's why it was never reproduced during our in-house testing. Should be fixable through code though, and it's good news for your save-games and the 360 crowd.
