Re: System.AccessViolationException in .NET 2.0 application

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Andrea,

Thank you for the feedback.

Yes, I do not think this is a problem of your application unless you have
done some type of unmanaged code interop in your application, which may
corrupt the process memory(such as buffer overrun). If all your code are
managed, you should be okay.

In current situation, I do not think there is any way to resolve this
problem from your application code. Because it is the customer's
responsibility to prevent instable code from injecting other processes.
Once the 3rd party code subverted the process memory or code execution
path, we have no way to recover back, because we even do not know how the
malicious code subverted the process.

The recommended defensive solution is providing a detailed crash report.
For example, your crash report may obtain a minidump of your application,
also contain the module list of your process and the process list of the
system. These information will be useful to find out the criminal. This
technology is also taken by Microsoft products. For example, Windows Error
Report will send detailed crash information to the Microsoft when internet
is avaiable.

The 2 articles below use dbghelp.dll MiniDumpWriteDump API to generate dump
for an application:
"XCrashReport : Exception Handling and Crash Reporting - Part 3"
http://www.codeproject.com/debug/XCrashReportPt3.asp
http://www.debuginfo.com/tools/clrdump.html

After getting detailed reports from production machine, you may analysis
them to find out the root cause. Then, you may attach announcement with
your application to warn end users that certain 3rd party softwares may
collide/corrupt your applications.

Hope this helps.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


.

Relevant Pages