Unhandled Exception - A Generic error occurred in GDI+"

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • j4richard
    New Member
    • Oct 2008
    • 4
    #1

    Unhandled Exception - A Generic error occurred in GDI+"

    Help please,

    I am getting this "Unhandled Exception has occurred in your application"
    " A Generic error occurred in GDI+"

    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    Code:
    System.Runtime.InteropServices.ExternalException: A generic error occurred in GDI+.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.DrawString(String s, Font font, Brush brush, RectangleF layoutRectangle, StringFormat format)
   at SaiEdit.SelectionSetEditor.DrawButton(Graphics graphics, Rectangle rectangle, Int32 left, String name)
   at SaiEdit.SelectionSetEditor.DrawData(Graphics graphics, Rectangle rectangle, Base selection, Base controls, Brush background, Int32 combonumber)
   at SaiEdit.SelectionSetEditor.DrawData(Graphics graphics, Rectangle rectangle, Base selection, Base controls, Brush background)
   at av.a(Graphics A_0, Rectangle A_1, Boolean A_2)
   at av.a(Graphics A_0, Rectangle A_1, UInt32 A_2, Boolean A_3, Boolean A_4)
   at av.a(Graphics A_0, Rectangle A_1)
   at af.OnPaint(PaintEventArgs e)
   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
   at System.Windows.Forms.Control.WmPaint(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.UserControl.WndProc(Message& m)
   at af.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: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Pr0fileEditor
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/Pr0fileEditor.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Pr0fileEditor_Forms
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/Pr0fileEditor_Forms.DLL
----------------------------------------
SaiDoc
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/SaiDoc.DLL
----------------------------------------
MutantRegistry
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/MutantRegistry.DLL
----------------------------------------
Pr0fileEditor_Forms.resources
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/en/Pr0fileEditor_Forms.resources.DLL
----------------------------------------
SaiFile
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/SaiFile.DLL
----------------------------------------
SDFolders
    Assembly Version: 6.2.2.4

    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/SDFolders.DLL
----------------------------------------
Pr0file
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/Pr0file.DLL
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
SaiDevice
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/SaiDevice.DLL
----------------------------------------
SaiPaint
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/SaiPaint.DLL
----------------------------------------
Base
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/Base.DLL
----------------------------------------
SD
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/SD.DLL
----------------------------------------
PInvoke
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/PInvoke.DLL
----------------------------------------
ReadPr0
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/ReadPr0.DLL
----------------------------------------
StrictTreebuilder
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/StrictTreebuilder.DLL
----------------------------------------
IReader
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/IReader.DLL
----------------------------------------
IElementHandler
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/IElementHandler.DLL
----------------------------------------
QuickerSchema
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/QuickerSchema.DLL
----------------------------------------
ValidatorInContext
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/ValidatorInContext.DLL
----------------------------------------
Vd
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/Vd.DLL
----------------------------------------
SaiEdit
    Assembly Version: 6.2.2.4
    Win32 Version: 6.2.2.4
    CodeBase: file:///C:/Program%20Files/Saitek/SD6/Software/SaiEdit.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 am getting this in other window applications also. Something appears to be not drawing properly in a portion of the window that is being displayed ( the area in the window in trouble has a RED X displayed)!

    System: Win XPpro sp3
    .net 1.1
    2.0 sp2
    3.0 sp2
    3.5 sp1
    Microsof tvisual C++ 2005

    This problem does not have to do with anything that I have written but with existing windows applications. Something may have been deleted in error or corrupted???

    So far and I have tried but cannot resolve this problem...neen help!

    Thank you, Papa
    Last edited by Nepomuk; Oct 11 '08, 07:16 PM. Reason: Added [CODE] tags to make post easier to read, although they're not strictly needed in this context
    Tags: None
    • mldisibio
      Recognized Expert New Member
      • Sep 2008
      • 191
      #2
      Do you have CVSNT or TortoiseCVS on your machine as well?

      There was a specific release of TortoiseCVS(sin ce fixed with newer releases) causing a very similar problem, causing other applications, notably VS2005, to crash when the File Open dialogue was called. However, the error was "GDI+ initialization" , not "Generic error," so not sure if this helps

      The issue was confirmed and acknowledged by the application owners.
      http://forums.microsof t.com/MSDN/ShowPost.aspx?P ostID=2600703

      Bottom line, IF you have those apps installed, make sure you have the latest releases.

        Comment

        • j4richard
          New Member
          • Oct 2008
          • 4
          #3
          Do you have CVSNT or TortoiseCVS on your machine as well? No, not that I am aware of, how can I verify this?

            Comment

            • mldisibio
              Recognized Expert New Member
              • Sep 2008
              • 191
              #4
              Those are "Source Control" (like Visual Source Safe and others) applications. CVSNT is a Windows version of CVS that usually has a remote server component for storing source code.

              TortoiseCVS is a handy application that lets you check source files in and out by right clicking on them

              They have to be installed, so nothing mysterious here. They are not system applications. If you are not familiar with them, then you probably do not have them installed, unless you received the machine already pre-loaded, such as might happen if you work for a software development company.

              So the issue is still unresolved.

                Comment

                • j4richard
                  New Member
                  • Oct 2008
                  • 4
                  #5
                  Thanks for the reply....under the circumstances I'm sure they are not installed..

                  Note: I have been searching for a fix for this problem all over the web and so far I have not been able so come close to solving it. Any suggestions at this point as to were to look would be appreciated.... This does affect more than one windows menu screen ie the same trouble appears in various other screens.

                  From what I can gather so far it appears to effect how portions of a menu screen are displayed (painted?).

                  Thanks,
                  Papa

                    Comment

                    • mldisibio
                      Recognized Expert New Member
                      • Sep 2008
                      • 191
                      #6
                      I had a hard time finding the cause of the GDI crashes with TortoiseCVS as well, despite doing exact quote Google searches.

                      I notice your debug output refers to a Saitek installation, which I gather is a game controller.

                      Have you recently installed or uninstalled either the controller software or a related graphics intensive game?

                      Also, do you have System Restore enabled? Perhaps you can find a Restore Point date shortly before this started. It should not affect any files you have worked on since.

                        Comment

                        • j4richard
                          New Member
                          • Oct 2008
                          • 4
                          #7
                          Originally posted by mldisibio
                          I had a hard time finding the cause of the GDI crashes with TortoiseCVS as well, despite doing exact quote Google searches.

                          I notice your debug output refers to a Saitek installation, which I gather is a game controller.

                          Have you recently installed or uninstalled either the controller software or a related graphics intensive game?

                          Also, do you have System Restore enabled? Perhaps you can find a Restore Point date shortly before this started. It should not affect any files you have worked on since.
                          Saitek is a game controller but this is only one of many applications that are displaying this problem, I use this as an example. I have uninstalled the Saitek program software but the problem remains in other windows.

                          There are No other graphic intensive games installed as I was in the process of cleaning up junk after a new windows install. ( this may have let to the problem?)

                          I tried system restore but could not restore to an earlier point that was effective.

                          Thanks for the input.

                          Papa

                            Comment

                            • mldisibio
                              Recognized Expert New Member
                              • Sep 2008
                              • 191
                              #8
                              Sorry, I can't help further. I hope someone will. If it's any consolation, I can say "been there done that." Personally I would reconsider a fresh re-install and making copious System Restore points before cleaning up the unwanted apps.

                              Mike

                                Comment

                                Previous template Next
                                Working...