EDN Admin
Well-known member
We have a rather large VB.NET accounting application that crashes occasionally for some customers. I have now been able to reproduce this particular almost 100% in my test environment using certain data. The crash happens when clicking a list box after printing
a report. The form involved has a list box listing available reports. You select one or more reports from the list box and click the print button. After printing, if you click the list box again, the program crashes, with an exception that does not seem like
one VB.NET should even be able to produce.
The exception message is: "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
The call stack is:
<pre>1. System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
2. System.Windows.Forms.NativeWindow.DefWndProc(Message& m) [IL offset: 0x3e]
3. System.Windows.Forms.Control.DefWndProc(Message& m) [IL offset: 0x0]
4. System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks) [IL offset: 0x1f]
5. System.Windows.Forms.Control.WndProc(Message& m) [IL offset: 0x5fe]
6. System.Windows.Forms.ListBox.WndProc(Message& m) [IL offset: 0x268]
7. System.Windows.Forms.Control+ControlNativeWindow.OnMessage(Message& m) [IL offset: 0x0]
8. System.Windows.Forms.Control+ControlNativeWindow.WndProc(Message& m) [IL offset: 0x8e]
9. System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) [IL offset: 0x25]
[/code]
To further troubleshoot this, I have run the VB.NET application under windbg to get more detailed info. Doing this, I discovered that the crash actually seems to happen in a few different places.
One crash is:
<pre>(cc4.144c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=feeefeee ebx=0fb60020 ecx=00000000 edx=00000001 esi=00000002 edi=7e379ed9
eip=77419796 esp=0012ed74 ebp=0012edb4 iopl=0 nv up ei ng nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010286
comctl32!ListBox_TrackMouse+0x579:
77419796 f6404420 test byte ptr [eax+44h],20h ds:0023:feeeff32=??[/code]
The call stack in windbg is the following:
<pre>0:000> k
ChildEBP RetAddr
0012edb4 773e1424 comctl32!ListBox_TrackMouse+0x579
0012ee34 7e368734 comctl32!ListBox_WndProc+0x6ac
0012ee60 7e368816 USER32!InternalCallWinProc+0x28
0012eec8 7e37a013 USER32!UserCallWinProcCheckWow+0x150
0012eef8 7e37a039 USER32!CallWindowProcAorW+0x98
0012ef18 7b1c8cd3 USER32!CallWindowProcW+0x1b
0012ef70 7b1c8c2c System_Windows_Forms_ni+0x1f8cd3
0012ef88 7ba2a11f System_Windows_Forms_ni+0x1f8c2c
0012efe8 7ba25ec9 System_Windows_Forms_ni+0xa5a11f
0012f094 7b1c86a0 System_Windows_Forms_ni+0xa55ec9
0012f09c 7b1c8621 System_Windows_Forms_ni+0x1f86a0
0012f0b0 7b1c84fa System_Windows_Forms_ni+0x1f8621
0012f114 7e368734 System_Windows_Forms_ni+0x1f84fa
0012f140 7e368816 USER32!InternalCallWinProc+0x28
0012f1a8 7e3689cd USER32!UserCallWinProcCheckWow+0x150
0012f208 7e368a10 USER32!DispatchMessageWorker+0x306
0012f218 03d3676a USER32!DispatchMessageW+0xf[/code]
The managed code stack from windbg is the following:
<pre>0:000> !sos.clrstack
OS Thread Id: 0x144c (0)
ESP EIP
0012ef38 77419796 [InlinedCallFrame: 0012ef38] System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
0012ef34 7b1c8cd3 System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
0012ef78 7b1c8c2c System.Windows.Forms.Control.DefWndProc(System.Windows.Forms.Message ByRef)
0012ef7c 7b6f73ba System.Windows.Forms.Control.WmMouseDown(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
0012ef98 7ba2a11f System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
0012ef9c 7ba25ec9 [InlinedCallFrame: 0012ef9c]
0012f09c 7b1c86a0 System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
0012f0a4 7b1c8621 System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
0012f0b8 7b1c84fa System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
0012f24c 003b217b [NDirectMethodFrameStandalone: 0012f24c] System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
0012f25c 7b1d8d2e System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32, Int32, Int32)
0012f2f8 7b1d8997 System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
0012f34c 7b1d87e1 System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
0012f37c 7b6eddec System.Windows.Forms.Application.Run(System.Windows.Forms.ApplicationContext)
0012f388 5e547c0d Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
0012f3b4 5e54817f Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
0012f3e0 5e546eb0 Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])
0012f43c 306223e2 Briljant.My.MyApplication.Main(System.String[])
0012f688 79e71b4c [GCFrame: 0012f688]
[/code]
Another crash is:
<pre>(384.f14): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=001d0b14 ebx=1937ef48 ecx=0012ed68 edx=7c90e514 esi=00000001 edi=00000200
eip=774193da esp=0012ed74 ebp=0012edb4 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
comctl32!ListBox_TrackMouse+0x1bd:
774193da f6435504 test byte ptr [ebx+55h],4 ds:0023:1937ef9d=??
0:000> k
ChildEBP RetAddr
0012edb4 773e1424 comctl32!ListBox_TrackMouse+0x1bd
0012ee34 7e368734 comctl32!ListBox_WndProc+0x6ac
0012ee60 7e368816 USER32!InternalCallWinProc+0x28
0012eec8 7e37a013 USER32!UserCallWinProcCheckWow+0x150
0012eef8 7e37a039 USER32!CallWindowProcAorW+0x98
0012ef18 7b1c8cd3 USER32!CallWindowProcW+0x1b
0012ef70 7b1c8c2c System_Windows_Forms_ni+0x1f8cd3
0012ef88 7ba2a11f System_Windows_Forms_ni+0x1f8c2c
0012efe8 7ba25ec9 System_Windows_Forms_ni+0xa5a11f
0012f094 7b1c86a0 System_Windows_Forms_ni+0xa55ec9
0012f09c 7b1c8621 System_Windows_Forms_ni+0x1f86a0
0012f0b0 7b1c84fa System_Windows_Forms_ni+0x1f8621
0012f114 7e368734 System_Windows_Forms_ni+0x1f84fa
0012f140 7e368816 USER32!InternalCallWinProc+0x28
0012f1a8 7e3689cd USER32!UserCallWinProcCheckWow+0x150
0012f208 7e368a10 USER32!DispatchMessageWorker+0x306
0012f218 0b466456 USER32!DispatchMessageW+0xf
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f234 7b1d8d2e <Unloaded_UIGP.DLL>+0xb466355
0012f2e8 7b1d8997 System_Windows_Forms_ni+0x208d2e
0012f340 7b1d87e1 System_Windows_Forms_ni+0x208997
0:000> !sos.clrstack
OS Thread Id: 0xf14 (0)
ESP EIP
0012ef38 774193da [InlinedCallFrame: 0012ef38] System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
0012ef34 7b1c8cd3 System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
0012ef78 7b1c8c2c System.Windows.Forms.Control.DefWndProc(System.Windows.Forms.Message ByRef)
0012ef7c 7b6f73ba System.Windows.Forms.Control.WmMouseDown(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
0012ef98 7ba2a11f System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
0012ef9c 7ba25ec9 [InlinedCallFrame: 0012ef9c]
0012f09c 7b1c86a0 System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
0012f0a4 7b1c8621 System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
0012f0b8 7b1c84fa System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
0012f24c 01c2cf7b [NDirectMethodFrameStandalone: 0012f24c] System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
0012f25c 7b1d8d2e System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32, Int32, Int32)
0012f2f8 7b1d8997 System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
0012f34c 7b1d87e1 System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
0012f37c 7b6eddec System.Windows.Forms.Application.Run(System.Windows.Forms.ApplicationContext)
0012f388 5e547c0d Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
0012f3b4 5e54817f Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
0012f3e0 5e546eb0 Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])
0012f43c 306223e2 Briljant.My.MyApplication.Main(System.String[])
0012f688 79e71b4c [GCFrame: 0012f688]
[/code]
As you can see, both of these happen in comctl32.dll in code related to handling the click in the listbox. Both also seem to have the same managed mode code stack.
I tried running gflags and enabling some checks I thought might help: "Enable page heap", "Enable heap tail checking", "Enable heap free checking", "Enable heap parameter checking", "Enable heap validation on call",
but this did not produce any additional messages. <br/>
I also noticed that there are two instances of comctl32.dll loaded in my application, but so far I have not been able to determine that that is abnormal:
<pre>0:000> lmf mcomctl*
start end module name
5d5b0000 5d64a000 comctl32_5d5b0000 C:WINDOWSsystem32comctl32.dll
773c0000 774c3000 comctl32 C:WINDOWSWinSxSx86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202comctl32.dll
[/code]
The error message indicates that the error is due to corrupt memory. How can I track down what is corrupting memory in my application?
View the full article
a report. The form involved has a list box listing available reports. You select one or more reports from the list box and click the print button. After printing, if you click the list box again, the program crashes, with an exception that does not seem like
one VB.NET should even be able to produce.
The exception message is: "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
The call stack is:
<pre>1. System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
2. System.Windows.Forms.NativeWindow.DefWndProc(Message& m) [IL offset: 0x3e]
3. System.Windows.Forms.Control.DefWndProc(Message& m) [IL offset: 0x0]
4. System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks) [IL offset: 0x1f]
5. System.Windows.Forms.Control.WndProc(Message& m) [IL offset: 0x5fe]
6. System.Windows.Forms.ListBox.WndProc(Message& m) [IL offset: 0x268]
7. System.Windows.Forms.Control+ControlNativeWindow.OnMessage(Message& m) [IL offset: 0x0]
8. System.Windows.Forms.Control+ControlNativeWindow.WndProc(Message& m) [IL offset: 0x8e]
9. System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) [IL offset: 0x25]
[/code]
To further troubleshoot this, I have run the VB.NET application under windbg to get more detailed info. Doing this, I discovered that the crash actually seems to happen in a few different places.
One crash is:
<pre>(cc4.144c): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=feeefeee ebx=0fb60020 ecx=00000000 edx=00000001 esi=00000002 edi=7e379ed9
eip=77419796 esp=0012ed74 ebp=0012edb4 iopl=0 nv up ei ng nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010286
comctl32!ListBox_TrackMouse+0x579:
77419796 f6404420 test byte ptr [eax+44h],20h ds:0023:feeeff32=??[/code]
The call stack in windbg is the following:
<pre>0:000> k
ChildEBP RetAddr
0012edb4 773e1424 comctl32!ListBox_TrackMouse+0x579
0012ee34 7e368734 comctl32!ListBox_WndProc+0x6ac
0012ee60 7e368816 USER32!InternalCallWinProc+0x28
0012eec8 7e37a013 USER32!UserCallWinProcCheckWow+0x150
0012eef8 7e37a039 USER32!CallWindowProcAorW+0x98
0012ef18 7b1c8cd3 USER32!CallWindowProcW+0x1b
0012ef70 7b1c8c2c System_Windows_Forms_ni+0x1f8cd3
0012ef88 7ba2a11f System_Windows_Forms_ni+0x1f8c2c
0012efe8 7ba25ec9 System_Windows_Forms_ni+0xa5a11f
0012f094 7b1c86a0 System_Windows_Forms_ni+0xa55ec9
0012f09c 7b1c8621 System_Windows_Forms_ni+0x1f86a0
0012f0b0 7b1c84fa System_Windows_Forms_ni+0x1f8621
0012f114 7e368734 System_Windows_Forms_ni+0x1f84fa
0012f140 7e368816 USER32!InternalCallWinProc+0x28
0012f1a8 7e3689cd USER32!UserCallWinProcCheckWow+0x150
0012f208 7e368a10 USER32!DispatchMessageWorker+0x306
0012f218 03d3676a USER32!DispatchMessageW+0xf[/code]
The managed code stack from windbg is the following:
<pre>0:000> !sos.clrstack
OS Thread Id: 0x144c (0)
ESP EIP
0012ef38 77419796 [InlinedCallFrame: 0012ef38] System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
0012ef34 7b1c8cd3 System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
0012ef78 7b1c8c2c System.Windows.Forms.Control.DefWndProc(System.Windows.Forms.Message ByRef)
0012ef7c 7b6f73ba System.Windows.Forms.Control.WmMouseDown(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
0012ef98 7ba2a11f System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
0012ef9c 7ba25ec9 [InlinedCallFrame: 0012ef9c]
0012f09c 7b1c86a0 System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
0012f0a4 7b1c8621 System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
0012f0b8 7b1c84fa System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
0012f24c 003b217b [NDirectMethodFrameStandalone: 0012f24c] System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
0012f25c 7b1d8d2e System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32, Int32, Int32)
0012f2f8 7b1d8997 System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
0012f34c 7b1d87e1 System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
0012f37c 7b6eddec System.Windows.Forms.Application.Run(System.Windows.Forms.ApplicationContext)
0012f388 5e547c0d Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
0012f3b4 5e54817f Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
0012f3e0 5e546eb0 Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])
0012f43c 306223e2 Briljant.My.MyApplication.Main(System.String[])
0012f688 79e71b4c [GCFrame: 0012f688]
[/code]
Another crash is:
<pre>(384.f14): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=001d0b14 ebx=1937ef48 ecx=0012ed68 edx=7c90e514 esi=00000001 edi=00000200
eip=774193da esp=0012ed74 ebp=0012edb4 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
comctl32!ListBox_TrackMouse+0x1bd:
774193da f6435504 test byte ptr [ebx+55h],4 ds:0023:1937ef9d=??
0:000> k
ChildEBP RetAddr
0012edb4 773e1424 comctl32!ListBox_TrackMouse+0x1bd
0012ee34 7e368734 comctl32!ListBox_WndProc+0x6ac
0012ee60 7e368816 USER32!InternalCallWinProc+0x28
0012eec8 7e37a013 USER32!UserCallWinProcCheckWow+0x150
0012eef8 7e37a039 USER32!CallWindowProcAorW+0x98
0012ef18 7b1c8cd3 USER32!CallWindowProcW+0x1b
0012ef70 7b1c8c2c System_Windows_Forms_ni+0x1f8cd3
0012ef88 7ba2a11f System_Windows_Forms_ni+0x1f8c2c
0012efe8 7ba25ec9 System_Windows_Forms_ni+0xa5a11f
0012f094 7b1c86a0 System_Windows_Forms_ni+0xa55ec9
0012f09c 7b1c8621 System_Windows_Forms_ni+0x1f86a0
0012f0b0 7b1c84fa System_Windows_Forms_ni+0x1f8621
0012f114 7e368734 System_Windows_Forms_ni+0x1f84fa
0012f140 7e368816 USER32!InternalCallWinProc+0x28
0012f1a8 7e3689cd USER32!UserCallWinProcCheckWow+0x150
0012f208 7e368a10 USER32!DispatchMessageWorker+0x306
0012f218 0b466456 USER32!DispatchMessageW+0xf
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f234 7b1d8d2e <Unloaded_UIGP.DLL>+0xb466355
0012f2e8 7b1d8997 System_Windows_Forms_ni+0x208d2e
0012f340 7b1d87e1 System_Windows_Forms_ni+0x208997
0:000> !sos.clrstack
OS Thread Id: 0xf14 (0)
ESP EIP
0012ef38 774193da [InlinedCallFrame: 0012ef38] System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
0012ef34 7b1c8cd3 System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)
0012ef78 7b1c8c2c System.Windows.Forms.Control.DefWndProc(System.Windows.Forms.Message ByRef)
0012ef7c 7b6f73ba System.Windows.Forms.Control.WmMouseDown(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32)
0012ef98 7ba2a11f System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
0012ef9c 7ba25ec9 [InlinedCallFrame: 0012ef9c]
0012f09c 7b1c86a0 System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
0012f0a4 7b1c8621 System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
0012f0b8 7b1c84fa System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
0012f24c 01c2cf7b [NDirectMethodFrameStandalone: 0012f24c] System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
0012f25c 7b1d8d2e System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32, Int32, Int32)
0012f2f8 7b1d8997 System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
0012f34c 7b1d87e1 System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
0012f37c 7b6eddec System.Windows.Forms.Application.Run(System.Windows.Forms.ApplicationContext)
0012f388 5e547c0d Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
0012f3b4 5e54817f Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
0012f3e0 5e546eb0 Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])
0012f43c 306223e2 Briljant.My.MyApplication.Main(System.String[])
0012f688 79e71b4c [GCFrame: 0012f688]
[/code]
As you can see, both of these happen in comctl32.dll in code related to handling the click in the listbox. Both also seem to have the same managed mode code stack.
I tried running gflags and enabling some checks I thought might help: "Enable page heap", "Enable heap tail checking", "Enable heap free checking", "Enable heap parameter checking", "Enable heap validation on call",
but this did not produce any additional messages. <br/>
I also noticed that there are two instances of comctl32.dll loaded in my application, but so far I have not been able to determine that that is abnormal:
<pre>0:000> lmf mcomctl*
start end module name
5d5b0000 5d64a000 comctl32_5d5b0000 C:WINDOWSsystem32comctl32.dll
773c0000 774c3000 comctl32 C:WINDOWSWinSxSx86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202comctl32.dll
[/code]
The error message indicates that the error is due to corrupt memory. How can I track down what is corrupting memory in my application?
View the full article