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

http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?ID=14

Possible Solution
http://blogs.technet.com/apurdon/archive/2008/01/31/is-your-sharepoint-server-reporting-event-ids-7076-6398-6482.aspx

Possible Workaround

Indeed, I noticed that SPAdmin throws a Memory violation exception and than start to write all these error to Event Log. I liked the solution in

http://soerennielsen.wordpress.com/2007/06/29/%e2%80%9dnot-enough-storage%e2%80%9d-event-log-error/

The author says:

However a simple work around is to schedule a task to restart your SPTimer service once a day. Not the server, not SharePoint, just the service.

There should no adverse side-effects to this as it is a proper service shutdown that should allow any running jobs to terminate prior to termination.

So, create a bat file “Restart SPTimer.bat” containing these lines:

net stop “Windows SharePoint Services Timer”
net start “Windows SharePoint Services Timer”

Schedule it to run once every night with the windows task scheduler.

Simple does it. Don’t care to waste any more time on this issue, don’t you all agree?