This is a very generic message that can be recorded by a wide number of .Net applications. It simply states that the specified application (recorded as P1) crashed (in programming jargon it has "thrown an exception"). Unless this application is a custom designed one, the user has very little control in fixing the problem, however, just as a best effort, the latest updates and patches should be installed for both the operating system as well as for the application itself, including depending services.
When trying to upgrade MSDE 2000 to SQL Express 2005, the installation would fail during the upgrade advisor with error -1. In Application log, Event 5000 was generated for process "bpacmd.exe". A quick search on the Internet revealed that the process is looking for BPAClient.dll in the wrong directory. Creating folder %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\BPA\BPAClient and moving the DLL into this folder solved the issue.
See "SQL Server 2005 Installation Problem" or "Error on Upgrade Advisor" links for details.
This problem occurs because the default policy for unhandled exceptions has changed in the .NET Framework 2.0. By default, the policy for unhandled exceptions is to end the worker process. In the Microsoft .NET Framework 1.1 and in the Microsoft .NET Framework 1.0, unhandled exceptions on managed threads were ignored. See ME911816
for additional information about this event's appearance.
for additional information about this event.