This is the meaning of the error code.
#define STATUS_ACCESS_VIOLATION ((NTSTATUS)0xC0000005 L)
Not sure it will make you any wiser, though.
[Update]
There is a difference between a working system and one that fails.
The trick is to find this difference.
- It might be worth looking into what kind of access rights they have set on the client computer.
If you can, set local admin rights an try to run for a while and see if the problem goes away. - If it is possible you can install your own computer with the deployed solution, not development, and test it both at home and at the client. If you still have have problem at your clients site, but not in your home environment, the problem should be in the database.
If no problem occur, then you need to look into the specific computer setup, especially if not all client computers have a problem. - Check which virus protection software the client is using.
Is this different from any other client?
[Update]
The steps below can be used of you get a blue screen of death, but it doesn't register anything if you get a regular dialog box with an error message.
You can try to enable the crash dump in order to get more error information.
- Go to Start, in the Search Box type: sysdm.cpl, press Enter.
- Under the Advanced tab, click on the Startup and Recovery Settings... button.
- Ensure that Automatically restart is unchecked.
- Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
- Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
- OK your way out.
- Reboot if changes have been made.
[Updated]
A more graphical instruction:
How to configure Windows to create MiniDump files[
^]
Here is some information how to analyze the crash dump in VS2010.
Application Crash Dump Analysis (Windows 7)[
^]