Attempted to read or write protected memory. This is often an indication that other memory is corrup

Lee Mellinger

Guest

Posts: n/a

20th Dec 2007

We're randomly getting this error in a win form app: "Attempted to read
or write protected memory. This is often an indication that other memory
is corrupt".

This app was recently recompiled in VS 2005/.NET 2.0 from .NET 1.1. This
did not occur in the .NET 1.1 version. There are many postings on this
error going back nearly a year, but I've not see a resolution.

We've download and installed the hot fix referenced in KB923028
(303312_intl_i386_zip.exe), but the problem persists randomly and cannot
be replicated.

Has there been any further information on this from Microsoft?

*** Sent via Developersdex http://www.developersdex.com ***

« DoEvents in Windows Service | Grid/spreadsheet control that binds to a System.Data.Dataset (multi-Datatable)and automagically creates multiple sheets »

Thread Tools
Show Printable Version Email this Page
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is On HTML code is Off Trackbacks are On Pingbacks are On Refbacks are Off Forum Rules

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Attempted to read or write protected memory. This is often an indication that other memory is corrupt	www.gusse.net	Microsoft Dot NET Framework	10	7th Sep 2009 08:06 PM
Attempted to read or write protected memory. This is often an indication that other memory is corrupt	Sugandh Jain	Microsoft C# .NET	6	10th Dec 2007 09:47 PM
Attempted to read or write protected memory. This is often an indication that other memory is corrup	Sanjeev Rane	Microsoft VB .NET	0	12th Dec 2006 11:06 AM
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.	Dhruba Bandopadhyay	Microsoft ASP .NET	0	12th May 2006 03:24 PM
Attempted to read or write protected memory. This is often an indication that other memory has been corrupted.	Dick van der Sar	Microsoft C# .NET	3	3rd May 2005 04:54 PM