Well Brian, can you suggest a better answer than a hardware problem given the following?

• It only happens on this machine.
• It doesn't happen when running a Terminal Server session.
• It started happening without any other change to the machine.

Access violations occur when a program attempts to read and/or write to memory not under its control. This can be the result of a program bug or hardware problem. Most access violations are harmless (although annoying), so we just report the error and continue, rather than halting the application, which we believe would be more disruptive. They will never go away entirely, as they can be created by race conditions in very specific hardware environments. Perhaps we should stop reporting them on the screen and simply log the occurrence in a file? However, that will mask problems that should be fixed, so I'm not sure it makes a lot of sense.

Perhaps you'd care to share the steps that can create this problem "on demand" with Steve and/or our Technical Support department as they have been requesting? The easiest way would probably be to record a video and send it to us using Jing.