Curiously, a search on the web for the image name “qcdx9um8960” returns several results referencing Windows Phone 8 and the WebBrowser control. Gathering the answers and replies (some even by MSFT), here is what you should possibly look into:
- If you upgraded your application from Windows Phone 6/7 to 8, make sure you are not still referencing any 6/7 DLLs. 1
- Make sure you aren’t testing or publishing your software in Debug mode. There is a “qcdx9um8960.pdb” file that might be missing, causing the access violation. 1
- “…there is a possible race condition known issue if the app has multiple copies of WebBrowser open. See if your code perhaps inadvertently makes more than one instance.” 1
- That image, “qcdx9um8960” is referencing a Qualcomm DirectX driver DLL. Perhaps it’s not the WebBrowser component’s fault, but the DirectX driver it might be using to render the web pages. 2
- The name of the image suggests that the crash is happening on devices powered by a Qualcomm Snapdragon S4 Plus with model number MSM8960. 3
- Assuming the processor above, and cross referencing Windows phones that use that chip, you’re likely looking at the issue occurring on the Nokia Lumia 920T. 3 That’s not to say that the driver doesn’t work on several processor architectures or phones.
There are several other hits regarding crashes and issues debugging in the presence of that DLL, so unfortunately for you, I think you might be at the mercy of some third party software that has a few unresolved issues.
References
1 Access Violation since updated to WP8