Share via

Microsoft .NetFramework unhandled exception System.OutOfMemory

Anonymous
2012-06-24T15:50:02+00:00

I keep getting a pop-up box telling me:

Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.

Exception of type 'System.OutOfMemory Exception' was thrown.

Details:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.

   at System.Diagnostics.NtProcessInfoHelper.GetProcessInfos()

   at System.Diagnostics.ProcessManager.GetProcessInfos(String machineName)

   at System.Diagnostics.Process.GetProcesses(String machineName)

   at System.Diagnostics.Process.GetProcessesByName(String processName, String machineName)

   at System.Diagnostics.Process.GetProcessesByName(String processName)

   at PhotoCanvas.MainWindow.WTSSession_WTS_Event(Object sender, EventArgs e)

   at PhotoCanvas.Helpers.WTSSessionChangeHandler.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)

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.269 (RTMGDR.030319-2600)

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

Canvas

    Assembly Version: 2.0.3917.26233

    Win32 Version: 2.0.3917.26233

    CodeBase: file:///C:/Program%20Files%20(x86)/hewlett-packard/touchsmart/canvas/canvas.exe

PresentationFramework

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.275

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll

WindowsBase

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.275 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll

System

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.269 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

PresentationCore

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.275 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll

System.Xaml

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1 built by: RTMRel

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll

HP.TouchSmart.InfoviewWindow

    Assembly Version: 1.3.0.0

    Win32 Version: 1.3.0.0

    CodeBase: file:///C:/Windows/assembly/GAC_32/HP.TouchSmart.InfoviewWindow/1.3.0.0__436e80ff5a6fd94d/HP.TouchSmart.InfoviewWindow.dll

System.Windows.Forms

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.278 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System.Drawing

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.282 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

System.Core

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.233 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System.Configuration

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Xml

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.233 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

LUZHP

    Assembly Version: 2.0.0.0

    Win32 Version: 2.0.0.0

    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/LUZHP/2.0.0.0__5b744bac3e20de8f/LUZHP.dll

PresentationFramework.Aero

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1 built by: RTMRel

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.Aero/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.Aero.dll

fybqtdw0

    Assembly Version: 1.3.0.0

    Win32 Version: 4.0.30319.269 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

agdvn2yn

    Assembly Version: 1.3.0.0

    Win32 Version: 4.0.30319.269 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

drl1qk1p

    Assembly Version: 1.3.0.0

    Win32 Version: 4.0.30319.269 built by: RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

UIAutomationProvider

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1 built by: RTMRel

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationProvider/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationProvider.dll

UIAutomationTypes

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1 built by: RTMRel

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/UIAutomationTypes/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationTypes.dll

System.Data

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.237 (RTMGDR.030319-2300)

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll

System.Transactions

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll

System.EnterpriseServices

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll

System.Speech

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1 built by: RTMRel

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Speech/v4.0_4.0.0.0__31bf3856ad364e35/System.Speech.dll

ShellLibrary

    Assembly Version: 0.0.0.0

    Win32 Version:

    CodeBase: file:///C:/Program%20Files%20(x86)/hewlett-packard/touchsmart/canvas/ShellLibrary.DLL

msvcm90

    Assembly Version: 9.0.30729.6161

    Win32 Version: 9.00.30729.6161

    CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57/msvcm90.dll

Accessibility

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.1 built by: RTMRel

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

I don't understand what any of this means, can someone please help?  Thanks!

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

  1. Anonymous
    2012-06-25T07:39:14+00:00

    Hi,

    1. When exactly do you get the pop-up?
    2. Did you make any changes to the computer prior to the issue?

    Method 1I would suggest you to try the steps from the following link:

    Diagnosing memory problems on your computer

    http://windows.microsoft.com/en-us/windows7/diagnosing-memory-problems-on-your-computer

    Method 2

    I would suggest you to perform clean boot and check if the issue persists.

    How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

    http://support.microsoft.com/kb/929135

    Note: Follow step 7 from the clean boot article KB929135 to reset the computer to normal mode.

    0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2013-05-16T20:50:43+00:00

    Hi Vijay

    I got the same message again and again while using GIS application and running a model. I tried both methods you discussed above and run the model again. The problem still remains the same, don't know what to do? Just stucked at this step from last 3 days. Any further recommendations??

    I also tried to perform the debugging as suggested in that error but don't have any clue where I could get the .config file. Any simpler steps to perform the following too??

    Error:

    "Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.

    Item has already been added. Key in dictionary:"RNGB". Key being added:"RNGB".

    .........................

    .......................

    ......................

    At the end

    ************** JIT Debugging **************

    To enable just-in-time (JIT) debugging, the .config file for this

    application or computer (machine.config) must have the

    jitDebugging value set in the system.windows.forms section.

    The application must also be compiled with debugging

    enabled.

    For example:

    <configuration>

        <system.windows.forms jitDebugging="true" />

    </configuration>

    When JIT debugging is enabled, any unhandled exception

    will be sent to the JIT debugger registered on the computer

    rather than be handled by this dialog box.

    Thanks for your time.

    Sham

    0 comments
  2. Anonymous
    2012-07-01T02:52:04+00:00

    Hi,

    Glad to know that the issue is resolved. Let us know if you face any issues with Windows in future.

    0 comments
  3. Anonymous
    2012-06-29T15:03:28+00:00

    Thank you! Method 1 seems to have worked.  The only changes made to the computer were just windows updates, and the message only came up on my user account (not an administrator), not any others.  Thank you again!

    0 comments