1. The article [Q308427] states that an "event" is any significant occurrence in the system or in a program that requires users to be notified or an entry be added to one of three logs. The Event Log Service records application, security, and system events in Event Viewer that can help identify and diagnose the source of current system problems, or help predict potential system problems.
2. The article [Q314084] describes how to gather more information about an error message that appears on a blue screen but may not provide conclusive answers and may only point you to another problem. Using Pstat.exe, a Resource Kit utility run from the command line, you are given a picture of the processes and drivers that are currently running. By using the starting address in the "LoadAddr" column, you can match the exception address to the driver name nearest and is most likely the driver that called the exception.
3. Access the TechNet "Windows XP Events and Errors" page and enter either the "Source" or the "Error Code". -- the two most important items of information concerning an Event.
Are there any negative effects in running Wimamp along with other applicaitons. I have a user on the network with a high perfomrmance workstation, 2.3GHZ and 2GB DRAM. He runs several applications such as Outlook, Solidworks, Word, and two or three more applications along with Wimamp and his system crashes every now and then. I suspected that Wimamp has something to do with these unexpected system crashes.
Any thoughts?
Thansk in advance,
Zeke

Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic