Possible walkthrough of a log and probable causes?

[ENO]

Eh guys-

 

We keep submitting all these error logs and letting them float around for awhile- frequently without feedback. I'm not sure I'm ask concerned with the absence of feedback as much as I am that there are indicators within the error / crash logs that point to "usual suspects."

 

As the operator of a full time server, I get my share of logs and frequently post them up. I know "someone" is looking them over, and gleening information from them- however what I'm most concerned about is aspects of the logs that I may be able to determine point cause at either a hardware or network malfunction that I may have some control over.

 

More often than not, it's just a 'common error' (weapons.dll for example occurs in MANY of mine). There are a number of these hot pockets... and I'm wondering if someone could post a sticky with "frequent fliers." This would help us identify the bugs that were software related (ED side) versus those that are server / network related (our side). We could then help ourselves a bit more. We could submit the error reports for the sake of submitting an error report as opposed to "looking for answers."

 

Thoughts?