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

Question

0.00/5 (No votes)

See more:

Hi all,

My first post, wish it was not a cry for help but hey what can you do.

I am getting an

{"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."} error and I have no clue where to look. Anyone can make something out of the exception?  

 at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
   at System.Windows.Forms.Control.DefWndProc(Message& m)
   at System.Windows.Forms.Control.WmCommand(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ComboBox.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(Form mainForm)

What I have tried:

I tried to isolate the error but no luck, and no clue where to look.

Posted 17-Feb-16 8:27am

Member 10629574

Updated 18-Feb-16 8:40am

Maciej Los

v2

Add a Solution

Comments

Maciej Los 17-Feb-16 14:47pm

Does your debugger is corrupted?
https://msdn.microsoft.com/en-us/library/sc65sadd.aspx

Foothill 17-Feb-16 16:24pm

Are you getting this error when running in the debugger and do you get the same error when not using the debugger?

Dave Kreskowiak 17-Feb-16 18:34pm

Show the code that's throwing this error. Without that, everyone is just guessing.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Member 10629574 · Answer 1 · 2016-02-18T08:39:00

Solution 1

Thnx for your comments guys, I found the problem. It was when debugging, I noticed in the Combobox being mentioned and that guided me in the right direction.

Posted 18-Feb-16 8:39am

Member 10629574