Hi Folks,
This seems to be an odd problem and many see it in different situations and think they have found solutions in different ways. Maybe they have for themselves.
I just want to describe what I think was a simple configuration change that gave me this problem and no way to fix it until I understood what "sirkirby" was saying on April 12 in this thread.
I moved from a dual display system, 2 1280.1024 displays, with a single ATI Radeon 4650 (515MB) card that worked just beautifully to a dual display system, 2 1920x1080 displays and 2 ATI Radeon 5450 (1GB) cards. Needed the two cards since the single one
maxed out at 2540x1600. None if this is close to a gaming system or anything else with more than minimal 3D graphics.
Shouldn't have been any problem, all drivers newest and works with both types of cards, etc. But this problem immediately surfaced especially most everytime I simply started IE9.
Now, thanks to sirkirby, the problem has been totally gone for nearly a week. The solution is simple - don't use IE9 on the secondary display, Chrome seems just fine, but IE9 causes the messages and switches to non-Aero. Never happens when IE9 is on primary,
always happens when IE9 is on secondary. So, I adjusted how I used the displays.
Clearly a serious but in the system, IMO, but no one at MS seems to want to own up to it. I can't claim it's not somewhat driver relateed since I'm only using ATI cards, but sirkirby sees the same on nVidia as well.
So, in my case, I'm now ok since IE9 appears to be the only trigger for me. Others probably have other triggers and/or no choice where IE9 (or anything else) runs. Bad situation that needs a fix.
If any of you get a situation like I had where I could reproduce the problem quickly, it was easy after reading sirkirby's post to test on the primary monitor where the problem doesn't occur for me at all.
Good luck to you all, and I hope MS sees this as a problem worth fixing.
-marsha