Thursday, July 15, 2010 7:06 AM
Thursday, July 15, 2010 6:30 PMModerator
Yes, this is an access violation on WPF's render thread. Looking at this, we've seen similar crashes that were mainly due to a problem with the video driver. If you are seeing this only on a few machines, this is likely the case here as well.
The main suggestion I would have for you would be to check the video card in the affected machine(s), and see if there is a later video driver available for it, or if not, see if you can try a different video card in the affected machine(s).
Another possibility to resolve this would be to disable hardware rendering. The code path in the call stack above indicates we are using hardware rendering, so it's likely that disabling that would work around the issue. In WPF 3.x, the options for doing this are on a per-machine or per-window basis. To do it for the entire machine (as a test, not long term solution), see the "Disable Hardware Acceleration Option" section in the following MSDN link.
To do this programmatically on a per-window basis, you can set the RenderMode of the window's HwndTarget to RenderMode.SoftwareOnly. http://msdn.microsoft.com/en-us/library/system.windows.interop.hwndtarget.rendermode.aspx
You could have code like this that ran from your Window's Loaded event.
HwndSource hwndSource = PresentationSource.FromVisual(this) as HwndSource;
HwndTarget hwndTarget = hwndSource.CompositionTarget;
// force software rendering for this window
hwndTarget.RenderMode = RenderMode.SoftwareOnly;
Hope this helps,
Microsoft Communities Support
Thursday, July 22, 2010 7:13 AM
We tried disabling hardware rendering and it seems to have fixed the issue. Thanks for pointers.