An unhandled win32 exception occurred


  • Dear all,

    I have several high memory usage program running on Windows Server 2003 with
    the latest patches installed.

    Recently I got an error message returned from the visual studio debugger,
    sayings that

                            "An unhandled win32 exception occurred in xxx.exe"

    At first, we were suspecting that the given error was caused by this
    particular exe,
    so ended up we started to do some stress test on it and hope that we could
    reproduce the
    problem again on our side with the same pc configuration, but no luck from
    the test.

    After google-ing around, i read an article stating that

        "..... you may get this error <An unhandled win32 exception occured
         in....>  frequently after you installed Visual Studio / SQL2005 on
    WindowsXP and above......"

               ..... because it changed your windows DEP settings from

        "Turn on DEP for essential Windows programs and  services only"


         "Turn on DEP for all programs and services except those i

     I would like to know that:

        1. Can we just simply change the DEP option back to the first one?

        2. Would there be any side effect if the server has the following
    component installed?
              - Host Integration Server (HIS)
              - Internet Information Services (IIS)
              - SQL Server
              - Clustering Server.

        3. How to ensure that this setting will not be change again by any other

     Kindly advice if there are other configurations need to be set to  overcome
    the problem.

    Appreciate for your kind help and assistance

    Thank You


    Friday, December 21, 2007 12:40 PM


  • It's not clear from your post that the Data Execution Prevention setting has anything to do with the problem you're running into.  In particular, you need to figure out exactly WHICH exception occurred in your program.  If possible, attach Visual Studio to the process that is crashing, and set it such that it captures Win32 Exceptions (Debug->Exceptions...).


    If VS cannot be installed on the machine on which the process is running, you can generate a minidump after the crash that you can load into Visual Studio for further investigation. 


    See the question entitled "What is a minidump and how do I create one?" in the Visual Studio Debugger FAQ at  Once you create the minidump you can take it back to a computer that has Visual Studio installed, and open it via File->Open Project.  Assuming you have access to your symbols and source, you should be able to discover where and why the crash occurred.


    Hope this helps!

    Thursday, December 27, 2007 7:55 PM