You may want to download WinDebug from Microsoft and run the user.dmp file through it, and figure out what is causing the problem.It should lead you to a specif .dll file that is causing the exception. From there go here and enter the filename into Microsoft DLL helpdatabase. It'll tell you what versions of the file are available and where to get the latest.
For instance you may have a shared .dll that IE installed, but the latest version of that file is actually bundled with Visual Studios .NET edition. You can than replace the crapped out DLL with a newer version, or even a checked version. This way if the newer version doesn't solve your problem, then the checked version will help you determine if you have heap corruption or not.
Just remember, it's faster in the long run to figure out what's causing your problems, rather than just ignoring them.
[edit]If you already know what application is causing your problem, go to Microsoft's site and download Process Dump. It's a service that eats a little resources, but you can have it monitor a specific EXE file, and when it crashes, you'll get an application.dmp file that you can debug. [/edit]
------------------
jim
Beauty is in the eye of the Beer Holder
Brews and Cues
This message has been edited by jim on May 02, 2001 at 06:42 AM