"Daniel Carlson" wrote:

> Hi everyone!
>
> I have a BIG problem regarding a windows application that unexpectedly quits
> (crash). I started in .Net Framework 1.1 with SP1 where I first notated the
> problem. I convertd to .Net Framework 2.0 but the problem remained. I then
> found a KB that descibed this issue, KB924895 which I have installed without
> any improvements.
>
> Today I received an dialobox saying: "[Application name] has encountered a
> problem and needs to close. We are sorry for the inconvenience."
>
> When do this dialog box appear?
> What error can cause the application to simply crash?

"dsandor" wrote:

> Hi Daniel,
>
> Without looking at the code it is pretty hard to answer this question. 
> Calls to unmanaged code via pInvoke can easily cause errors as you describe. 
> Have you tried running the program in debug mode and in Visual Studio for a
> period of time.  It might help pinpoint the area in which this code is
> failing.
>
> You can also load up Visual Studio and attach to the process that your
> failing application is running under.  Then run the app until it fails.  The
> Visual Studio debugger should kick in and locate the area that failed.
>
> -David Sandor
>
> "Daniel Carlson" wrote:
>
> > Hi everyone!
> >
> > I have a BIG problem regarding a windows application that unexpectedly quits
> > (crash). I started in .Net Framework 1.1 with SP1 where I first notated the
> > problem. I convertd to .Net Framework 2.0 but the problem remained. I then
> > found a KB that descibed this issue, KB924895 which I have installed without
> > any improvements.
> >
> > Today I received an dialobox saying: "[Application name] has encountered a
> > problem and needs to close. We are sorry for the inconvenience."
> >
> > When do this dialog box appear?
> > What error can cause the application to simply crash?