When a running program attempts to perform an operation and it cannot be accomplished, an error is generated. This occurs infrequently in most applications, but we don't know about them because the programmers anticipate the majority of these errors and provide code to isolate the error and prevent it from effecting normal operation of the program. This special code is called an exception handler.
When an error occurs that the programmer does not, or cannot anticipate, an error handler will not be provided, In these cases the operating system will generate an unhandled exception, which generally results in termination of the offending software and a notification message, like what you received. I used the term offending, because these errors can effect operation of your operations system and the OS must take action to prevent that.
These kind of errors usually only occur when a conflict arises between the software and some piece of hardware and is the reason why we often see lists of compatible hardware when we look at a software's requirements.
Frequently it is a problem with one of the following:
Damaged system memory- It only takes one bad memory node to cause these errors
Damaged storage (hard drive)
Incompatible device drivers
Software updates can sometimes be the cause in some computer configures far outside the expected norm.
At any rate, if you can make this happen repeating when doing the same operation, that is information the programmers need to resolve the problem. But if the problem is in your hardware, they will unlikely be able to isolate it for you.
Fusion
