Same here, too. What is odd is that it doesn't happen every time, only some of the time, which makes it hard to understand as a IE patch problem...