"Attempted to read or write protected memory" since 10 days...

  • Thread starter Thread starter Pieter
  • Start date Start date
P

Pieter

Hi,

Since 10 days (the first time was the 10th of november) I have some weird
exception happening in an application here:
All (except 1 of the total of 5) users had this error now 1 of 2 times
during the last 10 days. It happens mostly during startup or closing of the
application, but sometimes just in the middle of nowhere. It doesn't point
to anyting special. I don't get a clue...

It's a Windows Forms VB.NET 2005 application. I roll out updates regulary
(once a week), but nothing special has changed in the last update before the
first error.

Does anybody has any idea why this happens?


Thansk a lot in advance, any help will be really appreciated,

Pieter



This is the full exception:

Exception Source: System
Exception Type: System.AccessViolationException
Exception Message: Attempted to read or write protected memory. This is
often an indication that other memory is corrupt.
Exception Target Site: WSAGetOverlappedResult

---- Stack Trace ----
System.Net.OSSOCK.WSAGetOverlappedResult(socketHandle As SafeCloseSocket,
overlapped As IntPtr, bytesTransferred As UInt32&, wait As Boolean, ignored
As IntPtr)
Ghost.exe: N 00000
System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(errorCode
As UInt32, numBytes As UInt32, nativeOverlapped As NativeOverlapped*)
Ghost.exe: N 00177
System.Threading._IOCompletionCallback.PerformIOCompletionCallback(errorCode
As UInt32, numBytes As UInt32, pOVERLAP As NativeOverlapped*)
Ghost.exe: N 00103
 
Great! That does indeed help!! :-)
We have NOD32 too...

I had this error in the eventlog:
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 21/11/2006
Time: 11:35:13
User: N/A
Computer:
Description:
Faulting application myapplication.exe, version 1.0.0.0, stamp 455c858c,
faulting module imon.dll, version 2.50.25.0, stamp 42ae8989, debug? 0, fault
address 0x0000cd29.


Apparently that imon.dll file caused the trouble.

It's just weird it happened only since 10 days, and not before. The
application and NOD32 are already more than a year istsalled on the
clients...

Thanks a lot!

Pieter
 
Back
Top