Attempted to read protected memory.

I randomly get the error message below when I attempt to view the contents of a SQL table using Visual Studio 2008 Professional. I am the only one that has access to this database. This error message does not happen every time I view the contents of an SQL table. This error message is not specific to any particular table. It seems like it is a random occurrence.

Does anyone have an idea on what could be causing this? What type of memory is it referring to? Hard drive or Ram? Any information on how to solve this error would be great.



Error.PNG
JohnnyBCJAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

edbedbCommented:
It refers to the RAM. Try reseating the modules or testing it.
0
13598Commented:
Try this:

Tools->Options

Debugging->General

uncheck option "Suppress JIT optimization on module load"

 
0
13598Commented:
And you can also try:
With the solution open click on Window and click on Reset Window Layout
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

JohnnyBCJAuthor Commented:
I guess what the biggest problem with this is that it doesn't always happen. Sometimes I can go a week without seeing the problem and other times I see it 5+ times a day. Today was the first time I noticed this problem for a while but I'm so annoyed with this error I want it solved.
edbedb:   It refers to the RAM. Try reseating the modules or testing it.

I will try this later. I found out a program from Microsoft used for testing the ram. For some reason I believe I've already tested out the ram and it came out good.

13598:   Try this:
Tools->Options
Debugging->General
uncheck option "Suppress JIT optimization on module load"


What exactly does this do?  Would this simply avoid the error instead of correcting it?
13598:   And you can also try:
With the solution open click on Window and click on Reset Window Layout


I've done this.
0
13598Commented:
It won't avoid the issue. It will correct it by providing memory management by allowing JIT optimization:
Managed code runs in the Common Language Runtime. The runtime offers a wide variety of services to your running code. In the usual course of events, it first loads and verifies the assembly to make sure the IL is okay. Then, just in time, as methods are called, the runtime arranges for them to be compiled to machine code suitable for the machine the assembly is running on, and caches this machine code to be used the next time the method is called. (This is called Just In Time, or JIT compiling, or often just Jitting.)
As the assembly runs, the runtime continues to provide services such as security, memory management, threading, and the like. The application is managed by the runtime.
0
JohnnyBCJAuthor Commented:
I haven't had this issue  since I've posted this question. I did not do any troubleshooting steps for this problem besides resetting the windows layout. This is one of those wonderful situations where I can get the error 5 times in one day and not get it again for 2 weeks.

Also note, I do not get this error when I try to compile the program. I get this error when trying to display the values in a SQL table (under Server Explorer). I do not get this error when trying to compile the program.

With that said, I just unchecked "Suppress JIT optimization on module load". I will wait a while to see if I get this error again. If I do, I'll let you know. Thanks again.
0
JohnnyBCJAuthor Commented:
I've still had this issue a few times since doing the suggestions proposed by the experts. Any other suggestions?
0
JohnnyBCJAuthor Commented:
I've changed computers and haven't had this problem since so I would assume it is some sort of hardware problem. The problem is solved because I will not be using the computer that gave me this problem.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Utilities

From novice to tech pro — start learning today.