The memory could not be "written"

umesh chape

My Application is C# winform

I am facing below error at the time of form close and end of Dispose() method .

The instruction at "0xXXXXXXXX" referenced memory at "0xXXXXXXXX", The memory could not be "written". Click on OK to terminate that program.

Please help me how to avoid / catch this error .

Thanks .

9 Replies

Know the answer? Post it — somebody with the same question will find it here.

umesh chape13y ago
Dear All ,

Still hoping for solution.

Please help .
Vulpes13y ago
If you're creating any 3rd party components, then you should be calling Dispose() on them to release any unmanaged resources.

If it's still no better, then Environment.Exit(0) will kill the process stone dead though I'd only use that as a last resource.
umesh chape13y ago
I am not callling Dispose() . This is on form itself .

Already called Application.Exit().
Vulpes13y ago
In that case, you'll need to try and find a workaround yourself which doesn't cause the error.

The trouble with errors like this is that they bubble up from underlying unmanaged code (typically COM) and so are very difficult to debug. Also they destabilize the system and so it's not a good idea to catch and 'swallow' them because they usually surface again later.

You mentioned in your opening post that the error occurred "at the time of form close and end of Dispose() method".

Are you calling Dispose() here on 3rd party components (which you should generally do) or on the Form itself (which is unnecessary unless it's a modal dialog box)?

Also, are you quitting the entire application - in which case you could try Application.Exit() or Environment.Exit(0) as an alternative - or just closing a single form within the application?
umesh chape13y ago
I already contacted vendor and this issue is not from there site as per them and it is not possible to go back again with old version.
umesh chape13y ago
Thanks Vulpes .

You mean to say There is No Solution for this error .
Vulpes13y ago
You can't catch 'write protection' errors such as this which are invariably fatal.

I'd contact the vendor to see if there's a patch or workaround for what is likely to be a bug in the API. If there isn't one, I'd go back to using the previous version.
umesh chape13y ago
Thanks Sivaraman for Reply .

Yes. I closed everything from the form .

I am using some third party API . The previous API are working fine but these new updates and facing Issue .
If old API are installed on the system previously then I am not facing this issue but If I installed directly new API then I am facing the Issue .

Please help me how to avoid / catch this error .
Sivaraman Dhamodaran13y ago
I hope that you are accessing something from the form that is already closed (Wiped from memory).